Vienna Symphonic LibraryCompany Logo
  • Products
    Synchron
    • Synchron Series
    • Synchron Pianos
    • Big Bang Orchestra
    Starter
    • HELLO Free Instruments 🔥
    • Synchron Prime Edition
    • Special Editions
    • Smart Series
    Software
    • Vienna Ensemble Pro
    • Vienna MIR Pro 3D
    • Vienna Suite Pro
    • more...
    VI Series & More
    • VI Series
    • Freebies
    • Vienna Voucher
  • News
  • Music
  • Forum
  • Academy
    Instrumentology
    • Strings
    • Brass
    • Woodwinds
    • Percussion
    • more...
    Discover Strings
    • Violin
    • Cello
    • Double Bass
    • Harp
    • more...
    Discover Brass
    • Trumpet in C
    • Horn in F
    • Tenor Trombone
    • Bass Tuba
    • more...
    Discover Woodwinds
    • Concert Flute
    • Oboe
    • Clarinet in Bb
    • Bassoon
    • more...
  • Support
    Software Manuals
    • Vienna Assistant
    • Vienna Ensemble Pro 7
    • Synchron Player
    • Synchron Piano Player
    • more...
    Instrument Manuals
    • Big Bang Orchestra
    • Synchron Collection
    • Special Editions
    • Changelogs
    • more...
    Tutorials & FAQs
    • Installation iLok
    • iLok Video Overview
    • Sibelius Integration
    • FAQs
    • more...
    Company
    • About Us
    • Team
    • Press Area
    • Contact
    • Send a Message...
  • en|de
  • Toggle Light/DarkMyVSLMyProfile
    Login
Welcome Guest! To enable all features please Login or Register.
  • Forum
  • Active Threads
  • Search
  • Help
  • Login
  • Register

Notification

Icon
Error

OK


> FORUMS > Search
Search
Search for
Posted by
Forum
1.RAM and disabling Individual channels 11/19/2018 7:59:39 AM

Thanks Jasen - much appreciated.

2.RAM and disabling Individual channels 11/18/2018 8:21:54 AM

Thanks Paul,

Before I head down this path, if I was to stop using Aux channels and assign every instrument as plug-in, in my first instance I would have 140 instruments - so 140 uses of the Kontakt plug-in.   The chances are that I'm going to get to 4-5 instances.  While I will be able to offload all samples, reducing all the RAM would I be correct in assuming there's a downside (CPU?) to this approach?  

3.RAM and disabling Individual channels 11/17/2018 12:56:54 PM

Originally Posted by: civilization 3 Go to Quoted Post

It seems like you're saying that disabling them in Cubase doesn't change the samples load.

At any rate what you want is freezing the channel in VE Pro, which unloads its samples. There is a downside to this, if you have Host Automation in Kontakt it tends to not come back to the Automation Map when you unfreeze (this is true of Reaktor as well, I suppose for Native Instruments period).

Hi, and thanks.   

I don't think the issue lies with Cubase.  If I leave Cubase out of the equation and just disable tracks in VE Pro, the sample load stays the same.  It's not until I disable the VST instance I've loaed that the Sample load falls and every channel linked to that VST has its samples removed.

4.RAM and disabling Individual channels 11/17/2018 12:46:48 PM

Hi Paul,

Thanks and apologies for not getting back to you sooner - I thought I'd set things up so I'd be be informed if there was an answer. My bad...

It's probably best if I explain how I go about adding tracks.  the chances are I'm doing something wrong.

1) I right click in the left hand column of an instance, then go Insert Plug-in, VST - Native Instruments - Kontakt.  That loads Kontakt and I'm able to use what I've loaded as the first channel (track). 

2) I then go to the VE Pro Mixer page and add on channels (tracks) using the + sign above the outputs of the VST I've just loaded.  Those added channels are what I meant by "tracks linked to the plug-in"

If I disable those channels, it doesnt have any effect on reducing memory.  If I disable the first channel, it unloads not just what's on that channel, but everything else I've added under that VST instance.   I'd like to be able to reduce memory by disabling individual channels.

5.RAM and disabling Individual channels 11/6/2018 11:54:29 AM

Hi.  I'm not that familiar with VEPro so the chances are high that I'm probably after the impossible or, more likely, doing something wrong.

I've set up multiple instances of Kontakt in VE Pro with an average of 14 instruments per instance.  I've got them all working on seperate channels, in Cubase.  I can set things up so that I can I enable / disable VE Pro tracks from within Cubase (not pretty, but it works).  My reason for wanting to disable tracks is to offload samples on a track by track basis when I'm not using them. 

However, at the moment samples are only offloaded if I disable the track listing Kontakt as a plug-in.  Disabling tracks linked to the plug-in has no effect on reducing memory.  

Is this how it works, or is there a way I can disable individual tracks, offloading their samples at the same time?

Any help would be mch appreciated.  Thanks.

 

 

   

6.VEPro 6 and RAM 10/23/2018 9:34:15 AM

Hi,

Very much a newbie question...  I'm in the middle of bulding a large Orchestral template, using VEPro and Cubase.  I have 6 instances of Kontakt running in VEPro with approximately 84 instruments loaded.  I've purged all the samples, but VE Pro is still taking up 7 gig of memory.  I've deactivated all the tracks in Cubase - it doesn't reduce the amount of memory.

I'm on a 2012 Mac Pro, 6-core with 64 gig of memory.  I'm really only at the start of this template but if I'm running this level of usage at the start I can see problems well before I get to the end.   So - is this level of memory usage to be expected (84 tracks across 6 instances of Kontakt) and if so, are there any tricks I can employ to reduce it significantly?   

Any help would be much appreciated - thanks.

Loading...

Icon
Loading Search Results...

  • Forums
  • Search
  • Latest Posts
  • Terms of Service
  • Terms of License
  • Privacy Policy
© 2002 - 2023 Vienna Symphonic Library GmbH. All Rights Reserved.
This website uses cookies to enable you to place orders and to give you the best browsing experience possible.
By continuing to browse you are agreeing to our use of cookies. Full details can be found here.