Vienna Symphonic Library Forum
Forum Statistics

200,700 users have contributed to 43,207 threads and 259,118 posts.

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

  1. Home
  2. Software
  3. Vienna Instruments Pro (legacy)
  4. Freeze in Cubase & Logic doesn't Freeze!

  • Freeze in Cubase & Logic doesn't Freeze!

    M
    M

    I thought I wrote a thread about this but cannot find it - maybe it's in another section - if so, my apologies.

    I have written to VSL support about this to try and find out the answer, but thought I would post on the forum as well just to try and see if anyone else is having this problem.

    I'm finding that if I have various instances within the VE Pro 64bit server loaded, obviously I can freeze those within Logic or Cubase, and they should cut the CPU of those specific instances to zero, but that is not happening. Although the CPU load goes down with each freeze, the more instances I have open (but frozen) there seems to be some kind of latent cpu drag going on even when they are switched off / frozen - and this is building up to the point where even when all 6 - 7 instances are frozen, it is dragging so much on the CPU that it cannot play back. The solution to this is to set a larger buffer size in Cubase / Logic, but this shouldn't need to happen. I'm one of those people who likes low buffer times so I can perform parts more accurately.

    Isn't it right that if you freeze and instance, it should more or less cut that instances CPU drag to zero - ?

    The only plug ins I'm using are VSL suite plug ins, and a couple of instances of SSL, but even with none of those there is still a problem. I'm having the same problem when freezing instances of VI Pro within Logic or Cubase - once I get to a certain number of instances, the latent cpu drag from all of them just being there, even those frozen, seems to build up until the machine is unuseable. With any other software instrument, you would normally get nearly 100% of your cpu back when freezing, but that doesn't seem to be the case.

    I've been told this is unusual - anyone else having this problem? 
  • D
    D

    I've tried Freeze with my template on a number of occasions, and the CPU usage goes back to virtually nothing. I can see why this problem could occur in Logic, but can't confirm that it is happening here in Nuendo. I keep my buffer at 128. Could it be a bug with the latest version of Cubase or even an OSX thing?

    DG
  • C
    C

    That certainly sounds wrong.  I used to use Logic and when I would freeze I would gain tremendous CPU resources back.  Especially when using VSL products.  Additionally, I now only use Presonus Studio One.  It doesn't even have a free function yet.  I have to use bounce intrument track to audio track.  Even doing this all it does is create an audio track, then mute my original VSL sample track and I STILL save a ton of CPU so you're situation is definitely unique and something else is going on (or a bug).  Wish I could offer a solution but at least I can offer some information (helpful hopefully).  Cubase should be handling this with complete ease and giving you back tremendous amounts of CPU resources back I would think.

    Good luck,

    Maestro2be
  • M
    M
    last edited
    last edited

    @DG said:

    I've tried Freeze with my template on a number of occasions, and the CPU usage goes back to virtually nothing. I can see why this problem could occur in Logic, but can't confirm that it is happening here in Nuendo. I keep my buffer at 128. Could it be a bug with the latest version of Cubase or even an OSX thing?

    DG

    I have had this problem going back four years now, but I thought it was an inherent part of the server design. However I'm not using Logic at the moment, only Cubase 6.0.2. Even if I freeze with the "unload instrument" button checked, there is still a latent cpu drag coming from the vienna instruments. I must literally delete / remove the instance from the VE Pro server, then I get my cpu back. Of course the instance is powered off as well. It seems there is something causing each instance of vienna instruments pro to have a latent cpu drag whether it is on or off, just by being in memory.

    Well, I'm very glad to hear this is not normal, because that means there is a solution - but what on Earth could be causing this?  

    To be clear: everything is on the latest update: Cubase, the Mac, VSL software, etc.

    I am also running software instruments in the 32bit version of VE Pro, and when those are frozen, I get all the CPU back. Also if I load 64bit instances of Spectrasonics software into VE Pro 64bit, when frozen I also get the CPU back from those, even in large projects. The problem is there whether I have plug ins or not. It appears to be Vienna Instruments Pro - but I had the same problem with Vienna Instruments, as I said, going back at least four years now, through multiple software versions, re-installations of VSL software...

    What could be causing this!?? I really need to get it fixed, because it is limiting my project size - I get to the point that I can no longer perform new parts as I have to set the buffer setting too high. Unloading instruments is tiresome cumbersome and not practical again for time reasons. 

    Just to be clear, the problem appears not to be connected in any way to the amount of sample ram used, instead, it's directly related to the number of vienna instruments instances loaded (not server instances). This is true whether they are loaded as individual instances within Cubase or other host, or within Vienna Ensemble.  Hopefully that will narrow it down?
  • M
    M

    BUMP! No one? - I still don't have a solution - it seems no one else has this problem but what could possibly cause it? It seems from my experiments, the problem is directly tied to vienna instruments and vienna instruments pro, not ensemble pro, cubase, or logic...??
  • M
    M

    Ok well since nobody has any suggestion and since I need to get this fixed I'm going to do a full system install - wipe the whole machine and start again. BUT before I do would anyone from VSL please be able to confirm that no matter how many instances (20 - 30 - 50 etc) of Vienna Instruments Pro are running, if they are switched off in VEPro, they will NOT drain the cpu *at all*? Then I can be sure that I'm not wasting two days doing this.

    Thank you!
  • D
    D

    I would suggest that you send this question directly to support as well, in case the VSL powers-that-be don't see this thread.

    DG
  • M
    M

    I have - no solution, not much help to be honest, I got a copy and paste from the forum about thread counts - not relevant to my problem.
  • Cyril BlancC
    Cyril BlancC

    Are you using VE pro server 8008 ?

    If yes, freezing track will NOT improve system load.

    You need freeze track and remove the VI from VE  or VE from the VE's PRO server

    Can you put your configuration in your profile so it is in your signature

    Best

    Cyril
  • M
    M

    Yes I checked and it is 8008 - why is that it will not improve cpu load - is this an old version? I thought it was the latest version? How come earlier versions are apparently *not* doing that? Also, I am having the same problem even if I do NOT use VE Pro but load just VIPro into the host, be it logic or cubase? Why is there a latent CPU drag on the host just by virtue of the instrument loaded into memory (even if switched off completely, and even with no samples loaded)!?

    specs:

    Mac os 10.6.7

    Latest VSL

    Latest Cubase (6.0.2)

    Latest Logic (althoug not using that at the moment, happy to just get cubase working).

    8 core Mac intel xeon 3ghz 16Gb RAM.

    With 30 - 40 instances of FROZEN Vienna instruments, system cannot play back any more. I must manually unload the instruments. The problem with that is that usually one can work with two or three instrument groups at a time, and freeze the other 3, but once the project becomes that large, I can work with one, or none! Freezing becomes slower, and so the whole thing becomes unworkable. This is a major issue!! I hope there will be a solution!
  • Cyril BlancC
    Cyril BlancC

    Hi

    Can you explain where are your lib, your frozen tracks, your system ........, what kind of disk your data are on ?

    Did you look how much memory is used ?

    Look in system memory in activity monitor ; can you report the values when you have load the project that is making problem

    Best

    Cyril