Vienna Symphonic Library Forum
Forum Statistics

196,693 users have contributed to 43,029 threads and 258,427 posts.

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

  1. Home
  2. Software
  3. Vienna Instruments Pro
  4. Optimizing VI memory usage to avoid clipping

  • Optimizing VI memory usage to avoid clipping

    S
    S

    I bought a new mac mini I-7 quad to run my orchestral samples which includes the dimension strings and brass and MIRx (which all sound incredible by the way). I have 16GB of ram and the samples are split between 2 500GB SSD drives. I was told that this should handle my VSL library and allow me to run everything simultaneously however I am getting clipping and it appears I'm overloading my CPU. I've been adjusting the settings (preload size is set at 1536, I upped the voices to the max) and nothing seems to be helping. Not sure if it's just a case of the mac mini not being able to handle the load or my ignorance on settings adjustments.

    I was looking at picking up up Vienna Suite but if I can't run what I've got and need to get yet another slave computer then I'm looking at additional software purchases just to try to maintain what I have. Any ideas?
  • Cyril BlancC
    Cyril BlancC

    What DAW do you use ?

    What are is your I/O buffer size in your DAW ?

    Does you Mac mini have SATA III ?

    How are your SSD connected ?
  • civilization 3C
    civilization 3C

    Raising that preload buffer serves to take some load off of CPU in favor of RAM. I think that setting is a lot lower the the default, so you could raise it considerably.
  • S
    S

    I use dp. The ssd are internal sata III. The buffer is set to 512
  • S
    S

    I'll try adjusting the preload. Going to be trial and error to figure this out but I have to be able to play more samples than I am.
  • Cyril BlancC
    Cyril BlancC

    you can gain by using IAC and going to 1024 in your DAW

    You can also put Your VSL lib on a Raid 0

    To chose the right pre-load buffer in the Directory manager you must proceed this way

    you chose a passage where it is clicking. 

    Put it in a loop

    Solo all tracks until you find the one(s) that is clicking, then set the preload buffer bigger for this instrument(s) until you dont get clicks

    I have find out that Trumpet in C,Trumpet 3, Oboe and Oboe d'amore need a bigger preload buffer, I have not finish my trial but putiing those instrument to "Normal" fixed my problem
  • civilization 3C
    civilization 3C
    last edited
    last edited

    @Cyril said:

    you can gain by using IAC

    Gain what? CPU? I think not.
  • S
    S

    Here's what I'm finding now....

    It appears the big culprit was the latency setting on MIRx. While the clipping has disappeared, I'm starting to get the red line in the voices section of VI Pro within VE Pro 5. So now I'm trying to figure that out and see just how low I can set the latency on MIRx without killing the sound.

    I don't think any of the settings on my main computer or DAW have anything to do with the clipping on my slave. It's all slave CPU related.

    The learning curve on all this has been massive but I think I'm getting there.
  • Cyril BlancC
    Cyril BlancC
    last edited
    last edited

    @Cyril said:

    you can gain by using IAC

    Gain what? CPU? I think not.

    Have you try ? 

    I did try with Logic + IAC !
  • civilization 3C
    civilization 3C

    The latency of a reverb plugin shouldn't be of much moment to you. Give it as much as you have to.

    Do not use IAC. It is in fact going to add latency to your system needlessly. These comments are red herrings.
  • civilization 3C
    civilization 3C
    last edited
    last edited

    @Cyril said:

    you can gain by using IAC

    Gain what? CPU? I think not.

    Have you try ? 

    I did try with Logic + IAC !

    Why would I try? This adds latency, needlessly. You have fundamental misconstructions of what VE Pro does, apparently. VE Pro works well. It is made to obviate these little things you believe in. You're adding complications, adding a driver and its latency into something that works. You like a solution that isn't a solution to any real problem. You're actually giving the CPU MORE TO DO!!! There is no gain, there is only a loss.

    This whole kind of thing is you taking every opportunity to talk about things you like to futz around with for no good reason; it's not helping, this is a big red herring.
  • Cyril BlancC
    Cyril BlancC
    last edited
    last edited

    @Cyril said:

    you can gain by using IAC

    Gain what? CPU? I think not.

    Have you try ? 

    I did try with Logic + IAC !

    Why would I try? This adds latency, needlessly. You have fundamental misconstructions of what VE Pro does, apparently. VE Pro works well. It is made to obviate these little things you believe in. You're adding complications, adding a driver and its latency into something that works. You like a solution that isn't a solution to any real problem. You're actually giving the CPU MORE TO DO!!! There is no gain, there is only a loss.

    This whole kind of thing is you taking every opportunity to talk about things you like to futz around with for no good reason; it's not helping, this is a big red herring.

    Civilisation, Stop speaking things that you dont know about

    IAC is and internal of MAC OS X, it behave faster than VSL Event input plug-in with Logic and it does the same. 

    VSL plug-in is kind on IAC, it adds internal midi ports

    All my setup is running with IAC !