carry on bug fixing.. I might upgrade to x3 if I see enough issues are "twarted" and not rolled on to x4 or whatever it is called. I use other DAW's with at least the same amount of customers or more.. yes there are issues, but they don't cut off after a year update wise.... which makes me step back and not pay for sonar so quick any more.
 
 

Fog
carry on bug fixing.. I might upgrade to x3 if I see enough issues are "twarted" and not rolled on to x4 or whatever it is called. I use other DAW's with at least the same amount of customers or more.. yes there are issues, but they don't cut off after a year update wise.... which makes me step back and not pay for sonar so quick any more.

Download the trial, and see if any of the remaining bugs are actually relevant to the way you work.

Jlien X

lawp
well they confirmed an x3e but nothing about time or possible price, i expect they're still deciding

 
Not happy with X3d after giving it a try?

i'll let you know

I guess it's beating a dead horse, but anyway I want to counter a notion that I've seen going around.
 
After looking into it, I've determined that the UAD bug doesn't need any fixing from Universal Audio - all they have been doing is working around the way that Sonar treats UAD fx, and they haven't yet added that workaround for X3.  Sonar, on the other hand, is actively implementing a "custom chaining API" which has been abandoned by UA at least since version 6.4.  Once Sonar stops using the deprecated functionality, UA won't need the workaround anymore.
 
I believe that Cakewalk is planning to fix this in X3e, and I hope UA realizes that.

brian brock
I guess it's beating a dead horse, but anyway I want to counter a notion that I've seen going around.
 
After looking into it, I've determined that the UAD bug doesn't need any fixing from Universal Audio - all they have been doing is working around the way that Sonar treats UAD fx, and they haven't yet added that workaround for X3.  Sonar, on the other hand, is actively implementing a "custom chaining API" which has been abandoned by UA at least since version 6.4.  Once Sonar stops using the deprecated functionality, UA won't need the workaround anymore.
 
I believe that Cakewalk is planning to fix this in X3e, and I hope UA realizes that.

Without wishing to turn this into yet another UAD thread here the actual source which paints a different story (in bold), Cakewalk will be implementing a workaround and UA will be implementing a fix. Clearly they have been in contact with each other.
 
 

Noel Borthwick [Cakewalk]
Its possible that this issue is also a side effect of the plugin chaining API. All versions of SONAR since 8.5 use this custom UA API that we implemented for them years ago.
 
I was in touch with UA fairly recently about this and their response was that this API is no longer actively supported by them at the host level and only used by them internally now. I was also told that they would add a remedy from their end. From our side I have now removed custom UA chaining support from SONAR for the next X3 update so hopefully this shouldn't be an issue going forward.
BTW this isn't really specific to X3 technically - the only reason that you see a difference in behaviour is because the UAD driver seems to be testing for a specific SONAR version and masking the error messages - which is why the some UAD warning messages started popping up in X3.

 
Cheers..

lawp
i wonder if x3e'll be a free or paid update?

It will be a free update. 

So once Cakewalk releases X3e, the UAD issue will be fixed, most likely with no need for UA to do anything more.  This is why it's important to me that X3e comes soon - ideally before UA tries to work around the issue on their end, which could potentially conflict with Cakewalk's fixes.
 
Actually, Cakewalk already seems to have been aware of what was causing the issue when X3d came out, but I assume they were unable to address it quickly enough.  After the first few updates came out so quickly, I was expecting that an update adressing this and other already understood problems would come out right away.  It looks like they switched gears to put out the demo first - now that it's out I'm expecting X3e to arrive soon enough, I guess.
 
I would be even more interested to hear whether Cakewalk plans an X3f, after X3e, since there seems to be no expectation that everything will be perfect in X3e.

brian brock
So once Cakewalk releases X3e, the UAD issue will be fixed, most likely with no need for UA to do anything more.

OK let's make this bite sized:

Noel Borthwick [Cakewalk]
I was also told that they would add a remedy from their end.

 

Noel Borthwick [Cakewalk]
BTW this isn't really specific to X3 technically - the only reason that you see a difference in behaviour is because the UAD driver seems to be testing for a specific SONAR version and masking the error messages - which is why the some UAD warning messages started popping up in X3.

 
They are in contact with each other, I don't see the issue. I don't see any potential conflicts as they are doing different things and they are in communication. Noel has clearly stated exactly what is happening. BTW X3E is not just about working around the UAD issue, so I doubt they are going to skip testing or skip putting in extra fixes just because of UAD's release schedule. Neither of them are going to put in code without testing. Cakewalk stated a demo would come out after X3D and their plan did not alter. Nobody has given a schedule for X3E yet.
 
Cheers...