Sorry I have to rant here....reading code...?...something is causing the Problem...
 
Not sure..But, If the motherboard manufacturers raised the amount of physical Irq's in the build processes to accommodate multiple slotted device cards without having to share any IRQ's (make them exclusive),...I believe more exclusive Manual assigning of Irq's to devices would also resolve most of the problems encountered with multiple cards placed in slots on Motherboards, and oses (98/XP)...,,WIN 7  does not allow for this manual assigning, and software manipulation anymore.  The drivers might solve BSOD's for good when IRQ assignment is exclusively governed properly....Unshared Interupt request for 1 x cpu multi core threaded  processing, and virtual IRQ's that still request CPU time...might also reduce conflicts if they all had....(NOT FOR ME)..no more freezing or blue screens?..(Been there done that )..Perhaps 2 x Processors, multi threaded or cored kind of setup on the motherboards itself with more Physical IRQ's to do that all in one box Studio system we all want to have working flawlessly at session time, can be perhaps one day a reality if the problems are directed at the root cause, and addressed!....So...I found the IRQ problem in 1997 and onwards till today....not much more to say on this....only one card can be reliably working in any build at this time with present motherboards.
 
Not sure why only 16 physical IRQ's are assigned ever since ever was a PC with sharing going on, till today, with no update to that vital system spec....Time to change that number I say....
 
Well UAD Apollo 16 x 2 or more might be the right direction in reality at present motherboard build status for the studio peps....to resolve that problem....yep have it all on one device, with one driver using one standard and one IRQ.
 
Just look at the motherboard manuals...they put all these slots on the motherboard, but most of those slots share with one above or below...why?..."it's Cheaper to manufacture!"...And that is the only reason!
Redundant devices remain on newer boards...why do we need slower and more sata 2 ports, with less faster sata 3 Ports?...or more usb 2 ports with  less usb 3 ports?...see these older slower standards hogging the cpu...some can be reduced to nil...but they do not do that yet....and so...here in lies the problems the motherboard manufacturers should address more prudently...and move forward...usb 3 is backwards compatible they say...how long now?...sata 3 also...no need for sata 2 anymore or usb 2...I think...and yet...still being implemented.....on newer motherboards builds....not sure why...moving forward I guess takes time for technology to revamp/and the peps ...So when Building a system read the manual...and try to keep things to a minimum in added slotted cards, and know the Assignments of those slots and which ones share with which, how to turn things off in Bios that are redundant may help free up some IRQ's, and good drivers and proper installs of Os and such....and things will work much better....Wink :)...remember the root cause needs to be addressed.....and it is not..because people believe it is bad code or drivers....when it is not completely so, and the real culprit goes unaddressed....and the circle continues because of that delusion....and a endless hunt, while being blinded to the truth....AVID/PROTOOLS HAVE Already Posted some information about IRQ problems and win 7...and their software Just last year I believe...and I did post it here on these forms...In another RANTING....
 
So sorry for the rants I post People ...But if you take the time to look into what I am on about...and we address the Motherboard people with our desires....They may make a board for music or professional Arts , studio grade performance, and specifications, at a premium, so we can build it (DREAM STUDIO), and they will come!! ...Stable as hell using Less of the old, more of the new Faster Standards...and more of more exclusive Physical IRQs implements to help Microsoft manage thing better...To make us and any audio card manufacturers happy and less dung flung in the wrong directions...going round in endless circles....losing sleep and hair and dosh wasted in invested gear, that would or could work....If only....eh?
 
Sorry Mod Bod...I just had to say something ...Here....LOL
 
Thanks for the posts and all the rest, Trying to help is good, and giving up good info is great...and bad info....it all helps eventually find the root cause....when applied or tested over time by many.
 
Good luck!
Blessings .

Get RME. Get one of the really good ones... at least UFX or better. You'll be SO glad you did. RME are near faultless. I've been running the same RME Fireface 800 for 8 years now. Never a single hiccup. I use it as THE monitor controller, too. It has never crashed, never caused any abnormal loud volumes or noise to hit my monitors. I really wish I could upgrade to at least a UFX version. Money's tight right now, though... and this one's still working and sounding flawless to me.

chuckebaby
I also thought it was cool for noel to jump in and do an analysis.
hes a good guy. 

Yup!  Agreed...

I have a Lynx Two Model C, and after reading this thread, I decided to see if there were any updates for my driver. I've had the same one installed on this machine since I built it a couple of years ago. I checked with Lynx, and sure enough, there was a new driver for download. Installed it, and X2 is running much better. Currently putting together a song, and I have yet to run into a hiccup.

Mod Bod

Thank you for you concern and your encouragement.  I've been using Cakewalk products for a long time.  Somewhere in my studio sits a 3.5 floppy disk of Cakewalk for Windows 1.0 so I have history with them.

Noel, has PM'd me and I am trying to make contact with Frontier Design to convince them to just have a peek at the minidump and contact Cakewalk so that (maybe) an accommodation can be made code-wise to overcome the problem.  I'm going to wait and see.  However, this special attention has convinced me that the individual customer still has importance to the leadership of the Cakewalk team.  Who would want to abandon that kind of dedication?
  

That's pretty cool, and I hope there's a happy ending to your story. Maybe a nice return gesture would be to update the title of the thread to reflect the positive path this journey has taken? Just a suggestion...

Take care

rabeach

Guitarmech111

Mod Bod

robert_e_bone



  

Everything in business has a priority level. If you are referring to the CWAF tool then my guess would be very few people use it. I have not ever used it since pro audio 9. I'm not saying I'm representative of it's use. That aside if it is broken the likelihood that it will be fixed or dropped is I think residing under a fairly high probability. I'm sure it happens some where in the world but I have yet to experience it elsewhere; that is a CTO posting on a user forum and assisting with a solution. It is appreciated Noel.

CWAF? I still have no problems with it even in X2a... I believe that it was necessary to edit it's ini file to work with Xx, but that's a simple issue of updating the Sonar rev#...

What seems to be the problem? Jamie O'Connel (sp) who wrote it on his own while working fr Cakewalk is (sadly) no longer working there as far as I know...

Keni

Hi Dave, I'd be interested in hearing about what FDG might have to say. Iirc, you as well as Eric P and other Dakota users were at one time even offering to pay for them to develop new drivers, and they did eventually release some (beta?) drivers for Win7.
 
Also, as you had indicated that your Dakota was working fine in X1, I'm kinda curious about what may have changed between X1 and X2 wrt how Sonar interacts with the Dakota's (or other interface's) drivers.
 
Oh, and for everyone recommending RME, yeah right. Try using a 'Hammerfall 9652' or 'Digi 9652' in x64 Windows. And be sure to check RME's forum for how they respond to people trying unsuccessfully to do just that - "it's an old card, what do you expect, it still works in 32-bit Win7 and x86 Linux so don't complain. You have to buy the HDSP card for x64."
 

yeah I got the picture now Goddard.
 
My card is a Hammerfall DSP 9632 and is supported under Win 7 64 bit.
 
Sorry your's isn't.
 
George

Goddard
 
 
Oh, and for everyone recommending RME, yeah right. Try using a 'Hammerfall 9652' or 'Digi 9652' in x64 Windows. And be sure to check RME's forum for how they respond to people trying unsuccessfully to do just that - "it's an old card, what do you expect, it still works in 32-bit Win7 and x86 Linux so don't complain. You have to buy the HDSP card for x64."
 

I am using an FF800 UFX, as suggested in the thread, without ANY issues regardless of what the developers do to Sonar. Kinda funny Dave's interface worked in X1 and now fails in X2.

This is an old thread but I'll be installing a different soundcard this weekend to see if I have better luck with the problem project.  I found an RME Hammerfall HDSP 9652 on Ebay and picked it up on the cheap.  I'll post back here whether SONAR will play nicely with the Waves, Slate and UAD2 plugins in that project for anyone who may be interested.   The project is finished but it will be nice to know for sure that the Dakota was the issue.

I have a spanking new Octacapture and the other day I had a session-destroying time with a guitarist because X2 kept crashing the living daylights out of things. I tried a billion workarounds and even started pulling up DAWs I don't use for audio much anymore (Reaper, Vegas, ACID...) and for various reasons could not get anything happening. Finally, after he had put his stuff away and was getting ready to leave, I pulled up X1 and the session went flawlessly. Same VSTs on every platform.
 
X2 was 64-bit, X1 is 32. I'm not saying that's what it is but let me tell you sometimes the problem is just not knowable and very frustrating unless you painstakingly choose and burn in every single piece of gear and plugin you use and keep the rig very streamlined. I don't know about the zietgiest of plugins, but I'm returning to a "less is very much more" philosophy and trying to remove anything I don't use all the time to a small and tight rig.

"I'm returning to a "less is very much more" philosophy"
 
+1

I'm having good luck with my 64 bit system using the same approach.
 
best regards,
mike

daveny5
You didn't say how much RAM you have. Makes a difference if you're using a lot of plugs.

4GB DDR2 800 (PC2 6400)