Send Modiferdependant Monitor State

I'm planning on building my own MIDI controller. Before getting there i've been mapping a A&H1d to it's limits. I'm also trying out visual/mechanical feedback with BCR2000(leds) and soon BCF2000(faders). My layout will be a 4deck, 4fx, illuminated arcade buttons, all in one unit or split in 2 or 4 separate units. Pushencoder for browser on each deck or a seperate browserarea/unit. First i sketched an all in one unit thinking I would be satisfied without or only one fader, getting most done with encoders. Now, one year later, I believe it would be better having 16. They could be used for fx, decksettings, tempo-key-filter-gain , (deckvolume and eq if internal), or even controlling external DMX-box. The most important though would be alternating between fx and deckcontrols.

What could go wrong with Traktor Scratch Pro ?

Send Monitor State sounds good but it would have to be v.2, capable of filtering out what is important for the modifierconditions used after a modifierchange. And perhaps it would also need to be an ms-delay on the monitorsend so it could be triggered from the modifierbutton without reading the wrong modifierconditions that was in use before the modifierchange.

Another idea could be creating special feedback/monitorstate presets that could be called upon as a modifercommand instead of 'send monitor state'. This would maybe solve the conditionissue.

Other posts touching this subject
FREE Visual MIDI Guide and Reference
http://www.native-instruments.com/forum/showpost.php?p=462263&postcount=19
LEDS + Send Monitor State = ?
http://www.native-instruments.com/forum/showpost.php?p=454894&postcount=1

Thread about delay
Midi Commands delay
http://www.native-instruments.com/forum/showthread.php?t=75711&highlight=delay

Post about BomesMidiTranslator answered by Bentosan on DJTechTools
http://www.djtechtools.com/forum/showpost.php?p=43067&postcount=39

 

Ima little late. but i finally answered it

Edit: Bomes ftw - modifers are weak in comparison

 

+1