Andrew Rossa [Cakewalk]
There will be an X3e. Hope to have more details soon.

Thanks Andrew, as long as the Playlist Tool is fixed, I will be happy...along with the other 5 of us LOL!!!

No they withdrew your bug John, in error in my view, however it was not a major bug (although that is no excuse). Or made it into a "feature request" or something plain wrong (memory fails me)...  Just because one issue (or indeed many issues) didn't go through QA doesn't mean to say nothing is ever going to happen.
 
There are plenty of other issues that haven't been withdrawn.
I have also compiled a list of withdrawn bugs which I think Cake should look at again, however I am avoiding arguing about these withdrawn issues right now as this is a distraction from getting the confirmed issues fixed (as we all want Cake to be spending their time bug fixing rather than en mass bug debating).

CakeAlexS
Good Point. The next version should be called Sonar X11.

I'd like to see a Sonar Xx myself.... Let's eliminate numbers so we can't complain the new one isn't out yet...

I think Keni meant Sonar not ProAudio 9. Because we did actually have ProAudio 9.

Not sure if anybody is able to reproduce this. For starters I would make sure you are running the latest drivers and firmware for your audio interface, run windows update several times, then run full chkdsk on all your hard drives, and perform a defrag for good measure.

CakeAlexS
BTW as far as I'm concerned Sonar is a fully functioning DAW.

Perhaps this is a semantic issue. Yes I can do what I need to do in Sonar X3d, albeit with some workarounds to address some of the noted bugs that do affect my workflow. To me this makes X3d "functional" but not "fully functional."  In much the same way I would consider a 10-gear bike with 9 working gears to be "not fully functional" - it may get me where I need to go, but it still needs work.
 
In any event, I am not concerned about fixing every minor bug, and understand that some bugs are highly system-dependent and hard to repeat.  I am talking about the more significant and repeatable bugs ones like grouped takes not being always edited as a group, or inability to zoom as intended. These are significant (but not insurmountable) obstacles to workflow that I hope are addressed in X3e.  

X4 will be the paid update, rename X3E to X4 kerching... :)

I doubt it, I don't think Cake have never charged for an incremental patch?


They also know it will probably be all out forum war if they were to charge, many casualties, red button may be pressed, world peace (and domination) not achievable, not help in hells chance of getting Cakewalk 3.01 re-released onto CD format.

I am selling copies of X3D, ping me for a price list.

I've just had 3 PM's from interested parties, please let me clarify, I am reselling copies of X3D patch (normally available free) not the full Sonar itself. Cheers :)

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.
 
 

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

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..

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.