What the H , i will have a shot at " What it Does "
 
Ok so  Pro Audio 9 is cakewalk software.
 
VoMethod=N ( By the way the default =1 )
To me this  represents a tweak/adjustment available for a Track Volume Fader Mapping /Automation if when imported from Pro Audio 9 to later/other cakewalk products doesn't reproduce the same Mapping/Automation levels correctly to then go to the AUD.ini file :
Change the line that says VolMethod= “N.” If N=1, change N to 0; if
N=0, change N to 1.?
 
What 1 or 0 = ? ummm
 
Anyone agree !
If you do agree this could also be a somthing to try even if importing for another DAW and the same problem is occuring .
 
 

bitflipper
There is no need to periodically delete aud.ini. Doing so merely resets every parameter to default values, which is a quick and convenient way to recover from having accidentally changed some setting to an inappropriate value. But it also erases any custom settings you may have made.
 
Regarding MixThreadCount, leave it at zero, its default value. This lets SONAR manage threads, which is usually the best option. The idea is that you'll get maximum efficiency when SONAR is able to make use of all your cores, which is what MixThreadCount=0 does. Setting it to anything else will reduce SONAR's performance, either by not letting it use all the cores or (worse) forcing it to manage more threads than cores.
 
 

I need to state an exception to your MixThreadCount advice.  I have a UAD Appllo Firewire and a new purchase of Sonar Pro. The Appllo absolutely would not function with the default "0" . This maybe an exception because Appllo does it's own plug processing, I have no idea how that would or should affect thread sharing  or whatever really goes on...across cores......but I needed to change my MixThreadcount to 4 or 6 cores and it behaves quite well. It would be great to find a layman s explanation on the subject. I remember a post by noel years back.

taccess, I went through the same exercise about 12 years ago, creating a Word document where I'd written down everything I knew about aud.ini (and cakewalk.ini) at the time. I stopped updating it maybe 6 years ago, so it's undoubtedly missing stuff, but I'd be happy to send you a copy if you send me your email address in a PM.

bitflipper
taccess, I went through the same exercise about 12 years ago, creating a Word document where I'd written down everything I knew about aud.ini (and cakewalk.ini) at the time. I stopped updating it maybe 6 years ago, so it's undoubtedly missing stuff, but I'd be happy to send you a copy if you send me your email address in a PM.

Done and Thankyou

please keep documenting your findings here as it would be really good to know which parameters are relevant, which are obsolete and just floating about in old AUD.ini files ...

if any of the Aud.ini file entries are obsolete, where is Sonar pulling that info when it recreates a new file? While its interesting to know what everything does I'd also like to know where Sonar pulls the info from.
 
 

Good work, I intend to follow this thread.

mudgel
if any of the Aud.ini file entries are obsolete, where is Sonar pulling that info when it recreates a new file? While its interesting to know what everything does I'd also like to know where Sonar pulls the info from.
 
 

My guess on the undocumented settings is that they are there and still do something ,we all know how important 1 of these settings can be when correctly set for our own rig, to me this is vital information that is missing.

Some of the settings are indeed obsolete, but are maintained for backward compatibility.
 
Software vendors often deliberately don't document things because they don't want users messing with them. As soon as you document something, you're obligated to freeze its definition going forward, giving up the option of changing it in future revisions. Just because it's in aud.ini or cakewalk.ini doesn't mean it's meant to be a user-defined setting.

bitflipper
Some of the settings are indeed obsolete, but are maintained for backward compatibility.
 
Software vendors often deliberately don't document things because they don't want users messing with them. As soon as you document something, you're obligated to freeze its definition going forward, giving up the option of changing it in future revisions. Just because it's in aud.ini or cakewalk.ini doesn't mean it's meant to be a user-defined setting.

 
Firstly let me say you are a genuine asset to this forum bitflipper you help and do it indiscriminately (well to forum illiterate people like me that is) and your advice is always spot on.
 
Totally agree with what your saying although i don't agree that software companies should have that mentality at all, and i am not referring that to Cakewalk and i am not suggesting you are either bitflipper,  because with my experience so far there has been nothing but assistance from the cakewalk staff with any matter i have ever needed to contact them for which has only ever been about 2 x bugs and these undocumented settings.
 
However in relation to Cakewalk if there is a Advance setting particularly in Any of the ( 3 x .INI ) files that has a value that can be changed then we the users should have all the information available to make a choice on it, regardless if someone is going to make changes without fully understanding what they are doing because that would stop everyone from having those extra tools!
 
Lets say hypothetically if cakewalk did have that mentality some where along the line then Lets remember at the present moment there are a ton of undocumented settings that users can mess with that sound like they could relate to things that they are in the .ini settings file looking for regardless trying to troubleshoot/tweak, which in my eyes would make it worse than if they had documentation that clearly states what everything is for !
To finish i will say that cakewalk keep adding .ini settings every year or so since they started so we all know Cakewalk are not like this.
 
UPDATE: I have received a PM back from lance who has stated he has passed the undocumented setting to dev and doc and they will try to make them available as soon as possible.