Novation Dicer Mapping Cue/Loop Point mapping LED help

[Blak Majik]

I've searched a bit and haven't really found anything directly answering my question on if this is possible or not. I'm working on a Traktor mapping for the Novation Dicer that is based on the DJTT official mapping, with a few changes. What I'm trying to sort out is the LED feedback for loops versus cue points. If there is a cue point present on say slot 1, the LED on the 1st button on the dicer lights up fine, but if in the same slot, I save a loop, the LED doesn't light up. I'd like to have this LED feedback for loops and load markers in addition to cue points. I'm trying to make the Cue points/Load markers light up red, and the Loops light up Green. I've tried several options in the controller editor and so far haven't had any luck with any of them. Any suggestions/guidance would be greatly appreciated as this is the last thing I want to finish before I call it complete.

[Blak Majik]

Anyone?

[iona]

i don't know if i'm correct, but i think the controller range should be 5 to 5 for the loop. you have to map for hotcue one

OUT: hotcue 1 type - controller range 0-4 - note of red led --> (4 is normal hotcue i guess and 0 beatgrid - but not sure)
OUT: hotcue 1 type - controller range 5-5 - note of green led
(will work on xone k2 since every colour has its own note)

OR

OUT: hotcue 1 type - controller range 0-4 - midi range for red led
OUT: hotcue 1 type - controller range 5-5 - midi range for green led
(will work on apc-40 since every colour is connected to a midi range)

i think one of these methods should work on your controller too...

[iona]

oh and thank you for reminding me that i had to fix this in my own map

[Blak Majik]

Thank you for the help! I'll try this shortly. Just to be clear, you are saying that for EVERY loop stored, I need to map to "Hotcue 1" or just for the example I provided?

[iona]

you have two commands for each button, because you have two different states:

1. hotcue is no loop (means every other hotcue type like cue, grid, fade in, ....)
2. hotcue is loop

if i get this correctly, the dicer has 5 buttons to use as hotcues - so you have to map 10 commands per deck.

[Blak Majik]

Great! Ok, I'm trying it now and I'm halfway there. The controller ranges seem to be:

Min: 0, Max: 0 = Cue Point
Min: 1, Max: 1 = Fade-In
Min: 2, Max: 2 = Fade-Out
Min: 3, Max: 3 = Load
Min: 4, Max: 4 = Grid
Min: 5, Max: 5 = Loop

When I have two midi outputs mapped to the same button, only one at a time will work correctly. I have the following:

Hotcue State 1, Out, Deck A, Ch11.Note.C4 (Left Dicer Button #1), Controller Range Min: 1 Max: 1 (Cue), Midi Range: 15 (Red LED)
Hotcue State 1, Out, Deck A, Ch11.Note.C4 (Left Dicer Button #1), Controller Range Min: 5 Max: 5 (Loop), Midi Range: 127 (Green LED)

When I change the cue marker to a loop, the light is not illuminated, but when I change the marker back to a cue, it turns red. It seems that the output that I map first will work, and the second mapped one will not. I can delete them both, and make the loop one first, and it will work fine, but the cue will not light up. I'm so close!!

[iona]

does it work when you map like i said wit controller range 0-4=red and 5-5=green? are you changing the cue-points while you perform? because when not, this is no problem

[Blak Majik]

Unfortunately, it still only has 1 of the two states lighting up, and the other will not. When I closed Traktor and re-opened it the loop state will light green, but the cue state will not light at all

[iona]

here is a screenshot from my mapping. i just tried to do this with hotcue 3. the different assignment has to do with the controller, as i mentioned earlier it has different assignments per colour. perhaps it helps...
controller range is of cours 1-4 and 5-5... still works