What's new

Metagrid for IOS (Updated with LE Commands)

We would really love to provide the updated commands set for Logic X but Apple hasn't updated yet their Logic SDK - they've promised to send it to us as soon as they are ready but so far no news from them... Let's hope they will release it soon.

Thanks very much for the reply! Not a problem, I can get by with key commands for now.
 
They way I set up my multiple scenes reflects Cubase windows to a certain extent. For example I have a scene that is mostly focused on the mix console, another one for drum and edit, and one with many buttons for the project page.

I'm wondering if there is any way for Metagrid to simply follow whatever Cubase window I click on? For example, if my focus is on Cubase key edit, then metagrid automatically focus on the corresponding scene that reflects the Cubase key edit?

Also, and I think it was mentioned earlier, is there going to be additional icons added for Cubase? I like what exists, but find many missing.
 
I’ve been having fun setting up Metagrid too. In Cubase under device setup you create 3 generic remotes and import the 3 xml files from the Metagrid download for Cubase into these – the 1st for Metagrid, the second for Cubase, the 3rd for macros. Its the 3rd which you use for linking metagrid to PLE commands without using keyboard shortcuts - I think that's what your referring to in Jono's video.


Ahhhhh! That's it - thank you!!!!
 
They way I set up my multiple scenes reflects Cubase windows to a certain extent. For example I have a scene that is mostly focused on the mix console, another one for drum and edit, and one with many buttons for the project page.

I'm wondering if there is any way for Metagrid to simply follow whatever Cubase window I click on? For example, if my focus is on Cubase key edit, then metagrid automatically focus on the corresponding scene that reflects the Cubase key edit?

Also, and I think it was mentioned earlier, is there going to be additional icons added for Cubase? I like what exists, but find many missing.

Some time ago we investigated the possibility of intercepting windows info in Cubase and we coudn't find a reliable solution. However, recently we stumbled on an interesting idea that is worth investigating and may bring the desired results. No promises though - we will try hard to make it happen in Q1.
 
January is coming to an end and unfortunately, we are not ready with v1.5 yet - during beta tests we found some blockers that require some additional work. However, we have decided to send an update for Apple approval this week - small but important from our perspective. Here are the main features and improvements:

- Support for custom actions in Reaper
- Support for systems with language-specific keyboards - now all the keyboard shortcuts will register correctly regardless of your keyboard settings.
- Support for language-specific text characters (with regional diacritics) depending on your keyboard settings. Now you can create text macros in your language!
- Cubase timestamp issue fixed - now all CCs and notes are correctly placed on Cubase timeline.
- On some setups Cubase/Ableton Live on Windows didn’t register keyboard combos on Windows - this issue has now been fixed (and was a tough one).

Thanks for your patience!
 
Some time ago we investigated the possibility of intercepting windows info in Cubase and we coudn't find a reliable solution. However, recently we stumbled on an interesting idea that is worth investigating and may bring the desired results. No promises though - we will try hard to make it happen in Q1.

Thank you for your reply.

While I can only speak for myself, I think other Cubase users might also follow the same general scene concepts that match Cubase windows. While I have scenes that are not releated to a specific Cubase window, having Metagrid automatically switch scenes depending on which particular Cubase window is in focus, would be a great workflow improvement...at least for myself. Of course to make it optimal for most users, there would have to be a switch to turn this feature on/off.
 
Last edited:
One more Metagrid question:

When right clicking on the metaserver icon in the task bar "start with windows" is checked. But when I start Windows 7 it is not starting.

After Windows 7 loads, LoopMIDI automatically loads too, but not Metaserver. I must manually click on the Metaserver icon that I have placed on my desktop, then in the lower right corner metaserver opens on my bottom task bar. Is that the normal behavior? Unlike LoopMidi that opens automatically upon windows booting, I must click on metaserver, before launching Megagrid on the iPad?
 
Some time ago we investigated the possibility of intercepting windows info in Cubase and we coudn't find a reliable solution. However, recently we stumbled on an interesting idea that is worth investigating and may bring the desired results. No promises though - we will try hard to make it happen in Q1.

An easy (and great IMO) solution would be to have the icons at the bottom of Metagrid also switch between workspaces in Cubase. Say, I have a mixer related set of icons asigned to the third screen in Metagrid. Whenever I activate screen #3 in Metagrid, workspace #3 is activated in Cubase (which is my mixer workspace).

Metagrid is a really awesome product btw!! I’m excited for the forthcoming updates.
 
One more Metagrid question:

When right clicking on the metaserver icon in the task bar "start with windows" is checked. But when I start Windows 7 it is not starting.

After Windows 7 loads, LoopMIDI automatically loads too, but not Metaserver. I must manually click on the Metaserver icon that I have placed on my desktop, then in the lower right corner metaserver opens on my bottom task bar. Is that the normal behavior? Unlike LoopMidi that opens automatically upon windows booting, I must click on metaserver, before launching Megagrid on the iPad?
+1 on Windows 10
 
One more Metagrid question:

When right clicking on the metaserver icon in the task bar "start with windows" is checked. But when I start Windows 7 it is not starting.

I had the same problem with metagrid starting automatically on windows 7. I ended up pasting a shortcut from the app into the startup folder under ‘all programmes’ in the start menu. That did the trick. Not sure if that works for windows 10.

Agree, awesome app.
 
An easy (and great IMO) solution would be to have the icons at the bottom of Metagrid also switch between workspaces in Cubase. Say, I have a mixer related set of icons asigned to the third screen in Metagrid. Whenever I activate screen #3 in Metagrid, workspace #3 is activated in Cubase (which is my mixer workspace).

Metagrid is a really awesome product btw!! I’m excited for the forthcoming updates.
@Metasystem.io It would be great if the scene selection icons at the bottom of the page had assignable Action Queues as well. A few ideas:
- Selecting a scene from Metagrid has a workspace in Cubase assigned as mentioned above. My mixer shortcuts in Metagrid would correspond to my mixer workspace in Cubase.
- Selecting a scene from Metagrid triggers a macro. You could have Metagrid open a workspace, executing a Project Logical Editor command making just the relevant tracks visible etc. A very flexible solution, the possibilities here are endless.
 
@Metasystem.io It would be great if the scene selection icons at the bottom of the page had assignable Action Queues as well. A few ideas:
- Selecting a scene from Metagrid has a workspace in Cubase assigned as mentioned above. My mixer shortcuts in Metagrid would correspond to my mixer workspace in Cubase.
- Selecting a scene from Metagrid triggers a macro. You could have Metagrid open a workspace, executing a Project Logical Editor command making just the relevant tracks visible etc. A very flexible solution, the possibilities here are endless.

Something like this?



Dunno if it will be possible to trigger delayed actions with one scene change, but it's a great idea for sure.
 
Sorry for the repost, I think my last about this was confusing and/or too boring for anyone to respond. :)

I'm thinking about getting a used 12.9 iPad Pro just for use with Metagrid. Anyone know if a first generation iPad pro is just as good as a 2nd generation, purely as far as using it with Metagrid goes? thanks!
 
Anyone know if a first generation iPad pro is just as good as a 2nd generation, purely as far as using it with Metagrid goes? thanks!

I could be wrong, but for Metagrid use I can't see how there would be any performance difference between the 1st and 2nd generations of iPad Pro's. Even the 1st generation Pro is a very capable iPad, and Metagrid will run just fine on lesser iPads to the best of my knowledge.

However there may be someone with a different view.
 
Sorry for the repost, I think my last about this was confusing and/or too boring for anyone to respond. :)

I'm thinking about getting a used 12.9 iPad Pro just for use with Metagrid. Anyone know if a first generation iPad pro is just as good as a 2nd generation, purely as far as using it with Metagrid goes? thanks!

iPad Pro 1st generation is a perfect fit for Metagrid.
 
Top Bottom