When you visit our website, we store cookies on your browser to collect information. The information collected might relate to you, your preferences or your device, and is mostly used to make the site work as you expect it to and to provide a more personalized web experience. However, you can choose not to allow certain types of cookies, which may impact your experience of the site and the services we are able to offer. Click on the different category headings to find out more and change our default settings according to your preference. You cannot opt-out of our First Party Strictly Necessary Cookies as they are deployed in order to ensure the proper functioning of our website (such as prompting the cookie banner and remembering your settings, to log into your account, to redirect you when you log out, etc.). For more information about the First and Third Party Cookies used please follow this link.
More information
The Spatial Coding emulation in preferences turns on/off Spatial Coding emulation for speaker monitoring. Spatial Coding is always applied to re-renders except 9.1.6, BIN, AmbiX as noted independent of how it is set for speaker monitoring in preferences.
Best,
Adam
That brings up the follow-up question. The wording is a bit misleading when it says (Spatial Coding) "Settings apply to speaker monitoring only".
-1- If Spatial Coding applies to Re-renders, which Element setting does it use, 12, 14, 16? The one I choose in the preferences, even if it is disabled for speaker monitoring?
-2- Why is Spatial Coding applied to Re-renders in the first place? Isn't the reason for that to reduce the file size during the coding process? The re-renders are either recorded into the DAW (Live) or a file is created (Offline) without streaming necessities. So why the Spatial Coding implementation?