NI/Traktor need to change their approach to the latency/ "crackling" issues

13»

Comments

  • innerdrum
    innerdrum Member Posts: 97 Member

    @Dj Monde

    To me screen flickering is not related to the issues being commented here. I think they are separate problems.

  • olafmol
    olafmol Member Posts: 227 Pro

    argh. Coming back to this thread because yesterday I had to take out my “trusty” Traktor 2 + Audio4DJ + X1 mk2 setup as the venue didn’t have Pioneer CDJ’s.
    And yes, it happened again, audio playback all of a sudden slowing down, stopping, starting, verrrrryyyyy sllllooowww. ARGH!


    I always make sure to reboot my system, turn off WiFi and BT, reset soundcard buffer etc. And still it happened. It seems to be something in the playback speed getting all messed up for some reason, it’s definitely no buffer under run.
    Anyway, it’s a pity as I did enjoy the old traktor experience, but I need to be able to trust it.

  • AudiFreq
    AudiFreq Member Posts: 58 Advisor

    Happend to me on Saturday while spinning my own b-day party :p
    No idea what caused it, wifi was off, system was in high performance, traktor was locked to the logical cores, was running relaxed latency settings… First time this has happened live to me in 3 months

  • AudiFreq
    AudiFreq Member Posts: 58 Advisor
    edited May 8

    I give up, I can't get traktor 100% stable for over an hour unless I run 48khz at 512ms buffer.

    Ended up getting beatup old CDJ's as traktor crashed for me at 2 major gigs (My first non canada/usa gig in Bangkok) I have been on Traktor since 2010 and spun probably 300 event sets over the years but the latency/crash issue with TP4 is serious and is measurably getting worse since TP3

  • innerdrum
    innerdrum Member Posts: 97 Member
    edited May 8

    I use 48khz at 480ms with a behringer u-phoria umc on a lenovo ideapad 3 (ryzen5 - 12gb ram) . It's stable enough to me. Streaming 3-4 hs (2 decks + plenty fx, no stems)
    edit: im still on TP3

  • leesinthemix
    leesinthemix Member Posts: 359 Guru

    Disable CPU Core Parking
    Install LatencyMon to see which drivers are causing the most issues on your system with DPC Latency.

    DPC Latency with real time audio processing is the NUMBER ONE issue when it comes to audio glitches with Traktor.

    I've found in the past that using powered USB hubs can be the cause of the issue.

    I've had zero issues with the X1 MK3 since I bought it until I tried adding a Livid DS1 to my setup a month ago, which caused loads of issues with USB bandwidth and audio drop outs.
    Had to get rid straight after sadly.

  • AudiFreq
    AudiFreq Member Posts: 58 Advisor
    edited May 13

    You are replying to my thread where I outline all of that (and that I am a A+ certified windows admin that does this professionally) I have done that and more (customising power states on my thinkpad, stripping out all MS services, even the store, disabling security features)

    I have tuned my high-end system so well that I can run Ableton or traktor at 96k 64ms but only traktor glitches out even after detuning it to 48k 256ms

    My issue happens on both my S4 and X1 MK3 with tascam interface, but only in T4, not my old cracked ver of t3

  • leesinthemix
    leesinthemix Member Posts: 359 Guru
    edited May 14

    Buy a cheap macbook air then

    If you know inside and out why DPC latency is so bad, then why are you still using windows for audio related work?

    Have you tried other sound cards with TP4? Could be poor tascam drivers…

  • lord-carlos
    lord-carlos Member Posts: 4,136 Expert
    edited May 14

    Or .. and now hear me out this gets wild: Traktor changes their approach to the latency. As other programs work just fine on same hardware.

    Someone should make a thread where we can talk about this issue.

  • AudiFreq
    AudiFreq Member Posts: 58 Advisor

    Yes, as stated in the line you are replying to this happens on both my Traktor S4MK2 and the brand new tascam interface I bought to help mitigate this issue.

    My tone has changed from "This is a long standing issue but with a little hard work anyone can mitage these lock up issues"
    To:
    "Things are getting worse and what was once a safe level of buffer with ok latency is no longer safe, even on the same system, with the same settings but 2 independent copies of TP3 and TP4"

    Again, I moved on, still worth talking about as it gets posted daily.

Back To Top