7.2 Upgrade - problems with ASIO Driver

[JuanMico]

Hi, I just checked all the synths after the upgrade, and all of them in standalone seem to have problems communicating with my Yamaha/Steinberg ASIO driver.
They open with Generic ASIO, and when I change it, I get an error message in red lettering. It does select the driver though, and I can use it for that session, but when I re-open the next time, same story again.
No problem as plugins. They used to crash Cubase constantly when browsing presets, and that seems to have been sorted out.

[marie_arturia]

Hi, you should contact the support, if you haven't already

[JuanMico]

Hi thanks. I just did.
I'm pretty sure there's some kind of conflict with Sonarworks Reference 4 Systemwide, because if I disable it completely, then the V Collection synths do use the Yamaha ASIO Driver and remember it.

[MajorFubar]

Hi thanks. I just did.
I'm pretty sure there's some kind of conflict with Sonarworks Reference 4 Systemwide, because if I disable it completely, then the V Collection synths do use the Yamaha ASIO Driver and remember it.

Some apps will throw a tantrum with Reference 4 Systemwide because by default it runs in hog-mode (i.e. it demands exclusive access to your audio device). I wouldn't even bother trying to make it work because it will generate too much latency.

[JuanMico]

Thanks, I thought it would be something like that.
The thing is, I don't intend to use the V Collection through Sonarworks. I use it for other stuff, so it's there, but not even selected as the output for Windows most of the time.
In any case now they seem to be co-existing happily -fingers crossed- but now I've got the problem I've already read in other posts, with V Collection not remembering the Audio Settings and defaulting to Generic Low Latency ASIO every time. Oh well...

Edit: I've decided that, since I only use Sonarworks Systemwide from time to time, I've changed the settings so it doesn't start automatically on Windows start. And whenever I need it, I'll just launch it manually.
This seems to have sorted out all the problems with the V Collection, and it's now running 100% as it's supposed to.

[MajorFubar]

Glad you got it working.