Open michaelsjackson opened 5 years ago
It's a nice idea, but I really don't have time for starting and maintaining another project.
It also makes very little sense for me to do this, since I don't have interfaces I could test this with. Can try pitching it on the forums and see if someone else wants to pick it up. :)
No problem, thanks for answering. Even better would be a mixture of hackey trackey with its excel editing plus machines2 with its easy connectivity like pure data or buzz. The rectangles could have inside some excel/tracker like columns for editing or so... And the exported/imported text format could be more or less same as this tracker column view, as it is text anyway.
Its columns could be: parameter_name, note, cc, channel, min, max
This is how my Catia looks after connecting 4 midi devices, machines2 could look similarly, but using as target objects fx-parameters.
Just had this idea and wanted to share quickly here, so it is not forgotten.
As Reaper has still no powerful midi mapping management system, one way could be something like hackey machines, let us call it here machines2, where each box/machine would represent a hardware interface you have. Those would be our hardware-sources. They would be connected to other rectangles/objects which would represent fx, or simpler, directly fx parameters, and you would connect them freely. A connection would create a midi mapping and you could specify its values. Then export/import all setup in some text format would finish this idea.
The beautiness of this approach: First you just add all your hardware interfaces you have. They need to be learned once, so the system knows to which events to react. Adding parameter rectangles via 'add last touched parameter' would be just perfect. Or better add and connect last touched parameter to selected hardware-source.
Btw. I know which format midi mappings need, let me look it up quickly.
FXID {... <PARMENV...