I have just tried Sonarworks Reference for the first time.
How have you included Reference to your workflow? When do you use Systemwide, when VST plugin and when both are loaded simultaneously?
When working with DAW do you have Systemwide running in background or not? I am a bit worried that it will cause CPU, glitch or latency issues and I am not sure if it is a good thing to keep it in background.
Do you use Systemwide in WASAPI or ASIO mode and could you explain strengths and weaknesses of both modes?
I've read FAQs from Sonarworks pages but I would like to hear experiences of users.
Feels like a great software and makes huge difference in sound but I am worried about system stability, CPU/RAM consumption, glitches, cooperation between Reference, soundcard drivers, basic windows software like web-browser audio, WASAPI software, ASIO software, etc...
Also every time I change anything in Reference (like sound output) there is long processing delay. It might have to do also with my audio interface (Scarlett 8i6 3rd gen) which does have a bit slowish drivers and audio control software.
Sonarworks workflow tips (especially in Windows)
-
- KVRist
- 498 posts since 6 Feb, 2010
-
- KVRAF
- 2066 posts since 11 Aug, 2012 from omfr morf form romf frmo
I use Systemwide just so I don't get used to a different response curve. I don't care to get my vidya gaming sound or YouTube videos sweetened, brutally flat is fine. When the plugin is activated it can automatically deactivate Systemwide. But since Systemwide is its own output device in Windows it doesn't matter when my DAW goes straight to the interface via ASIO. Systemwide's on WASAPI, it's plenty good enough for apps that don't need ASIO speed. If you do some hardcore gaming or compiling software or rendering 3D then you might want to turn it off I guess.
If Systemwide causes latency in your DAW that is because other apps are trying to output sound. But why do you want other apps outputting sound while using your DAW? In any case, one can simply kill those apps which are eating CPU cycles, though not necessarily increasing DPC latency which has more to do with drivers.
It's updated regularly. I haven't had problems with it. Why are you changing the output of Reference so often though? You realize any app using Reference as its output device needs to reconfigure too? Stick to one system and one sample rate that matches your DAW.
If Systemwide causes latency in your DAW that is because other apps are trying to output sound. But why do you want other apps outputting sound while using your DAW? In any case, one can simply kill those apps which are eating CPU cycles, though not necessarily increasing DPC latency which has more to do with drivers.
It's updated regularly. I haven't had problems with it. Why are you changing the output of Reference so often though? You realize any app using Reference as its output device needs to reconfigure too? Stick to one system and one sample rate that matches your DAW.
-
- KVRist
- 352 posts since 24 Aug, 2017
You should only use the plugin while working in your daw, and not monitor via systemwide. You can gave systemwide running at the same time though, and you can play say a YouTube clip while having your DAW open if you like. Just make sure you use your normal asio interface driver and the plugin to monitor your dawgolemus wrote: Sun Nov 15, 2020 4:01 am When working with DAW do you have Systemwide running in background or not? I am a bit worried that it will cause CPU, glitch or latency issues and I am not sure if it is a good thing to keep it in background.
Do you use Systemwide in WASAPI or ASIO mode and could you explain strengths and weaknesses of both modes?
I've read FAQs from Sonarworks pages but I would like to hear experiences of users.
Feels like a great software and makes huge difference in sound but I am worried about system stability, CPU/RAM consumption, glitches, cooperation between Reference, soundcard drivers, basic windows software like web-browser audio, WASAPI software, ASIO software, etc...