# Loop on/off status and cues

**URL:** <https://forum.djtechtools.com/t/loop-on-off-status-and-cues/30937>\
**Category:** Controller Mappings\
**Created:** [October 9, 2011, 5:44am UTC](https://forum.djtechtools.com/t/loop-on-off-status-and-cues/30937 "2011-10-09T05:44:32Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![willrjmarshall](https://avatars.discourse-cdn.com/v4/letter/w/e36b37/32.png) [@willrjmarshall](https://forum.djtechtools.com/u/willrjmarshall)\
**Post date:** [October 9, 2011, 5:44am UTC](https://forum.djtechtools.com/t/loop-on-off-status-and-cues/30937/1 "2011-10-09T05:44:32Z")

</div>

**Loop on/off status and cues**

Hi guys,

I’m currently working through mapping my Xone DX. I’m using the A&H-provided mappings (updated for Traktor 2), but there a couple of bugs I can’t fix.

The biggest of these is around looping. The “Loop on/off” button is mapped to “Loop active” (input and output). Generally speaking it follows the loop status correctly.

When a deck is looping and a cue point outside that loop is activated, Traktor automatically unsets the loop. This is pretty sensible behaviour.

Unfortunately, Traktor does _not_ seem to update the “Loop active” status. The loop itself is turned off, but the green “ACTIVE” button at the bottom-right of the deck remains lit. Because the MIDI-mapping follows this light, my Xone DX gets out of sync with the current loop status.

Does anyone know how I might fix this? It actually looks like a bug in Traktor … but there may be some subtleties in the looping behaviour I don’t understand.

Thanks!  
-W