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?

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.

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.

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

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

KWILD


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

Ok...some things need to be known here...


Are your trying to load the plugins in a NEW project OR a project already created under X1?


The reason I ask...

I recently encountered a problem with X2 (with quickfix) under Win 8 using Waves x64 plugins (I own a lot)
I had just purchased Waves Vocal Rider and wanted to check it out.  So I opened up one of
my completed X1 projects and attempted to insert VR on the Vocal Track.  Instantly X2 crashed
and burned.  So I opened it up again and tried again to make sure it wasn't a fluke.  X2
crashed and burned AGAIN.  So my curiosity was aroused.  I had been using my Waves 
plugins in X2 with NO ISSUES whatsoever. 

So I open a new project and inserted Vocal Rider.  It functioned perfectly.  I opened another X2
project and inserted VR on the Vocal Track.  It functioned perfectly.  

Now, my curiosity has PEAKED.  So I open my X1 Project and SAVE IT under a NEW name.
I close the current project created in X1 and open the one I JUST SAVED in X2.

I then insert VR on the Vocal Track and IT FUNCTIONS PERFECTLY!

There is a probem (where I don't know) with projects saved under X1 when bringing them
into X2 and inserting Waves x64 plugins.  This has been verified by others here.

This is the reason I ask, because that may be the problem  Waves doesn't like X1 projects (opened under X2)
I think there are translation issues when bringing in an X1 project to X2 that causes Waves x64 to crash.
It appears to be an issue with X2, not with the Wave's or UAD plugins.

Just a thought.

backwoods


Nice catch cc- I hope the 'bakers read this.

Thanx BW...


I've posted it here and in the software fred...


So hopefully they will see it.

:) There could be a knowledge base article ;).
I still believe the smoking gun to be the faulting module itself...
It's way past midnight I need some Fairy sleep...

cclarry

Ok...some things need to be known here...  


Are your trying to load the plugins in a NEW project OR a project already created under X1?


The reason I ask...

I recently encountered a problem with X2 (with quickfix) under Win 8 using Waves x64 plugins (I own a lot)
I had just purchased Waves Vocal Rider and wanted to check it out.  So I opened up one of
my completed X1 projects and attempted to insert VR on the Vocal Track.  Instantly X2 crashed
and burned.  So I opened it up again and tried again to make sure it wasn't a fluke.  X2
crashed and burned AGAIN.  So my curiosity was aroused.  I had been using my Waves 
plugins in X2 with NO ISSUES whatsoever. 

So I open a new project and inserted Vocal Rider.  It functioned perfectly.  I opened another X2
project and inserted VR on the Vocal Track.  It functioned perfectly.  

Now, my curiosity has PEAKED.  So I open my X1 Project and SAVE IT under a NEW name.
I close the current project created in X1 and open the one I JUST SAVED in X2.

I then insert VR on the Vocal Track and IT FUNCTIONS PERFECTLY!

There is a probem (where I don't know) with projects saved under X1 when bringing them
into X2 and inserting Waves x64 plugins.  This has been verified by others here.

This is the reason I ask, because that may be the problem  Waves doesn't like X1 projects (opened under X2)
I think there are translation issues when bringing in an X1 project to X2 that causes Waves x64 to crash.
It appears to be an issue with X2, not with the Wave's or UAD plugins.

Just a thought.
 

   

  Well,i was testing the UAD's with other plug-in brands and i've discovered the same issue with Brainworks plugs , insert 1 Brainworks after 1 UAD and you got crash : 

https://dl.dropbox.com/u/...2BBrainworks_Crash.JPG

Please bakers take contact with Universal Audio ASAP!

The incompatibility is with other brands too (Plugin Alliance,Surfer EQ and others) but  i've found a workaround.Inserting after the UAD a plug without issues (Cakewalk Channel Tool for example) you are able to insert Waves,Plugin Audio and other plugs that crash before with no problems,but take in mind  do not try to remove or disable the Cakewalk Channel Tool from the fx bin (disable/bypass it from the GUI clicking on POWER) or you got the same annoying crash.     You must put another instance of Cakewalk Channel Tools if you wanna insert another UAD even if you got that advice : https://dl.dropbox.com/u/..211/UAD_LAtency_ADD.JPG otherwise you got crash!

I have no doubt you are having issues, but I have been using the X2 x64 demo with lot's of UAD-2, Cakewalk and other third party FX with no issues whatsoever. I am using all x64 plug-ins mind you (no Cakewalk bitbridge or third party bridges, I don't use them for performance reasons) and the latest x64 versions of each. I don't use any Waves however......

  Hi Dean , please can you post your Sonar configuration file?That's mine : 

[Aud]
DataDir=X:\Wavedata
PictureDir=X:\PCACHE
PicCacheMB=500
PicCacheZoom=128
PicCacheLevels=2
EnablePicCacheThreads=1
ComputePicturesWhilePlaying=1
CopyOnImport=1
ReadCache=0
WriteCache=0
EnableCacheWriteThru=1
VolMethod=1
PanMethod=1
DiskBufSize=256
DiskRecBufSize=256
ExtraDiskBuffers=2
DitherAlgorithm=0
ZeroFillMethod=2
RecordPreAllocSeconds=0
ZeroFillDB=300
FlushWriteBeforeRead=0
FlushMultiple=1
DefaultEqPosition=0
DefaultAudSnapOfflineStretchMethod=3
DefaultAudSnapOnlineStretchMethod=1
RadiusStretchingPitchCoherence=50
RadiusStretchingPhaseCoherence=50
RealtimePreroll=0
SuspendPluginsOnBounce=1
[Wave]
DefaultSampleRate=44100
DriverID=0
WaveInID=3
OpenInputFirst=0
SmpteMode=1
TimingOffsetMsec=0,000000
TimingOffsetBuffers=0
LatencyMsec=11
BounceBufSizeMsec=0
FlushOnStop=1
ThreadSchedulingModel=2
EnableMixThreads=1
MixThreadCount=0
EnableSetThreadIdealProcessor=1
CSUseSpin=1
AllowOfflineRenderMixThreads=1
UseMMCSS=1
MMCSSThreadPriority=2
MMCSSTaskKey=Pro Audio
FreeMemOnUnload=1
AlwaysOpenAllDevices=0
MinimizeDriverStateChanges=1
RemoveDCOffset=0
EnableAsioBufferSwitchTimeInfo=1
EnableDeviceOutputLatencyCompensation=1
UseHardwareSamplePosition=1
BitsPerSample=24
FileBitDepth=24
RenderBitDepth=32
ImportBitDepth=0
ExtraPluginBufs=0
MixDezipperUsec=50
GapDezipperUsec=500
WaveInBuffers=8
WaveOutBuffersMME=4
WaveOutBuffersKS=2
MeterFrameSizeMS=40
SyncMaxDriftMsec=2
SyncDivisor=8
ProfiledMME=0
ProfiledKS=1
ProfiledWASAPI=0
UseWDMDmaForWASAPI=1
LinkSendPan=0
LinkPFSendMute=0
StopOnEmptyPlayQueue=0
KsUseInputEvent=0
WaveOutExtraBuffers=1
AutomationDecimationMsec=50
EnableSSEMixing=1
ThumbnailCacheSize=100
ManageASIOThreadPriority=1
EnableLiveADCRecalc=1
UseAlias=1
DropoutMsec=250
StartFadeMsec=1
StopFadeMsec=1
PanLaw=0
PanLawCompatMode=0
DisableIMDuringPlay=0
ShowMultiChannelInputs=1
ShowMultiChannelOutputs=1
[RME HDSPe AIO (9 in, 14 out)]
MigratedDMA=1
Name=AIO Analog (1+2)
InputLatencyOffset=0
UseAsioReportedLatency=1
WidePacking=4
Interleave=2
Use24BitExtensible=1
UseExtensibleForMultiChannelIO=1

 I didn't read what UAD cards you have but only one UAD plug-in loading has a familiar ring to it. Your UAD cards don't happen to be UAD-1 are they?

After weeks that i was using UAD 6.3 i've try to reinstall 6.4 and i've found some clues. 
Im a Novation Automap user (SL61MK2 with Zero SL) the crashes are caused by Automaped UAD plugs!
Deleted the automap wrapped files and crashes are gone!
Sonar seems to had a bad compatibility with some other automap plugs.Some seems to work well alone but when you mix togheter different automaped plugs from different brands you got crashes,freezes and headaches!!!!
Anyway i can say for sure that Automap 4.6 with UAD 6.4 (X64) crashes Sonar X2 and X2a every time you insert more than one automapped/UAD plug-in.

  Vocal Rider seems working good for me.All my problems were caused by the novation automap,after removing the automapped versions of my vst plugs all my crashes are gone completely!The major issue was with UAD x64 plugs but automap seems making weird stuff with a lot of other plugins as i've already say,sometimes all seem to work well but when you add multiple type/differend brand of automapped plugs the Sonar projects becames corrupted and you got all kinds of crashes. 
I was able to re-open a lot of projects that crashes soon after opening just removing the automapped plugs (an so loading the NON automapped versions of the same plug).
Really disappointed about that...