I’ve got a button on a control surface that misbehaves every time I start VDMX. I use it for controlling the show/hide button for Layer 1, but it does nothing at startup. Bringing Layer 1 to focus in the Workspace Inspector fixes it, button always works fine after that. So not exactly screaming for a solution, but maybe someone knows what could be causing it?
Button is the first one (#0) out of five Many-Boolean toogles inside a Multi-Button on a Control surface. (in turn midi-controlled, but button won’t work when clicked on in software interface). All other buttons work as they should, showing/hiding other layers. It’s just this one button #0 & Layer 1.
VDMX 1.2.2
MacOS 26.2 (unfortunately)
What does that button send out if you look at it in the comm inspector (or better yet, Protokol)?
It might be sending out more than a single MIDI command.
Installed Protokol, great tip, thanks!
Button sends no MIDI, so nothing to show in Protokol or comm inspector. I tried disconnecting everything MIDI, no difference. Made a new identical Multi-Button (no copying it), except it receives no MIDI. It does the same thing!
Turns out other buttons wouldn’t work properly with that one layer either, so layer must be the culprit. Made new layer w/ same settings, copied fx chain, deleted problem layer – Problem solved!
1 Like
Glad it worked out. Protokol has been a lifesaver for me. I had a SAMSON Conspiracy controller that would send out some strange values when VDMX was “detecting” MIDI and it was much easier to go through the protokol logs and determine the culprit.
Also, you can always manually enter the MIDI info, so if VDMX needs to "ignore” something during detection, you can use protokol to figure out what the CC or notes should be.
1 Like
I used MIDIMonitor before but Protokol is way better IMO. It has helped already investigating some MPD218 weirdness. Thanks again!
Also, not sure why I posted the whole walkthrough before, two last sentences would’ve been enough for ‘issue solved’ lol