Kontakt 7 crashes Logic when I try to do multiple outputs for drums

Options
2

Answers

  • ChampionBot
    ChampionBot Member Posts: 17 Member
    Options
  • Jeremy_NI
    Jeremy_NI Customer Care Posts: 10,335 mod
    Options

    @ChampionBot Well, it's probably part of the problem. When an issue is 100% reproducible and on all systems it's usually easier to find the source of the issue and fix it.

    @Gee_Flat Unfortunately this also happens in other DAWs.

  • Matthew_Morse
    Matthew_Morse Member Posts: 4 Member
    edited March 2023
    Options

    I’m experiencing the same issue. Unable to route drums through multiple outputs without out it causing Logic to crash.

    Nudging NI to get this fixed.

    Running logicProX

    Mac Studio / M1 / Ventura / 64GB Ram

  • shockratees
    shockratees Member Posts: 6 Member
    Answer ✓
    Options

    The support team emailed me to try setting up the 16 multiple outputs before opening the 40's Very Own patchkit. I did this, and it worked. I emailed them back to let them know. I still wonder why the person on the tutorial video can do it without the pre-setup, though?

  • Edouardo
    Edouardo Member Posts: 1 Newcomer
    Options

    Same situation here, and I am using Reason.

    K7: systematic crash as soon as I fiddle with the output

    I tried with K6 also that I still have installed, I was able to reproduce what the guy in the video did with the 40s beat machine. The condition is to configure your outputs before you load the instrument otherwise, the instrument will not see the new outputs. For now, I am keeping with K6 at least until they fix K7!

    For those using Reason, In Kontact, Don't forget to attribute the output of the Kontakt out mix table to the channels outputs of the back of the rack's (seen when clicking 'optional inputs and outputs'), and then connect each output to the mixing channels of the main output table.

  • YoHarry
    YoHarry Member Posts: 1 Newcomer
    Options

    I have Ableton and Im going thourgh the same situation.

  • cherryBlossom
    cherryBlossom Member Posts: 8 Newcomer
    Options

    This is still happening for me in ABleton Live Suite 11, trying to set up outputs to factory setting mono x16 results in instant crash upon sending any midi signals

  • Jeremy_NI
    Jeremy_NI Customer Care Posts: 10,335 mod
    Options

    @cherryBlossom What version of Kontakt are you using, this bug was fixed in Kontakt 7.6.1. Please update Kontakt and make sure you have the correct version in Ableton by clicking the NI logo.

  • cherryBlossom
    cherryBlossom Member Posts: 8 Newcomer
    Options

    Thanks for your suggestion @Jeremy_NI , but the issue is persisting. My Kontakt version is 7.7. Here is a portion of the Ableton crash report when I tried the same steps again (loaded 40s drums, output rack, mono x16, then clicked on the instrument to produce a sound and Ableton crashed).

    Process:        Live [53070]

    Path:         /Applications/Ableton Live 11 Suite.app/Contents/MacOS/Live

    Identifier:      com.ableton.live

    Version:        11.3.13 (2023-10-17_b376a4ffe2) (11.3.13 (2023-10-17_b376a4ffe2))

    ...

     {

      "source" : "P",

      "arch" : "arm64",

      "base" : 12350799872,

      "CFBundleShortVersionString" : "7.7.0",

      "CFBundleIdentifier" : "Kontakt 7.vst3",

      "size" : 94978048,

      "uuid" : "ee912aad-2a65-308e-98d2-b7a9f8a98b5f",

      "path" : "\/Library\/Audio\/Plug-Ins\/VST3\/Kontakt 7.vst3\/Contents\/MacOS\/Kontakt 7",

      "name" : "Kontakt 7",

      "CFBundleVersion" : "7.7.0 (R0), Copyright © 2023 Native Instruments GmbH"

     },

  • Jeremy_NI
    Jeremy_NI Customer Care Posts: 10,335 mod
    Options

    @cherryBlossom please get in touch with our Kontakt specialists here: http://bit.ly/NIsupport_kontakt

  • Chokaprod
    Chokaprod Member Posts: 3 Newcomer
    Options

    Crash as well, I just upgraded from Komplete 12 Ultimate collection to 14. I installed Kontakt 7, the latest version. I have the latest version of Protools and Studio One 6, and in my case, it crashes on both software as soon as I try to use multi-outputs for each pad in 40s Very Town Drum and Empire Break. The drum sounds are great in both, but not being able to use them in multi-outputs is of little interest to me. My Mac is an M1 Max with 64GB RAM and 4TB storage, so I don't think it's a problem with my computer. I will do what everyone else is doing, download a previous version of Kontakt, namely Kontakt 6, and when version 7 works, I will test it again. When I read the thread, I see that the problem dates back a year or more, it's a bit long to allow the customer to use a software that should work, we pay for it.

  • EvilDragon
    EvilDragon Moderator Posts: 1,023 mod
    Options

    Please change the output settings in an empty Kontakt rack BEFORE loading an instrument, then it won't crash. This will be fixed in 7.8 (it's a different issue that is not related to the fix from K7.6.1).

  • Jeremy_NI
    Jeremy_NI Customer Care Posts: 10,335 mod
    Options

    @cherryBlossom @Chokaprod The bug mentioned in this thread was fixed with Kontakt 7.6.1. Make sure to change the output configuration of Kontakt BEFORE loading the instrument/nki.

  • cherryBlossom
    cherryBlossom Member Posts: 8 Newcomer
    Options

    @Jeremy_NI is it then necessary to save the output configuration as "default", delete the kontakt instance, then reload a new kontakt instance (which will load with that "default" configuration)?

  • Chokaprod
    Chokaprod Member Posts: 3 Newcomer
    Options

    Crash as well, I just upgraded from Komplete 12 Ultimate collection to 14. I installed Kontakt 7, the latest version. I have the latest version of Protools and Studio One 6, and in my case, it crashes on both software as soon as I try to use multi-outputs for each pad in 40s Very Town Drum and Empire Break. The drum sounds are great in both, but not being able to use them in multi-outputs is of little interest to me. My Mac is an M1 Max with 64GB RAM and 4TB storage, so I don't think it's a problem with my computer. I will do what everyone else is doing, download a previous version of Kontakt, namely Kontakt 6, and when version 7 works, I will test it again. When I read the thread, I see that the problem dates back a year or more, it's a bit long to allow the customer to use a software that should work, we pay for it.

Back To Top