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.