Vienna Symphonic Library Forum
Forum Statistics

199,075 users have contributed to 43,152 threads and 258,889 posts.

In the past 24 hours, we have 3 new thread(s), 15 new post(s) and 69 new user(s).

  1. Home
  2. Software
  3. Vienna Instruments Pro
  4. Could not load plugin (K4.1 and VePro4.0.5814)
  • N
    N

    I am also having this problem when I load up a new project in DP7.2 (and all the previous version of DP) using the latest VE Pro.  It only happens when I'm actually loading the DP project with VE Pro open.  And if I have another K4.1 Player, only the first instance says it cannot load the plug-in.  I'd be happy to send a console report.  Please let me know if you want me to.

    Interestingly, a way around this problem is to save the metaframe and open VE Pro and the saved metaframe AFTER the DP project is open.  When I do that, the metaframe loads just fine.  But it is a hassle.
  • A
    A

    I've got the same problem but in VePro was instaciated Play.

    So, very confused, it's a shared 3d parts problem or VePro ?

    The strange is : i've loaded  the same project many times, to work on it,  but suddendly i've got "could not load plugin"

    -A
  • K
    K

    Is there any way to reliably reproduce this problem? So far I haven't had any success unfortunately.
  • M
    M

    We will try to reproduce this problem and get back to you ASAP.

    Kind regards,

    Maya
  • A
    A

    ..again, if i open the source template i get no problem at all. Maybe the problem it's Logic-> Save PJ->VePro etc......?

    -A
  • A
    A

    ...another hint : if the mac i am using as a slave is disconnected from the ethernet :

    No crash on exit even if Kontakt4 is instanciated.

    -A
  • T
    T
    I get this issue now as well with 4.0.6150 and Kontakt 4.1 on a Mac as Master and PC as slave. I thought it was mainly happening with Libraries. I just reloaded the instrument and patch and saved and reloaded and it loaded fine. It is difficult to get this to happen consistently. Can anyone confirm if it happens loading regular sampler instruments as well?
  • F
    F
    last edited
    last edited
    Thanks "anton" I was having he same problem with Kontakt 4.1 and Omnisphere and your workaround is working for me. I opened various Cues in DP7.2, repairing the missing plugins with saved Metaframes an projects, added the ghost Vienna Instrument at the end, resaved an all works great now.

    @anton said:

    Same problem in 4.0.6150. Could not load plugin if Kontakt 4.1 instanciated as a last plugin in the chain.

    Workaround is to load a "ghost" Vienna Instrument at the end.

    But it's just a workaround.......

    -A
  • A
    A

    ;-)

    -A
  • T
    T
    Anton deserves some serious Kudos for his workaround. Since applying it to all of my VEP instances that have Kontakt loaded I have not seen this issue since. This is a minor inconvenience for a nightmare bug. I have not tried Play yet since I did not know it was compatible with VEP yet. But I would think that the fact that there needs to be a dummy plugin sandwiched after a 16 channel multi-timbral (and multi-output) sampler like K4 or Play would identify there is an issue with the way VEP is saving that VEP instance when there is a single instance of the sampler loaded. Maybe it has something specifically to do with plugins that load large multi-sample libraries? I also sent an email to support confirming that some earlier bugs that existed with VEP and certain softsynths that were eradicated in the previous build came back in this build of VEP.
  • A
    A

    Still Crash on "Exit" on slave mac in version 4.1.6776.
  • A
    A

    Still on 6853.
  • L
    L

    Same problem crash on exit and could not load plugin ...

    VSL 7043 !
  • A
    A

    Strange : without any advise i get the last Vienna Instrument in Vepro no patch loaded.

    In 4.1.7043
  • civilization 3C
    civilization 3C

    Make sure Kontakt Memory Server is OFF. Also, in a host, do not use multiprocessing option in Kontakt.

    Also, if you are instantiating Play engine, it has a memory server and the two memory servers on OSX will probably not work together. It will crash at the last instantiation of one or the other, was my experience.
  • A
    A

    Thanks for sharing your informations. The problem is different.
  • N
    N

    Hi all.

    Any news on a fix for this yet?

    Best.

    Nick
  • S
    S
    Ran into this bug again today and it set me back quite a bit. Any official word yet? Is it definitely tied into the kontakt/play memory server? This seems to be the only bug that really gets in my way, would love to hear an official word from vsl. Seems to be tied in to plugins/instruments with high memory requirements. and therefore i see it mostly with Kontakt. Has popped up with Omnisphere too.
  • D
    D

     It seems to be solved with Kontakt 4.2. - since yesterday in a public beta test. All the issues (I've had some on my system) are gone away.

    But one new weird thing happens: In a reloaded metaframe in every Kontakt instance every instrument has loaded TWO times...???

    So if you want to avoid this wait for the official Kontakt version.

    For me that update is a very big improvement and this issue is not a big problem.

    With the new K 4.2. version seems clear now, where does the issues are coming from...But I'm far away to running down K 4. In this spinning world it will be not so easy to build a VSTi that fits in every host. They have heavily worked on this. That's great!

    Frank
  • T
    T
    Have all of the Kontakt Issues been worked out with 4.2.3 and 5.0.1? Does Kontakt still have loading issues with VEP? Either blank instances or Could not Load messages? I have avoided using Kontakt on my slaves but would like to start doing so again. Is it the version of Kontakt or VEP that needs to be updated? Logic is my DAW. Please advise.