Hi All,
I've built a midi controller using a teensy 3.6 and adafruit trellis modules. I've gotten everything working up to a point.
I'm using the controller to interface with the DJ software Serato. The setup is pretty simple, and mapping controls to buttons has been a breeze, however getting messages back the other way not so much.
It's pretty important as a visual feedback. For example, if I used a button to start a 4-bar loop, I'd expect the button to stay lit for as long as that loop was active - until I pressed it again to remove it, started another loop, ejected the track etc.
If I was using another midi controller that I'd bought - such as one I've got, this behavior happens automatically when I enable output lighting in the software.
For a number of reasons, I need this to come back from the software. I can't put logic into the controller to decide which lights to turn on/off.
What I'm seeing is a series of MIDI messages from the software back to the teensy after I map a new control, or enable the lighting setting. I assume that because this works with pretty much any MIDI controller with lights on straight out the box (or at least mine did) that it's a standard protocol that I'm simply not privy to. I assume that the software sends messages to my controller effectively asking if it's got output lighting and that with the correct response I can begin receiving messages when lights should be turned on / off.
Hence my main question is has anyone come across this before/know of the interface and how to work with it?
Failing that can anyone recommend a good USB sniffer for windows? If worst comes to worst I can watch how my other controller communicates and figure it out from there!
thanks
Edward.
I've built a midi controller using a teensy 3.6 and adafruit trellis modules. I've gotten everything working up to a point.
I'm using the controller to interface with the DJ software Serato. The setup is pretty simple, and mapping controls to buttons has been a breeze, however getting messages back the other way not so much.
It's pretty important as a visual feedback. For example, if I used a button to start a 4-bar loop, I'd expect the button to stay lit for as long as that loop was active - until I pressed it again to remove it, started another loop, ejected the track etc.
If I was using another midi controller that I'd bought - such as one I've got, this behavior happens automatically when I enable output lighting in the software.
For a number of reasons, I need this to come back from the software. I can't put logic into the controller to decide which lights to turn on/off.
What I'm seeing is a series of MIDI messages from the software back to the teensy after I map a new control, or enable the lighting setting. I assume that because this works with pretty much any MIDI controller with lights on straight out the box (or at least mine did) that it's a standard protocol that I'm simply not privy to. I assume that the software sends messages to my controller effectively asking if it's got output lighting and that with the correct response I can begin receiving messages when lights should be turned on / off.
Hence my main question is has anyone come across this before/know of the interface and how to work with it?
Failing that can anyone recommend a good USB sniffer for windows? If worst comes to worst I can watch how my other controller communicates and figure it out from there!
thanks
Edward.