VCI-400 Standard Edition LED Mapping - Page 2
Page 2 of 3 FirstFirst 123 LastLast
Results 11 to 20 of 25
  1. #11
    DJTT Mapping Ninja Moderator Stewe's Avatar
    Join Date
    Aug 2010
    Location
    MIDI
    Posts
    7,493

    Default

    Quote Originally Posted by clkwk View Post
    Stewe is there a reason you don't use 0 as a modifier value in your post?
    I don't use value 0 because it can't lite up LED. Don't get me wrong - you can still set 0 as modifier condition it's just the fact 0 = LED off so there is no indication that mode is on.

    I don't see how this so complicate?

    Cue mode - value 1
    Gratify mode - value 2
    ? mode - value 3
    ? mode - value 4

    No need for 'Send State' command tho.

  2. #12
    Tech Guru Nicky H's Avatar
    Join Date
    Jan 2009
    Location
    Leeds UK
    Posts
    2,485

    Default

    Ok I was drinking this afternoon watching rugby don't know if I explained properly..

    What you are trying is in theory correct, the led's should update when you change the modifier to enter cue/grat mode.

    Quote Originally Posted by clkwk View Post
    From what i can tell traktor only sends the controller the state of the cue point when it changes.
    As you have found out when doing it with cue states it doesn't update - I don't know if it's a bug or by design - I had the same thing mapping my F1.

    The way to turn the leds off is to map the modifier condition to them:

    Add Out > Modifier > Modifier 2 : (your pad led) : condition m2=1 : midi range 0 - 0

    Do that for all 8 pads and when you change from cue mode and set m2=1 it turns them off.

    Because it is modifiers updating led's you should also add send monitor state and invert it as you said.
    SC | MC

  3. #13
    Tech Convert
    Join Date
    Oct 2012
    Location
    Canada
    Posts
    16

    Default

    I agree Stewe...this all seems complicated for what I am trying to do. I am going to try a couple things later tonight based on what yourself and Nicky H has said. I post my results later.


    Thanks for your help to this point guys....

  4. #14
    DJTT Mapping Ninja Moderator Stewe's Avatar
    Join Date
    Aug 2010
    Location
    MIDI
    Posts
    7,493

    Default

    Cue button: M2=1
    Grat button: M2=2

    Hotcue in and out modifier condition: M2=1
    Grat FX in and out modifier condition: M2=2

    Put it this way, when you press cue button 8 button grid should display all hotcues that are assigned in track because you have M2=1 dedicate to 'Hotcue' LED outputs. Once you hit grats button, the modifier value switch to M2=2 and hotcue LED's go off because you have M2=2 dedicated to 'FX on' LED outputs if all of effects are currently disengaged. TADA!

    Makes sense?

  5. #15
    Tech Convert
    Join Date
    Oct 2012
    Location
    Canada
    Posts
    16

    Default

    OK so I got it two work with both of your methods:

    Nicky H:

    Add Out > Modifier > Modifier 2 : (your pad led) : midi range 0 - 0

    In stead of using the Modifier condition I left it blank; thus allowing me to clear the LED when my grid is in the other 3 modes (M2=1,2,3) and it seemed to work fine. Whenever i change my gird to something other then cue the led go out. When set my grid to cue again the led light up.

    Question for you: What would changing the controller range do in this case?

    Stewe

    Using your method works as well , but have 2 buttons that change the fx amount and use the same effect. I tried to turn on the led based on the fx amount using the controller range but I don't fully understand this controller range. For example button 1 uses FX unit 3 fx 1 gater = 0.5, button 2 uses FX unit 3 fx 1 gater = 0.7.

    Thanks for both of you help!

  6. #16
    Tech Guru Nicky H's Avatar
    Join Date
    Jan 2009
    Location
    Leeds UK
    Posts
    2,485

    Default

    I'm a bit confused at what the problem is mate...

    You should be able to change the leds when changing modifiers as long as you use Send Monitor State when changing M2.

    But you said the leds were not updating for you just using the modifiers..
    I suggested the other way as a workaround really because you said it was not working, but I think you must have something wrong somewhere - the full correct way is:

    Assuming M2 = 0 is cue mode and M2 = 1 is grat:

    Add M2=0 condition to all of your Hotcue types;

    Add Out > Track Deck > Cue > Hotcue 1 Type
    M2 = 0
    Type = LED
    Interaction Mode: Output
    Assignment: Deck A
    Controller Range: 0 to 5
    Midi Range 0 to 127 blend unchecked

    Repeat that for all 8 hotcue types for Deck A (Hotcue 2 Type etc...)

    Then on the button(s) that changes from cue to grat, (or anytime you change M2), add Send Monitor State
    As long as you have Send Monitor State when you change to grat mode it will turn the cue leds off.
    When you come back to cue mode they will light again.

    By setting controller range to 0 - 5 it will only light up if there is some type of cue set (-1 = no cue set)
    By unchecking blend it will light the led to full brightness if there is any type of cue point set.
    If no cue point the led will be off.

    That's the correct way to do it and should work fine.
    SC | MC

  7. #17
    Tech Guru Nicky H's Avatar
    Join Date
    Jan 2009
    Location
    Leeds UK
    Posts
    2,485

    Default

    Quote Originally Posted by clkwk View Post
    I tried to turn on the led based on the fx amount using the controller range but I don't fully understand this controller range. For example button 1 uses FX unit 3 fx 1 gater = 0.5, button 2 uses FX unit 3 fx 1 gater = 0.7.
    The controller range tells traktor when to turn the led on.
    In the hotcue type output above we have it set to 0-5.
    -1 = no cue
    0 = cue
    1 = fade in
    2 = fade out
    3 = load
    4 = grid
    5 = loop
    So traktor turns the led on when the hotcue type is between 0-5 (cue set) and off when -1(no cue).

    The controller range is different for all outputs - for instance Play/Pause only has 0 & 1 (play/pause)

    So to map your fx outputs, you need to know what the controller range is referring to.

    I'm guessing the 0.5 & 0.7 refers to FX Unit Dry/Wet?
    Add Out > FX Unit > Dry/Wet Adjust (M2 = 1) (range 0.5 - 0.5)
    If so the pad 1 led will only light up when the dry/wet reaches 0.5 (50%)
    Pad 2 led will only work when the dry/wet is 0.7

    I guess the dry/wet is only set when you hold the pad - so it will only light up when you hold it down.
    If you set the range from 0 - 1 they will light up all the time when you change to grat mode.
    If you tick blend the led brightness will change when you adjust dry/wet.
    If you untick it it will be full strength all the time.

    If you want different led brightness then you have to do it a different way - get this working properly and I'll show you how
    Last edited by Nicky H; 11-18-2012 at 06:01 AM.
    SC | MC

  8. #18
    DJTT Mapping Ninja Moderator Stewe's Avatar
    Join Date
    Aug 2010
    Location
    MIDI
    Posts
    7,493

    Default

    I'm guessing the 0.5 & 0.7 refers to FX Unit Dry/Wet?
    My guess is those are slow and fast gaters

  9. #19
    Tech Guru Nicky H's Avatar
    Join Date
    Jan 2009
    Location
    Leeds UK
    Posts
    2,485

    Default

    Yeah maybe the knob settings - tbh if he's making a grat map, when he presses the pad it should do a few things as you know, load fx, set parameters, hold fx unit on etc.

    But the principle is the same clkwk, the controller range tells traktor when to do something.
    Knob 1 > range 0.5 will only light when knob 1 hits 50% (when you press pad)
    SC | MC

  10. #20
    DJTT Mapping Ninja Moderator Stewe's Avatar
    Join Date
    Aug 2010
    Location
    MIDI
    Posts
    7,493

    Default

    As for LED behavior between performance modes I got nothing more to add, I use it like described for ages and it work flawlessly (effect on LED range 0-1). I would only add one suggestion for grats mode - don't forget to map in 'FX Store Preset' command to all pads to prevent pressing button twice when switching and engaging effects.

Page 2 of 3 FirstFirst 123 LastLast

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •