I have a practically new S4 mk3 controller Macbook PRO M1 laptop The problem is that after a while of using the SW the CUE button does not respond correctly TRAKTOR PRO PLUS latest version Anyone have had this happen?
On all channels? Or a specific deck?
And does it work again after you restart the software and is not now completely gone?
mac os 15 M2 , i updated to os 15 sequoia while using traktor pro 3 and it started doing a lot of weird things. I'm back to pro4 and not getting the issues. also updated pro 4 to the latest version and it helped a great deal. i shouldn't have updated but mac made me to do a diagnostics on my computer
What is 'not properly'? After how long?
It happens on both decks, after not long
Once more:
"The problem is that after a while of using the SW the CUE button does not respond correctly"
How does the CUE button respond? What does 'not correctly' mean?
And what's 'not long'?
I mean the normal operation of the CUE when you press it and release it the track does not start (the button on the controller and on the program lights up but the track does not start when released)
The problem is very similar to this one to be clear https://www.reddit.com/r/Beatmatch/comments/nkdmob/traktor_s4_mk_3_cue_issue_in_jog_mode/
Tried remapping it with a "new" CUE command inside the Controller Manager? What happens if you click on CUE in GUI (screen)?
Could be also the jog touch on issue.
I've heard about this "jog touch on issue." problem, what do you mean? If I understand correctly from what I've read it seems like a problem that this controller has been carrying on for a long time from older versions, never solved by NI
I think it's a native SW + HW problem between S4 and TP, related to JOG?
Besides, it's a random problem, which occurs quite often
I did another test and when it happens I find the same problem on another MIDI controller (Xone K2) connected in parallel for the occasion for the test In the past using a Pioneer XDJ this type of problem has never happened (it's a problem with the NI S4 controller)
To solve it I have to disconnect and reconnect the S4 controller, really boring and annoying
No problem with hot cues, these work well
It's not about SNAP, Quantize, Latency (it has nothing to do with it, even changing these settings the problem remains) I find it crazy that NI has never found a solution to this serious problem!
Ah, that thread has a good explanation in the comments.
I think I had it once or twice in the time I owned the s4mk3, though it was rare and slightly nudging one of the jogs resolved it for me. But I can see other hardware being more sensitive to it.
I think it's a defect that happens randomly It's as if the track is not perfectly still or rather as if the Jog rotates slightly in TT mode even though it is in JOG mode, in this way the CUE is not taken
Not sure if this helps ?
Preferences > Transport
Cue Play (cup) Mode Instant
