This may have been covered before but I still could not find a solution. I have the Metagrid X / Y Pads set up to control the X/Y Pads in U-He Zebra and Native Instruments Thrill, Mystery, ETC. I have assigned the CC Data that corresponds to each VI and it works fine but It only records CC Data, not the track automation that is written when you move the the X/Y grid with the mouse. Is there any way to have the Meta Grid work in that manor so when you move it, it controls it on automation data and not CC Data?
Basically MGP grid with MIDI actions send MIDI messages on Metasystem MIDI port and these should be recorded on your tracks if you have this port enabled in All MIDI column as illustrated. Let me know if it is the case in your setup.
Thanks for the response on this. I have checked my settings and they are the same as you have listed. Im still having the same issue that when I enable r/w on a VI track and then move the x/y point. It only gets recorded as midi data via metagrid and not automation data. If I move the x/y point with the mouse the automation will record. I know I can covert the cc data to automation data but it would be great to just be able to have it record as automation data. Ive attached a screen shot and a link to a video to better explain.
Hi @LCub10M , this is a Cubase limitation not a MGP one, i.e. the only solution is to have Cubase convert c data to automation. An alternative could be to use Focus Quick Controls; this will be recorded as automation and you cold make a MIDI Remote or a generic Remote that assign the CC sent by the XY Pads to focus quick controls and then you could assign this to focus quick controls in U-He Zebra or Kontakt
Thanks for the response. I thought it may be a Cubase thing. I’ll try your recomendations with a custom Midi or Generic remote and re routing the CC data… It would be great if this could be somehow implemented in Metagrid but I see why this would be a Cubase limitation.
