Is the freeze function on traktor meant to do this?

Toltemic

When exiting a loop in -Slicer mode- it completely exits freeze, instead of going back to freeze mode

When changing loop select on freeze mode (not slicer) it resets the starting slice to the play head messing up the placement of your freeze cue

I've tested this on my mapping, as well as natively on the d2, with traktor 3 and 4 and it ends up doing both of the above I don't know if its always been that way since its implementation

last adjacent question for the mapping community, is there a point to mapping freeze slice count adjust?

Sûlherokhh

First questions: that's how it's been since the start.

Last question: The count will lengthen/shorten the slices with 8 being the default value, going from 1 to 16. It's only helpful to go to 16 if you use a 4x4 pad matrix, like on the F1.

Sûlherokhh

First questions: that's how it's been since the start.

Last question: The count will lengthen/shorten the slices with 8 being the default value, going from 1 to 16. It's only helpful to go to 16 if you use a 4x4 pad matrix, like on the F1.

Toltemic

https://community.native-instruments.com/discussion/comment/224622#Comment_224622

Cheers,

regarding second question it's seems moving the loop cue out will always move the freeze starting point which is thoroughly frustrating as I wanted my loop/slicer size and placement to match freeze's size and placement