The error occurs when MuLab contains the only active instance of Halion (no error when the 2nd instance is active - 2nd Halion within another instance of MuLab or Halion Loaded directly into DAW). The first part of the video shows another issue I didn't mention before: Halion's program (plugin state) is not being preserved when MuLab is re-enabled (Halion restarts with empty program slot). The second part of video shows re-enabling MuLab containing Halion when no other instance of Halion is active (this is where the error message appears).mutools wrote: ↑Mon Apr 08, 2024 12:26 pm If that's the case please try this: Insert a 2nd instance of MuLab Plugin and insert Halion in that 2nd instance, without using it, but only to make sure that the MuLab Plugin instance you're disabling will not be the only MuLab Plugin instance using Halion. When that's done disable the original MuLab Plugin instance as before. Do you still get the error alerts?
---
https://youtu.be/iIpFJI88uss