|
Post by machinesworking on Dec 4, 2020 15:47:17 GMT -8
So I probably can guess, but I bought the iOS app Metagrid not knowing it used the Mackie protocol. It installs it’s own MIDI based commands, supposedly doesn’t overwrite the Raven one etc. I’m pretty certain that it’s not comparable with the Raven but I figured I would check.
|
|
|
Post by jameyz on Dec 5, 2020 12:35:15 GMT -8
So I probably can guess, but I bought the iOS app Metagrid not knowing it used the Mackie protocol. It installs it’s own MIDI based commands, supposedly doesn’t overwrite the Raven one etc. I’m pretty certain that it’s not comparable with the Raven but I figured I would check. depending on the DAW it may work. But I have never tried it.
|
|
|
Post by machinesworking on Dec 6, 2020 20:55:25 GMT -8
So I probably can guess, but I bought the iOS app Metagrid not knowing it used the Mackie protocol. It installs it’s own MIDI based commands, supposedly doesn’t overwrite the Raven one etc. I’m pretty certain that it’s not comparable with the Raven but I figured I would check. depending on the DAW it may work. But I have never tried it. So messing around with it, it's not too bad, the Raven mostly relies on existing key commands, Metagrid adds App specific CC commands. You can run the track display on your computer using Mackie Control but that IMO might conflict with the Raven, and mostly I'm going to end up using Metagrids default layout, since the Raven covers everything else.
|
|
|
Post by jameyz on Dec 7, 2020 10:41:30 GMT -8
Yeah, I hope to add MIDI control to RAVEN in the future as eventually we will run out of key commands to use.
|
|
|
Post by machinesworking on Dec 9, 2020 21:48:38 GMT -8
Yeah, I hope to add MIDI control to RAVEN in the future as eventually we will run out of key commands to use. Makes sense, I think Metagrid was cautious about key commands, with Logic they’re using a control surface bundle in that folder etc. It’s pretty cool, kind of redundant with Batch Commands though, probably use it more when I’m away from the studio.
|
|
|
Post by machinesworking on Dec 15, 2020 13:09:30 GMT -8
Just a quick reply to this since I'm bringing up direct competitors to Batch Commander and we talked about MIDI control etc.
I think Slate are doing the right thing sticking to key commands. I just found out that the CC mesages in the Commands list in DP10 get switched to ANY if Metagrid is not running, which mirrors the behavior DP has when you set the input to any in the menu. So I'm playing an MPE intrument and the Tempo pop up window keeps opening up because that's the CC Metagrid assigned to the Commands window...
Until this changes I would much prefer not to be forced into using something.. might just uninstall the Metagrid Commands and ditch it.
|
|
|
Post by jameyz on Dec 15, 2020 17:36:58 GMT -8
Just a quick reply to this since I'm bringing up direct competitors to Batch Commander and we talked about MIDI control etc. I think Slate are doing the right thing sticking to key commands. I just found out that the CC mesages in the Commands list in DP10 get switched to ANY if Metagrid is not running, which mirrors the behavior DP has when you set the input to any in the menu. So I'm playing an MPE intrument and the Tempo pop up window keeps opening up because that's the CC Metagrid assigned to the Commands window... Until this changes I would much prefer not to be forced into using something.. might just uninstall the Metagrid Commands and ditch it. yeah, troubleshooting MIDI is not fun and switches depending on the DAW. (I am stoked for MPE in Ableton 11). Bad side of key commands is for AZERTY or German keyboard have the keys all switched around.
|
|
|
Post by machinesworking on Dec 15, 2020 22:27:54 GMT -8
Just a quick reply to this since I'm bringing up direct competitors to Batch Commander and we talked about MIDI control etc. I think Slate are doing the right thing sticking to key commands. I just found out that the CC mesages in the Commands list in DP10 get switched to ANY if Metagrid is not running, which mirrors the behavior DP has when you set the input to any in the menu. So I'm playing an MPE intrument and the Tempo pop up window keeps opening up because that's the CC Metagrid assigned to the Commands window... Until this changes I would much prefer not to be forced into using something.. might just uninstall the Metagrid Commands and ditch it. yeah, troubleshooting MIDI is not fun and switches depending on the DAW. (I am stoked for MPE in Ableton 11). Bad side of key commands is for AZERTY or German keyboard have the keys all switched around. For sure, but Metagrid assigns cc74 to opening the track tempo dialogue box in DP when Metaserver isn't running. There's no penalty for using key commands with Falcon from this end. Oh and yeah it's cool to have MPE in Live for sure, now DP is the last big DAW to not have MPE... I'm certain it's coming, and all the track assigning group commands you can do in DP make it relatively painless to set up, I still want native though.
|
|