Vienna Symphonic Library Forum
Forum Statistics

194,331 users have contributed to 42,916 threads and 257,955 posts.

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

  1. Home
  2. Software
  3. Vienna Instruments Pro
  4. VE Pro not playing well with cc intensive Kontakt instruments (LASS, The Trumpet) in Pro Tools
  • N
    N

    OK. Getting somewhere now.

    I took my main MacPro out of the equation and used one of my MacBook Pro slaves as the DAW and the other as its slave. I then loaded up numerous Kontakt midi tracks and they all worked fine.

    I guess that this means that the problem is probably at the MacPro end of the chain. Obviously this still needs to be my main DAW, so until a fix can be found (wherever the fault lies) VE-Pro is sadly unusable for me.
  • F
    F
    last edited
    last edited

    @Nick Harvey said:

    Incidentally I've just tried to create a new template omitting Kontakt altogether. Only using Omnisphere, when I reached the fourth midi track the 'no sound but obvious triggering' problem occured.

    This obviously indicates that the problem doesn't actually lie with Kontakt at all.

    Nick

    As posted here: http://community.vsl.co.at/forums/t/23126.aspx

    Also having troubles with LASS

    We need a fix for this as soon as possible...

    Mac Pro 2 x 2,93 GHz, 16 GB RAM

    OS 10.6.1

    Logic 9.0.2
  • N
    N

    Thanks for the link to the other thread. Yep, that's what's happening my end too.

    Sorry to hear you're having problems, but glad that Wolfsterik and I aren't the only ones encountering these issues.

    Nick
  • C
    C

    hanging notes here:

    LASS +

    Ensmeble 3 pro +

    Kontakt 3.5

    Driving me up the wall.

    Getting stuck notes on bank changes....a lot.

    I am also using VST expression maps.
  • M
    M
    I'm having the same problem. After reopening the project in Cubase I'm getting the error "please close and re-start Kontakt after a sample rate change" Then, not only LASS doesn't work properly anymore, even Galaxy Pianos has problems with CC64 (sustain). System: Quadcore, 8GB, Vista x64 Audigy 2(only supports 48Khz in ASIO mode) Software: Cubase 5.0.1 Kontakt 4.0.2 VE Pro DEMO (4881)
  • M
    M
    So are you still working on the problem? What I don't understand: Why is there a change in sample rate after all?
  • B
    B

    I'm happy to stand corrected on this point but as I understand it, Steinberg has Cubase send out a 44.1kHz 'ping' upon startup (why???), which if you're working at 48kHz is confusing for Kontakt (which is already open in VEP) which interprets this as a sample rate change.  If you just click OK on the message all will be well. 

    For what it's worth, LASS and The Trumpet are mostly behaing here, but I'm still on v4686!

    Brett
  • M
    M
    Unfortunately, just clicking OK doesn't solve the problem. Kontakt doesn't even recognize note-off-events anymore after reloading the project.
  • B
    B

    Try rolling back to v4686 and see if that makes a difference

    Brett
  • C
    C

    Hi Brett

    Does rolling back to v46868 solve the problem of:

    >Messed up scripting in LASS (awful hung notes etc on Legato specifically) after reloading a saved project with decoupled Ensemble connecting to  loaded meta frame containg Kontakt 3/LASS.

    It would be really, really good to save a Cubase 5 project and not have to worry about disconnecting from the meta frame/perserved instance every time to avoid corrupting the LASS banks/instruments.

    Surely there must be a fix for this!?.

    Cheers
  • M
    M
    Wow... In my case rolling back to the old version 4686 solved the problem. Now everything works as it should. Tested with: VEP 4686 Kontakt 4.0.5 running Galaxy Pianos and LASS Cubase 5.0.1 Windows Vista 64bit Audigy 2 @ 48kHz Unfortunately, my demo version is running out in a few days :D I think I will buy the full version, when the problem is also fixed in the latest build
  • M
    M
    Update: I just installed the newest version 5436. The problem was not solved. So, only v4686 works for me.
  • B
    B

    Glad you've got it sorted.  @Calculus, I had all sorts of probs prior to 4686 (documented in another thread) and so when everything settled down with 4686 I just stopped upgrading.  VEP does everything I need it to at the moment save for hosting PLAY reliably so I will probably stick on 4686 until that problem is addressed down the line.

    Brett
  • C
    C

    Cheers Brett have just reloaded 4686.

    The trouble is that dam cubase pinging out that 44.1khz sample rate at start up is a real pain as it breaks my Kontakt/LASS metaframe if it is loaded before I start up cubase (my default is 48khz and all my projects). LASS gets messed up everytime with the dreaded hangin notes on Legato. So if I shut Cubase at any point during the day, then I have to reload the whole template.

    The workaround of disconnecting the Slaves before saving Cubase project each time works but I can't always remember to do this.

    If only Ensemble pro ignored the ping from cubase......maybe the clever VSL guys can do this somehow. Or maybe Steinberg stop this pinging nonsense.
  • C
    C

    Vienna said earlier:

    'The bug you are experiencing will only occur at non-44.1k samplerates, and is related to Kontakt not being able to change samplerates on-the-fly. I have made a workaround for this, which fixes the problems with LASS and TheTrumpet. This will be included with the next update'.

    So what/where is the workaround?
  • K
    K

    We are looking into this. Unfortunately the main problem is the inability of Kontakt to change samplerate without reloading the plugin. No other plugin does this, so we'll have to make an exception for it probably.
  • C
    C

    Thanks Karel

    It would be really terrific if somethinig could be done, maybe soon?. Preloading and keeping open all day my Meta Ensemble Templates is not practical for me due to this instability, very, very frustrating.

    Kind Regards

    Calculus
  • C
    C

    HI
    After further investigation:
    My System Sample rate is now set to external sync at 48KHZ (by syncing RME Fireface as slave(autosync) to external soundcard set at 48KHZ. This totally eliminates 44.1KHZ behaviour 'ping' at Cubase startup. 48KHZ permanently on!.

    This now totally highlights (having got Cubase ping of the way) the problem with VSL/Kontakt limitation.

    Before starting cubase:
    1.Create new metaframe instance with Kontakt and LASS
    2. Open new Cubase project set at 48KHZ (never pings 44.1KHZ)
    3.Connect to Metaframe that was newly created.
    4. Play some notes, LASS legato is fine and works correctly
    5. Go to the connected Slave VSL Ensemble and turn audio engine power button off then on again.
    6. LASS is now corrupted as the Sample rate in VSL has switched from its 'default' 44.1KHZ to the desired 48KHZ. The corruption level can vary but it always happens. The same thing will happen by saving the cubase project.

    This clearly shows that when loading a VSL Metaframe (without Cubase 48KHZ project open) it will always load at 44.1KHZ as there is no way of setting a fixed sample rate in Ensemble Server or choose the current system clock setting.

    You can see the default sample rate in VSL Server by loading a new empty metaframe instance (without cubase open) and turning on the Audio engine power button. Instead of the sample rate being set to the current system setting of 48KHZ it ignores this and opens at 44.1.

    If VSL Server (on starting up) was modified to adopt the 48KHZ current system sample rate there would be no corruption. This is as long as the Cubase ping is eliminated with the hardware solution. Maybe Steinberg will get rid of this behaviour but this cannot be waited for.

    Finally, a temporary workaround:
    1. start Cubase project at desired 48KHZ
    2. Connect to all ensemble slaves with VSL ensembles in VSTi rack.
    3. Load kontakt and LASS sample instruments on slaves.
    4. preserve Ensemble slave instances and save metaframe
    3. Make sure decouple is not enabled as this new project needs to load at the start of next days work to get all ready for connecting to projects.
    4. Save Project as default Cubase project!
    Cubase can now be closed and restarted at will and all slaves remain fixed at 48KHZ enabling connection to any 48KHZ project that has the project saved with Ensemble decoupled.
  • F
    F
    Hi, Has anyone figured out a solution to this? I am having big problems with audio dropouts and stuck notes. It seems to particularly be a problem with LASS. I am running Logic 9.1.1 on OS 10.6.3 with VE Pro 5436 on the same machine. I have 18 gb of RAM on the machine and am running VEPro decoupled. My audio system is MOTU 2408mk3. I never have dropouts or stuck notes on the 64 bit server. I am running my sessions at 48k. I have read the threads about the problems Kontakt has switching from 44.1 to 48k but I'm pretty sure that I'm loading the metaframe at 48k. The MOTU is set to 48k as is Logic. I have the process buffer range set to medium. Any suggestions would be greatly appreciated. This is a real drag. Thanks, Fletcher
  • F
    F
    last edited
    last edited

    @AndrewW said:

    Fletchtown,
    You may want to go back to VEPro built 4881.  I ran across the same problem with hanging notes with the newest version. Yes there are few very interesting features, like force disconnect from the VEPro server, but not having hainging notes is more crushal.

    I've experienced this also on MacPro, Logic, VEPro combination. 

    Try the earlier version of VEPro and see if it solves your issues. 

    Best of luck.

    Thanks, I just tried that suggestion. Unfortunately, build 4686 (the most recent one I can find a build of prior to 5436) won't load the metaframes I have saved in version 5436. Basically, it's impossible for me to go back to a previous version. This seems to be a serious bug with VEPro and Kontakt. A response and workaround from VSL would be greatly appreciated.