[Download] Midihub 1.16.1 - Comments, Mappings and More!

Hey guys! What better way to celebrate Midihub’s 6th birthday than with an awesome new software update!? :glowing_star: 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! :star_struck:

Many thanks to @resonotter for his invaluable feedback on the new features!

Downloads

Detailed Changelog

1.16.1 Editor & Firmware 1.16.3

1.16.0 Editor

  • Inline Comments.
  • New MIDI Mapping options - Mode, Low, High and Drop. See MIDI Mappings for details.
  • When dragging new pipes over existing ones, they will shift away to better indicate the drop position.
  • Related port pipes will be indicated by a slim rectangle outline, so you can see the same ports and virtual buses easier.

1.16.0 Firmware

1.16.1 Firmware

  • Fixed Clock pipe’s Start, Continue, Stop and Tap Tempo parameter mapped operation.

1.16.2 Firmware

  • Fixed mappings processing for parameter updates when the control’s value stays the same since the last event.
13 Likes

Hi, I’m getting the following error with the x64 appimage on ubuntu:

error while loading shared libraries: libssl.so.1.1: cannot open shared object file: No such file or directory

libssl and libssl.so.1.1 are installed, do you have any clue?

Hey, is this on x86_64 Linux build? Did the previous version work fine?

For now, you can install libssl1.1 from the system package manager.

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`

Ok, thank you, I’ll look into it, a new build will be up on Monday.

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

Great, thank you! :heart_hands:

New Linux x86_64 build is up, the link is the same.

Let me know if this fixes the issue for you @staubi and @djenzar.

Hi, it’s working fine! Thank you for the quick heads up, much appreciated! :star_struck:

1 Like

I am travelling and can not test in the next days. @giedrius and @djenzar: Thank you for your fast reactions !

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?

We’ll figure something out, I’ll send you a PM :slight_smile:

I patched up the .mhp for now to fix it, if anyone finds a way to reproduce the issue, let me know. :slight_smile:

LFO Context help issue on ancient Mac OS

Hey @Giedrius
an odd little glitch with 1.16.0 where the Context Help pane doesn’t update when LFO is selected:

select a different pipe…

…LFO shows that pipe’s Help:

same issue after clicking on the background:

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

1 Like

Now I can also confirm that the new Linux x86_64 build is working fine :slight_smile:

1 Like

A post was merged into an existing topic: [For Beta Testers] Midihub Flasher Tool

Thanks for the update! :slight_smile: :ok_hand:
What’s the character limit on the new Comments feature?

1 Like

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.

1 Like

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.

Ok, if you have some steps on how to reproduce the issue, just let me know. :slight_smile: