MidiHub Editor feature request:

Midihub Feature Requests
1

I´ve at the moment been using my MidiHub for monitoring the Midi Traffic at the IN and OUT ports, to investigate possible faults within my footcontrollers (and might actually have found a bug in one). And not for any MidiHub specific situation/solution.

Editor feature request / suggestion:

  • If possible in the Midi Monitor window section. It would be really helpful to have an ability to select several ports to be monitored at the same time.
  • They could (when activated by selection in Midi Monitor setting) appear as additional 4-part columns (Timestamp, Type, Incoming (port N), Outgoing (port N).
  • Since I can resize the window sections in the Editor (as well as resizing the columns themselves within the Midi Monitor), one could use that to investigate certain issues regarding peripheral units connected into the MidiHub.
  • It can also be used to check that the programmed Pipelines actually works as intended in ‘realtime’ in regard to multiple IN and OUT ports (and channels):
    => Incoming messages at (i e) port A (and Channel N, by filter settings) =>
    => Pipelines doing its things etc =>
    => Outgoing messages at (i e) port D (and Channel N, by filter settings) =>
    => The same incoming messages at port A =>
    => Other pipelines doing other things etc =>
    => Outgoing messages at (i e) port B =>
  • Thus, I get the ability to get a little bit clearer if something might actually be odd within the peripheral units themselves. As well as checking if the pipeline programming/structure seems to function as intended.

As of today, I have to select any of each IN or OUT pipe. But as soon as I do, it also clears the Midi Monitor.

If possible, this in itself would allow the Midi Monitor within the Editor to be able to do something that I haven´t been able to do with either MidiView nor PocketMidi (midi monitoring apps).
Having an easy overview and seeing the Midi traffic at several ports at once within the same window.

2

Hey @miketheman,
I’m trying to picture how this would look/happen if the guys at Blokas decided to implement this

  • would these extra message flows be in separate panes (that would pop up and sit like the MIDI monitor pane does when you drag it out of the main window)?

  • or would they sit in the same pane with some sort of dividing line (no idea if this is technically possible!)?

  • what sort of visual link between a given (sub-)pane and its parent pipe do you envisage?

  • at present, the time-stamp start from when the pipe is selected. Would this be echoed in subsequent (sub-)panes (i.e they don’t each have individual timings)?

Presumably these extra monitors would not affect the Properties pane being focussed on the first pipe selected.
On a Mac, at present, Cmd-select does the same as select (dunno about other systems) so I guess that could be used for “Monitor Selection”



If could be done nicely, I’d use it a lot:
at the moment, I’ll often use virtuals to create flows just for side-by-side monitoring when there’s subtle stuff I need to compare in real-time (then I have to remember to simplify when I found where my mistakes are!)

3

I´m thinking that they could be in the same window but a dividing line or something. But even separate pop up window would work as well.

1 Like