Hi,
Just recently updated to the latest versions of MGP and Metaserver. Loving the Plugin Manager implementation and have started incorporating those into my Grids. But have been observing these things after the update on my end:
The biggest one, ‘Selected Channel’ control surface has been disappearing every time Cubase exits. I have to add it again for the next start up.
Toggle From External Sources, which used to change Latch states in certain staple buttons like ‘Edit Channel Settings’ and ‘Edit VST Instrument’ which correctly reflect the selected track’s status if these windows were open, no longer does that.
Running the Plugin Manager to insert VST Instrument has some inconsistencies. I have a button to replace the VST Instrument on the selected track with the one specified via MGP. The ‘Editor’ button is kept on. If the selected track doesn’t have an existing instrument i.e it’s in the NO VST Instrument’ state, MGP correctly inserts the Instrument plugin and opens the editor. But, if the track already had a VST Instrument, then MGP correctly changes the instrument, but it does not open the plugin editor. If the plugin editor was already open, then you can see it change as MGP changes the instrument
Thank you for the detailed report. There appear to be three separate symptoms here, so I would like to verify the exact versions before treating them as one issue.
Please provide the exact MetaGrid Pro build, MetaServer build and Cubase version you are currently using. Please also confirm whether you reinstalled the latest bundled Selected Channel script after updating MetaServer.
MetaGrid Pro 1.7.4 contains improvements to incoming MIDI state restoration, including correct port-aware state replay for latching switches. Once 1.7.4 is available, please check whether this restores the Toggle From External Sources behavior for Edit Channel Settings and Edit VST Instrument.
The Selected Channel device disappearing after Cubase exits remains under investigation as a persistence issue.
For the Plugin Manager case, please repeat both operations during the same session with the Editor option enabled:
Insert an instrument into an empty slot.
Replace an instrument already present on the selected track.
If replacing the existing instrument still changes the plugin without opening its editor, please attach a short screen recording or screenshots. That will allow us to investigate the replacement and editor-opening sequence separately.
MetaGrid Pro 1.7.4 and the companion MetaServers are now publicly available. Here is the production status of the three items reported in this topic.
Toggle From External Sources
MetaGrid Pro 1.7.4 includes the incoming-MIDI cache replay correction. Port identity and MIDI channel matching are now preserved when a grid is displayed, allowing latching switches to restore the latest state received from the configured MIDI source.
Please repeat the original test with Edit Channel Settings and Edit VST Instrument after updating.
Selected Channel disappearing after Cubase exits
MetaServer Windows 6.0.4 includes recovery for stale or temporarily unopenable Windows MIDI Services endpoints. Please test several Cubase start/quit cycles with MetaServer and Windows MIDI Services left running and confirm whether the Selected Channel surface remains available.
If it disappears again, please capture a MetaServer support package before restarting anything and check whether the relevant MetaGrid ports are still visible in Cubase.
Plugin Manager replacement does not open the editor
This behavior is separate from the 1.7.4 hotfix. Please let us know whether it still occurs with the production release and include the exact Cubase version, instrument being replaced and whether the editor was open or closed before the replacement.
This topic will remain open until the three behaviors have been verified independently.