Vienna Symphonic Library Forum
Forum Statistics

201,216 users have contributed to 43,235 threads and 259,215 posts.

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

  1. Home
  2. Software
  3. Vienna Instruments Pro (legacy)
  4. VE PRO 4.1.7043 - CPU Overload, Dropout Issues

  • VE PRO 4.1.7043 - CPU Overload, Dropout Issues

    J
    J

    System: 8-core Mac Pro with Mac OS X 10.5.8, VE PRO 4.1.7043 64-bit, Logic Pro 9.1.1

    Problem: VE PRO starts introducing small playback interruptions in VE PRO only (other tracks in Logic keep playing), with increasing timeouts as time goes on, most pronounced when the system has been left unattended for a time and continuing to work on it

    Details: 

    I have reported this issue before in the official announcement thread for 4.1.7043 and continue to have that problem. When I first start with a project in Logic, after loading a meta frame with various plug-ins (Kontakt 4, Omnisphere, etc.), initially I do not get any playback interruptions from VE PRO running on that same machine. 

    Working with that project for a while, VE PRO introduces these playback timeouts, that first start as small dropouts and then continue to increase in duration as time goes on. If I leave the system unattended for say, 30 minutes, the interruptions can last from 1-2 seconds, longer if the system is left alone for a longer pause.

    Interesting aspect is that I have VE PRO connecting to a slave workstation (Windows XP 64-bit), which does not exhibit those timeouts during playback, only the local VE PRO instance. All other tracks in Logic play back as expected, including audio tracks and virtual instrument tracks.

    The only way to eliminate the problem at that point is to shut down Logic and VE PRO to initialize VE PRO and start with small timeouts. However, once the timeouts occur, shutting down VE PRO will not perform normally and I have to force quit the application.

    Monitoring the CPU load while the timeouts and the final shut down occur shows that a single CPU will spike for the duration of the timeouts and on final attempt to shut down. During shut down attempts, the number of CPU the spike occurs will switch, meaning that it may start out on CPU 4 and then switch to 2, followed by 7, and so on.

    I hope all this helps getting to the core of the issue. To me it seems that VE PRO is starting some process internally on the Mac that is not resolved during those timeouts (spikes). 

    Let me know if you need any other input. My hope is that this can be resolved quickly, as it is impacting work significantly.

    Thanks,

    JB
  • K
    K

    Could you send crash reports and Console logs to ? Thanks.
  • J
    J

    Will do, Karel, although no crash reports are available, as VE PRO doesn't really 'crash'. I have to force quit it, so nothing is produced there, at least not that I have seen in the CrashReporter. However, I will send you the Console logs.

    Thanks,

    JB
  • H
    H
    Have you tried the previous version 6853 ? Cause I have similar problems with this lastest version.
  • J
    J

    Unfortunately, 6853 is exhibiting other issues across my systems, so for the moment I am sticking with 7043, even if I have the CPU problem to deal with on the Mac.
  • U
    U

    Yeah!

    I´ve got same problems with serious dropouts, where as my system was running relatively stable with non of these issues on VEPro Version before 7043. I was already wondering what could be the reason for this. So do think this problem came with the upgrade?

    Ritchie
  • P
    P
    Hi I wanted to chime in on this. I have a PC based system with 2 slaves running all my VSTi with VSL. After I installed 7043 I was having dropouts then after a while, my Host computer's cpu would start to overload after working in a session. Something would trigger it and it would crack very horribly until I released the VSTs and then reloaded them. When something made it go up past 60%, there would be some snowball effect where the CPU could not die down to a lower percentage and would then start to crack the audio. Unfortunately, at the time, I did not realize it was the upgrade that was causing this. I had made some changes to my system at that time and thought it had something to do with that. I actually switched DAWs because of it, and was on the verge of purchasing a new computer today, when at the last second I realized it may have something to do with the 7043 upgrade a while back. So I reinstalled the 6853 version and guess what.. system works fine now, like it did before. Now when it goes up to 50% or 60% for any reason, it dies down again and does not hover then spike out of control. Also the dropouts stopped. ***UPDATE!!!!!*** - I spoke too soon. The problem is back. When I opened up the key editor in Cubase, the cpu spiking and audio cracks came back with a vengeance. Well - back to the drawing board! :( ***UPDATE PART 2*** - I installed ViennaEnsemblePro-WIN-4.0.5436 and now its stable again. Does anyone have similar issues or is it just me? :)
  • K
    K

    That's odd. Could you e-mail  with this information, so we can handle this as a proper support case? Thanks for reporting.
  • P
    P
    Thank you, I just sent it in
  • K
    K

    What is your ticket number? I can't seem to find the case.
  • P
    P
    I sent the email to support@vsl.co.at But did not get a number. Is there another method?
  • P
    P
    Problem is back - it must be something unrelated to VSL since I used VSL on 10 scores and haven't had this problem before. It may be related to some sample rate change.... but I can't pin point it. Sometimes (not always) the cracking happens and I get this messae on my slave (please close and restart Kontakt after a sample rate change) However as far as I know everything is 48k
  • K
    K

    So the VE Pro version makes no difference? That is at least a relief on my part. It seems Kontakt is the culprit in this regard.
  • J
    J
    I've been having a similar issue with Pro Tools as the DAW, for me it seems that the latest release of VE pro is the cause, as that has changd and my Kontakt has not. I'm wondering if there is anything I would have to manually delete to go back to a previous version on VE Pro that the uninstaller would not get rid of. I was running quite well for a couple of months before upgrading and encountering this problem
  • K
    K

    The uninstaller removes everything except preferences. As a last resort you can find them in ~/Library/Preferences and /Library/Preferences. There are a couple of plist files there that mention VE Pro. They can all be removed if you want a totally fresh start.
  • P
    P
    All I can say is I've used VSL with no problems at all for most of this year. Then last month I started getting audio spikes and cpu audio overloads. I can work for 20-40min just fine and then it shows up. The only think I did was update Kontakt, VSL & put PLAY on my laptop. And the last two movies I scored had that setup with no problems. But then the overloads started about 4 weeks ago during that time I may have done an update on something. Since it's still doing it with earlier versions of VSL, then it must be something in regards to Kontakt. Kontakt is the only program that gives me errors about the 'wrong sample rate'.. and the sound does sound like clashing sample rates. However the Kontakt error doesn't always show up when this problem occurs, so hard to narrow it down.
  • P
    P
    I wanted to add a couple screenshots.. This is whats happening to my CPU when things start cracking -> http://img534.imageshack.us/img534/3179/cputf.jpg It hovers there and wont go back down unless I turn off the VSTs and then turn them back on again. Here is the same part playing back fine -> http://img14.imageshack.us/img14/1127/afterrest.jpg Then after a while - cpu goes back up and stays there. I want to say again - I've scored several films with my system and never had a problem with this. So it must be something with an update somewhere with Kontakt, VSL, PLAY..etc... Specs.. Windows 7 Pro(64bit) / Cubase 5.5.2 (32bit) Altiverb 6 Intel Core 2 Quad CPU Q9300 2.49 GHZ EMU 1616m 8 GB Of RAM ATI RADEON HD 4650 w/ dual monitors
  • K
    K

    What does the CPU meter in the VE Pro instances say?
  • P
    P
    I didn't think to look but I will next time it comes up. Also - are there recommend Kontakt settings for VSL? Things like whether or not to use multiprocessor support in Kontakt, etc... I saw something about memory management in Kontakt, but aside from the Instrument preload buffer size, it gives me no other options. thanks
  • D
    D

    Turn multiprocessor support off.

    DG