Just kidding – let’s keep it constructive!
Hi and welcome to the thread intended for MIDI Maestro App Beta testers – it’s about time we all got together to talk!
I’ve been having an offline conversation with the Singular guys about (my humble opinion on) what the Maestro has right, what it has wrong, and what it needs to live up to the name and the hype. They’ve been really receptive to my ongoing bitching (it’s kind of my superpower), so now I’m going to share my thoughts here.
And I hope you’ll do the same.
Okay, first, what you already know:
PRO: The MM app supports coding commands and then assigning them – and calling them – by natural language names. So you can build a command that starts the Aeros recording, call it “Start Recording,” and then stack that code onto a command stack on a given switch just by adding the English command, “Start Recording.” Commands are reusable and are part of a library. This is brilliant
PRO: The hardware is “vintage-Apple” spectacular, as good as or better than anything else out there.
CON: There doesn’t seem to be a facility to import command libraries – which is something I’m sure I heard SS talk about at one point.
BIGGEST CON: The MM app ONLY does CCs, nothing else. So it will in no way be of interest the rest of the (non-SS) MIDI world, much less resolve all of my use cases.
Okay, here is a digest of the rest of my thoughts…
If I was directing traffic for the market (not for me, my needs would want a different order of execution), I’d want:
-
Program changes: This is the basic building block of ALL MIDI pedals. Without it, the pedal is a glorified outboard switch for the SS products, and will never catch on outside of our group.
-
12-16 commands per preset on both step and release: The best pedals do more. The MM should be (and really could be) among the best pedals out there.
-
Sequences: The ability to define a list of commands, and then have the programming step through them when you press a given button. That’s going to require some level of persistence in the programming, I suspect.
-
Notes: You gotta be able to send notes, right? I would suggest start with sending a Note-On on press and a Note-Off (Or Note-x Velocity=0, which is what the BB does right now) on release. It’s simple and flexible, it’s not uncommon, and it’s probably the easiest thing to implement, so it’s relatively low-investment and high return.
-
Command Library Import: If the app supported importing command lists, SS and us users could create/market/share command/control packages for other products, fulfilling the promise they made when they said the MM would come with commands for other products included.
Okay, let’s get a discussion going…