![]() |
Midi Monitor - Printable Version +- Conductive Labs Support Forum (https://conductivelabs.com/forum) +-- Forum: MRCC - MIDI Router Control Center (https://conductivelabs.com/forum/forumdisplay.php?fid=13) +--- Forum: General Support (https://conductivelabs.com/forum/forumdisplay.php?fid=14) +--- Thread: Midi Monitor (/showthread.php?tid=3650) |
Midi Monitor - gm-labs - 05-20-2025 Hi guys, I bought an MCRR a few days ago and I’m trying to set it up in my studio. The first issue I’ve encountered is how to monitor what’s happening on an output port. I see that I can monitor incoming messages on the input port via the routing menu, but I have no way to tell if a filtered clock is actually being filtered on a specific output port. The MIDI monitor section is too small to effectively check what’s going on, especially if you’re dealing with a large number of messages. I’m also wondering if there’s a way to monitor this on a bigger screen, but so far I haven’t been able to figure it out. The only solution I found is to connect a MIDI cable from the output port to a computer and check the stream with software. Any advice? RE: Midi Monitor - Jesse Johannesen - 05-25-2025 Here are the ways it is possible to monitor MIDI information being passed on MRCC: 1 - Looking at the routing in question - Going to the routing page shows symbols which blink on as they occur. Here are the abbreviations for each message type: NOTE ON/OFF: "O"/ "X" AFTER TOUCH - POLY/CHANNEL: "AT" PITCH BEND: "PB" CONTROL CHANGE: "CC" PROGRAM CHANGE: "PC" CLOCK: "TIC" START: "->" STOP: "!!!" CONTINUE: ">>" ACTIVE SENSING: "..?" SYSTEM EXCLUSIVE: "SX" TIME CODE QUARTER FRAME: "QT" SONG POSITION: "SP" SONG SELECT: "SS" TUNE REQUEST: "@" (EAR) SYSTEM RESET: "XX" UNKNOWN: "??" 2 - The Activity page - The main activity page allows you to view incoming messages and see where they are routed. Incoming MIDI Data is Green, Clock data is Red. White squares show where routings occur between incoming ports on the horizontal and outgoing ports on the vertical. 3 - The MIDI monitor tool - This shows the most information and has play pause functionality to help to isolate data. This seems most likely to help with your search, but my advice would be to turn off other routings (save your setup and then disconnect all routings you don't need and then test the MIDI data in the monitor tool, then once you confirm, reload all routings. 4 - Port monitor Light Show - This one shows MIDI notes only as far as recall, but shows when notes are sent from a port as an LED blink. For all other testing you'll need to use an exernal device. That could be a PC, or setting up an experiment to detect Data (like hook up a sequencer and see if it's getting clock, etc. As far as Port level filters go, I haven't heard of any reports that filtering wasn't working. I would guess that if you set a clock filter on a port output, it should be filtering clock. |