Right now it's very hard to figure out if and how an external MIDI signal is affecting the bluebox. To figure out what a certain knob on a MIDI controller does, one has to cycle through a lot of views to find the mapped target while changing the value constantly to see the change. It would be very helpful if there was a list view in the bluebox which contains every existing mapping. This could be a good foundation to implement additional features in the future as well (ie. editing the affected range or deleting a mapping)
Announcement
Collapse
No announcement yet.
A list of all MIDI mappings.
Collapse
X
-
Originally posted by matthast View PostI agree, a default Midi Implementation Chart would be super helpful if included in the updated manual.
What I mean is a list of things I mapped as a user. Sometimes it's not easy to remember the mappings I did some time ago if I don't use them constantly. Using labels on a controller helps but they can be easily wrong (outdated) or damaged or get lost.
Comment
-
0101-Usr, I guess what Klaustrophil means, if I may reformulate, is that the BB has MIDI learn, which means there are no hard coded MIDI CCs to list in an implementation chart.
However a list of what can be mapped could indeed be helpful.
On my side, I would love to see a repository with projects that include MIDI mappings, and if someday 1010music could decouple PSET and midi mapping files as one may want to import a MIDI mapping made for another project.
EDIT : BTW, just posted a new idea in the wishlist for that project/MIDI mapping decoupling here :
This works for both the Blackbox and the Bluebox or any other hardware with MIDI learn, but I post it in the Blackbox wishlist as I believe it is the most needed for this product. Separate MIDI mapping from project : I believe that 1010music should decouple the MIDI mapping and the preset file (or project on the Bluebox).Last edited by jayneural; 03-17-2023, 06:42 AM.
-
Comment