Hey guys! What better way to celebrate Midihub’s 6th birthday than with an awesome new software update!? This time we bring you the means to write out your comments within the Preset, as well as extended mapping modes and ranges for even more versatility and fine tuning your audio setup with milliseconds based Sync Delay Ms!
Many thanks to @resonotter for his invaluable feedback on the new features!
Hi, yes it is the x64 appimage version 1.16.0. The previous I have is v 1.15.3 and it runs perfectly on ubuntu 24.04
Still getting this issue with libssl1.1 installed: /lib/x86_64-linux-gnu/libcrypto.so.1.1: version OPENSSL_1_1_1’ not found`
The same here with Ubuntu 24.04.2 LTS.
1.15.3 runs perfecly. With the x64 build of 1.16.0 I am getting this error message:
/tmp/.mount_MidihupBu35S/usr/bin/midihub-editor: error while loading shared libraries: libcrypto.so.1.1: cannot open shared object file: No such file or directory
Hello There, i’ve run into a delicate problem. Somehow i created a pipeline where i both have a CC-table as a generator (yellow indication) and an input - in the same fucking pipeline, not logical, can’t compute, massive error!!!
The problem this has created is, that every time i try to delete that CC-table, my midihub editor crashes, and it cannot complete the deleting process. I own 2 midihubs and i like to share presets between them, but anytime i try to open the save file for this particular preset, midihub editor crashes and both my midihub devices fails to recognize the preset.
I programmed quite extensively on a sequencer patch with a lot of mappings and i reallllyyy would hate it, if i had to redo all my programming because of this.. any suggestions?
Issue reproduced on another Mac running Mac OS 10.12. (with fresh install of Editor1.16.0)
Not an issue with Editor1.15 on these machines
Not an issue with Editor1.16 on Sequoia
It’s around 1020 bytes, depending on how many comments there are. The remaining space is shown in the status bar at the bottom while a comment is being edited.
Thank you for the quick response. Completely missed the information in the status bar.
I did experience the limitation while I was editing, because of the input that was blocked. Also some unexpected behavior when copy / pasting an existing comment; it did paste to a blank comment field, but seems to delete characters from following comment fields.