I am going through my Aud.ini file and trying to find out what everything means . In order to do this i have re organised the aud.ini manual in alphabetical order then i have added the rest of the settings from the aud.ini file that are not listed in the manual .Leaving alot of settings without "What it Does ".
 
So i have found that there are some example : WriteCache= , which "I Believe" is in edit > preferences > sync and caching >file system. This Value states 0 in the aud.ini file but 256 in the preferences . So either WriteCache= represents a different setting or the value in aud.ini file is no longer valid or the value 0=256 ???????????????
 
I just want to understand what the value of everything in the aud.ini represents so i can make decisions on what to do properly. 
 
Can you Please help me clean this up.
1) should any of the below be deleted ?
2) can you provide a path to preferences  for any of the below
3) can you provide a "What It Does " for any of the below
4) once the below is sorted i will upload a alphabetical aud.ini manual for everyone who wants it . 
 
This is the remaining list from aud.ini with NO "what it does "
UPDATE:
 
 
 

CSUseSpin=
DriverID=               
EnableAsioBufferSwitchTimeInfo=
EnableDeviceOutputLatencyCompensation=
EnableSSEMixing=
ExtraDiskBuffers=
FreeMemOnUnload=
Interleave=
ManageASIOThreadPriority= MORE INFORMATION IS NEEDED FOR THIS
MaxInputChannels=
MaxOutputChannels
MigratedDMA=
MixThreadCount=
MME.DriverMap.UseWaveIn1=
MME.DriverMap.UseWaveOut1=
OpenInputFirst=
PicCacheLevels=
PicCacheZoom=
ProfiledKS=
ProfiledMME=
ProfiledWASAPI=
RadiusStretchingPhaseCoherence=
RadiusStretchingPitchCoherence=
SyncDivisor=
SyncMaxDriftMsec=
ThumbnailCacheSize=
TimingOffsetBuffers=
TimingOffsetMsec=
TransDetectorModel=
UseAlias=
UseWDMDmaForWASAPI=
WaveInID=
WaveOutBuffersKS=
WaveOutBuffersMME=
WaveOutExtraBuffers=
WidePacking=

Here is The LATEST AUD.ini Alphabetical Manual :
https://files.fm/u/k7zudbxg

Thanks for your post. I know absolutely nothing about AUD.ini, but would love to learn. I hope there will be some really helpful responses to this subject.  

UPDATE : i have found a few and removed them from the list .
 
Can someone confirm this is correct and what it would benifit ?
EnableMixThreads=
 
When MixThreadCount is set to zero, SONAR will allocate one thread per CPU. By setting it to 1, you are overriding this behavior and forcing SONAR to use a single thread even though you have multiple CPUs.
So setting it to a value of 2 explicitly ends up creating 3 threads in all, one original thread and two extra worker threads.
 
Is this correct ??

I guess MMCSSThreadPriority is something like AvSetMmThreadPriority() in Avrt.dll or mmcss.dll.........

It used to be considered beneficial to delete Aud Ini occasionally, Is this still a thing and, if so, how exactly do you do this in Platinum?

rodreb
It used to be considered beneficial to delete Aud Ini occasionally, Is this still a thing and, if so, how exactly do you do this in Platinum?

Alot of the settings in AUD.ini represent  the Edit> Preferences of Platinum , there are additional settings which are advanced settings that also can be configured and should i my opinion be understood by the user. If you delete the AUD.ini file platinum will recreate  a new one at default values > so if you do delete it you will have to make the changes manually again to the AUD.ini file and preferences "i Believe " all over again .


 
Your choice but when you get to know the AUD.ini theres no need to delete it unless you want to start from scratch and troubleshoot things , me personally when i make a change to the AUD.ini i make a note of it in a separate notepad text doc that i save / MY AUD.INI settings for future reference .

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.
 
 

Ok so i have sent a PM to Jon at Cakewalk asking if he can source the missing "What It Does "
 
Here is a link to the started but not finished alphabetical AUD.ini Manual.
 
https://files.fm/u/kternvbq
 
I have not double checked it although I am confident nothing pasted in the wrong row as i was doing it .
 
Reason I  am posting the unfinished link is because i want you to see how much easier it is to have this Manual
A) in Alphabetical order when skipping through your AUD.ini file
B) How important knowing what every single AUD.ini setting relates to ( as your skipping through it ) , even if it points back to the ( EDIT >PREFERENCES> ??? for some of them , at least when you go through your AUD.ini file from top to bottom you will know that you have thoroughly done it properly without missing anything because your not sure !! Kapeeaaasssssh !
 
So if you can download the started manual and contribute to finishing it for the sake of The Best DAW on Earth and there Alien benefactors please Do .

In search of filling out the blank "What it Does"  as you are aware of if you downloaded the AUD.ini Manual from the link above :
 
VoMethod=N , I found this which is one of the missing one's in an old Sonar Manual ,
 
My interperet is sometimes off and often i need to offset my brain to keep up so would someone care to elablorate on this function and what the value's <0 or 1> mean ? Please!
 
Pro Audio 9 has a setting in the Audio Options dialog box called MIDI
Volume Mapping. This setting determines how many dB that a movement of
a volume fader produces. This setting is not stored in each project file, so
SONAR can’t tell precisely what dB scale was used to produce the file
you’re opening. If the volume sounds incorrect:
1. Open SONAR’s AUD.INI file (find it in your SONAR folder and doubleclick
it).
2. Change the line that says VolMethod= “N.” If N=1, change N to 0; if
N=0, change N to 1.
3. Save the file and close it.
4. Reopen the Pro Audio file in SONAR. If the volume sounds correct,
save the file in Sonar.
If other Pro Audio 9 files were opening correctly in SONAR, change the
VoMethod=N line in SONAR’s AUD.INI file back to what it originally was, and
re-save the file.

Cool! Thanks for the document. I'm thinking this would be more convenient in spreadsheet format. I know, I know. Beggars can't be choosers, but still ....