Modifier Output not working correct

What Am i doing wrong?
My modifiers work but the Output LED is not working properly.
It does Light UP but it never Goes Out. Why?
I am using a Vestax VCI-100 frm 1.3

example:

Mod1 is Switch25

Control /I/O /Assignment /Mode /Mapped to /MOD1 /Mapping Details

Modifier1 /input /Global /Direct /CH01-D5 /Mod1=0 /Button-Direct-Set to 1
Modifier1 /input /Global /Direct /CH01-D5 /Mod1=1 /Button-Direct-Set to 1
Modifier1 /input /Global /Direct /CH01-E7 /Mod4=0 /Button-Direct-Set to 0
Modifier1 /output /Global /Output /CH01-D5 /Mod1=1 /LED-Output-


This Line is for, when Modifier 4 is turned on (SW11, note:E7) to turn off Modifier1

Tell me am I missing something?
I can see the Modifier State working Properly when pressing the Assigned Mod Buttons but Why is the Output LED not turning the LED off?

 

Hmm .. I also saw similar issues. In my case I removed the modifier from the output and it worked fine after that. Maybe 1.1.2 ignored modifiers on the output?

 

I use the modifiers in an ON/OFF way so each modifier has 2 states 0 and 1. When mod=0=off and when mod=1=on
i want the LED to light when the modifier is in the state of ON=1 so then I know that the state of the certain team of buttons corresponding to that modifier has changed.
The LED lights up the first time you press the mod button but the second time you press it to change the state back, the light remains on
This worked just fine in 1.1.2 but it is not working right now and i cannot find how to do it.
Is it a bug? or is it something i am missing?
---

the first Lines work as a TOGGLE mode to switch from 0 to 1
the 3rd line is for setting mod1 to 0 when i press Mod4
The forth line is the LED output that used to work in 1.1.2

 

Right, I understand what you said.
I ran into similar issue in with the DJTT mapping, though these were on buttons assigned to handle on/offf states. I havent quite wrapped by head around how and when out messages are triggered.

In my case I had 3 LED's (enable/disable deck D, right EQ fx and juggle mode) that were working fine on the one side of my VCI-100 and werent turning off on the second. When I investigated the differences, I noticed that probably accidentally one side had an additional modifier check. I removed them and now all is working fine.

So maybe just try it out without the modifiers on the out message .. if you havent done so yet.

 

I was about to write my findings (I found that by accident) when I read your last post.

I removed the Modifier in the MAPPING DETAILS and it is working as it should.

But I do not understand why this is happening, I believe this is a bug.

 

Yeah .. neither do i .. it works .. but its magic

 

Remember that modifiers are filters for the actual message so if the message you are outputting the to is say Ch2:CC14 and you press a button to get the LED to light up i.e. you've set the value in the message Ch2:CC14=127 (7fh) then what you need to do to get the led to turn off is set Ch2:CC14=0. What the modifiers do is filter whether of not the message as actually sent. so if in the end your modifiers do allow the meesage to be sent out but the actual message VALUE sent is still 127 or 7fh then the LED will stay lit.

Now all that being said, there May well still be a bug here One possibility is that the Modifiers may not be filtering properly. Try removing the modifiers from the output to see if the message being sent to your output LED is actually changing when the button is pressed. Remember, to make it work properly the Message value has to be set properly AND the modifier has to be of the correct value to allow the message (also with the correct appropriate value) to be sent. By themselves MIDI Modifiers on outputs do NOT cause an out to turn on or off, they merely determine whether a message that would be sent out is filtered or not.

Make Sense?

 

Well you did got me a little confused, but from what i wrote earlier i got it working by removing the modifier from the Output, so it is working

What i do not understand is how did it simply worked in 1.1.2 and now it works different?

 

As I recall in 1.1.2 Modifiers did not work on Out messages. the message always went out unfiltered.

 

Aha .. so I was right with my assessment of the situation. And you are right in pointing out that if we use a button as a toggle and we enable it, then the CC/note will be held and therefore the LED stays lid. So it does make sense .. the confusing part was just that due to modifiers being ignored in 1.1.2 we got away with "faulty" mappings before.

 

Yeah and one more thing for those just getting their heads around modifiers its a much different thing to put a modifier on a output control that maybe on but is being turned off, vs no modifier and letting the control freely change state. in the case where the modifier is applied you will prevent the proper message from reaching the Midi controller and thus changing state. My experience in doing LOTS of programming with outputs is that in many/most cases, modifiers are not needed on outputs and indeed will often cause toggle state outputs to not actually keep the out in the proper state.

Where modifiers on outputs would be really valuable is to say things like this:

Code:

If Ch1:CC14=0 && M5=1 SET {Ch1:CC93=127 && Ch1:CC94=0  && Ch1:CC95=0 && Ch1:96=0}

So you base your controller assignment of the presence of the output message, the value of the output message and the value of a modifier then you output more than just one value.

This is Bome territory though and maybe better off left there. Few people may use it even if it was an option.


Phil