Vienna Symphonic Library Forum
Forum Statistics

196,219 users have contributed to 43,015 threads and 258,397 posts.

In the past 24 hours, we have 1 new thread(s), 9 new post(s) and 165 new user(s).

  1. Home
  2. Software
  3. Vienna Instruments Pro
  4. Kontakt 5.3.1 issues

  • Kontakt 5.3.1 issues

    M
    M

    If anyone else has experienced issues with cpu crackles/ breakup in ve pro with sounds like Berlin WW , I have managed to solve it by reverting to Kontakt 5.3.0 . Thank the lord , I have been going mad for a few days with a new mac pro and ssds . Turns out Kontakt is the culprit.
  • C
    C

    Yes, I had the same problem. But interestingly Kontakt 5.3.1 only had the problem from inside VE-Pro.
    If I loaded a Kontakt instance directly from within Logic there were no issues. I also ended up reverting to Kontakt 5.3.0
  • E
    E
    Yep, issues here, too. FWIW, I'm not using Berlin WW but Berlin Strings and I'm having issues with it. More specifically, I think that some Kontakt scripts are incompatible with one another. I was having CPU and hard drive spikes (resulting in pops, cracks and audio dropouts) from playing a single note of Symphobia pizz strings. After doing some non-scientific tests, I realized that Adagietto and Cinematic Strings didn't like being in the same metaframe. Berlin Strings is also acting up when mixed with other libraries. Note that I don't mix different libraries within a single Kontakt instance, which is all the more worrisome. Unfortunately, I wasn't able to roll back to 5.3.1 (I regularly batch re-save libraries, which creates brand new Kontakt instruments, and prevents me from opening them in an older version of Kontakt). I'm on a fast MacPro with SSD drives, 64go of RAM, OS 10.8.5, and run all latest versions of VEP, Cubase and (unfortunately) Kontakt. Edouard
  • L
    L

    Me too! Big cpu spikes with pops and crackles in Kontakt 5.3.1 on my Mac.

    I'm testing out K5.3.1 on my sample server (Windows 7 64bit PC). 
  • P
    P

    Hmm, I thought it might be VEP 5.3.13240 which was a recent update. I'll try reverting to VEP 5.3.13151.
  • P
    P
    last edited
    last edited

    Reverting VEP did not help. Will revert Kontakt 5.3.1 to 5.3.0 now.

    @paul_18461 said:

    Hmm, I thought it might be VEP 5.3.13240 which was a recent update. I'll try reverting to VEP 5.3.13151.
  • P
    P
    last edited
    last edited

    So far having good results from K 5.3.0 and VEP 5.3.13240

    OSX 10.7.5, PT10.3.6, OSX 10.8.5, L9.1.8

    @paul_18461 said:

    Reverting VEP did not help. Will revert Kontakt 5.3.1 to 5.3.0 now.

    Hmm, I thought it might be VEP 5.3.13240 which was a recent update. I'll try reverting to VEP 5.3.13151.
  • M
    M

    As there are so many of us with this issue and reverting to Kontakt 5.3.0 in ve pro solving the issue can we ask anyone from vsl monitoring this to try to solve this because some libraries are only working on 5.31 such as the new embertone violin 1,5 . And we can't just blame kontakt because 5.3.1 works fine in logic x but not in ve pro .
  • P
    P

    Spoke too soon. Still having issues. Stuff that worked fine in K4.2.4 and VEP4.1.11889 doesn't work in K5 and VEP5. Not sure who the culprit is.

    Playing with thread count now. What fun....
  • E
    E

    Out of curiosity, what sound card is everybody using? Call me crazy but I'm starting to wonder whether I should blame my UA Apollo for this madness...

    Edouard
  • C
    C
    last edited
    last edited

    @EdouardB said:

    Out of curiosity, what sound card is everybody using? Call me crazy but I'm starting to wonder whether I should blame my UA Apollo for this madness...

    I don't think it is a sound card issue (using MOTU Ultralite here). It must be something somewhere between MacOSX/Kontakt 5.3.1/VE-Pro/Orchestral Tools. For a possible solution they probably need to get together in some way and do the trouble shoot in a groupe effort... IMO...

    Well, at least right now it works for me under Kontakt 5.3.0 while everything else is in its latest version. It just won't guarantee that it will work in future versions of Kontakt or even the other involved components...
  • L
    L

    Im on:

    Pro Tools 10.3.8 HD

    Mac Pro Inel Xenon 2.26 8 core 16GB RAM 

    Mac OS 10.7.5

    I get pops and crackles on all of my Kontakt Libraries.
  • P
    P
    last edited
    last edited

    Protools HDX2, OSX 10.7.5, PT10.3.6

    As far as I can recall, thing were fine with K4.2.4 VEP 4.1.11889

    @EdouardB said:

    Out of curiosity, what sound card is everybody using? Call me crazy but I'm starting to wonder whether I should blame my UA Apollo for this madness...

    Edouard
  • D
    D

    Has anyone contacted Native Instruments about this issue? If VE Pro is a supported host, NI should be able to guarantee that their applications work when hosted in it. Also, have you narrowed down whether or not it is an OSX problem or a Windows problem?

    Another couple of thoughts, if you're using OSX, have you switched the Kontakt memory sever off? Also, have you switched off Kontakt's multi processing?

    DG
  • S
    S

    I have the same problem and reverted to 5.3.0 fixed the issue. It only happens when Kontakt is hosted in VE Pro - directly loaded in Logic for example, Berlin Woodwinds plays back fine. And no, it is not soundcard related. So it seems to be a VE Pro issue with the latest Kontakt somehow.
  • P
    P
    last edited
    last edited

    I sent a report, but only sent the VEP project of the LASS instance with all the porta scripting that was displaying the problem. May not happen on it's own, I forgot to check.

    I run VEP 64 bit 4 threads, kontakt mem server off and mutliprocessor off. But my problem may be that there are 9 instances in VEP server. Finally shut off my gigas and each one of those is a VEP instance. That is probably not recommended, but it was working in K4.2.4 VEP4.1.11889 with only 2 threads per instance with those versions. There is a bug in VEP4 that it does not search for missing samples in kontakt. Upgrading was the only solution for that. Both NI and VSL didn't want to look at the older versions.

    @DG said:

    Has anyone contacted Native Instruments about this issue? If VE Pro is a supported host, NI should be able to guarantee that their applications work when hosted in it. Also, have you narrowed down whether or not it is an OSX problem or a Windows problem?

    Another couple of thoughts, if you're using OSX, have you switched the Kontakt memory sever off? Also, have you switched off Kontakt's multi processing?
  • M
    M

    I can confirm this as well . The issue is with Kontakt 5.3.1 hosted in ve pro not logic . 5.3.0 fixes it but ... It crashes when auditioning and means we can't use new updated libraries , so a fix is needed. 
  • T
    T

    I find it weird that all of you only seem to have this problem when using kontakt 5.3.1 inside of VEP. I am having, well maybe not very clear CPU spikes, but I can´t load more than about 70 instruments track in logic pro x using kontakt 5.3.1. When I reverted to kontakt 5.3.0 (and also had to go back to Moutain Lion) I can load around 150 instrument track in Logic Pro X. So Kontakt 5.3.1 is messing up my logic pro x template even if I don´t really get CPU spikes when using 5.3.1. 

    If I load my 150 channel template with kontakt 5.3.1 (well I can´t really load it because the cpu hits the top almost all the time, and get stopped samples etc etc..), I get CPU spikes when using berlin woodwinds samples, unplayable. 
  • P
    P

    Well I reported to NI several weeks ago and no response, no updates...
  • M
    M

    I'm having stutter issues too in 5.3.1 within VE Pro. Majorly annoying. I've worked around this by using 5.3.0 for now, but the problem is that newer Kontakt libraries are requiring 5.3.1 and it's becoming frustrating.

    Native Instruments is aware of the problem. See their email to me below:

    Hello Sam,

This issue seems to be caused by a bug in the current version of the application.

Thanks for your report. We have referred this issue to our developers and will try 
to fix it in a future version.  As a workaround we’ve found that changing the 
buffer setting may fix the problem. If not, the only fix is going back to 5.3.0 
for the time being.  

Nicholas
Native Instruments Support Team