I've just found a weird error that crashes Sonar X2 (latest quick fix) everytime you try to load a waves 9.1 x64 plug with an x64 version of any UAD plugs (latest 6.4). 
  There's no way to use the two brands plugs together,everytime you try to load a Waves plug and after a Uad one (and vice versa) you got that crash : 

Problem signature:
Problem Event Name: APPCRASH
Application Name: SONARPDR.exe
Application Version: 19.0.0.308
Application Timestamp: 50649f5d
Fault Module Name: WaveShell-VST 9.1_x64 (Automap).dll
Fault Module Version: 1.1.32.0
Fault Module Timestamp: 50a4d16f
Exception Code: c0000005
Exception Offset: 000000000001301f
OS Version: 6.1.7601.2.1.0.256.4
Locale ID: 1040
Additional Information 1: d8b4
Additional Information 2: d8b43b506fee0d6af0abadb3c9a05d99
Additional Information 3: 9089
Additional Information 4: 908903bf7a21fb3c78286dc32b16237b

Also take a look to a snapshot of the error :

https://dl.dropbox.com/u/...es%2BUAD-X64_error.JPG

  Reported various times , from CWBRN-13330 to CWBRN-13343 .

Im very disappointed...Cakewalk seems stuck with a piece of software still bug as hell and without all the features of the rest of the market...obsolete and buggy!What a shame...

Fault Module Name: WaveShell-VST 9.1_x64 (Automap).dll
Fault Module Version: 1.1.32.0
Fault Module Timestamp: 50a4d16f

 
So where´s the fault again?

Ha :) I think Mike pointed to the faulting module here, although to be fair it may be just reacting to a conflict caused by another module.... Either way not seeing what Cake has got to do with this, have you tried both plugins in cubase for example? ;).

I have also problem with X2 on Win 8 Pro 64-bit with plugin (Addictive Drums) that works without any problems in other hosts (Cockos Reaper)  on the same computer.

But I would like to give the cakewalk tech support change to fix it. So I will see in next few weeks.

It would be very nice and long overdue to hear something,at least an explanation on how far they are with the repairs. I am almost afraid to use X2 because of the chances of crashes and loosing all my music tracks. I understand it is not easy to get everything right, but giving the users a bit of information in my oppinion would be the least they could do.

Danny

cowboydan


It would be very nice and long overdue to hear something,at least an explanation on how far they are with the repairs. I am almost afraid to use X2 because of the chances of crashes and loosing all my music tracks. I understand it is not easy to get everything right, but giving the users a bit of information in my oppinion would be the least they could do.

Danny

It's a tough one - on the one hand we'd like to get a few crumbs just so that we can feel comfortable that someone is addressing our concerns. OTOH, management doesn't want to say anything that might cause them to step on their own ****. It's not a Cakewalk thing - the entire software industry is this way. In my opinion, CW is addressing concerns, but maybe they're a little on the leery side of giving too much detail to consumers - for obvious reasons. There's nothing worse (or more dangerous) than somebody going off half-cocked based on a limited understanding of a technical issue. But I feel most of us know CW is being as forthright with us as they can.

My best advice is to setup a hot key to the 'save' function on your keyboard or controller. F4 on my Alphatrack controller is setup to execute a save - I just press it every time I get a small unit of work done. On average, about every 5 minutes. It's not a hassle to do, the save is instantaneous - takes no time at all. Of course, I'd prefer not to do it at all, but that'll come.

The last 3 posts have nothing to do with with the issue reported (which appears to be a non Cakewalk issue looking at the first post) - please stick to topic or create/join an existing thread (other issues have been discussed to death :).

It's nice to have a narrator to the Moderators. ;-p

Yup... Once upon a time there was a thread which attempted to blame Cake for an issue that was nothing to do with Cake. After this was pointed out by a couple of people, along came a bunch of people who didn't exactly read the thread and decided that as somebody wanted to blame Cake they in turn would blame Cake for their totally unrelated issues, even though the issue was nothing to do with the original issues or Cakewalk.. Then along came a person with a completely different issue which caused another to comment about the state of software in general. Then along came the fairy godmother who waved a wand.... Then the thread broke down and none of it made sense in the end (because nobody could be bothered to read it, too busy posting "their opinion" about nothing to do with what the thread was about). Anyway they all lived happily ever after after each blaming each other. The end.

I never knew you were GAY. (FAIRY GODMOTHER) Nevermind about the wand. Dont need to know.