I had high praise when i first loaded X3(a) on my computer... I still have very high hopes but as time has gone by I am experiencing multiple crashes upon exiting X3 and sometimes during project operation. No hardware or software changes since initial install. At first, my issues seemed confined to automapped plug ins so I just removed the Nocturn from my 64 bit install all together. Now I am getting program shutdowns almost everytime and it list IK Amplitube 3 as the fault module and sometimes Slate VTM/VCC. It happens when the track is frozen as well
 
I am sending in the problem reports..two..sometimes three per session/night
 
I really, really like X3 and want to use it but over time it is becoming more and more unstable .. to the point of becoming unusable and that seems very weird? I would love some interaction with what I see with this great new tool.. The problem reporter.. but what I am finding right now is that I am pushing the information out but not getting any feedback
 
Have you noticed the same or are you guys having good interaction with them via this tool? Is anyone else out there having issues with these particular plugs? Anyone out there having issues with Soundtoys plugs 64 bit? I am getting crackling, popping and zipper noises when adjusting parameters on Decapitator and Echoboy.
 
Would love to help work on this or get some feeedback...
 
tks
peace
 
 
 
 
 
 
 
 
 
 
 
 

Steven Slate's stuff is unfortunately some of the most reported plugins as far as stability is concerned. I have emailed them personally a few times now without much luck. I'm sorry that you experiencing issues with their stuff. If you want, you could send a long a project. I own VTM and VCC and could possibly try to reproduce the problem.
 
The crackling and popping when adjusting parameters is something that we are aware of, but I will connect with the team on this issue to see what's going on.

As far as Amplitube 3 goes, I do not have a copy of this here, but I may be able to get one to try and see what's going on. Feel free to PM a link to your project that has issues, maybe we can find out what's going on.
 
-DG

Thanks Dan!
 
Ill do that as soon as I get to the studio this evening

Ya VCC and VTM are truly two of the biggest culprits in terms of causing my sessions to crash before I can even load them.  It's been that way since X1.  Every time I load a session I'm mixing I cross my fingers.
 
I often send in the reports, but it's happened so often that I figured it'd be wasted time to continue to do so.
 
I find it disheartening that Slate doesn't contact Cakewalk regarding this.

Maybe Sonar X series users need to start getting in Steven's ear .... I know for a fact that VTM was not tested in Sonar 

I personally sent a ton of analysis to the folks at Slate Digital since. To give them credit, they actually reached out to us in hopes to improve the compatibility relationship between SONAR and their products. I'm happy that they did. Hopefully they can make sense of some of the data and can figure out what's going on. In any case, they have my direct contact information if they need to follow up with us so this is hopefully forward progress.
 
Incidentally, Amplitube 3 is up there with our biggest reported crash offenders also. Usually as a user you can get an idea of what the cause of the crash is by checking out the "Faulting Module" reported by the crash. It's not 100% accurate though which is where the fault reporter is helpful. The fault reporter is an automated system though, so you're not going to get responses from anyone in support. If you send us CWBRN numbers, however, we can try to dig in to see if there's an obvious cause of the crash. I just took a look.
 
Faulting Modules reported from your data (in order of most recent to oldest):
 
AmpliTube_3
AmpliTube_3
SONAR Crash (whoops!)
AmpliTube_3
vumtsolo__automap_
uad_pultec_eqp_1a__automap_
vumtduo__automap_
bx_cleansweep_v2__automap_
uad_pultec_pro_legacy__automap_
vumtsolo__automap_
waveshell_vst_9_2_x64__automap_
slate_digital_virtual_channel__automap_
 
So we have three Amplitube 3 crashes and a bunch of stuff referencing Automap. Can you try ruling out Automap to see if it makes a difference? It may or may not. Also, do you know what version of automap you're on? Incidentally someone else was reporting crashes with automap but we weren't able to recreate it internally. The fact that it's listed in the string we capture doesn't necessarily mean that automap is the culprit though, all it means is that the plug-in was wrapped in automap which gave it a unique identifier when we parse the .dmp file for relevant information. Anyhow, worth ruling out.

It's not just Sonar  - just read a Cubase thread on KVR mentioning SS plugins failing to initialize...

SS- stands for Steven Slate AND Stuffed Shirt
 
Great pulgins though- but might be even greater ironing out the attendant weirdness.

I guess ive been lucky with the Slate stuff. I have the VBC, VCC, FG-X, Trigger 2 and SSD4. Had trouble with Trigger 2 but it was a license issue. I have to say I rarely use the VCC but I use the others a lot! VBC and Trigger was just recently updated and supposedly all his plugs are supposed to be updated so maybe people who are having trouble will have better luck.

Ryan Munnis [Cakewalk]
I personally sent a ton of analysis to the folks at Slate Digital since. To give them credit, they actually reached out to us in hopes to improve the compatibility relationship between SONAR and their products. I'm happy that they did. Hopefully they can make sense of some of the data and can figure out what's going on. In any case, they have my direct contact information if they need to follow up with us so this is hopefully forward progress.
 
Incidentally, Amplitube 3 is up there with our biggest reported crash offenders also. Usually as a user you can get an idea of what the cause of the crash is by checking out the "Faulting Module" reported by the crash. It's not 100% accurate though which is where the fault reporter is helpful. The fault reporter is an automated system though, so you're not going to get responses from anyone in support. If you send us CWBRN numbers, however, we can try to dig in to see if there's an obvious cause of the crash. I just took a look.
 
Faulting Modules reported from your data (in order of most recent to oldest):
 
AmpliTube_3
AmpliTube_3
SONAR Crash (whoops!)
AmpliTube_3
vumtsolo__automap_
uad_pultec_eqp_1a__automap_
vumtduo__automap_
bx_cleansweep_v2__automap_
uad_pultec_pro_legacy__automap_
vumtsolo__automap_
waveshell_vst_9_2_x64__automap_
slate_digital_virtual_channel__automap_
 
So we have three Amplitube 3 crashes and a bunch of stuff referencing Automap. Can you try ruling out Automap to see if it makes a difference? It may or may not. Also, do you know what version of automap you're on? Incidentally someone else was reporting crashes with automap but we weren't able to recreate it internally. The fact that it's listed in the string we capture doesn't necessarily mean that automap is the culprit though, all it means is that the plug-in was wrapped in automap which gave it a unique identifier when we parse the .dmp file for relevant information. Anyhow, worth ruling out.

Correct.. You and I were the ones talking about automap before...that's been pulled and out of the equation. The top three represent more of what is happening now. I sent Dan a message as requested and will help in any way I can
 
Let me say this.. Thank you.. to you and Dan and the rest of the bakers for interacting with us out here. This is a very powerful DAW you boys and girls have been cooking... 
 
 
X3 =  Beast Mode