MIDI Activity Monitoring
Neurode MIDI exposes activity in several places so you can follow a message from its source to its destination. There is no separate Activity tab in the current release.
Where activity appears
| Surface | Where to find it | What it shows |
|---|---|---|
| System Activity | Status screen or Unified layout | Recent activity across connected sources, grouped by MIDI channel |
| Source activity | Routing → select a source | Recent incoming activity for channels 1–16 and system messages |
| Destination activity | Routing → select a destination | Recent outgoing activity for channels 1–16 and system messages |
| Statistics | Tools → Statistics | Message rates and totals, plus routing and transform latency snapshots when available |
| Event Visualizer | Tools → Event Visualizer | A live visual representation of MIDI events |
Reading the indicators
Activity cells become highlighted when a recent message arrives. Colours distinguish broad message families such as notes, control changes, program changes, aftertouch, pitch bend, and system messages.
The Statistics screen uses compact values such as:
12/s • 84712/sis the number of messages seen in the latest one-second rate window.847is the running total for the current activity session.
Rates refresh once per second. Totals reset when activity is cleared or the app restarts.
Trace a routing problem
A source is connected but appears idle
- Play the controller and check System Activity.
- Open Routing, select the source, and watch its channel activity.
- If it remains idle, verify the physical, Bluetooth, virtual, or network connection.
- Refresh MIDI devices if the endpoint was connected after launch.
A source is active but a destination is silent
- Confirm incoming activity on the source detail screen.
- Open the destination and watch its outgoing activity.
- In Tools → Statistics, compare the source and destination trends.
- Inspect the route, its channel mapping, filters, and NeuroScript diagnostics.
Source and destination totals do not always match. Filters may drop events, one source may fan out to several destinations, and transforms can generate additional events.
Activity appears on an unexpected channel
Check the source and destination channel grids. Then inspect the route's input channel, output channel, and channel-changing transforms.
