All I need is a pipe with plain text so I can put notes anywhere in the patch as my patches are quite complex so I can remember what is going on when I go back to editing after a while. It would also be very nice to set a different color for this pipe for better organization.
@Marek Iāll second that - what Iād call an Info pipe. Iād guess that while the info would sit in the file, the Editor would not send it to the device.
btw, When this was discussed before, another user pointed out that while there is a limit of the description length, they build patches out of appended patch āmodulesā each of which has its own description notes.
(Iād still like to litter my pipelines with info pipes though!)
welcome to the forum.
I almost always work with the presets inside the device so it wouldnāt make much sense if those text pipes couldnāt be stored internally. This type of āinfo pipeā must be pretty easy to implement.
Yeah, simple enough to implement, Iād have thought (a bit like a custom label) but given each pipe only uses 11bytes (and each mapping 10), & still midihub has a ceiling of 128pipes/patch, my guess is it tries to be pretty concise with data.
Itās actually 255. Indeed, we try to save as much memory as possible, but implementing info/comment sections should be possible too, weāll get around to it at some point.
Hi. Using MIDI to change Virtual Pipe source, I think I snip off some Note OFF messages.
I want to be able to slip in an extra Note OFF somehow, without the hardware buttin (which is cool), like just before a change via mapping.
Its a long shot and you have priorities. Hopefully you are a gardener?
Thanks.
Is it possible to add the ability to map a midi CC to Preset in Scale remap so the scale can be changed remotely?
I am hoping to use Arp and SCRemap pipes to add quantised midi arp capability to Digitone and Syntakt midi tracks and would like to be able to control and P-Lock the scale thatās being used.
Any update about this? Itās very simply done in Max. You run clock into the hot inlet of a [onebang] and use note-ons to load the cold. It only fires when itās been loaded.
Yes, I would really like this as well. Patches can become quite complicated and not having a way to just throw in labeled blocks and notes is almost like having a programming language without the possibility to make comments.
Yes, several users have returned to this request since
Last time,
made it sound like itās not that high on the development agenda!
The big difference, of couse between Midihub and scripting on a computer is that the hub seems to have strict limits on size of files (255 x 11 bytes for the pipes, 1024 chars for the Description, 32 x 30 chars for the Labels, etc). So my guess is if/when it happens, the characters per Info Pipe would be limited/ borrow from the Description bytes/share some discrete block after the Description bytes.
Personally, Iād still welcome it!
Swing & Groove!
I was thinking about this (I agree it should be within the realms of āeasily possibleā & would likely be popular) and it got me on to something related which might be more than a little trickier, namely swing.
- My guess is itās more difficult cos Midhub needs to know where āthe Oneā is.
- And, maybe, (cos Midihub likes to be as general as possible) what time signature
- But the mappable rhythmic modulation potential there starts to get quite exciting, I think.
So where Iām going with this is:
- Quantise hard to the beat, in the simplest case
- Have variable Quantisation Strength
- Vary offset from the beat for a given beat pattern (ie. Swing on Steroids)
Ultimately, Iād dream of a Midihub version of this*:
Where Timing, Gatetime and Velocity can all modified differently according to which beat the āsequenceā is on.
A lot more complex, but with Mapping, some crazy potential - welcome to the (Individual) Beat Variation Pipe!
*this is a blast from the past: Yamahaās QY700! But that wasnāt variable in real-timeā¦
a simple quantization scheme would be very helpful for the time being. Iāve got a friend who would be very interested in purchasing one of these if it had one, but Iām about to build them one with teensy since this canāt.
Edit: sorry if this is harsh, Iām just being real. I very much appreciate my midihub, but I think itās wild that it still canāt rhythmic quantize against a clock given how long this feature request has sat in this thread.

Edit: sorry if this is harsh, Iām just being real. I very much appreciate my midihub, but I think itās wild that it still canāt rhythmic quantize against a clock given how long this feature request has sat in this thread.
@vvilms Yeah, I hear you. Maybe in the next major update. (Personally, Iām looking forward to scaleable mappings which has also been on the agenda awhileā¦)
In the meantime, Lucky your mate has got you and Teensyā¦(They should still get a Midihub though, eh? )
(As for my extension ideas - Iām just dreaming of further into the future, hoping it might catch an eye at Blokasā¦)
Velocity mapping would be great so itās possible to manipulate it as any other CC message.
Also functionality to hold the velocity value, i.e. ignoring āVelocity = 0ā, so just holding the last velocity before velocity was set to zero.
For modular synths this would be great, then velocity could be used as a fixed CV parameter for the full duration of a note and not go down to zero during the release section of the envelope.
Also +1 for Delay, but also make the delay available in milliseconds as well as related to the beat.
This is a functionality I want also for the current delay function.

Velocity mapping would be great so itās possible to manipulate it as any other CC message.
Also functionality to hold the velocity value, i.e. ignoring āVelocity = 0ā, so just holding the last velocity before velocity was set to zero.
For modular synths this would be great, then velocity could be used as a fixed CV parameter for the full duration of a note and not go down to zero during the release section of the envelope.
You could use Transform to convert Note Onās velocity to CC and get it converted to CV, or just drop Note Off messages to never set it to 0.
I also second that ( and Iāve read the comments below, they all make sense)
11 bytes is a very short comment, but could be enough sometimes. I believe it is also valuable to insert a comment like āSee note A1ā in a specific pipe).
As it is pretty quick* to implement (I guess just a new filter, that behaves like it is always bypassed), and painless on the processing side, only the editor needs to be upgraded. And in that case it would be possible (if necessary for longer comments) to make the edit aggregate consecutive comments in the āfilter parametersā window.
* I understand coding is not just as simple as āOh this is nice idea, it will be quick and easyā
The work that has been done so far is still amazing, and I really appreciate how the MH has improved my setup.
Iād love some way to do this (vel remap) with the release (noteoff) velocity
know is something most people donāt have (my very cheap roland a500pro sends it) and so it would be quite a lonely requestā¦
but to me would just be awesome to remap that to the decay or reverb length params in my synth and get some āvariable-per noteā poly sustain, for that staccato/legato classy way
Midihub doesnāt read it right? didnāt seem like it just by reading the pipes and context but maybe I missed it, very new to this, gotta see again
You can use the Transform pipe to convert Note Off velocity into some CC.
Okay thanks, got it working, starts looking easier to figure out the howās with the hub.
Also had to filter out note-ons before the transform and invert the range of the cc
I think itās still doing something weird like the dispatcher is sending the notes-on and the offs to separate channels, getting some stuck notes, I have to check that on a midi monitor
You may post your preset in a new topic. Make sure the dispatcher pipe is receiving both the Note On and Note Off events, so it can operate correctly.