Traktor Pro 4 crashed twice!

Gully B
Gully B Member Posts: 13 Member
in Traktor Software & Hardware

I bought a brand new M3 Pro Macbook Pro last week and it's been an absolute joy, especially as the day it arrived was the day Traktor Pro 4 was released, so it was the best upgrade day ever for me.

I've been loving the new features and the new Macbook pro had no problems handling 4 stem decks at once.

However!

Last week in a normal gig, not using stems or anything fancy, just your standard bar gig, Traktor crashed when loading a track from Beatsource. The S4MK3 screens also froze with it, so I couldn't do anything. Thankfully I had an outro loop already turned on before the crash, so that bought me some time to run to the manager and ask them to switch me back to the venue's spotify for a few minutes to reboot.
I put the error down to Beatsource as it could have been a whole host of issues with Streaming.

Until last night, when I tried to load a normal track from my collection that I've used loads of times in the past, so it's not corrupted etc. And it semi-loaded the track into the deck, but there was no artist/title information (yet there was the cover art, BPM, Key and my hotcues etc showing). The deck was crashed. This has happened before and usually a fix has been switching to a live audio input or remix deck, then changing back to a track deck. Or sometimes just loading it into C or D and then it usually comes back on it's own after a bit of time.
This time was worse though. The crash then froze my playing deck and within a few seconds all of the audio cut out and all of Traktor stopped working. The playing song kept playing on the screen but there was no audio to the S4 anymore and Traktor wouldn't let me quit the program. I had to force quit Traktor in the end as it was stuck on flushing background tasks.

I've attached a video of what happened after the crash, and when the bar put their playlist back on. As you can see the song is still playing in Traktor in deck B, but no audio is coming through anymore. And you can see the frozen deck A that caused the crash too.

Untitled Image



NI - PLEASE help us with a stable update, as Traktor 4 is amazing, but this has happened twice in a week now on a top of the line Macbook Pro.

Tagged:

Comments

  • SpirosG
    SpirosG Member Posts: 18 Member

    Good luck on having an answer.

    It has been reported long time ago here, not only by me, there are multiple threads. No one cares.

  • Gully B
    Gully B Member Posts: 13 Member

    it’s just happened AGAIN! This is unacceptable from native instruments.

  • Kubrak
    Kubrak Member Posts: 3,009 Expert

    Maybe good to contact NI with crashlogs and so on.

    It has never happened to me, that Traktor 2 or 3 would crash or disbehaved….

  • DJ Dart
    DJ Dart Member Posts: 21 Member
    https://community.native-instruments.com/discussion/comment/169734#Comment_169734

    I have Traktor Pro 3 or Traktor DJ 2 running as a standby in case anything happens with TP4 (fortunately no issue so far). I prefer that over having to ask the manager for music, even if it's only a workaround.

  • DJ-Andre
    DJ-Andre Member Posts: 114 Advisor
    edited August 2
    https://community.native-instruments.com/discussion/comment/169734#Comment_169734

    You should always remember that the first version after a major update can contain bugs and/or might have stability issues. That's the fact with almost all software. Always take precautions when using it in the wild or wait for a few bug fixing versions have been released.

    Can you share the track(s) with us?

    @Kaiwan_NI @Friedemann_NI

    Can you take a look at this?

  • Kubrak
    Kubrak Member Posts: 3,009 Expert

    There is also another aspect. There may be some kind of problem with your computer. New computer does not necesserarily mean 100% functional computer.

    Might be good to run SW to thoroughly check, that computer's elements work well. Mainly RAM and SSD. Strange behaviour of SW may be caused by malfunction of RAM and or SSD (and other computer parts).

    I do not say, the computer is problem in your case. But it could be as it is brand new and brand new computer has much higher probability to malfunction than older one being used for few months without problems.

  • Gully B
    Gully B Member Posts: 13 Member

    So it seems that this crash happens everytime I'm updating cue points to new music that I've added to my collection.
    It sometimes happens randomly in a gig too, with songs that are analysed etc. So it's so hard to tell the trigger, but I can usually recreate the crash everytime I'm updating loops/cues on new music.

    Hopefully this will help developers find the bug!

Back To Top

Categories