[Solved] X3 Driver and Config Issues

You may want to reset X3 to factory defaults by holding the CTRL and SHIFT keys while starting SONAR. Then configure X3 again. Consider adding information about your hardware and software configuration to your .sig or post. It may help with further suggestions.

I'll just attack it again tomorrow...had enough tech for the day.

I have the latest drivers...what about rerunning this Wave Profiler?

Yes, the X2 is WDM...but I had X3 setup as ASIO before this update...damn.

I was going to recommend renaming aud.ini (search google for details) but Scooks suggestion might do the same thing.

and what I also said...

Can you check if you have issues with new projects (not using any template)?

I also recommend running windows update several times (including optional) in case of library issues (such as C++).

Thanks...

Give my regards to the missus ;)

Cheers.

1. Don't uninstall previous Sonar versions, they each come with some potentially valuable content that isn't in any of the others. The actual unique Sonar version program files aren't very big at all. That said, if you feel it's messy and you want to "start over" you could remove everything, do a custom install of X2 and only install the basic program (to get V-Vocal in X3) and R-Mix (which isn't in X3). I think those are the only unique ones you'd otherwise miss. But again, space wise it doesn't actually make a significant difference.
 
2. I tend to do the same thing and also keep "additional content" off my system drive, that is, anything that's labeled as such during installation. None of the default stuff like project templates is very big. The most annoying exception is Dimension Pro which always installs a large amount of samples on C: even if you tell it not to, and there is a whole page of instructions on how to move them. Personally I've grown weary of this stuff so I gave up and left them.
 
I agree that Sonar, compared to Reason (or Ableton or Logic and perhaps others), is relatively finicky to set up with complicated looking preferences too. There was a thread about that recently actually. It is a great program though and once you have it set up to your liking and discover how easy it is to comp, use Melodyne, or save and insert multi-track templates you won't want to go back!

It does sound more like a breakdown in communications between Sonar and the audio interface compared to some internal problem within Sonar. One area where IMHO the Mac has it all over Windows is Core Audio, which is universal and predictable. Although it's great you didn't have issues with Reason, install enough Windows programs and eventually you'll run into some Windows hiccup. Many times it's due to other elements of Windows trying to take control of your sounds and conflicting with the program you want to use.

Yeah, I know Windows is wonky at times...I code it for a living actually, although mostly in SQL Server these days.  In any event, what was jerking my chain was that things worked fine in X2 Studio, X2c Producer but not X3e Producer -- even though the preferences looked the same under cursory inspection.  When I ran the Wave Profiler, it set it to WDM and things worked again.  Then, I simply flipped the device driver over to ASIO/triangle and all was well.  I am trying to slog through the 38(!)mb manual to get a sense of installation and preference options now.  A little light reading, as we say at work 

In any event, I truly appreciate everyone's input and patience with my "challenged" attitude last evening.  Much yet to learn, but one advantage I have seen in SONAR town ios a happier population which is a blessing.  The Reason community is very fragmented and angry by comparison over the recent R8 release (Lord knows why), but I digress again.  Looking forward to music making by checking out the synths, strum collection and other things that make my inner musician's mind boggle -- sort of like looking at the cockpit of the Space Shuttle the first few times lol...

scook
The wave profiler is used for WDM driver mode. If you are using WDM run the profiler. Check the driver mode, it should be set the same as X2. Assuming X2 is working properly.

This ended up the answer, more or less.  Kudos....

CakeAlexS
Can you check if you have issues with new projects (not using any template)?
 
X3E may have triggered off a bug with your driver or a library dependency issue:
The latest driver is 6.1.10 and you can install it here:
 
 
I also recommend running windows update several times (including optional) in case of library issues (such as C++).
 
Cheers...
 
Alex

OK Alex, I owe you a big thank you and a bit of an apology!  I made an ASSUMPTION that my driver was the latest, and that was because the last time M-Audio updated my sound card driver -- I think Bush was President here in the US.  Turns out had I actually recognized that you were saying V6.1.10, I might have saved myself a ton of hassle.

Long story short -- new driver equals 64bit performance and amazingly better in all ways, not to mention fixing this issue once and for all.


So my take away here is to read the entire answer and assume nothing.

Great, so everything truly works well now and Reason is far better off now with a true x64 driver to boot, so many, many thanks!

SiberianKhatru59
I am trying to slog through the 38(!)mb manual to get a sense of installation and preference options now.  A little light reading, as we say at work 

Since you are new to Sonar, it has to be said: You should take a look at Sonar X3 Power!, the book by Scott Garrigus. He's been writing these after market "manuals" for Cakewalk DAWs forever, and many -- myself included -- have found them indispensable, because they are more user friendly than the official documentation. For example, there is an entire section that answers your earlier question about file and folder locations, complete with a good organized way to deal with the issue.
 

SiberianKhatru59
...one advantage I have seen in SONAR town is a happier population which is a blessing.

Word.