Here’s a minor update for Midihub, featuring majorly upgraded Clock pipe:
From now on, it can be placed either as the leftmost pipe or inline with the others. That means the Use … Port parameters are no longer necessary, as you may simply provide (or even map) the start, continue & stop to the Clock pipe placed inline.
It also has a Tap Tempo button now that can be clicked either within the Editor or mapped to MIDI CCs (only the highest value 127 works for triggering) or Note On & Note Off. As well as Nudge Up and Nudge Down buttons for reaching equilibrium with external tempo.
This release also contains some additional fixes, detailed below.
Clock Pipe in 1.14.1 Mac High Sierra ,lacks now of “Use Midi” option,how to control START/STOP?
i tried to insert it after input port but does not work
Yes, the betas are not announced within the Editor, we first release the updates on our forum, and once some time passes without anyone raising any newly introduced issues, we’ll push the update out through all the usual channels.
it works,
i was doing it wrong way by draging CLOCK pipe from existing pipeline
it needs to be “fresh” Clock pipe since it seems it does not convert it self upon draging
maybe it could be implemented in the future,cause otherwise if i have long pipeline i have to build all over
yes, from Deluge connected over USB, distributing CLK via virtual port. so I put an inline clock next to this virtual and receive clock. Meanwhile solved…the BPM I can read in the Monitor so far, so good.
What if switch of the source aka deluge and want to make the internal clock continue with that “learned” BPM?
edit: I switch of “started” and so its getting the clock from the left, but there is no clock that goes out !?
When I was doing 1.14 testing, I had occasion to take one MH back to FW1.13.2
“Un-updating” is a bit more fiddly than updating, though, so it’s not something I’d do for fun!
Thanks for the hint with firmware upgrade, I have to modify all my transform pipes again (after adapting them with the new editor on the old firmware)
Lot´s of work but I am up to date now…
That’s not been my experience; all my old Transforms have updated quite gracefully.
re
I will test the new features to the limits
That would be great:
I realised I don’t have the understanding to properly roadtest the new Clock features for live/improv use, so I’m looking forward to feedback from other users who have been hoping for Tap Tempo and the like.
(calling @Seth, @jazzboxuz, @FallingWaterSound , et al – Sorry, @Honken; Midihub’s not ready for Sysex-driven Tap Tempo quite yet!)
Could you please provide me with your presets / memory dumps prior to the upgrade? (personal message is fine) The Transform pipes are supposed to seamlessly upgrade, it shouldn’t require any manual patch up.
You can find the memory dump backups, done at the time you did a firmware upgrade, all named similarly to Midihub Backup 2023.12.27 14.52.43.mhd at these locations:
Linux: ~/.local/share/Blokas/Midihub Editor/
macOS: ~/Library/Application\ Support/Blokas/midihub-editor/ (Paste this into Finder → Go → Go to Folder)
Windows: %LOCALAPPDATA%\Blokas\Midihub Editor/ (Paste this into Start → Run)
I’ve looked into the Transform pipes of Midihub Backup 2023.12.29 11.52.07.mhd of the first Preset (the others don’t contain any it seems), however, I didn’t notice anything going wrong in upgrading them from 1.13.4 to 1.14.1.
Btw, this file seemed to indicate it was produced by an earlier version than 1.14.0, most likely 1.13.4 version of the editor, did you do an offline upgrade using .bfw?
Could you let me know what sort of Transform pipes you had to replace? Did it have wrong arguments?
