I am currently running Sonar X1 Producer expanded 64 bit. I have a machine built specifically for me by a well known audio computer builder. Windows 7 pro, i7 proc. 16 gigs of ram, 3 hard drives. Sonar will freeze on me every now and again if I am starting / stopping over and over again like punching a part in or working out a part. Sometimes if I hit stop halfway through the song it will freeze as well. I have to call up task manager to get out of it, then re-boot the computer so it recognizes the Echo again. It has been suggested by my builder that the interface I use is a bit dated. I use an Echo Layla 3G. I am not running a lot of stuff when this happens, maybe a couple instances of VST guitars and one instance of Superior drummer. Does this sound plausible? With the interface being the issue?
 
I am looking for a new interface, it has to be PCIe because of the speed and I need something rock solid for when I get into heavy editing. From what I can tell by research the RME products stack up pretty high for stability, but I really want to make sure I get something that works perfectly. I don't need a lot of in's and out's, something along the same lines as the Echo unit is fine. I just want something that doesn't freeze, I know they must exist!
 
 

1.  Are you using a Recording Mode of ASIO?  Per your audio interface's documentation, they recommend ASIO for use in Win 7.
 
2.  There are many great USB interfaces - some even support USB 3, though many are designed for USB 2.  I have a Presonus AudioBox 1818VSL, and it uses USB 2.0 and works fine with no audio issues, even with all 8 mic pre-amps in use.
 
3.  Many threads exist in the Sonar forum, where Sonar crashes and a full reboot is needed to get Sonar back up and running.  The culprit in most, if not all, of these cases seems to be that BitBridge is in use (due to 32-bit plugins being present in the project), and it take as long as 10 minutes for BitBridge to be unloaded from memory following a crash of Sonar.  The above being the case so frequently, I suggest that you set up a test of this situation as follows:

• Start with a project that you know has these issues, but rather than altering the project itself, copy the entire contents of the project folder to a newly-created project folder, ALSO renaming the CWP file to something with maybe the word 'Test' in it or whatever.  This way, you can in the first place protect your original project, and secondly you can then do direct comparison between the 2 projects, to help isolate your issues.  (The rationale for renaming the CWP file as well is to avoid subsequent confusion when loading the real project up, using the Quick Start dialog.  Having 2 distinct project names will eliminate that from happening).
• OK, so load up the test version of this project, and start by examining all plugins that are present in the project.  If ANY 32-bit plugins are present, even if they are not actually used, BitBridge WILL get loaded.
• If ANY 32-bit plugins are present, delete them from the test project.  We are not interested for the moment in what that does to the sound of anything, we just want to isolate the issues and 32-bit plugin presence is a likely culprit.
• Work for a while with all 32-bit plugins removed, and post back your results.
• If you are STILL having issues where a full restart is needed, use the same test project, with all 32-bit plugins removed, and remove ALL 64-bit plugins, then test again.  If you find that it works when there are no 64-bit plugins present, then one of your 64-bit plugins may be having a bad hair day, and you may need to load one 64-bit plugin at a time until you get to the point of failure, then find a solution or replacement for using that plugin.

I hope something in the above leads to identification of the reason for Sonar's woes on your system.
 
I would hope also that the build took into account your use of a PCI/PCIe connection for your audio interface.  You might also consider researching using a different slot or checking on any known issues with your audio interface involving PCI/PCIe.
 
Bob Bone
 

I use an Echo Layla 3G and run at 96khz/24-bit without trouble. When I decide to get another card I'll be sticking with PCI/PCI-e as well...unless Thunderbolt proves to be a huge advance. USB is easy but too problematic and doesn't have the same throughput of PCI/PCI-e.
 
You may want to check the videocard driver and update it. Is this a dedicated DAW or an all-in-one machine(DAW, internet, gaming, etc.)?
 
Good luck,
Bill
 

Thanks for the reply guys! I am not using any bit bridge or anything that I feel is too excessive for the computer to handle. The computer stands alone, no gaming, internet, nothing. It's only used to record.
 
The builder took everything into account when building the system, I just think he might be right with the fact the Echo being a PCI instead of the newer PCIe design, along with a product that really isn't supported anymore is the problem. The echo worked great on my old 32 bit system and it does work ok on the 64 bit rig, it just locks up at times, especially when I am messing with midi in piano roll view. I have read nothing but positive stuff about RME and I might just go that direction. Maybe if I spent a ton of time researching I could identify the bugs in the Echo, but quite frankly I just don't care. I don't want to be a computer expert, I just want to make music.

Firewire 400 has a proven track record for recording many good interfaces are out there and a Ti firewirecard, your good to go! as for thunderbolt interfaces such as the apollo
http://www.uaudio.com/interfaces/apollo-16.html    to run on intel you require a firewire 800 card ... On Windows systems, Apollo, Apollo 16, and UAD-2 Satellite require a qualified PCIe-to-FireWire adapter card. See the product support pages for details: Apollo