Vienna Symphonic Library Forum
Forum Statistics

181,835 users have contributed to 42,188 threads and 254,610 posts.

In the past 24 hours, we have 4 new thread(s), 30 new post(s) and 53 new user(s).

  1. Home
  2. Software
  3. Vienna Instruments Pro
  4. Enable/Disable Kontakt 5 in VE Pro 6 via Parameter Causes Crash.

  • Enable/Disable Kontakt 5 in VE Pro 6 via Parameter Causes Crash.

    C
    C
    I plan to start experimenting with enabling and disabling in VE Pro 6 via parameter changes in Cubase. I found that disabling works fine, but VE Pro crashes when I try to enable a disabled instrument or channel. This doesn't happen with VIpro, but does with Kontakt 5. I've updated both VE Pro 6 and Kontakt 5 to the latest versions...
     
    Considering this would be such a handy feature I'm wondering if people are having success with it, and if there's something I'm missing. I go to view automation mapping, "add", then on the left, pick a parameter, then on the right, select the first instrument then "disable". I go to Cubase, move the parameter dial to "on", the instrument successfully disables. Then I turn it off, VE pro crashes. 
  • PaulP
    VSL Team
    PaulP

    Hi, 

    Please send such a crash report to support@vsl.co.at, we will take a look. Did you try with different Kontakt libraries? I suspect a Kontakt crash for a specific library. 

    Best, 
    Paul

    Paul Kopf Product Manager VSL
  • C
    C

    Thanks Paul. Will do. I tried it with Cinestrings and Spitfire Chamber Strings. Might try with a Native Instruments library and will report back.

    Works fine with Play 5.0.0.
  • C
    C

    Also I should mention, I tried again after the first post, but dragged the parameter from .50 to .49. The channel sucessfully enabled without crash. but then moving the parameter dial around more after this caused the crash. It seems from my limited testing that it could have something to do with Kontakt or VE pro receiving multiple enable requests in rapid sucession...
  • S
    S

    As of August 2017, this is an ongoing issue with Cubase 9 and latest VE Pro 6. Trying to enable or disable Kontakt tracks in VE Pro via parameter automation always results in a crash.
  • C
    C

    I believe this got fixed in the latest update. Have you tried the latest version on your end?

    Sorry just realised what you meant. Issue must have resurfaced in this months update. I'm still on an older one so I haven't noticed.
  • PaulP
    VSL Team
    PaulP

    Hi, 

    We checked here, and there is a conflict between messages with VE PRO and Kontakt, but here it results in a freeze. 

    @Symfoniq: Can you please send me the crash log you get? Which Cubase versions, Kontakt version and VE PRO version are you using, on which OS? => support@vsl.co.at

    We have alread informed Native Instruments about the conflict, but have not heard back yet. 

    Best,
    Paul

    Paul Kopf Product Manager VSL
  • S
    S

    Hi Paul:

    I'm away from my workstation today, but I'm using Windows 10 (Creator's Update, I believe), Cubase 9.0.20, latest VE Pro and latest Kontakt.

    Perhaps I'm using terminology incorrectly, but VE Pro freezes and becomes unresponsive when using the parameter automation on a Kontakt plugin. It's VE Pro Server that is "crashing," not the entire system (I get a "[NOT RESPONDING]" notification in the VE Pro window title bar).

    Thank you very much for looking into this, and for getting in touch with Native Instruments. Hopefully they'll have a fix out soon, as it would tremendously increase the usefulness of the Track Enable/Disable feature in VE Pro 6.

    Somewhat related, I think it would be extremely useful if VE Pro 6 could be configured to enable a track once it received any MIDI activity from the DAW on that respective track's MIDI channel. Having to set up parameter automation for each track in each VE Pro instance isn't an ideal workflow (for me).