I am not sure what changed, but metagrid has a really hard time finding reaper and switching to its profile when reaper is active. Please let me know if there is anything i can try to debug/fix this.
Perphaps Reaper has changed it is name and the name now differs from your profile name?
have tried that.
it might be chrome or something in chrome hogging the show. if i close chrome it starts to work again. also seems to be ok for a bit after i reload chrome. but its only affecting reaper so, doesn’t make sense. will keep trying to track what else is active.
OK - let’s monitor this - we can’t replicate it on our test systems.
ok will post more when i find stuff, it was happening to reaper then i loaded another app and the main grid would work in reaper and not in another app. clicking on a secondary grid tab would go back to desktop workspace. Does not seems Reaper specific now.
server version is 5.1.7
mgp version 1.6.13 build 34476
tried rolling back metaserver to 5.1.5 , didnt help
made a profile for windows explorer. when issues occur it is focused on the explorer profile
sometimes the toolbar at the top will get messed up also. not sure if its related to the same issue though.
This issue is fixed with MGP 1.6.14 to be released on Monday.
mgp flickers/ switches more since last update. I can see it get to repear momentarily then it switches back to default/desktop profile. Has not fixed the issue but maybe another clue there.
would love to be able to revert to a previous working version in the meantime.
@Muscly - it seems that we need to dig deeper on your case. In the meantime please do the following:
-
Set the Fallback Profile to Reaper in MetaGrid Pro Settings (Automation and Scripting). You shouldn’t revert to the Desktop profile then.
-
Please enable the logging (set it to Trace) in MetaGrid Pro Settings, replicate this case a couple of times and send us the logs.
We can’t revert to previous version due to App Store limitations. We will need to solve this through TestFlight. Please email us at help@metagrid.app - we will take it from there.
ok will do, i should mention again it is not exclusive to reaper. will happen with other apps.

