Love the gadget, not too keen on the editor

I find the editor really opaque to use. If I contrast its design with the layout of the display panel on the Line 6 Helix Rack, the latter is so easy to use, the eye can sweep once from left to right and understand the entire signal flow in one go and this has numerous hardware inputs and outputs plus the potential for multiple complicated signal paths. Using the editor feels like using an old patch bay or modular synth, to understand where a signal is going, you have to follow each wire and see what the socket is labelled and then build up the signal path in your mind each time. Today, I wanted to process each of the 16 channels differently, so this requires me setting up a vertical column of 16 individual filter blocks between in and outs and if I want to start sending them off to other places it’s going to require loads of vertical scrolling and scribbling of notes to keep track of what goes where. And that would be just for input A to output A. To my mind, signals flow from left to right, ‘in’ is on the left, ‘out’ is on the right. It would be great if we could connect stuff with magnetic lines that can be defined like the filters, transformers etc, like Audio Midi Setup on the Mac.

I noticed the word ‘argument’ in the CC transformer section, I’m assuming this is a mathematical or engineering term, I looked it up but couldn’t find anything, I’m only a guitarist so I just fiddled around until it did what I wanted. If it means ‘number’ that would be clearer for dopey guitarists like me.

The editor has a pane called ‘description’ this has remained resolutely blank so far, there’s a lot going on in the editor window, could this area be better used? There are two buttons below that are marked ‘view’ and ‘edit’ that haven’t done anything useful so far.

Could there be key commands for the different presets? Many users might be unaware that they can be assigned in the Mac system prefs.

As I said, I LOVE this gadget, it is going to solve all my MIDI woes but the editor feels like it has been designed by someone with very large side burns and a substantial collection of oscilloscopes at home. I’m not trying to be a dick but the editor could put people off, I reckon.

1 Like

Hey, thank you for the feedback. :slight_smile: We plan to make some improvements for easier understanding of what the presets do, like in-place comment sections and port naming.

It’s a constant value (variable if it’s MIDI mapped) you could choose to use in the resulting transformed message, if it’s selected to be used via [Value for Byte n] properties (the name of this selector property is context specific, like ‘Set CC Number To’).

On Description - it’s a place for documenting your preset for your own future reference, or if you intend to share it with others, sort of like a Read Me file. You can edit it while in the ‘Edit’ tab, it uses Markdown syntax for formatting, the View tab shows the formatted contents. You may turn that widget off using View->Description option (or F2 key).

Could you share a list of suggested hotkeys to access the presets that you’d find convenient? :slight_smile:

Barber shops were closed in these quarantine times! :smiley:


I just assigned command 1, command 2 etc but it made all the presets look like the same pipe combination, possibly the last one I was working on. I haven’t tested whether they all now function the same too.

If you assigned the ‘Store’ actions, then the currently open preset would overwrite the slots. To switch to another stored preset, create hotkeys for the Load actions.

I see the problem now, the menu entries (Preset x) in ‘store’ and ‘load’ are identical so the system can’t distinguish. I have run into this very problem with Guitar Pro too.

1 Like

@Giedrius one type of visualisation I’d love to have is some kind of graph, I’m using my Midihub as a router and the different presets route different channels from different INs to some virtuals that then merge to some of the OUTs, I’d love to have a graph representation of the flow MIDI A/B/C/D -> virtual A/B/C/D -> OUT without having to peek through each MIDI -> virt to see if I set the correct channels/inputs. Had quite a few bugs on my custom presets because I missed changing a property here and there due to the columnised visualisation.


I agree. Currently it’s hard to get a workflow going. It’s not engaging. I think “ugh” when opening the editor. I wish I could think “great now let’s do this”. The gadget allows me to achieve what I plan to do, but actually using it feels like playing a game of mikado with a box of spaghetti. COOKED spaghetti. Anyway, thank you for your hard work!


Although some of the comments and suggestions are interesting and I’m sure the MIDIhub editor can be improved, to me, the editor as it is currently implemented looks clean, neat, well presented both visually and functionally, and is easy to understand. In addition, it works great in Linux, for which I’m grateful.