Using NAM in live hosts like Gig Performer or Cantabile can get a bit cumbersome because the host cannot really identify which .nam model is currently loaded inside the plugin.
Right now, the workaround is often to use multiple plugin instances or duplicated rackspaces just to switch captures between songs or variations.
It would be really useful if the plugin exposed the currently loaded model identity (filename/path or some kind of model ID) to the host through the plugin state.
That would make it possible to manage model switching and preset recall much more cleanly in live workflows while keeping a single NAM instance.
I think NAM already internally knows which model is loaded, so this would mostly be about exposing that information to the host side.
Thanks again for all the work on this project.
Using NAM in live hosts like Gig Performer or Cantabile can get a bit cumbersome because the host cannot really identify which .nam model is currently loaded inside the plugin.
Right now, the workaround is often to use multiple plugin instances or duplicated rackspaces just to switch captures between songs or variations.
It would be really useful if the plugin exposed the currently loaded model identity (filename/path or some kind of model ID) to the host through the plugin state.
That would make it possible to manage model switching and preset recall much more cleanly in live workflows while keeping a single NAM instance.
I think NAM already internally knows which model is loaded, so this would mostly be about exposing that information to the host side.
Thanks again for all the work on this project.