Vienna Symphonic Library Forum
Forum Statistics

184,673 users have contributed to 42,366 threads and 255,357 posts.

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

  • VI Pro2 GUI eats CPU

    So, I'm in my 30 day demo window...wanted to report that VIPro2 is doing something that neither VI, nor VIPro1 did--the GUI is doubling the CPU useage. I've got a full pop string arrangement going at 128 samples in Cubase 6.0. It's using about 20% CPU (per task manager)...but when I open one of the vipro2 GUIs during playback, it jumps to 45-50%! Close GUI, back to 20%. 

    Anyone else seeing this?

    Win7x64/c2q 2.4/8gb/1gbnvidia9500gt cubase 6(64bit mode). Echo gina3g card. 

    Anyone else seeing this? 

  • For the record, I was not on the latest build...I am now, but it has not changed the behavior. 

  •  Have you got the tuning curves switched on?


  • Yes. 

    1. Does it make any difference what view (basic/advanced) is seen when you open the GUI?
    2. Do you get the same issue when you open the Cubase video window?


  • Basic (taking away the curve graphics) makes no change.

    I will try the Cubase "video window" I need to find a video to play, or just open the window? Never actually used any video features in Cubase.

  •  Just open the video window and hit Spacebar.


  • Video window does not cause it. 

    More data:

    Standalone, 64bit vip2 does NOT exhibit the issue. 

    As plug in Reaper doesn't seem to have the issue...but, I can't get reaper to pass audio anymore--it's not an app I use, I installed it to demo last year and it must've lost all my config. 

    Lit actually spikes the CPU even when nothing is playing back--meaning, cubase open, song loaded, but not currently playing. 

    Turned off hardware video acceleration and the problem got a bit worse, so I turned it back on. 

    I will Update Cubase, since that's the only place this problem is showing...but, I don't know that I want to do that until my current project/session are done for fear of it causing some other issue. Thoughts? Are you guys using the latest version there on win7x64?

  • Decided the risk was worth giving you guys feedback while it was fresh in your mind. Upgraded from cubase 6.0 to change in behavior. 

    Again-doesn't even have to be playing back, so it's not like it having to update the GUI while playing is causing the issue. 

    Unrelated note, for anyone else reading, now bfd2 64bit crashes cubase. Off to get THAT update now. 

  • Latest bfd2 public beta fixes it's crashing. Tried other third party VIs...play3, bfd2, jbridged atmosphere, kontakt4, as well as old version of VI and VE. None duplicated the issue with vip2.

  • last edited
    last edited

    @popmann said:

    Turned off hardware video acceleration and the problem got a bit worse, so I turned it back on. 

    Turning down hardware video acceleration should never be done, it will only give worse performance. It does in fact sound like your system has some problems with video acceleration. Have you tried updating your graphics card drivers?

    Which CPU meter are you referring to when you speak of "20% jumps to 50% with gui open"?

  • I am also experiencing this problem.  When using VI Pro2 in standalone mode, I see a large difference in Windows Tasks Manager CPU usage depending on if the GUI is open or not.  With the GUI open VI Pro2 uses 30% of my CPU.  WIth the GUI minimized to the task bar VI Pro2 only utilies 5%. I get similar differences inside Cubase and when using VI Pro within Vienna Ensemble.

    I've assumed that something is being redrawn in the GUI very frequently.  Minimizing the GUI is an easy workaround, but I would like to see this fixed.

  • Actually, turning off acceleration, while it should yield worse performance, is solid trouble shooting for video overlay related issues. The fact that it didn't make it MUCH worse means they may be making a API call that my hardware isn't accelerating, and it's driver instead is passing it along to the CPU. 

    Task manager is the meter I'm looking at. Cubase's asio is not strictly a CPU meter...and it just jumps from 25% tp overs/glitches and back if you watch it during playback. 

    I have downloaded the latest nvidia drivers. Will install tonight, but even if that fixes this for me, this is something a good software dev will address if they can duplicate it. It's not like year old unified drivers should cause bug behavior like this. They can add that to their knowledge base, but they will want to address whatever API call they're making. If they're making DX10+ acceleration calls for a 2d instrument GUI, they should change the call. If it turns out its just some oddball card specific thing...might just suck to be me. 

  • What's odd, that I don't get that at ALL in stand alone mode. I wish I had another host to fully test. Reaper has always had plug GUI issues, and I really don't feel like troubleshooting it's config to get all the routing worked out. I have Logic on the Mac upstairs, but that really would only tell us if totally different hardware undera a totally different OS running at a totally different bit depth had the same issue. It likely won't--the VSL devs would've noticed this if it were happening across the board. If I had to make a prediction, it's that they (likely unknowningly) made a very uplevel DX call that a 9500GT isn't accellerating--and it's driver is hadning off the the CPU to full fill.

    Sorry, if that's too geeky. It's what I do for a living. And also why I HATE updating Wintel machines at home. I've FINALLY gotten a great performing Wintel 64bit machine...update one thing, and that can fall apart. See how the VIP2 demo has gotten me to update Cubase, which caused BSOD with BFD2, so I had to update, I'm going to update the video drivers...potentially chipset drivers if that doesn't fix it...I hope at the end of this, I still have a stable system. :) 

    ...I'm feeling more confident, because I bought a Korg Kronos a while back that means I only turn this thing on for string sequencing and drum editing. So, if it totally craps out, I'm not actually at work stoppage. And why I'm demoing the library extentions...and VIP2...looking to make it a dedicated string sequencing box, which is what it's really become anyway.

  • Latest nvidia drivers=no different behavior. If anything, between the cubase and now video driver updates, the over all CPU usage has gone up a few percentage points. 

    Also note, in stand alone, the difference in minimizing is about 7%-which technically is doubling the CPU usesge for a single live instance...but, I guess I didnt consider it because showing the single GUI in cubase takes it from like 20-25% to 50-60%, a much more noticeable jump. 

  • VIPro 2 is a pretty graphics intensive gui, since there is lots of visual feedback. But these graphical updates are running in a low priority thread, which will never affect audio performance. So even if you do see a jump in CPU on your task manager, this will not affect audio performance at all.

    There might be some optimizations possible from our side, which we will look into.

  • last edited
    last edited

    @MS said:

    VIPro 2 is a pretty graphics intensive gui, since there is lots of visual feedback. But these graphical updates are running in a low priority thread, which will never affect audio performance. So even if you do see a jump in CPU on your task manager, this will not affect audio performance at all.



    That is a really good point. Have a look at the ASIO Performance meter in Cubase to see if that jumps. If it doesn't, you have nothing to worry about. If it does, you still have a problem.


  • Yes, I have. As I mentioned the asio meter goes from about 20% to OVER causing the audio to glitch repeatedly while the GUI is up...only when the GUI is up. This is why I noticed the problem. Not like I'm hanging out looking at task manager! [;)] for fun. 

  • OK. I have isolated this further. It appears it has something to do with the particular couple of Cubase projects I'm working on. If I start a new project in Cubase...load up the VIP2--assign it a medium workload, whether the GUI is open or not, it makes only a slight difference on the CPU.

    So, I will trouble shoot it from here on out as if it's a Cubase project issue and report my findings to Steinberg (and here)...I don't know if it's something to do with some other plug in running in that project that somehow only manifests in VIP2...? Or the VST Expression maps being used in it...? Or just some sort of project corruption....? But, I can duplicate it 100% of the time in those projects, but not in a new one--even with VIP2 under the same or heavier workload. Seriously weird. And, people wonder why I hate computers so much. [:@] It's all I do every day--fix malfunctioning ones. Nothing I hate worse than working on my own when I get home. 

    Anyway, it does appear that VIP2 is only one ingredient in the "CPU eating reciepe" here.

  • project...same exact midi tracks (exported from the big project) jumps from 5-10% playing back to 25-30% with the GUI open. Not quite the same increase, but more than is acceptable. 

    Cutting the display to 16bit color buys a few percentage points, but just a few. 

    Im really not feeling good about buying this. If it means I'll need to replace my video card, too...adding up the library extensions, Ssd raid, and vip2, AND a new video card...getting to be quite a pricey upgrade. I do love the VSL chamber/solo sounds, but neither LASS nor the often maligned PLAY version of QLSO give me these system issues.