Good Day,
 
I'm wondering if anyone out there using RME UFX or similar RME interfaces, have found any specific non standard settings that optimize performance (ASIO mode) in Preferences, more so in more advanced settings that can be modified in Audio - Configuration File, and/or Sync and Caching, Playback and Recording, (I'm thinking many configuration settings may be more related to the computer system used than the audio interface). For example I typically use 96K sampling, and check 64 bit double precision engine, does using 64 bit engine have significant benefits/demerits, not really explained in help?
 
On this subject, it would be good if Cakewalk provided a more advanced Technical User Guide with more in-depth help and explanations and information/training on the relative reasons and merits/demerits of the various Configuration File settings, if not all settings, why and when they are used or are even available to be changed, as current help references don't really explain some of these setting in much detail. (while some features are very well explained, others I guess you'd have to have a PhD in electronic/audio signal processing to even start to understand the relevance). I have one training video on Sonar X1 that suggests some settings for maybe 2 or 3 of the configuration file items, such as thread count (for multi core), some buffer settings and basically suggests experimenting with these (you could spend a life time experimenting), or not to change them at all (why make them available then?).        

Can't say I've even needed to start changing the more esoteric preference settings to get better performance out of my UFX because I can't really see how it could perform better. I can run buffers giving under 10ms round trip latency without any problems. Even the minimum sized buffer (around 6ms round trip latency @44.1KHz) works fine so long as I haven't too many heavy duty plugins running.

As for Sonar's configuration files being text, my guess os that the builders realised someone might need to change those variables, even if only very rarely, so they put the stuff in text files.

It also means the developers can easily change or experiment with Sonar's configuration settings without having to hack into the source code and recompile, which may or may not be why they did it this way but is one reason why things sometimes get done that way.

tlw
...
As for Sonar's configuration files being text, my guess os that the builders realised someone might need to change those variables, even if only very rarely, so they put the stuff in text files.

It also means the developers can easily change or experiment with Sonar's configuration settings without having to hack into the source code and recompile, which may or may not be why they did it this way but is one reason why things sometimes get done that way.

Consider drum maps. Same idea.

Pretty much all the settings in a DAW are related to the system,  not to the audio interface.  The ASIO panel is the only one that will allow you to enter the UFX's system settings and alter the latency, trim the sample rate (though it is usually locked to the DAW session), or switch digital I/O and clocking settings if needed.  Otherwise it does not need tweaking.  

I use an RME UFX and now using 96khz following recent revelations about using higher sample rates (this is a long term experiment) but as far as Sonar's 64 bit double precision engine it's only necessary at final mix down for export.