Event trigger from external MIDI ignored by counter
Archive · 20076 old posts
From the original SynthMaker forum (2004–2014), with its members’ names and dates.
Loonie ·
I seem to have come across an odd MIDI trigger issue affecting the timer module, and it seems to exist on any module that takes a MIDI input.
I came across it while working on a project which has an LED indicator which flashes when a MIDI message is received. For most part of the development I have been using the PC keyboard, which does indeed cause the LED to flash, both for a note-on and note off event. Just now I tried it with a proper MIDI keyboard, and the result was that the LED indicator lit up, and remained lit. I tried this with a couple of other interfaces and keyboards and found the same problem.
The LED is simple, it is just two switched bitmaps. When a trigger event is received, the 'on' bitmap is drawn and a timer is activated. When the timer finishes, the 'off' LED is drawn.
The problem is that when the MIDI event splitter receives an event from an actual MIDI interface and not the keyboard, it appears that the timer module ignores it, which is why the LED remains 'on'. I checked to see it wasn't just receiving shedloads of MIDI data by using the counter module, and it counted two events per note press - note on and note off - as expected.
I tried using some of the other modules that have a MIDI input to generate a trigger as a workaround, but found they all seem to exhibit the problem: the counter just will not be triggered by them, unless 'PC keyboard' is the selected MIDI in device.
Acrobat ·
Loonie wrote: I seem to have come across an odd MIDI trigger issue affecting the timer module, and it seems to exist on any module that takes a MIDI input.
I came across it while working on a project which has an LED indicator which flashes when a MIDI message is received. For most part of the development I have been using the PC keyboard, which does indeed cause the LED to flash, both for a note-on and note off event. Just now I tried it with a proper MIDI keyboard, and the result was that the LED indicator lit up, and remained lit. I tried this with a couple of other interfaces and keyboards and found the same problem.
The LED is simple, it is just two switched bitmaps. When a trigger event is received, the 'on' bitmap is drawn and a timer is activated. When the timer finishes, the 'off' LED is drawn.
The problem is that when the MIDI event splitter receives an event from an actual MIDI interface and not the keyboard, it appears that the timer module ignores it, which is why the LED remains 'on'. I checked to see it wasn't just receiving shedloads of MIDI data by using the counter module, and it counted two events per note press - note on and note off - as expected.
I tried using some of the other modules that have a MIDI input to generate a trigger as a workaround, but found they all seem to exhibit the problem: the counter just will not be triggered by them, unless 'PC keyboard' is the selected MIDI in device.
You can see the same issue in groovebox collaboration' slot LED (which is the same as the wiki version).. dunno why it acts that way...
Loonie ·
Well, for now, I've made a workaround LED.
Not ideal, but will do for now:
ik_ik_ik ·
Hi Loonie,
See here (and elsewhere) about MIDI and triggers : [old link]
I've ended up using a single global tick25 at the top level of my schematics with wireless connections to all trigger LEDs below - works really well.
Loonie ·
Wow, I need to not be so keen to post bugs at 2 am. That thread wasn't even far below this one. I guess using a single timer for all of the LEDs is a better solution.
Still, it's very weird that the generated trigger can trigger some components in the schematic but not others.
malc ·
It's all down to timers and the way they work in threads. I posted an explanation in the topic ik_ik_ik has referred you to. If you need any more info let me know.
Another topic worth looking at is this one:
Using timers with MIDI
It's not an ideal situation I know but there's nothing we can do about it right now - sorry.
Wrote something here? To have a post removed or your name hidden, write to [email protected].
SynthMaker