Hey guys! We’re wrapping up the 1.14 Beta with a Public 1.15 release! You may find an overview of everything that’s happened since the last public release in our blog post.
Congrats again since it’s official now! Midihub is essential for reimagining my old and new midi hardware, it does things I never would have thinked of…
First of all: congratulations for this update, friends!!
Unfortunately I have not yet been able to make it run.
I open the Editor — it recognizes my four MidiHub units — but then it gives me an error when I try to connect any of them.
Most likely something related to having multiple units, I guess?
It was working nicely until yesterday.
Already tried with and without USB hub, nothing changed.
I’ll appreciate any clue.
This is kind of by design - the Arguments 1 and 2 have the range 0 - 127, the Channel have the range 1-16, so the values must be linearly remapped between the ranges. Consider having mapped a CC knob to one of the Argument parameters, it would be quite difficult to select a channel only with CC values 0-15, with values 16-127 being a ‘dead zone’ for the highest channel.
That’s why there’s an additional “Channel Argument” that has the range 1-16 that is naturally useful for ‘Set Channel To’ property. If the Ch. Argument is used for one of the data bytes that have the full 0-127 range, it also gets automatically rescaled from 1-16.
It’s best to perform the firmware upgrades for each unit one by one. Keep the rest powered off or disconnected until all of the units are on 1.15.0 firmware.
I’ll send you a PM with some further troubleshooting instructions.
This was solved via PMs, it was caused by an early internal alpha test build, so it shouldn’t affect other users but if anyone hits any issues, do let us know.
when i enter TO MIDI OT#1 pipe (selected in the screenshot), go to EDIT button from PROPERTIES window,then i press ok,
and then when i want to change DESTINATION in TO MIDI OT#2 pipe ( one just below OT#1 selected in the screeenshot) it crashes.