Traktor pro 3 crashes with apple m2

124

Answers

  • lord-carlos
    lord-carlos Member Posts: 3,590 Expert

    Months of this is just too much

    If you earn money with this, a few weeks is too much.

    It's sickening.

    Have you tried using Traktor 3.8?

  • DJDL
    DJDL Member Posts: 78 Helper
    edited February 21

    I wonder if I can get 3.8 to read off of my 3.11 collection. At this point I wouldn't mind going back to Rosetta, as long as I can keep my current collection status and not lose the prep and organization hours I've put into 3.9, 3.10 and 3.11.

    Anybody with insights as to how to downgrade without losing work done on newer versions?

    I will create a post with this question so that it has better chances of it being addressed. Sorry in advance for the double post.

  • BK_
    BK_ Member Posts: 2 Newcomer

    I have the same problems - the song just breaks off at random. Sometimes after 2 hours, sometimes after 4 hours. Different songs, different parts of the track.

    I played with 3.8 yesterday - everything seemed to work. Suddenly just before the end - music off. Waveform continues to run, no more sound! If you start the song from the beginning, everything starts again and then the sound stops at the same point. No more songs can be loaded into another deck. The information is there, but no waveform is loaded.

    I have a MacBook Air M2! The problem only occurs somehow with 2000 Nexus Player. With 3000 and 900 mixer it runs mostly stable.

    I have now downloaded Serato and will (have to) switch! Too bad, but this is no way to work professionally and earn money! I'm pissed off...

  • Pedrofeder
    Pedrofeder Member Posts: 8 Member

    Hola, quiero decir que la ultima actualizacion, se ha resuelto el problema. Traktor pro 3.11 esta funcionando bien y no se cierra.

  • Pedrofeder
    Pedrofeder Member Posts: 8 Member

    Hello, I want to say that the last update has solved the problem. Traktor pro 3.11 is working fine and does not crash.

  • DJDL
    DJDL Member Posts: 78 Helper

    I am using 3.11 on an M1 Max and the problem is still present. The program hangs and you have to restart it, or it completely quits by itself and you have to restart again. I am glad it is working for you, but perhaps you need to test it out more. Good luck!

  • viper9711
    viper9711 Member Posts: 163 Advisor

    I don't know if it's really the processor?

    I use a Macbook Pro 14" with M1 Pro, Sonoma 14.4 with Traktor 3.10 and S4MK3 - runs super stable without any problems.

    The processor architecture of the M1-M3 is basically the same - I would suspect the error somewhere else...

  • DJDL
    DJDL Member Posts: 78 Helper
    edited March 13

    I am very glad it is working for you and others. However, many of us are still having constant crashes. The common denominator seems to be Apple Silicon and native Traktor versions. I have less crashes with a 3rd party mixer as a soundcard (every other gig) than with my S4, which produces crashes almost every time.

    There might be several factors for the crash, and the fact that Native Instruments are silent about it suggests that either they have no idea what is causing this, or that providing a fix requires more time and resources than they are able to dedicate right now.

  • Pedrofeder
    Pedrofeder Member Posts: 8 Member

    Hello, I have a Macbook Pro M1 MAX 16" 32GB RAM, 1TB HDD. With the version of "Traktor Pro 3.10.0.71 & Kontrol S3" and it has been working perfectly for 6 months. Every Saturday about 5 hours of music session since October .

  • DJDL
    DJDL Member Posts: 78 Helper

    Wonderful to hear that. Perhaps we can get to the bottom of what is causing the crashes for some of us. I see we are both on Ventura. Traktor has crashed both with 3.10 and 3.11. I stick with 3.11 because of the Kontrol X1 MK3.

    Which settings might we have different? Do you have "Load Only Into Stopped Decks" enabled? Multicore Processor Support enabled? Which sample rate and buffer size are you using?

  • Pedrofeder
    Pedrofeder Member Posts: 8 Member

    Audio Setup -> Buffer Size 512

    Sample Rate 44100hz

    Multi-core Processing ENABLE

    Loading only into stopped deck ENABLE

    Macbook Pro M1 MAX 32GB RAM, 1TB HDD, 16" MacOS Monterrey 12.7

    Traktor Pro 3.10.0.71 & Kontrol S3

  • BK_
    BK_ Member Posts: 2 Newcomer

    Changed to Serato! Thx for nothing…

  • Heboracing2
    Heboracing2 Member Posts: 25 Member

    M2 Air 8/256

    The newest update with audio 6.

    Multicore dissabled

    Loading only in to a stoped deck off.

    44100hz

    256 Buffer

    No problems!

  • Yong-Moon Lee
    Yong-Moon Lee Member Posts: 5 Member

    I'll be using Traktor normally, then randomly the mouse gets stuck and I can't move the cursor at all after about an one hr use.


    Sometimes it will be okay for a few hours. It's random. However, when the mouse cursor DOES GET STUCK, the last track will be playing but I won't be able to do anything else. I can't navigate with the controller X1 as well. The last track will keep playing but since I can't transition into the next track, I HAVE TO QUIT THE SOFTWARE.

    The mac OS is still active though. I can move to a different Desktop, the mouse functions normally, but if I move to the Traktor desktop, the cursor will remain stuck after about 0.5 seconds.

    This has happened to me during a professional gig a few times. I've been a long-time Traktor user (Since 2012 Traktor Pro2) I'm seriously thinking about switching to another platform if this doesn't get fixed. I love Traktor compared to any other DJ software out there but this is really a deal breaker.


    Does this happen to anyone else lately?

    Any type of help will be appreciated!


    --------


    Traktor Version: version 3.11.117

    IOS: Sonoma 14.4

    Hardware: M2 Max, Traktor X1 mk2 & Z1

  • DJDL
    DJDL Member Posts: 78 Helper
    edited April 4

    My symptoms vary but none have to do with a stuck mouse. Stuck decks and unresponsive Traktor with no sound seems to be the recurrent issue. Program unexpectedly quitting a couple of times also. I guess it might have to do with the implementation of the Apple Silicon native version of Traktor and some legacy code not playing well with it. Or something along those lines, cause stability has been compromised ever since.

    Again, lack of acknowledgment from the team after countless posts and desperate messages from frustrated users could only mean that they either don't know what is happening, or can't deal with it right now. In any case, bad or lack of communication is the worst possible response, and is in no small part what has users doubting their continued support.

    I am way too invested in the ecosystem to consider leaving at the moment, but have to confess that even though I keep doing my prep work in Traktor, I export my playlists weekly to USBs for use in other platforms. No the ideal scenario, but it's the one we have at the moment.

    I just hope that in time and with a whole lot of patience we'll get back the robust work and play tool that Traktor once was.

Back To Top