Hi
I am looking for a non computer midi processor that can function as a long delay, preferably beat quantised. For example set a delay for 10 bars at 90 bpm. From the manual I see Midi hub has a delay but it is very short. Any ideas how I can solve this problem? Can Midihub function as a long delay? The only kind of solution I can see so far is the squarp sequencers, which are a bit overkill, as I just need the one function.
cheers!
L
It is theoretically possible, but you would have to build a little bit complicated preset to extend the delay period, as well as take care of the limited amount of notes each Delay pipe can keep track of by dispatching the notes into multiple channels and merging them back again.
FYI @Leon, @Giedrius neat strategy would give you a max of 16*32 notes in a 10bar period.
That works out to be about 19 notes/sec for 0 repetitions
(I’m assuming here that your delay just means copying every Note On & Note Off and you’re not wanting to delay other message types.
How may repetitions were you thinking of?)
has a delay but it is very short
Delay goes as long as 16bars, plus you can use the Tempo Divider pipe
Hi Thx both for that info. The note limitation was a bit of a concern, but 16x 32 is enough to work with, but sounds a bit involved. I often use tempo changes but I guess that would just entail switching a patch.
Probably a silly question but I have no knowledge of this system, are rests counted as notes? Also, if I did construct this patch, would there be any room left for other processes?
Bit of background, although initially I said I only need the one function, I am interested in performing solo on a keyboard with midi processing such as Long delay, short delay, plus stuff like chord rotators, note blockers, randomisations, real time remapping etc. The delay patch functions as a kind of frippertronic looper, mimicking what I do with audio on hardware loopers like the Loupe, Zoia etc.
Btw, Midi hub looks like a great box!
No, if Clock is sent to Midihub (and routed to the Clock Div & Delay pipes), the setup will carry on quite happily.
The 32 number is related to Delay…
Each pipe remembers up to 32 notes at a time, including the velocity and length of each note.
…so that’s all that matters
The Dispatcher pipe also has constraints as it sends each new note to a new channel, meaning that when it runs out of channels it starts again so any more than 16 concurrent notes will lead to the oldest being “truncated” by a Note Off.
If you can spec this out in detail, it be fun to see what’s possible!
PS. “Cannons” is a new term for me
Good to know about clock, I thought as much.
Cannons, really cannon, musical device used in pieces like Conlon Nancarrows “Cannon’s for Ursula” or Bach’s Musical Offering.
Think i will order a hub and dive in… thx for the help!
Aaah, Canon, capiche
Thx for Nancarrow’s piece, new to me.
Don’t forget to report back on your Midihub ventures, sounds like you’re going to have a lot of fun.
chord rotators … real time remapping
There’s a pipe called Scale Remap that you’ll want to get to know.
It’s primary intention is a musical one; forcing notes into defined scale.
Unfortunately, the Preset property (ie which scale to use) is one of the very few pipe properties that isn’t mappable.
(Download the Editor and start exploring btw)
It is possible, however, to have several Scale Remap pipes and use mappings to enable & disable them…
…or to have parallel pipelines each with a Scale Remap and use mappings to choose between them.
This is not bog-standard patching, I mention it cos I suspect your creative desires will likely take you in that direction 
it can also be leveraged for other generative routing purposes
Something to be aware of when you dive in is this:
I think @Giedrius & @Pranciskus (The Blokas guys) have placed a high design priority on preventing hanging notes.
The practical upshot of this is that certain real-time changes (e.g switching a output destination or toggling a Scale Remap) will result in ‘All Notes Off’ in that pipeline for safety purposes
