In the SAME version 1.1 the following limitations exist:
Closing Audio Pilot does not release Monitoring DSP-Process and PROCs
When closing the Audio Pilot, the adopted Monitoring DSP-Process and associated PROCs do net get freed-up. To release these resources, open the Audio Pilot again, select "No Audio".
In Direct Control Mode, opening a mixer or plugin from the Patch Matrix can open the correct type but the wrong configured instance, with mismatched naming and missing metering.
For a SAME DSP Engine in Direct Control mode, opening a mixer or network plugin from the Patch Matrix may launch the correct type but the wrong configured instance. This can happen when there are multiple SAME DSP Engines in Direct Control Mode and these engines use the same DSP Volume definition.
Workaround: To avoid this issue, open the corresponding mixer or plugin from the Mixers / Plugins tab instead.
SAME Direct Control Mode Receiver does not adapt channel count to patched sender channel count
A SAME Engine in Direct Control Mode does not update the channel count and the RTP payload type for its configured receivers based on the sender information that is patched to the receiver externally through NMOS.
Workaround: Make sure to configure both the channel count and the RTP payload type correctly when setting up the receiver.
With no Jobs running - 250 PROCs are not released when closing Audio Pilot
When closing the Audio Pilot, the adopted Monitoring DSP-Process and associated PROCs do net get freed-up.
Workaround: To release these resources, open the Audio Pilot again, select "No Audio".