joepvanlier / hackey-machines Goto Github PK

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

From the Discord:
error when loading the project
'...REAPER\Scripts\Routing tools\MachineView\MachineView.lua:1097: bad argument #1 to 'GetTrackNumSends' (MediaTrack expected)'
it wasnt intended to handle project changes was it
not sure how youd be able to check for that even

Being able to add track templates to the module menu (for reacalling whole buses and routing configurations instead of just single devices) would be cool.

Holding shift will use smaller increments on dials.

When clicking on a bus/device, selecting that channel (i.e. making that channel active in the Reaper console, so that it can be followed up with scripts that target the selected channel) would be nifty. No need to hunt in the console if working in the Buzz-like view at that moment.

Add option to hide specific tracks with a toggle to show all.

Adaptive zoom speed. Shortcuts for instant to 2x or 4x.

Add an optional grid snap.

Also, it would rock if it was possible to double click (or modifier-click) on a box representing a bus, and it didn't open the GUI of the first FX plugin on that channel, but actually another viewport done in this same style, representing the routing on that channel. Pretty much like this https://forum.cockos.com/showthread.php?t=209768 hah, maybe just add a call to MPL's script on the relevant channel for that one?

Ultimately, for a self-contained vibe in this environment, a way to call Hackey Trackey (and alternatively the standard piano roll editor) for the currently selected track / device, select/insert/rearrange MIDI items on that track, and edit them right then and there... Would wrap this up as a full-fledged Buzz frontend for Reaper . I know, I know, it's kind of a tall order, hahh. And mostly fueled by pure nostalgia.

Add two extra controls to the signal menu that allow manipulation of the source and destination channel.

Consider how to deal with multiple channels going from a single block.

Investigate whether it is possible to pass through shortcuts.

See if possible to preserve location of machine after undo.