I’m currently mapping my s4 with the freeze mode. And I’m a bit annoyed as I didn’t see the correct solution for what I want.
there are for me (for now at least) three main ways to map in a practical sense (there are more but I leave them for now here):
engage the freeze mode alone (set the slices), the track continues to play and if you trigger a slice the track comes back to that slice and continues to play from that point. Meh, don’t like it.
engage the freeze mode and the flux mode, way better. The slices are set, you trigger one it activates the track plays from this point and you release it/them the track goes forward to where it was supposed to be in the 1st place (thanks to flux). Like when dropping X hotcues in a row with flux.
engage a loop/ freeze mode/ flux mode. Same as above but this time the track is looped at this section, the track continues to play within that loop but the slice plays as long as you hold it. Great (tempered by a comment I’ll cover later).
My issue here is that I want that behavior (a slice plays as long as I hold it) BUT I want the track to continue to play out of that loop.
Get it?
If someone as any advice to achieve that please?
another behavior that annoys me is the following:
I like a slice to be played as long as I press it. Fine, works like that when looped BUT not for the other ‘modes’ I described in the previous post (I get that it’s the intended behavior but it would have be cool to have the choice).
In loop mode if you press more than one slice they will ‘add’ so if you press slice 1&2, the length of the slice played will be 1+2, same if you press 1&3, the length of the slice played will be 1 to 3.
Mmmmh. I’m the only one who finds that annoying (even if once agin that’s the intended behavior).
Don’t get me wrong, I’m quite excited about this update and it’s cool they have implemented the slicer/freeze BUT it’s so much less better than Serato’s one, I’m a bit disappointed (that’s subjective of course).
well, it’s fucking buggy as hell anyway. I have waveform that gets blurred, sliced section that goes back to previous cues, loop active or loop size/set commands that have a mind of their own…Slices themselves that tend to not work properly when held.
Doesn’t make sense or maybe it’s because I’m using freeze mode/flux/loop set a the same time, but even like that it doesn’t make sense for a section to goes back waaaaaaaay behind the point I’m activating.
Added a thread to the growing list of technical issues about that update on NI’s forum. I’ll see. And now go back to 2.6.8 ^^, slicer will wait.
I think I understand what you mean, I am trying currently trying to implement a novation twitch style slicer for my F1 but I am having the same problems, I will get back to you if I get anything working.
Might be something to do with the order they’re triggered? I found this tutorial useful on getting loop, freeze and flux to work together (though might not be relevant if you want the loop to exit)- TUTORIAL: Mapping freeze mode in Traktor 2.7 [VIDEO] – DJWORX