Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

offtopic but related idea: hackey-machines2 for hardware machines midi mappings #17

Open
michaelsjackson opened this issue Mar 6, 2019 · 4 comments

Comments

@michaelsjackson
Copy link

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.

PARMLEARN 0 19376 1 for your VST(i) parameter
-- the 0 is the parameter number
-- the 19376 is the CC number and message type
-- the 1 is the Mode

now 19376 is 4bb0 in hexadecimal,
4b is 75 in decimal (which was the CC# that I Learned),
Let's say that I want to change it to CC# 72,
72 in decimal is 48 in hexadecimal,
So the full hexadecimal number is 48b0,
48b0 in hexadecimal is 18608 in decimal.

FXID {...
<PARMENV...

PARMLEARN 4 2960 0
WAK 0
BYPASS 0 0

@JoepVanlier
Copy link
Owner

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. :)

@michaelsjackson
Copy link
Author

michaelsjackson commented Mar 7, 2019

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

@michaelsjackson
Copy link
Author

Auswahl_404
Menü_405

@michaelsjackson
Copy link
Author

This is how my Catia looks after connecting 4 midi devices, machines2 could look similarly, but using as target objects fx-parameters.
Auswahl_407

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants