How to Re-Assign Action Context Menu to Another Profile?
Consider this scenario, with Presets e.g iZotope RX 10 → RX 11 upgrade.
Given that I have previously installed an iZotope RX 10 application
And I have installed a new “Profile” presets for RX 10 for MetaGrid Pro
And that I have created a “Menu Command” for iZotope RX 10 with “View → Time (h:m:s)”, please images for further understanding.
To upgrade I had to rename the profile from iZotope RX 10 to iZotope RX 11.
And I had the delete the previous context menu.
And to make context menu work, I had to re-assign context menus actions to the RX 11 server version’s context.
This is also happening for official installed profile presets ( see images )
Imagine having to do this for custom workflows. Even for the official “MetaGrid Pro” Profile can be long.
So to my question, is there an easier way to re-assign the context menu to another parent profile owner?
@sealtunes Here is MetaServer 5.3.4 Internal Beta with the solution for the problem you have described. Please test it to see if it solves the problem (it works on our test systems).
MetaServer_5_3_4_Internal_Beta.zip (6.1 MB)
And here is the explanation:
When an app updates to a new version (for example: RX 10 → RX 11, Cubase 13 → Cubase 14 the internal macOS name of the app changes.
Because of that:
-
Menu commands saved for the old version were still targeting the old application name
-
macOS saw the new version as a different app,
-
And MetaServer couldn’t send the menu command to the new version
-
So users needed to manually remap all menu actions again.
That was obviously frustrating.
What We’ve Implemented (5.3.4 Internal Beta)
We introduced a new smart redirection system in MetaServer.
1. MetaServer now recognizes when the frontmost app is a newer version
Examples:
-
RX 10 → RX 11
-
Cubase 13 → Cubase 14
Even though the internal name changed, MetaServer now sees these as the same application family.
2. When you trigger a menu action, MetaServer checks:
-
“Was this action recorded for RX10?”
-
“Is RX11 currently the frontmost app?”
-
“Is this obviously the same application, just a different version?”
If yes → MetaServer automatically redirects the menu action to the new app.
No user action required, no remapping, no migration.
3. If MetaServer is not sure → it safely falls back to the old behavior
So there’s zero risk of commands firing into the wrong application.
What This Means for You
-
When an application updates to a new version, your existing MetaGrid menu actions continue to work automatically.
-
Actions recorded in RX10 will work in RX11.
-
Actions recorded in Cubase 13 will work in Cubase 14.
-
You don’t need to rebuild or reassign your grids anymore.
This makes updating your software far less painful and keeps your workflows intact.
@MetaGrid_Admin thanks will test and report back
OK, thanks for the feedback - so we will release the new MetaServer version together with MetaGrid Pro 1.6.15.
