• SONAR
  • Sonar x3 Pro crashes (p.2)
2014/12/10 15:24:55
fads
I ran both of the latency test that was suggested by JohhnyV.  Both test said the computer is capable of handling audio streaming without dropouts.
 
I am using Presonus Firestudio Tube.  The sample rated is set to 44.1 on the Presonus interface.  Runs via Firewire.
Sample rate in Sonar is set to 44.1 for new projects.  Audio driver  Bit Depth is 24 64 bit double precision Engine.
 
Is this what you guys are looking for.  Thanks for helping.
Fads
PS how do I list my equipment as part of my profile like you guys have yours.
2014/12/10 16:01:07
ampfixer
Based on posts from others, you should check and make sure your fire-wire chipset is made by Texas Instruments. I've seen lots of posts on this issue.
2014/12/10 19:29:50
viziovizio
one thing that I have noticed in x1, x2 , and now x3 is that dpc latency will run just fine, but what I ve learned in sonar is that you've got to click  "p", then  config file, the very last line reads
dropoutmsec.... all three come with a setting of 250, and they don't make many computers that will not drop out at that setting with all the real time f/x going on .     750 is where I keep it and the drop outs and crashes have stopped with this one setting.
 
once in a blue moon I ll add 512 to the already 1024  playback buffer when mixing like 60 some tracks
 
another thing I do is set my computer up for best performance when mixing and mastering. no problems with the record buffer using studio capture (also 1024)  and asio reported latency of 921. I do not check enable read caching or enable write caching.
 
recorded bit depth and render bit depth stay at 32 as they have no baring on the fact that I usually record at 24-4800.
 
but sense sonar 8.1 these basic settings haven't changed much and are usually  the basses for toggling a new install into high performance gear.
 
I have i7,win 64 bit, 16 gig , sp1, studio capture, sonar x3, bluecat,blue tubes, pro channel add ons. using run between 25 and 70 tracks with bus count, all running with pc galore.
 
2014/12/11 09:24:41
johnnyV
Signature is in "User control Panel" at top of this page right corner. 
 
That's good the test shows OK but did you run it with Sonar running a problem project? 
 
 
 
2014/12/11 10:48:35
Josh Kipersztok [Cakewalk]
I'll jump in here and offer a few suggestions--as ampfixer mentioned, if you are using a Firewire audio interface it would be worth ensuring that Texas Instruments is the manufacturer of your Firewire chipset. Most times, this will mean replacing your computer's onboard chipset with a new one. Presonus has a super helpful list of approved chipsets for their Firewire devices, which can be accessed in the link below:
 
 
 
There are also a couple resources in our Knowledge Base that I would recommend taking advantage of, as they contain useful tips to ensure proper configuration and optimal performance:

Audio Hardware Setup Guide:
--This helps make sure all drivers for your device are up to date and recognized/configured correctly in your program.
 
Windows Optimization Guide:
--This contains useful tips on changing Windows settings for optimal performance.
 
Searching either of those in the search bar on our site will take you right to the articles. Hope that helps!
2014/12/11 11:36:43
fireberd
Also, using the Legacy Firewire driver in Windows is suggested for many Firewire devices.
 
I used to have a Focusrite Saffire Pro 40, Firewire, and when I installed Win 7 on a system I forgot to change the driver to the Legacy driver.  I was having dropouts.  I remembered about the Legacy driver and changed it and it fixed my problem.
2014/12/11 12:01:52
Muzock
Fads, to write down your specification: 1- You have to log in 2- go to the User Control Panel 3- go to Signature and Comment.
2014/12/12 11:06:55
fads
I am in the process of testing the firewire.  I moved the firwire from the presonus firestation tube to the firewire port that came with the computer instead of an add on card that I had added later to accommodate a video device that I had needed.  I read above that the firewire could be causing the problem.  i will  post the results as soon as I have had enough time to try it out.  I am trying it now.
 
Thanks
FADS
2014/12/12 12:53:48
Splat
fireberd
Also, using the Legacy Firewire driver in Windows is suggested for many Firewire devices.
 
I used to have a Focusrite Saffire Pro 40, Firewire, and when I installed Win 7 on a system I forgot to change the driver to the Legacy driver.  I was having dropouts.  I remembered about the Legacy driver and changed it and it fixed my problem.




If you are using Mix Control 3.4 (or any 3.X version) you should not be using the legacy driver. Earlier versions you should.
http://global.focusrite.com/answerbase/are-focusrites-firewire-products-compatible-with-windows-7
 
**** This advise may not be applicable to non forusrite audio interfaces, generally best contact the support of the manufacturer for their recommendations as to what driver to use ****
 
Here is a list of recommended chipset that Focusrite recommends:
http://uk.focusrite.com/answerbase/en/article.php?id=1057
 
Here is a general troubleshooting thread:
http://uk.focusrite.com/answerbase/saffire-product-troubleshooting-connection-difficulties
 
Of course this is just Focusrite specific, and the OP is using another audio interface.
 
Cheers...
2014/12/12 23:41:54
cpkoch
fads
Having problems with Sonar x3 crashing. 
 

 
I have close to  zero expertise  in this regard so take what I say with a grain of salt.  I posted a  problem earlier today!
 cpkoch 3 hours ago  
 
Out of pure frustration I ended up re-installing Sonar X3 Producer.  I have no idea as to why; but, life with  the re-installed Sonar has returned to normal.   
© 2026 APG vNext Commercial Version 5.1

Use My Existing Forum Account

Use My Social Media Account