You know what? I think there is a bug with Sonar 6's Wave profiler. Check out this post. same thing happened to me and others
what's new..
rant starts here- It has been going on for years.. the wave profiler was always cr***y and that's one of the major reasons why to delete the aud.ini and let Sonar
inspect all the drivers from scratch again..
The point is that nothing really changed much and Sonar has "its way" of doing things, i'm not complaining, mostly the users got it right by now -
You need to select from the lists the drivers you want to use (Audio>Drivers) ..now, if Sonar wasn't restarted there's a good chance the lists there don't really reflect the right order/amount of available drivers on the system.. so then everyone learned that you need to restart Sonar after every change (it actually opens a screen that says so most of the time) and only at the next launch make the other changes or inspect if the audio engine works right/right I/O driver options appear..
if not - everyone learned by now to delete the aud.ini and do all the above again..or just let Sonar run its wave profiler without any onboard cr***y "soundcard" with their cr***y drivers ... etc. etc. etc.
True , maybe things could change at some point? a better way of detecting and setting how Sonar works with soundcards and their drivers?
We've all seen Sonar's file "corrupted" in a way that drives you crazy..sample rates that suddenly don't work..the infamous "audio driver is not compatible with the audio format" - these days the users find this forum and ask..i'm sure that before these forums were created only a few went to the newsgroup for asking what to do..
how many times we heard "all the other apps work well, just sonar doesn't work with my soundcard"? that wave profiler could use some good upgrades..but there are too many other things to do (thank you Cakewalk for fixing what really needs to get fixed..)
[end of rant?] of course i blame here also the MS Windows and the lack of a "BulletProof" standard for how (lousy?) soundcards work with the system..between all the registry keys in Window, ASIO WDM and MME for each card (or not) and all that it's easy to mess up.. I don't think that Sonar always WORKS right out of the box (multiple cards, onboard or Creative cards..soundblasters..) and the SECOND time users are trying to "set up" things (after changing selections of the Drivers lists, playback/recording master..etc.) - too many things can go wrong, many times a second (or more) re-profiling actually does more damage than good..therefore the "delete you aud.ini" to begin all over. why going out of Sonar for this? put some "reset to default"
buttons in Sonar's audio options (more on that below)..it will look more "professional" for most and many new users will be able to find these instead of going outside of Sonar and messing with ini files.
The aud.ini contains too many other "sections" so IMHO deleting it all without merging some of your older (trusted?) values can be a bad thing to do.
I mentioned "reset" buttons because the i/o detection is one thing there.. give some more checkboxes inside Sonar for controlling all the new things since CWPA..these will set the 0 or 1 flags in the registry or that ini file.. or value boxes for setting (you guessed right) some of those new aud.ini options -
why do everyone need to mess with the aud.ini and finding some "secret" magic lines here in the forums?
put it all in a "super advanced- handle with care" or whatever section inside the Audio options window!!!
Yes , it's 2007 soon! ... so even include a context sensitive pop-up help/tooltips when you hover around those super duper advanced complex audio settings
post edited by Honest_Al - 2006/11/30 12:34:01