What's new

Metagrid for IOS (Updated with LE Commands)

I just want to say to those who are considering the big 12.9 iPad, don't hesitate -- it's really amazing having all of that real estate to use. I wasn't sure when I first got it, but now I can't live without it. :) At some point I'll get a second one...that will be insane.
Hmm, two iPads for the price of a powerful slave Desktop

No thanks :sneaky:
 
Hmm, two iPads for the price of a powerful slave Desktop

No thanks :sneaky:


And that is the beauty of freedom of choice! ;)

In my case, an additional desktop (which I already have, though I long for the day when that won't be necessary) doesn't do what two Metagrids would do at all, and doesn't serve a similar purpose in any way. Two iPads with Metagrid would be incredible for me once we get faders and the like on Metagrid.
 
MG on a couple of IPad Pros would be amazing but too much money for me at this point in my life. 4 would be out of this world great!

The thing to remember with the iPad Pro is that you still have the same number of buttons whether it’s on an iPad or iPad Pro. If the option to have more buttons on the iPadpro version I may have been swayed to have bought and iPad Pro.

Instead I have now got a 27 inch Acer Touch screen in my Music Lab (and using MG on an iPad when mobile - and will use the the faders as they will allow for multiple CC assigning to same fader etc).
 
Last edited:
MG on a couple of IPad Pros would be amazing but too much money for me at this point in my life. 4 would be out of this world great!

The thing to remember with the iPad Pro is that you still have the same number of buttons whether it’s on an iPad or iPad Pro. If the option to have more buttons on the iPadpro version I may have been swayed to have bought and iPad Pro.

Instead I have now got a 27 inch Acer Touch screen in my Music Lab (and using MG on an iPad when mobile - and will use the the faders as they will allow for multiple CC assigning to same fader etc).


Yes, very true. For me it's great because I can have more buttons on the MG grid because of their bigger size on the 12.9, which is what lured me into buying it.

I'm looking into a 27-inch screen or larger, myself. I would love to get rid the two monitors I have side-by-side right now.
 
Yes, very true. For me it's great because I can have more buttons on the MG grid because of their bigger size on the 12.9, which is what lured me into buying it.

I'm looking into a 27-inch screen or larger, myself. I would love to get rid the two monitors I have side-by-side right now.

Isn’t the max number of buttons on the iPad Pro a grid of 11 x 10?

That’s the max number of buttons the iPad. Which, unless I’m wrong, just means MG on an iPad Pro just has bigger buttons not more buttons. This, for me, makes buying an iPad Pro not worth the financial investment worth it (as much as I would love one) just for MG.

I was working with MG on an iPad Pro in December as I was working with a couple of film composers that wanted to have a touch controller. I didn’t see an option to have a bigger grid than 11 x 10 but I did like he buttons being larger obviously.
 
Isn’t the max number of buttons on the iPad Pro a grid of 11 x 10?

That’s the max number of buttons the iPad. Which, unless I’m wrong, just means MG on an iPad Pro just has bigger buttons not more buttons. This, for me, makes buying an iPad Pro not worth the financial investment worth it (as much as I would love one) just for MG.

I was working with MG on an iPad Pro in December as I was working with a couple of film composers that wanted to have a touch controller. I didn’t see an option to have a bigger grid than 11 x 10 but I did like he buttons being larger obviously.


Yes, totally -- what I meant is that because the buttons size is bigger on the 12.9, I can have a smaller grid size on MG and still have buttons large enough for my preference. I did get an amazing deal on my iPad: $580 for a refurbished one, otherwise I would have gone for the smaller one.
 
Yes, totally -- what I meant is that because the buttons size is bigger on the 12.9, I can have a smaller grid size on MG and still have buttons large enough for my preference. I did get an amazing deal on my iPad: $580 for a refurbished one, otherwise I would have gone for the smaller one.

Ah I get it. Yeah, man, the IPad Pro is definitely an amazing option for MG especially if you get it for a great price like you have!
 
Once I create a Macro in Cubase using the Logical Editor, how do I select it in Metagrid? I get it with the Project Logical Editor because there is a specific folder of Scenes to copy to the Preferences folder but I don't know where to save the Cubase Macros for Metagrid to find them. Any help would be great!

I am stuck on this at the moment. I can get some scenes created as Cubase macros to work from metagrid, but others dont (like one Macro I created to make everything above the Divide Track list show up, just does nothing when triggered from Metagrid but works fine when triggered by itself as a macro from in Cubase) any ideas?

EDIT:
Actually just figured it, and it might be a method to adapt your version jonotbono from your excellent video, I think its simplifies the whole process a bit , I found it out quite by accident:

First I created a Project Logical Editor Scene for Metagrid to make all the relevant bits visible above the Divide Track line, then assigned that scene to MACRO 1 in the Generic Remote 3 setup for Metagrid in Cubase devices setup section (as per cubase and macros in the metagrid manual.)

Now I just have to stick the app-specific command Metagrid: MACRO 1 at the end of any button setup and it triggers visibility for everything above the Divide Track Line.

(Still havent found a way to add the ruler back in as visible though for some reason there isnt an option for it in Project Logical Editor)
 
Last edited:
(Still havent found a way to add the ruler back in as visible though for some reason there isnt an option for it in Project Logical Editor)

Currently having roadworks outside so there is no electricity (using phone at minute) but if you want the 2nd Ruler you could put all those track above Divide Track list into a folder and using the naming of the folder. I don’t bother with the ruler though because I have a button for toggling timebase.

The quote you taken from me is from quite a while ago and the macros are just the 3rd XML page. It’s really simple to save them and make sure to export and reimport the XML (its a Cubase quirk) otherwise when you restart Cubase the XML won’t remember any changes.
 
The new version of Metagrid/Metaserver isn't working that smooth in my case. 1/3 of my buttons don't work anymore and trigger different key commands then they should do. I guess I have to figure out how to downgrade my app.
 
Currently having roadworks outside so there is no electricity (using phone at minute) but if you want the 2nd Ruler you could put all those track above Divide Track list into a folder and using the naming of the folder. I don’t bother with the ruler though because I have a button for toggling timebase.

The quote you taken from me is from quite a while ago and the macros are just the 3rd XML page. It’s really simple to save them and make sure to export and reimport the XML (its a Cubase quirk) otherwise when you restart Cubase the XML won’t remember any changes.

thanks figured it out finally. I also just figured how to show the Ruler using the PLE:

( container type is, Equal, Track, And
Name, Equal, Ruler ) note: not the name of the ruler but literally the word 'Ruler'

and then in the action target pane at the bottom add:
Track Operation, Hide Track, Disable.

Also found a way to de-select other tracks, which seems to happen a lot when jumping around the Metagrid Buttons.
Did this by selecting the Ruler which then deselects everything else by default.

Achieved it using the same macro in PLE as above but remove anything from the action target pane at the bottom and set Function to Select (at the very bottom of the PLE window)

interestingly this also selects the ruler even if it is hidden but the main thing is it deselects everything else by selecting something I cant ruin accidently.
 
The new version of Metagrid/Metaserver isn't working that smooth in my case. 1/3 of my buttons don't work anymore and trigger different key commands then they should do. I guess I have to figure out how to downgrade my app.

This happened immediately after installing the new version?

Not sure if this will help, but I have experienced certain buttons not working. It had nothing to do with a new version. Make sure you right click the megaserver icon (on a PC in the lower right corner) and confirm the port set ups have not been changed. I'm not sure why, but several times in the past few months, the metaserver ports have been changed rendering some buttons useless until I correct the ports.

If anyone knows why the port set-ups would sometimes randomly change I would like to know how to prevent this.
 
Last edited:
Something funky is definitely going on. I'm used to just hitting PLAY in Logic and playing something in and then hitting "Capture as Recording" but for some reason it IS capturing the recording but its also muting the track. Quick fixit I just deleted the METAGRID command for "CLR" and programmed in my own via the Keyboard shortcuts menu.
 
If anyone knows why the port set-ups would sometimes randomly change I would like to know how to prevent this.
Just make sure that you always turn on all your Midi devices. Once I forgot to turn on my XTouch Compact and the ports were out in Metaserver. I think the ports are assigned numerically, so if you don't start a midi device, that messes up the assignments. This is in Windows 7 like you.
 
The new version of Metagrid/Metaserver isn't working that smooth in my case. 1/3 of my buttons don't work anymore and trigger different key commands then they should do. I guess I have to figure out how to downgrade my app.

Hi Guys, if you have some problems with v1.4.4 (keyboard shortcuts don't work as they expected) please go to www.metasystem.io and redownload Metaserver (please remember to refresh your browser before redownloading). We have rewritten the keyboard shortcuts support to enable automatic remapping based on the keyboard language chosen by the user - however, on some systems it didn't work as fine as on our testing setups. Anyway, everything should be back to normal. Metaserver version hasn't changed yet you will still see it as v1.4.4 - we will adjust it during the next maintanance release. Thanks for your patience!
 
Hi Guys, if you have some problems with v1.4.4 (keyboard shortcuts don't work as they expected) please go to www.metasystem.io and redownload Metaserver (please remember to refresh your browser before redownloading). We have rewritten the keyboard shortcuts support to enable automatic remapping based on the keyboard language chosen by the user - however, on some systems it didn't work as fine as on our testing setups. Anyway, everything should be back to normal. Metaserver version hasn't changed yet you will still see it as v1.4.4 - we will adjust it during the next maintanance release. Thanks for your patience!
@Metasystem.io Has the updated SDK been released by Apple yet for the new version of LPX? or even for version 10.3? since as I understand it, Metagrid is still on 10.2.4 key commands...
 
Also found a way to de-select other tracks, which seems to happen a lot when jumping around the Metagrid Buttons.
Did this by selecting the Ruler which then deselects everything else by default.

Yeah regarding the ruler, I’m sure in the last Cubase update they put in some extra PLE commands That gives the option for Ruler (and if my memory is correct - something to do with Disabled tracks). Cool that you have sorted that out. Still not bothered about having two rulers though.

As for tracks disabling when you select visibility buttons. I showed how to do that in a video on Metagrid and templates. It was annoying until you create a PLE to deselect last selected track. I found that each time you change to another visibility option, they stay selected, and stacked on top of each other. Isn’t the PLE (and LE) wonderful! :)
 
Just make sure that you always turn on all your Midi devices. Once I forgot to turn on my XTouch Compact and the ports were out in Metaserver. I think the ports are assigned numerically, so if you don't start a midi device, that messes up the assignments. This is in Windows 7 like you.

Thank you. That may have something to do with it. I use a lot of ports via USB. 4 MidiTimepieces networked for 32 midi in/out ports, (Windows 7 "sees" that as 2 usb banks of 16). Maschine, Kore, Tascam audio, IconPro controller, so maybe that is the issue. Everything is usually turned on and off in proper sequence, so I'll keep a closer watch next time it does this.
 
Top Bottom