Hi Blokas, Great release of great product! Thanks! Question: Will the editor protocol (SysEx I presume) be documented? Does the device respond to these messages on other ports then USB 5? Cheers! PS I’m one of the ‘super early bird’ customers

Hey! Thank you! The communication is currently in SysEx, the 5th reserved USB port is used entirely for the communication, the other 4 ports are used only for musical data. We will be looking at using COM / CDC instead for communication, this way the programming MIDI port won’t appear in audio sof…

Hi @Giedrius , Thanks for your reply. Because of so many possible gear setups, I’m into automating (scripting) a lot of it, and Midihub could play a crucial role in that. I was hoping for a public SysEx description, like the iConnectMIDI4+ (which is indeed controlled by SysEx). Would another solut…

Hello, I just started playing with the editor before considering buying the Midihub. As @Joris I’m considering automation and an open protocol through sysex would be very convenient. I understand your point about the potential confusion of having that additional control midi port. But maybe it i…

Hi @Giedrius , Please keep your SysEx approach, not only because of automation, but also because I foresee that using COM /CDC means that Midihub needs to be connected directly to a computer, and no other system like iConnectMDID4+ can sit in-between, right? I would like to have Midihub work on the…

Thank you! :slight_smile: A composite device can still be class compliant in all interfaces it provides, I have already tried this out on a couple of phones, they see Midihub correctly, and not having the 5th MIDI port, dedicated for communication with the editor, should provide for a smoother user…

Hi @Giedrius , So you are saying that Midihub would work & be editable via your software when I have it connected via a iConnectMIDI4+ host port? Are you sure? My understanding is that anything besides class compliant MIDI will be terminated there and then. This is also what one typically sees with …

A USB device can have multiple interfaces and still be class compliant. Yes, I’m aware of that. … it seems iConnectMIDI4+ is misbehaving being a USB hub then. It is not misbehaving, it is by design as it IS not a USB hub, but more a MIDI router that works in DAW-less setups, and as such hosts…

my personal opinion… although I generally don’t like, closed protocols, I agree supporting an api can be a drain on development resources - so, even though I’m a developer, I’m with @Giedrius , its much better concentrating dev effort on editor which 99% of users are going to use. perhaps a compr…

[image] thetechnobear: another alternative, perhaps later - open source the editor and firmware of midihub? For me the most important part of that is to be able to have support on futur OS even if MidiHub is no more supported by Blokas. I still have my Nord Modular G1 :wink:

Documentation of Editor Protocol

Midihub Support

Giedrius October 25, 2019, 6:25am 8

A USB device can have multiple interfaces and still be class compliant. I don’t think it’s the issue of the devices connected to iConnectMIDI4+, rather it seems iConnectMIDI4+ is misbehaving being a USB hub then.

MIDI only (SysEx) Editor, no USB

Topic		Replies	Views
MIDI only (SysEx) Editor, no USB Feature Requests	7	1175	September 10, 2021
CC to Sysex transformer Feature Requests	29	1518	July 16, 2025
Human readable (editable) file format Feature Requests	14	813	January 27, 2025
Very simple sysex pipe Midihub	11	2053	April 16, 2022
Midihub Docs Midihub	9	1259	April 8, 2024
Open up the Midihub editor for public contributions Feature Requests	7	195	August 15, 2025
[Pipe Request] Open sourcing the pipe sdk Feature Requests	14	1091	September 3, 2025
Midihub needs SysEx, Variables and Logic Structures Feature Requests	15	1383	September 16, 2025
Transform - Midihub Docs Midihub	12	922	April 10, 2023
SysEx feature request Feature Requests	1	95	October 31, 2024

Documentation of Editor Protocol

Related topics