2014/12/09 21:27:45
kitekrazy1
Anderton
Almost invariably, whatever you recorded is in your project audio folder. The file will usually incorporate the track name depending on when the freeze occurred, but you can always click through the project audio file in the media browser to find it.
 
Don't know if this applies in your case, but running 32-bit plug-ins in a 64-bit environment is risky. This is why DAWs like Studio One, Pro Tools, Cubase, etc. don't even let you run 32-bit plug-ins (most don't support DirectX, either). While I appreciate that SONAR makes an effort to provide backwards compatibility, using older plug-in formats and bridging technology to fool SONAR into thinking the plugs are compatible can definitely impact stability.
 




I heard from developers that running 32 bit plugs in a 64 bit app uses more resources. I wonder when Sonar is going to drop DX support. Image Line will drop it in FL12. Sonar may be the last one left.
2014/12/09 22:48:35
Anderton
All Sony software (Vegas, Sound Forge, Acid), Acoustica Mixcraft, and Magix Samplitude still support DirectX. I think Reaper does too.
2014/12/09 23:49:39
noynekker
rfreeze
CakeAlexS
rfreeze
The reporter did ask and I told it yes.
 
Delta66 ASIO
 
Don't waste a lot of time.  My hardware is rock solid with Reaper.  I'll pick back up with that until I see some maint releases for Sonar.  I'll just make sure not to trust it to quickly next time.




Might be rock solid with Reaper but could be causing Sonar to crash. It's different software maybe making different procedural calls and code to access the driver, or even windows library routines getting the way. I would definitely check you are on the latest driver version and firmware, and make sure you are on X3E, and run Windows update everywhere.
 
Otherwise you are probably looking at plugins.
 
Cheers...




The BT Tempo Delay was bypassed in an empty track that was not involved in the comping that was going on at the time.  It is the only plugin in the project.
 
X3e, Win 8.1 fully updated.
 
I appreciate that a card can cause problems with one piece of software but work fine with another.  My hardware is my hardware ... Delta66s have been around forever and have worked fine forever - with performance that is difficult to match with modern interfaces - at 'reasonable' cost.
 
BTW, my last takes are nowhere to be found.  That's not a big problem though - I enjoy playing my guitars.  :)  The real problem is time lost working thru the takes with the comp tool.  Now, if I was paying for talent, it would be a different story.
 




I will agree that the Delta 66 is a rock solid audio card, I've been using a long time now, and have very few crashes that weren't caused by my own operator error.  Comping has worked very well for me on X3e with the Delta 66 card on Win 7 sp1 . . . but I'm wondering how you have it working on Win 8.1 ?  One reason I haven't moved on to Win 8.1 is that the M-Audio site shows there are no drivers available for that OS.
 
2014/12/10 04:21:40
BobF
I've been using the latest drivers with Win8/8.1 for about a year and a half.  Win7SP1x64
I didn't bother loading Sonar when I got this one.  I was previously still on XP running Reaper and continued to do so on this machine.
 
I should point out that trying out Sonar again has nothing to do with *stability* problems with Reaper.  I much prefer the UI and overall layout of Sonar.  I figured 'why not?', thinking I could always use fresh plugs if Sonar didn't work out.  Of course I found out yesterday how much is tied to Sonar - a practice I think stinks of insecurity. 
 
At this point I'm really hoping we see point releases addressing stability before another new version.  I've always hated having to pay in advance in the hope that some of the bugs might be squashed in the new release.
2014/12/10 04:57:14
kakku
I have automatic saving on every 7 minutes in case something happens.
2014/12/10 04:59:26
Kev999
Anderton
Almost invariably, whatever you recorded is in your project audio folder...



True. I recently lost a set of takes. They just vanished while I was editing some other track elsewhere in the project. Anyway, I discovered that the recorded audio still existed within several files in the Audio folder. It was all rescueable, albeit with a lot of messing about.
2014/12/10 14:10:12
Atsuko
rfreeze
I've been using the latest drivers with Win8/8.1 for about a year and a half.  Win7SP1x64
I didn't bother loading Sonar when I got this one.  I was previously still on XP running Reaper and continued to do so on this machine.
 
I should point out that trying out Sonar again has nothing to do with *stability* problems with Reaper.  I much prefer the UI and overall layout of Sonar.  I figured 'why not?', thinking I could always use fresh plugs if Sonar didn't work out.  Of course I found out yesterday how much is tied to Sonar - a practice I think stinks of insecurity. 
 
At this point I'm really hoping we see point releases addressing stability before another new version.  I've always hated having to pay in advance in the hope that some of the bugs might be squashed in the new release.


 
 
Strange...  M-Audio states that there are no drivers or firmware updates available for windows 8 and 8.1 for Delta 66.
2014/12/10 16:23:34
BobF
As stated (maybe not clearly) I'm using the Win7SP1x64 drivers ...
 
At the time I built this machine there was a blurb somewhere on the Avid site that said if they didn't have drivers for your specific Win version, the drivers for a previous version might work.
 
And so they have.  No audio app has ever crashed on this machine until Sonar X3.  As Alex pointed out, there could be something different in the way the drivers are accessed by Sonar vs other apps that causes it to not be compatible.   I don't know.  All I do know is that Sonar went poof while working with 2 take lane with the comp tool.
 
None of the bakers has answered my question about the fault reporter.  Perhaps there is some info captured somewhere that can point to the actual problem.
 
I'm open to using Reaper for tracking/dubbing and using Sonar for mixing for a while to see if more info can be gathered.  It's really easy to configure Sonar to use a different, albeit slower USB interface, which shouldn't matter at that point.
 
The way this 'discussion' has gone so far though, I'm su****ious that *that* driver will come under su****ion before Sonar actually gets looked at.
 
Yes, I realize repeatability is key to trouble resolution.  :)
2014/12/10 16:29:10
hockeyjx
How old is the Delta 66? Like 10 years+?
2014/12/10 16:34:06
stoutlyric
One thing to try that helped me is to disable the high defiintion audio controller in your control panel device manager. Thanks to Anderton for this great tip.

Details here on this thread:

http://forum.cakewalk.com...this-Out-m3103263.aspx
© 2026 APG vNext Commercial Version 5.1

Use My Existing Forum Account

Use My Social Media Account