Vienna Symphonic Library Forum
Forum Statistics

190,362 users have contributed to 42,737 threads and 257,119 posts.

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

  • VEP Server 32bit (4.0.6150) crashing when removing last Kontakt 4.1.1.3832 instance under OSX 1...

    I have 2 near identical Mac Pro slaves, and on one of the 2 slaves, every time I remove the very last instance of Kontakt (4.1.1.3832) from VEP Server 32bit (4.0.6150), the VEP Server "Quits Unexpectedly". They are both running OSX 10.6.4 all fully updated with the latest NI Plugins, VEP, OS etc. 64bit server works fine on both with no hitches. The crash only occurs when removing the _very_ last instance of Kontakt 4.1.1 from the 32bit server (i.e. by deleting the last K4 plugin from the last VE Project instance, or deleting the VEP Instance that contains the last Kontakt, or by quitting the VEP server 32bit.)

    I have tried repeatledy manually un-installing (including all Support Files, User > Support Files, User > Preference Files, Plugin > Components/ VSTs, Application Files etc etc.) and re-installing both NI Kontakt 4, NI Service Center and VSL VEP. This has not changed the behaviour.

    I have tried various combinations of MultiThreading between VEP & Kontakt with no change in behaviour. I have tried enabling and disabling Kontakt Memory Server with no change in behaviour.

    The 2 systems are nearly identical, both are 8core (16 virtual) Nehalem Mac Pros clocked at 2.26. Both are running the latest versions of all software.

    Here are the differences I do know about:

    - The non-crashing system has 6x2GB RAM chips // the crashing system has 6x1GB RAM chips (but this is unlikely to be the issue as I'm only running empty MetaFrames for testing purposes with lots of free RAM and it's still crashing consistently, every time.

    - The non-crashing system was installed entirely from scratch on a clean install of 10.6.4 // the crashing system was uprgraded to 10.6.4 from 10.5.8, and also has Kontakt 3.5 installed alongside Kontakt 4.1.1 (I haven't yet tried uninstalling Kontakt 3.5, because I _REALLY_ want to keep it running for back compatibility with the old slave system we were using with MOLcp and standalone Kontakt 3.5!

    - The non-crashing system has no additional MIDI drivers installed // the crashing system has MOLcp MIDI over LAN installed presenting Kontakt and VEP with extra MIDI ports compared to the non-crashing system.

    - The non-crashing system has no additional audio interface // the crashing system has an RME RayDat 8xADAT card installed running the very latest driver and firmware. (This is what we were using for audio return with standalone Kontakt and MOLcp). It needs to stay for backwards compatability with the older setup.

    Please help! [:|]


  • <BUMP> I could really do with one of the VSL support team/ developers to take a look at this for me. Pretty please!


  • last edited
    last edited

    Send the crash log to support@vsl.co.at

    DG


  • Hi,

    I´m pretty sure that our developers already try to reproduce this behaviour. Sometimes we take the liberty to wait and see if someone else is reporting a similar behaviour, over the weekend.

    Best, 

    Paul


    Paul Kopf Product Manager VSL
  • This crash occurs in Kontakt 4 rather than VE Pro. I also haven't been able to reproduce it as of yet. I recommend contacting Native Instruments support and giving them the crash report as well.


  • Hi,

    I´ll have to confirm this: No crash on 10.6.4 with the latest Kontakt 4.1.1.3832

    Really strange that this happens on only one of 2 "nearly" identical machines, however "nearly" is defined.

    Best,

    Paul


    Paul Kopf Product Manager VSL