Looking forward to trying the new features out!
I use my Midihub in such a simplistic manner compared to what I could do with it. still very happy with this little box though!
The Midihub is such an essential bit of kit for me, itâs like the nervous system that makes my whole setup work. Makes all the basic MIDI headaches trivial and allows for so much flexibility.
Iâm still waiting for the ability to do annotation/colouring/grouping of individual sections though, thatâs really my only complaint. Still, once you have everything set up the box just works and you donât need to worry about that.
Does anyone know a place in Berlin that sells the Midihub? I would like to order one, but i dont have paypal/credit cardâŚ
I donât think so. Couldnât you just ask a friend with PayPal account to order?
They actually answered me and told me it is possible to pay via bank transfer 
Just ordered one of these, need it for Midi from Ableton. I also need it to convert Midi CC to programme changes, so I can sequence scene changes on the Eyesy from the OT live. Cant wait to dig into all the other stuffâŚ
Probably a stupid question, can I upgade over midi (like an Oto Bim) using this?
Iâm already having fun with mineâŚ
Updating firmware is done via Midihub Editor, not by MIDI
the latest Editor and Midihub firmware is here
Sorry for not being clear, I wrote my post while rushing, getting ready for work. Can I update another devices firmware, i.e. Oto Machines Bim 12 bit delay, using the midi hub as a midi interface?
I donât know BIM butâŚ
If youâre just sending a MIDI stream, say sysex, through I donât see why not:
MH wonât manipulate or create sysex but it will pass it on (or filter it out where you donât want it!)
How many LFOs can it send simultaneously?
Can someone help me out?
Blokas Midihub works perfect with my TT-303 > Midihub > S1.
But once I send clock from TR8s to TT-303, the Midihub doesnât trigger its internal arps/delays to the S1 anymore.
(When I then disconnect the Midi out from TR8s to TT-303, it works again)
Must be some clock? sync? trigger setting or something?
Anyone any idea whatâs going on here?
Thanks!
ANSWER: I figured it out!
TT-303 > MIDI A > Blokas Midihub > to Virtual A = note data
TR8s > MIDI B > Blokas Midihub > to Virtual A = tempo/clock
Virtual A > Insert any kind of Filter/Modifier from the editor > MIDI A > S1
Itâs just strange that the TT-303 doesnât send tempo/clock through its own MIDI to the S1 when receiving tempo/clock, but OK, it works! 
it looks like the TT-303 only has midi in and out, not thru. midi out is usually only midi data generated by the device itself, not data it has received. so if you set it to sync to the TR-8s, itâs receiving clock from the TR-8s and not passing it along to its midi out. which is actually normal. the TT-303 may have a âsoft thruâ though, where it treats its out like a thru. youâd have to check in the manual (I donât know the device directly).
Hey, thank you for explaining.
Good to hear this is normal Midi behaviour. Kind of makes sense too.
(The TT-303 has a Midi Thru function, but it didnât do the thing I wanted to.)
Itâs also kind of logic to connect the TR8s clock to the Blokas MidiHub.
And use the internals of the MidiHub to deal with the Midi patching.
Ok, back to the MidiHub Editor, such a strange & nifty device. 
yeah sounds like youâre basically using it as a merge device, to merge clock from one device and note data from another. looks like the TR-8s doesnât have midi thru either, so itâs not like you can reverse the order and have TT-303 generate clock/transport and note data.
slightly off-topic
the amount that midi thru has been pushed to the wayside and removed from devices over the years really irks me. sure, midi thru devices exist and theyâre more efficient/less latency than data going through another machine first. but you shouldnât have to use those.
A personal observation: What I see online is a lot of âGenerative Patchesâ, those are great for Ambient, but I would rather have it repeat a set of instructions, with different time intervals and probabilities.
Not so much an endless generative random machine, more a generative sequencer and patch generator, if that makes sense. (Loopy stuff, for Techno
)
Gonna check Blokas website & Midihub Forums, maybe I just havenât found the right logic/elements yet. Maybe some of you know?
âGenerative Patchesâ abound partly cos MH makes it easy to create many notes from each message input and then use pipes like Scale Remap to make them musical.
If I was toâŚ
have it repeat a set of instructions, with different time intervals and probabilities
âŚIâd start with a Saw LFO (I use a 180° offset SawUp to go 0~127 every interval)
Then a series of Transforms to say whatâs going to happen at given steps in the cycle.
Getting it to modify itself is now more possible with Virtual Mappings.
Iâve done some stuff on this but not published it*. If you make a start, give me shout over there.
*from memory any sequence patches on MH forum donât go as far as you want.
As many as you have pipes for.
Plus LFOs can modify eachother.
Not yet had a chance to make good use of the 14-bit option that was added recently.
Hey indeed!
Yesterday I made a patch using Midi Clock > LFO > to (a free) MIDI out.
- And then use the LFOâs cc data to âMidi-learnâ and modulate the ARP bypass switch.
- And used another LFO - with a different cc & offset - to modulate the DELAY bypass switch.
So instead of random/generative modulation, you get repetitive/sequential results!
Going to have a look at the Transform node soon.
Cool, iâll keep you updated
Maybe I should post it on MH forum too.