The MIDI Monitor shows the MIDI events that are being processed by the currently selected pipe in real time. Filters for incoming and outgoing data can be set up to hide irrelevant events. The events may be displayed in their raw hex form, or decoded into a readable form.
A BPM field in the monitor header provides the BPM estimate based on the timing of the recent Clock messages, even if they're filtered out from display.
If the monitor is scrolled to the very bottom, it will stay at bottom and follow the new events.
Each event consists of the following fields:
|Timestamp||It is recorded when the event is being processed, based on the internal clock of Midihub, and is in millisecond accuracy.|
|Type||They type of the event. It can be one of:
Event: A regular MIDI event.
Timed: An output was generated based on time.
Mapping: A mapped parameter change caused an event to be generated.
Param Chg: The pipe parameter change caused an event to be generated.
Overflow: If there's more events occurring than the monitor can read, an overflow is recorded, and some monitor data can get dropped.
|Incoming||The incoming event data.|
|Outgoing||The outgoing processed data. If the field is empty, the event was discarded. There may be multiple events produced from a single incoming message, each event is display in its own row.|
Comments & Questions
For more tips & tricks join our community forums! 👋If you have any questions about the information on this page let us know below! 👇