I’m having trouble getting this version to run on my patchbox, I execute the appimage and nothing happens
What output do you get if you start it from a Terminal?
fuse: failed to exec fusermount: Permission denied
Cannot mount AppImage, please check your FUSE setup.
You might still be able to extract the contents of this AppImage
if you run it with the --appimage-extract option.
See FUSE · AppImage/AppImageKit Wiki · GitHub
for more information
open dir error: No such file or directory
I found a workaround by using this command line (I changed the AppImage name to just be MidiHub.AppImage)
./MidiHub*.AppImage --appimage-extract-and-run
1 Like
Hi,
I just updated to 1.15.3 (windows) and noticed a bug right away. When bluetooth is enabled, the editor is unable to connect to midihub. After pressing the connect button, the “Looking for Midihub devices” popup stays blank.
However, once I disable bluetooth Midihub connects fine. Don’t know if it helps, but here’s the log file:
mh.log (27.8 KB)
This is not an Editor bug, but rather a Windows issue, see here for how to get it fixed: Can't connect to midi hub - #28 by Giedrius - you should reassign the COM port numbers of Midihub or your Bluetooth device(s), so they don’t overlap each other.
I´ve updated to 1.15.3, unfortunately I did not backup before and MH was hanging on 99% while it was playing back the presets…a total noobs fault.
To my big surprise it also has destroyed my aconnect settings (that were managed by amidiminder on my RPI zero)
amidiminder rules is still undamaged.
Can I find parts of the presets anywhere on my RPI or inside the MH?
and how to connect the Synths again like before as it was written in the amidiminder rules?
The backups are made just before doing the firmware upgrade automatically, the locations are:
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)
Yours should be under the Linux one. If there’s any trouble importing the latest one, PM me the file, I’ll take a look.
How did your rules look like? What in particular is not working anymore? It might be enough to restore the memory backup to Midihub.
1 Like
big thx for your immediate help, everything fine again: Found the backup and did some reboots…
Great design to have an automatic backup before updating 
Now I will look further for the issue that caused my uncontrolled update behaviour for the MH: I have a preset that is sending a START to MIDI DIN in a recurring interval, also loading this preset (with no external Clock running) sends this start command (and every START/STOP is filtered on that port !)…very strange
1 Like
If you think the preset is misbehaving after the update, feel free to post it here or via PM so we can investigate. 
Thx a lot, I´ve found the faulty egg in one pipeline at last 