1. IMPORTANT:
    We launched a new online community and this space is now closed. This community will be available as a read-only resources until further notice.
    JOIN US HERE
NOTICE:

Our Traktor Pro Public Beta is available again in our new online community. Join us if you want to try new features.

MORE INFO

New MacBook Pro 16 M1 Pro - Beta 3.5.2 285

Discussion in 'Bug Reports' started by mraloys, Nov 8, 2021.

  1. mraloys

    mraloys New Member

    Messages:
    2
    hello I can not use traktor Beta 3.5.2 285 on MacBook Pro 16 M1 Pro with Monterey 12.0.1, after being able to close the beatport popup ad not without having to force close many times now at least I can start it but when I load a song stays with play pressed but without playing anything either with the internal sound card or with the z1 and when I go to close it freezes in program and I have to force close it also happens when you analyze the database or delete something from it when closing traktor crashes.


     
  2. radiokrishna

    radiokrishna NI Product Owner

    Messages:
    175
    Try disabling Multi-Core, the problem remains?
     
  3. mraloys

    mraloys New Member

    Messages:
    2
    now if it works thank you very much, I didn't think that having the multi-core option enabled would affect the program.
     
    • Informative Informative x 1
  4. DJ SKRAT

    DJ SKRAT New Member

    Messages:
    1
    Had the same issue on Monterey with S2 MK3 console. Seems like disabling multi-core did the job. Seems like T is unable to handle external audio interfaces on Monterey (or is it new M1 macs?).
    Anyway, the experience is really poor - T simply does not allow some controls like playback, navigating track etc... It's not clear what's the issue, then when I just selected S2 in settings -> audio output as an interface, it freezes completely. Then even after I unchecked multi-core, it didn't help, I tried to close T and it had frozen again. Then after reopening T it still didn't worked. Finally, after I got back and gave it a try again, it suddenly worked fine.
    Making all-cores utilisation working would be the best solution. If not easily possible, then please not even show that option to M1 users and keep it always turned off in the background to avoid such hassles.
     
    • Informative Informative x 1