When Would DAW Plugin Method Be Preferred Over Standalone?

Answered
0

When Would DAW Plugin Method Be Preferred Over Standalone?

 

I used the Standalone App to align the studio near-field speakers, e.g., system wide.

 

When would the DAW Plugin method be preferred? When a given project requires/prefers the SoundID files to be included/integrated into the project? Use as a mixdown reference for a record?

 

Any other suggestions or uses?

Cheers, 

1 comment

0

Hi William Johnson (Billy), thanks for your post and questions!

If you use the SoundID Reference standalone app for calibration, you can have everything calibrated, including your DAW signal, when it's routed to the SoundID Reference standalone app. In this case, there would be no need to bypass anything when you're rendering your mix. There will be some added latency when using the standalone app.

When using the SoundID Reference DAW plugin (true zero-latency), your DAW will have to be routed directly to your interface. You can use the SoundID Reference standalone app simultaneously for the rest of your sounds, though. There also won't be any double-calibration happening in this scenario. If you are utilizing the DAW plugin, you will have to bypass the plugin when rendering (there is a built-in warning message for this).

In the end, it actually might depend on your specific workflow and what you find more comfortable. Some users do prefer using the SoundID Reference plugin in their DAW, while others are running the DAW output to the SoundID Reference standalone app, which means you don't have to worry about bypassing the calibration when rendering. It also may be worth trying both workflows and see which one you prefer.

Please sign in to leave a comment.