Flux mode not working with loops??!!
Hey
Is there a known problem with flux mode not working properly in the latest update?
It works as it should with cues and scratching but when I set a loop and then come out of it, play continues from where the loop ends rather than jumping to where the track “should” be if it had kept playing.
Ive seen this thread on the NI site but there is no response: http://www.native-instruments.com/forum/showthread.php?200390-Flux-mode-doesn-t-work-with-loops
Cheers
What you mean Flux with Scratching?
Are you setting and exiting a loop while in flux mode, or triggering an already stored loop?
No I activate flux mode and then set a loop. works like normal loop mode would when I’m sure it used to work like flux mode should where the track kept progressing in the background and when you exit the loop it jumps to where the track would have been had you left it playing normally.
Sarasin - by scratch what i mean is i can stop the waveform in flux mode and the track will keep going.
Does it happen when you use the controller or same’s happening with a mouse? Asking this just to eliminate the mapping issue possibility as I didn’t update latest version to test.
I first noticed it when I was mapping my midifighter but I also tried it with a mouse. When I mapped my stantons a couple of months ago it worked perfectly but I have since update traktor.
I’ll try it again when I get back from work this afternoon.
So im going crazy. Flux definitely doesn’t work with loops on my system.
Im starting to question whether it ever worked the way I think it did.
Can someone clarify that if you set a loop in flux mode, when you come out of the loop the track jumps to where it would have been had you not set the loop and continued playing the track?
Just out of my head i have to try it, but if i remember it only works with loops as you set the flux mode on before you make a loop. if you already set a loop and then fluxmode on it won’t work. and i think you have to hold the loop as soon as you let go it jumps to the new position.
But there will be a “time travel” mod in 2.6.4
Yeah this is how I thought it worked. Seemingly it doesn’t. Weird.
You think it’ll be that soon??!!
It will happen yesterday.
It happened tommorow.
I feel bad for making jokes in this thread - 'cos now I’ve got the same problem… 
Anyone found a way to use non-hotcue loops with Flux?
Necrobumping!
Does anyone has any update on that issue, it drives me crazy, so effin’ stupid.
It’s pretty tight to mapping. Seems the ‘loop set’ in particular would allow mapping this function to a controller.
This basically never worked the way it should.
The problem is that Flux Mode works if a loop is triggered by the Loop Set command, which is how the S4 push-encoder is mapped, but when the loop is triggered by the Loop Size Select + Set command Flux Mode does not work, even though the button is clearly lit orange. The same problem occurs when you click one of the loop size selection buttons in the UI with the mouse.
Basically this is a design flaw…
You can still use the “Loop Set” and add/map the “Loop Size Selector” command to the same button to recreate the “Loop Size Select + Set” command that works with the Flux Mode. Though, it couldn’t be done with the mouse as you pointed it out.
I also figured out it doesn’t work anymore..
Made it work again by setting the loop you want as a cue loop, turn on flux make a cue point with the loop and then hold the cue point for the loop.
Bad thing is that you have to hold down the cue point to keep it in a loop, it will return to original position when released.
Push encoders still work tho..