Actually all these below can be applied to any kind of midi controller
For me I am using the controller to send out command to 2 devices only, Empress ZOIA & Source Audio Reflex foot controller. But I have already fed up with everything I need to do.
It is true that when the device comes more generic, more work have to be done to achieve something, even it is very simple.
But the app really gives me more and more work to do.
So please concentrate on how to reduce user workload when they want to achieve something. For me, assigning just 10 PC commands costs me 20~30mins, I think.
I have to assign 10-times sperately, field by field, for every similar patches/commands. So please consider letting us simply config those command by just a csv file
6 commands x10 pages is far less than enough, for even a single device.
Crash when Browsing custom mode
Avoid duplication when downloading custom command/mode
Unable to delete the command
Difficult to rearrange the position of the command
The below points are related to how we share those custom command. There should be a better organised custom command list.
It is like how you are going to manage a database / something like MIDI 2.0 principle.
7. How do you sort out the same command uploaded by different users, for example, they are using different channel for the same device?
8. How do you handle, when different users upload the same command for the same device, but they a using a “DIFFERENT NAME” aka Beatbuddy & BEATBUDDY?
9. How do you cope with, when the target device is also genericly designed for user defined command/preset eg. Empress ZOIA % other multi effects? (Unlike there is already a defined Command mapping like Beatbuddy)
10. How do we/you verify whether the command provided by user is correct or not?
The idea is good, but when it comes to practical, everything mess up.
Hopes you will improve the situation.
I would like to know when Singular Sound is going to fulfill their promise to make midi maestro work with Aeros. We keep being told is in development. I hate to go back to old ground but, when I first saw these products I was really jacked up and bought all three of them. Midi maestro is useless for anything but Beat buddy. The ad showed the ability to use it for those two products exclusively. But now we’re told you’re working on it. Pretty much false advertising to begin with. I’ve tried to be patient but I think you should take these back if they will not work. I can use my BeatBuddy without the maestro I can use Aeros without the maestro. I paid good money to get all three of your products at one time. Knouff said I’m tired of talking about it
we’re looking into making this easier – maybe not exactly a csv, but a quicker way to do things.
6 commands is not quite it. It’s 6 buttons, with up to 8 commands per state, and up to 2 states (so you can toggle)… so about 96 commands per page. We’re increasing the amount of commands you can send per state dramatically in an upgrade coming before the end of the month. In any case, is there any suggestion as to how the availability should go? we may be able to accommodate different needs.
This crash is being addressed for the aforementioned release.
We’re working on this, too.
This has been addressed in the aforementioned release.
This also is being addressed - some fixes in the mentioned release, some forthcoming soon.
is also being addressed - coming soon
Not great, we’re bringing up a solution to this in the near future, part of it will involve normalizing existing data
Not great, either. This is also something that is coming in “the near future”. Like 8, it’s not this month.
By trying it, we’re not doing QA in shared commands at the moment. We are planning to address this “in the near future”. Like 8 and 9.
Thx for your reply and it must be plenty of stuff for the developer to be done
For the page and numbers of commands we can assign, I come up with this just because, like Beatbuddy, it has already occupied couple of pages, so it is not enough for more and more devices/software.
For generic midi device/software that user can assign any command as they wish, I think it is difficult to cope with, even with you established a shared library, since everybody use case is not the same. Pt 7~10 are really out of the scope for you guys, just like every command for every device have its own fingerprint…maybe this is what MIDI 2.0 is doing. But who to verify? Manufacture themselves? How they update the whole list? How they sync to every device. (sorry for bs)
The idea of sending multiple command in a single press is good but…I cant think how it could be used by user, maybe they have a part of song that need this, maybe they are sending a chord to the sampler.
(May be as user is not necessary to press 2 buttons to send multiple commands, please consider to let us config press 2 button…for next page. This can save some space on the pedal board for the ext switch
Anyway for any midi device. It is painful for user to
Make sure what they really want to do
Set up the device themselves
Assign the functionality of each button, one by one
After having a conversation with the dev on your reply, here’s what we can say:
We think, as we keep evolving the device’s capabilities, use cases will evolve, too. We can even visualize the MM having more than one custom mode at the same time, and switching among them. So you could have different setups for different parts of your set, for instance. The world is our oyster, in a sense (A memory-limited, input-limited, situation-specific, multi-layered but manageable oyster.)
We expect the capabilities for the MM to keep evolving, and people will use it differently! Making the tool’s niche come into better focus, directing our updates from there.
One use-case for several commands at the same time is being able to change page on a music score or lead sheet while triggering a BB transition, for instance
To quote one member of dev team:
“I feel in my bones the vision is still taking shape and that possibilities are endless”
I have some ideas after using the Ios betha app for a better user experience:
The utily to assign the midi channel to a device.
Organize the (user defined) controls in device categories.
So in the app you could have the list of devices u use and the accesory commands.
When u want to assign a button to a control you only have to choose your device (midi chanel) and scrol through the list of control commands.
At this time the app is barely useable, to much trial and error…
Need to backup custom settings. My Android tablet crashed, had to get a new one. Lost all the custom settings I had created on the old tablet.
Is there a way to download them from the MM?
Can SS just get rid of the default modes on the MM and just make them available for download if anyone wants them? Three custom modes on the MM is definitely a lot more useful specially if users are not interested with just the AEROS or Beatbuddy mode. I have all three devices but I still use a custom mode.
We’ve toyed with this idea and may do it eventually but first things first is v2.0.0, it should not be a lot of work after that to make this doable, but it is not our priority at this time.
Does anyone have experience with combining Ableton, Beat Buddy and Maestro? How does it work? My goal is to have an easy drum machine for performance or jamming and to be able to move around in scenes and clips in Ableton. Thanks.
JUST DO IT !