Jump to content

Sonar - backup/restore settings


Recommended Posts

Hi there,

this feature seems really useful, however I tried to change my audio configuration (using a different asio driver) and tried to save the setting before and after.

In my system it seems that the asio driver "saved" in the configuration is not saved (or not loaded... I don't know).

Can someone try the same thing and verify if there is problem is there?

Thanks,

Giorgio

Link to comment
Share on other sites

Your audio driver preferences are stored in %APPDATA%\Cakewalk\Sonar\AUD.INI - the configuration settings save the contents of this file in the settings file and restore them to this file when you load or restore the configuration settings.

The easiest way to test if the configurations are being loaded, is:

1. When using the old configuration, save the configuration

2.  Copy AUD.INI and rename it to AUD.test1

3. Change your configuration to the new settings, and save it (under a different filename to the first one)

4. Restore the old configuration

5. Restore the new configuration, then copy AUD.INI and rename it to AUD.test2

6. Compare AUD.test1 and AUD.test2 - they should be different 

  • Like 1
Link to comment
Share on other sites

Mmmh, there is something strange happening. 

I attach the file gt.ini (Boss GT1000 asio driver) and the midas.ini (Midas VeniceF 16 asio driver).

If I copy the file in %APPDATA%\Cakewalk\Sonar\ the relevant INI file then it seems to change my asio driver (Boss or Midas).

However, using the "backup/restore" feature it seems to change the AUD.INI file too, but (even after restarting Sonar) the audio driver is not changed.

I have to investigate a bit....

Thanks,

Giorgio

 

gt.INI midas.INI

Link to comment
Share on other sites

Just re-tested the backup/restore here with my two audio devices and it seems to be working fine for me using it to switch devices.

The only thing that could possibly causing the issue for you is the presence of the Generic Low Latency ASIO Driver?

Link to comment
Share on other sites

Mmm, unfortunately no. I just deleted all the references of the "Generic low latency asio driver" in the AUD.INI file and tried again, saving the configuration in MIDAS mode, then switching to GT 1000 mode and saving a different configuration.

Then, again, loading the MIDAS mode (my default mode) does not give me the the Midas driver in use, but still the GT 1000.

Any other ideas?

Thanks a lot,

Giorgio

 

Link to comment
Share on other sites

1 hour ago, Giorgio Gabriel said:

Mmm, unfortunately no. I just deleted all the references of the "Generic low latency asio driver" in the AUD.INI file and tried again, saving the configuration in MIDAS mode, then switching to GT 1000 mode and saving a different configuration.

Then, again, loading the MIDAS mode (my default mode) does not give me the the Midas driver in use, but still the GT 1000.

Any other ideas?

Thanks a lot,

Giorgio

 

Removing it from the .ini file won't help - Cakewalk will still evaluate it if it's still installed.

Here's what I suspect the issue is - the Generic Low Latency ASIO driver is wrapping up the Midas device, making it unavailable to the real ASIO driver.  Cakewalk can't open the real ASIO driver, so it picks the first ASIO driver it can - which is the GT1000.

Link to comment
Share on other sites

Thanks again.

Let me explain one thing: I suspect that the "generic asio driver...." was installed much time ago, when I installed Cubase.

Then, after a while, since Cubase's "asio" driver was causing problems I removed it from the registry (see attachment).

In my system only the 2 asio drivers seems to be in place (GT-1000 and MidasFW).

I just tried another thing: I removed the AUD.INI file and a new one has been created by Sonar (which is much smaller in bytes) and this one has only the 2 drivers shown.

Then I tried again saving the configuration (Midas), then switched to GT1000 and saved again.

Nope, still reloading the MIDAS configuration the GT1000 asio remains....

Anyway it's not that important and I don't want to create troubles.

Bye,

Giorgio

 

Cattura.JPG

Link to comment
Share on other sites

Hmm - I wonder if the problem was at save time.  AUD.INI get's updated when you close Sonar, but if you've changed your audio settings without restarting, maybe AUD.INI isn't in a complete state.

Can you try something?

Manually set your config to use the Midas, then close Sonar.

Re-open Sonar - double check it's still using the Midas,  then save your Midas config.

Does switching between configs work then?

Link to comment
Share on other sites

I tried in several ways and I also tried in a different pc (a laptop) connecting a Steinberg UR22mk2.

Even in the laptop it seems that saving the configuration and recalling it (after changing the audio driver to use) it seems that the audio driver is not recalled.

However, making 2 different copies of the AUD.INI file for different 2 different settings, it works fine.

Anyway, it's not so important....

Thanks,

Giorgio

Link to comment
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
×
×
  • Create New...