Dear SoundID team,
I would like to share a workflow idea related to SoundID Reference that could potentially be implemented using two instances of the plugin.
Occasionally, by selecting a SoundID headphone profile different from the one corresponding to the headphones I am actually using, I end up with a result that sounds significantly better to me in terms of balance, texture and overall musical feel. This result is clearly produced by the specific correction curve applied by SoundID, not by the headphone itself.
The idea would be the following.
The first SoundID instance would apply the headphone correction profile that produces this preferred result, even if it does not match the physical headphones in use.
A second SoundID instance, placed after the first one, would then apply an inverse correction corresponding to the actual headphones being used. Its role would not be monitoring, but to flatten the signal so that the resulting audio can be exported as a master.
In that workflow, the first instance should remain active at all times, since it is precisely what creates the desired sound. The second instance would ensure that the rendered mix, once played back later through a single SoundID instance using the correct headphone profile, reproduces the same perceived result.
In short, instead of bypassing SoundID when exporting, the idea is to use a second instance to compensate for the real headphone profile, allowing the creative correction to be embedded into the mix itself.
I wanted to share this idea in case it aligns with your development roadmap or inspires future functionality.
Thank you for your time and for your excellent work.
Best regards,
David
0 comments