LED updating wish

So, I bought maschine. It's great. The controller works really well with traktor, and I've got everything laid out nicely.

The one thing that Traktor doesn't do (that would make this solution perfect for me) is update the LED statuses (stati?) on a modifier change.

For example, I've mapped out the deck controls to the main pad bank, and am using modifiers mapped to the bank buttons to switch decks. I can set up LED output stuff for one deck, but of course, traktor doesn't relate LED output stuff to modifiers, so with multiple decks set up in this fashion, the LED updating stuff is just gobbledygook.

Just think, if traktor would do this, you could have almost everything useful mapped to lighted buttons on the controller, and when you changed modifiers, the keys that were active on the deck (or whatever) would light up and you would have to interact with the computer screen even less...

Hopefully this made sense.

FWIW, I also tried setting up discreet pages in the maschine controller with different midi channels for the banks, but maschine doesn't keep up with changes to buttons in banks that aren't active. In fact it will forget the stati of buttons in the non-active banks when switching back and forth.

Thanks!

 

Well.. you can have traktor display the LED's depending on what state they are in, using the Controller-range:

Controller-Range: 0 - 7
(default when using modifiers to toggle LED's)
This means that the given LED will light up if it's in any state between 0 and 7. So if you were to set it to:

Controller-Range: 1 - 7
it would light up when the modifiers state is 1 or greater, and to be yet more specific:

Controller-Range: 1 - 1
would make the LED light up on state 1, and only on state 1

There is a limitation to this system though, and that is that you can't have a modifier-enabled LED light up on two separate modifier states, like for instance number 2 and number 5:
Controller-Range: 2 - 5
This would make the LED light up in all the states between 2 and 5... and creating two modifier outputs like:
Controller-Range: 2 - 2
Controller-Range: 5 - 5
won't work either... either it won't turn on at all, or just one of the states will activate the LED.

 

I think I got that to work. The LED's will light up for the buttons that are related to a given modifier, but the issue is that when I change to a different modifier (different deck), the LED's won't update to reflect the status of the related deck control buttons unless I use one (such as a loop setting, or transport control). Conversely, if I use controls from a deck that is not currently selected by modifier, the outputs still send the statuses to the buttons.

I think what I'm wishing for is that when I select a modifier, any output settings that are associated with the modifier would be parsed, and their states sent.

Let's say that I set up one of the main pads as CC38 on midi channel 1. I want to set it up as the play/pause button for each deck. I would set up 4 modified instances related to each deck (m1=0,m1=1,m1=2,m1=3) for it in the mapping screen. I would also set up an LED ouput for the controller for each of the modified states. So, there would be 4 output definitions, each one reflecting a modifier (m1=0,m1=1,m1=2,m1=3). At this point, if I choose deck one by activating m1=0 and deck one is playing, it should send CC38=127. If on the other hand, I activate m1=1 for deck two that is not playing, it should send CC38=0 and turn off the LED.

I have gotten all of the LED's to work for a given deck, as well as for my modifier selection buttons, but when I switch decks the LED's aren't refreshed to reflect the new modifier state.

I read somewhere in the forum that the midi mapping system ignores modifiers assigned to output, such that it only pays attention to the parameter and the output assignment. It will send the output regardless of the modifier state.

For someone with a controller with buttons that light up like the maschine controller, he could get all of the lights to update their status as he changes decks. He could then see when he selects a deck what it's play state is, what it's looping state is, which cue point is selected, etc... The controller would be like one control surface with 4 layers, and as he switched between layers, everything would update accordingly.

I think I said before, but I did also try to set up the pages within the maschine controller, having each bank have its own midi channel, but the controller doesn't keep track of light status for parameters that aren't currently shown (as far as I can discern).

 

+1

The ability to save and load the previous state as u switch modifiers would be nice.
Manufacturers are getting around the issue by using midi pages for their devices via software so as u switch modifiers (pages) the same LED is assigned a new midi CC and can be controlled by that CC until u switch modifiers (pages) again.
I'd much rather it was built into the software than having to run a 3rd party midi translation tool like Bome's and have to map the controls out time after time for each modifier

 

I have EXACTLY the same problem! do you know a fast fix for it?

 

+1 on the better update from a status outputs!

I have inconsistent problems with my set up and LED feedback too. I have to double check often between the leds from my controller and the screen.

 

Yeah, the led states should be updated whenever a modifier is changed and also whenever a 'output led states according to modifier' command is triggered. That'd probably sort out the remaining problems with my Nocturn

 

Do you know a fast fix? No

A slow and labourious fix? Yes

There a few work arounds but they require 3rd party midi translation software with rules or pages for multiple use of the same controls.

Use pages to duplicate controls and reassigning the LED output CC values as u switch pages.
or
Use IF and THEN commands within the midi translator software just like setting up the modifiers in Traktor.

 

+1 for the request in general,
but i am afraid there is also a risk the implementation would invoke too much probably unwanted, unnecessary midi traffic. For instance in my setup i use modifiers as a "shift" state, with many, many mappings "associated" with these modifiers. What i would appreciate though is a implementation that would allow me to selectively "mute" all unnecessary output commands in that respect.

 

+ yes yes yes for sending monitorstates for possible midicommands after a modifierchange (A filterered "Send Monitor State").
The more of this that can be done in Traktor instead of Bome's the better. For me it will be complicated enough in Bome's before diving into this, so please vote for this one.
(I wrote this one before, no longer up to date: http://www.native-instruments.com/forum/showthread.php?t=84723)

 

I think it not only related to the modifier changes. It's a problem with Deck focus commands, which change it's status when you change the deck, too.

 

Oh, bumer, another variable. But I will not loose hope...

 

+1 .. though i must admit the entire modifier stuff is so cumbersome to me, that i am dropping to bome's for stuff like this.

 

+1