Kernel Panic on macOS 15 Sequoia with M4 Chip Opening Kontakt 8 and Reaktor (Komplete 15)

124»

Comments

  • nanotable
    nanotable Member Posts: 104 Advisor
    https://community.native-instruments.com/discussion/comment/222769#Comment_222769

    There must be some kind of misunderstanding. I don’t own an external 5K display and never said so. The crashes I’m experiencing happen on a bare bone MBP with nothing attached at all, although the built-in display has a refresh rate of up to 120 Hz.

    Also, it’s perfectly possible that „my“ crashes have a different root cause than those of others, as they happen a few hours after I’ve started using Reaktor/Kontakt and not immediately, for example.

    The link you’ve posted is confusing (not your fault, but NI‘s), because according to this one Reaktor is fully supported on a.) Apple Silicon and b.) macOS 15:

    https://support.native-instruments.com/hc/en-us/articles/360014900358-Compatibility-of-Native-Instruments-Products-on-macOS

    Anyway, I hope NI has a nice, long weekend, and hopefully they can tell me more next week.

  • Vocalpoint
    Vocalpoint Member Posts: 3,905 Expert

    "There must be some kind of misunderstanding. I don’t own an external 5K display and never said so. The crashes I’m experiencing happen on a bare bone MBP with nothing attached at all, although the built-in display has a refresh rate of up to 120 Hz."

    Fair enough.

    And yes - NI can be very confusing via different parts of their website. I had always thought the link I posted was the "official" company line on compatibility - but it appears not to be.

    Hope you get some info soon.

    VP

  • Kymeia
    Kymeia NKS User Library Mod Posts: 5,764 mod
    https://community.native-instruments.com/discussion/comment/222774#Comment_222774

    Generally 'compatibility' just means no major problems related specifically to Sequoia have been reported, after several months of people using it - which I think is reasonable as this does not seem to be a Sequoia issue so much as a chip issue.

  • Vocalpoint
    Vocalpoint Member Posts: 3,905 Expert
    edited April 20
    https://community.native-instruments.com/discussion/comment/222776#Comment_222776

    And I always thought an official "compatibility" listing is/was based on internal Q&A and actual testing by NI. Not a bunch of random reports from the field.

    A guy could simply install a new OS and have a plugin just startup successfully one time - and logically - that means its compatible?

    If their baseline for this official list is seemingly random "no problems reported" - why bother?

    VP

  • Kymeia
    Kymeia NKS User Library Mod Posts: 5,764 mod
    edited April 20
    https://community.native-instruments.com/discussion/comment/222777#Comment_222777

    I'm sure that's the first level of testing but 'in the field' reports are important too because test systems cannot replicate all real world experience which is often down to certain mixes of software and hardware (as this issue seems to demonstrate).

  • nanotable
    nanotable Member Posts: 104 Advisor
    edited April 20

    Yeah, according to NI they’re „conducting systematic tests (…) in order to offer full compatibility“, and I’m inclined to take their word for it. Doesn’t mean they can guarantee it’s completely bug free, of course.

  • Vocalpoint
    Vocalpoint Member Posts: 3,905 Expert
    edited April 20
    https://community.native-instruments.com/discussion/comment/222779#Comment_222779

    Certainly not downplaying intel from the field.

    But those reports cannot be used to determine actual compatibility. There are limitless configurations in the real world - meaning one user's "It's good" is easily another's "it's not good".

    At some point - only hard core Q&A can establish enough technical trust to put a product on a published "officially" supported listing.

    VP

  • Matthew_NI
    Matthew_NI Product Team Posts: 1,833 mod

    to publicly remind NI that I’m still waiting. I’m doing my best to stay patient

    So are we still waiting, and doing our best to stay patient.

    This appears to be an Apple-side bug; as such the issue is filed with them and we continue to pass along the findings. The continued reports are helpful additions.

    There is nothing we (NI) can do to fix this ourselves at this time.

Back To Top

Categories