Traktor pro 3 crashes with apple m2

Dj Special K

Nevermind... found the info here for anyone else who needs it, in the home page search field just type: "How Can I Downgrade my TRAKTOR to an Earlier Version?"

Pedrofeder

Estoy realizando las sesiones actuando tractor con ROSETA, sin roseta es imposible trabajar, el programa se cierra de repente, cargando pistas desde listas de reproducción previamente analizadas. Con roseta tambien falla, se congela y hay que cerrar el progama. He detectado que tracktor analiza las canciones ya analizadas con anterioridad, aunque los hot cues si aparecen, esto no ocurria antes en ninguna versión de tracktor, por lo que creo que es otro fallo. En resumen, la última actualización no ha servido de nada, continuo actuando con inseguridad y trabajando mal. Muy frustante, doy como maximo un mes o dos y posiblemete cambiare a Pioneer y recordbox. Por supuesto, siguiendo todas las recomendaciones del soporte técnico, es destacable lo mal que nos está atendiendo, en realidad es una estafa, hemos comprado un producto que no funciona.

Dj Special K

I can confirm that 3.8 is stable. I have played 2 successful gigs. That version is in your BACKUP!

Cambiando al version 3.8 es la solucion hasta Native instruments puede areglarla. Acabo de Dj 2 veces sin problemas!

gorkita

hello guys any solution?

Yesterday it started pulling when I changed songs, I opened the traktor again, it loaded the same song and it didn't pull.

After a few minutes I put on another song and it starts playing again, it's exasperating, I have an M2

greetings and Happy Holidays

andrea_capecchi

Hi guys!

Same here... I recently bought a macbook pro m2 and upgraded to Traktor Pro 3.10. Yesterday, new year eve, i played for more than 4 hours and experienced 2 random crashes during the night... In 10 years i've never had such problems. I still have my backup pc with the latest version of traktor 2 and surely i will use it for the next gigs... It just sucks that this issue is sooo common and there is no solution.

Hope that NI is going to fix this asap...

Andyaustin1234

I have the same issues with crashing to desktop with Traktor Pro 3 with native support for new Apple silicon (M1 and M2 machines). No problems with corrupt files/directories etc.

I rolled back to Traktor Pro 8.10 (which uses Rosetta instead of native Apple silicon) and I've had no further issues - even for 6 hour sets.

Looking at all the comments on several threads, the consensus seems to be that there's a bug in the latest Traktor software (that's supposed to run natively on Apple silicon M1 M2) . Moving back to the older versions that run Rosetta has worked for just about everyone (including me).

I hope NI addresses this issue -- I bought a brand new MacBook Pro with M1 Apple silicon and can't run Traktor natively without random crashes.

Andyaustin1234

Does anyone know if the newly released TRAKTOR PRO 3.11 has fixed this issue? The release notes mention stability fixes but not this specific crashing with Apple silicon machines.

lord-carlos

Hi guy.

People who have problems with crashing, can you give a quick feedback if that only happens when you load a track (probably not analyzed yet) or also just in the middle of mixing?

I know Andy already said he also has crashing even after loading.

NI team is aware of an issue when a track is loaded that is not analyzed yet. I'm trying to get a feel for how many have crashes besides that. Thank you.

DJDL

3.10 had crashes while doing random things. Previewing a track, deleting a history playlist, and also while doing nothing but letting a track play out. Crash mid track, not even touching the controller. Upgraded to latest 3.11.1 yesterday, will test soon.

Maco OS Ventura, Apple M1 Max.

OliverGross

Hi Carlos,

for me it was happening while loading a track. In this case another track was loaded in this deck but stopped.

But all Tracks were analyzed before.

Interestingly I didn‘t have any crash since I disabled Loading only into stopped Deck.

I have a MacBook Pro with M2 Pro and the latest OS Ventura.

Dj Special K

Carlos, I'm using an M1 and it would crash randomly on 3.10 , with no actions from me.

Andyaustin1234

My crashes happened with 3.10 when I wasn't even touching the computer or controller (I'm using a MacBook Pro with M1 chip and an S5 controller). Just 'bang' straight to desktop. I rolled back to the previous version (using Rosetta), and did not experience any crashes.

Update: I installed the latest update 3.11 (and updated my OS to the absolute newest), and played all night in a club with no crashes or other performance issues. Fingers crossed that the update solved the problem. I'll report back if I experience any more crashes.

J. Spencer

I will say that I've been having this issue for a while in 3.x on my MacBook Pro 13" M1. I don't remember where I found it, but there was a suggestion to disable (untick) the "Enable Multi-Core Processor Support" and so I tried it. That was in December, and while it could be pure chance, I've not experienced a crash.

Prior to unchecking this option, I had actually crashed 3 times in the same 24 hour period (during prep times and once during performance).

I have updated to 3.11 since then and that could have solved the problem, but you could try disabling that option if you're still having issues.

Dj Special K

i disabled the multi core processing after upgrading to 3.11 --- about 2 hours into my set, i chose a folder in the tree and i got the rainbow of death spinner. I had to completely shut down my mac to get out of it. Absolute party killer. I'm going back to 3.8 :(

DJDL

I've tried all user suggestions. Disabling "Loading Only Into Stopped Decks" seemed to help a bit. Tried disabling the Multicore Processor function last week and lo and behold got a complete program quit while playing at an important corporate fitness event. This is the first freeze I've had recently, cause I had not been using my S4MK3. But this one gig was complicated so I brought it out, had 2 fitness instructors with microphones running into the S4, and the show was going well until midway Traktor Pro 3.11 unexpectedly quit. Straight back to the desktop, and the worst thing was that the S4 also went into silence, so not only the music stopped but the 2 instructors were muted. I quickly played some music from my phone that I always hook up to the speakers now that this will happen so frequently, and shamefully apologized to the instructors and the crowd. I've resorted to other brands now, and am using standalone controllers with USBs for regular gigs. Simply cannot have my gear quitting everytime. Next time I have a complicated event, I will run Traktor into a separate mixer that controls the microphones and keep a spare channel with my phone or some other source to fill in when Traktor quits or crashes.

Months of this is just too much. Tried to keep faith, be patient, polite, understanding, but without even a response, I am forcefully considering my options moving forward. The standalones work for certain situations, but I need my full library and quick track and playlist access for more complex events. Sadly, my setup with an 2021 M1 Pro and Traktor is simply not safe for work.

I wish NI would prioritize and just focus on much needed, urgent, critical stability at this point. The absence of acknowledgement is disheartening, and I truly hope this is not the end of such an otherwise inspired, wonderful platform.