jstoecker

Where in this circuit are you intending to connect your "control" line from the DOUT or whatever? As it is right now, I don't think you could make it work. But with some changes, maybe: if you had an NPN configuration, where the transistor is "below" the LED/resistor pair (as opposed to the configuration in the diagram"above") [so in other words, change the circuit to current sinking instead of sourcing], then you might get away with feeding each LED from the DOUT as per the example for 32 LEDs from a DOUT http://www.ucapps.de/mbhp/mbhp_doutx4_32leds.pdf and then instead of tying all the other end of each LED to ground, tie it to your flasher circuit.. (Or maybe the existing circuit would work OK as a current sink?) Of course, all the LEDs would pulse/flash at the same rate. If you had quite a few of them turned on, you might find you need a beefier transistor... Just an idea, John

Thorsten: Wow ;D - that's *really* nice for MIOS to be event driven like that. I'm looking forward to rolling up my sleeves and building some stuff.... Thanks a lot! John

I'm looking for something to simplify my gig setup, which has two keyboards and six midi modules. The first keyboard sends to four modules (right now they're all daisy-chained via MIDI thru's), the second to the other two. I want to be able to select a patch on the 'proposed gizmo' and have each module change patches (each module receiving its own bank select and patch number). For example, selecting patch "1" might cause the first module to receive bank #1, patch 7; the second module, bank 11, patch 14, the third, bank 1, patch 9, the fourth, bank 3, patch 120. This gizmo would have one MIDI input for each keyboard, and a MIDI output for each module, and all note data and controllers would be "echoed" from the first input to the first four outputs, and from the second input to the last two outputs.. No sysex or MTC or song position stuff would be passed through or processed. Patch changes seen on the input would be filtered out, or possibly mapped onto the patch setups within the gizmo. So, sort of like a glorified "through" box for two keyboards. I'd like to be able to easily change the patch configuration from a "front panel" (LCD display and buttons e.g. up, down, select/enter, and exit/esc) and have the gizmo remember setups from one usage/gig to the next. Am I correct in thinking I could build essentially the equivalent of four "MidiFilter" (http://www.ucapps.de/midifilter.html) units for the first controller keyboard, all sharing the same MIDI inputs but having seperate outputs? Am I correct in thinking I'd need additional modules, e.g. the LCD, DIN (for the buttons), and BankStick (for remembering setups) modules? Also, I want to be clear on one other thing: is it correct that the MIDIFilter project does not use MIOS, so if I want to take advantage of MIOS I have to port or build from scratch the MIDI message processing capabilities present in the MIDIFilter project? TIA, John