Sorry Paul, I was referring the threads / posts I've made. I'll send you an email.

Thanks for the info. I'm just wondering if there is a way to avoid "things sometime get clicky on dense passages" which essentially translates to "the software doesn't work". I'm assuming there isn't way to get VE and Pro tools to work properly as I can't seem to get a response from VSL.

I'm genuinely curious. Is ANYONE able to do this? On every system I've ever encountered, setting Pro Tools at less than 1024 samples while playing anything with over 5 or 6 tracks results in clicks and pops. This is on powerful systems too, including my 4.4 GhZ 64 gb sequencer+slave setup. Does VE just not play nice with Pro Tools? It's virtually unplayable at 1024 samples, because midi notes played in at 1024 buffer results in everything being way off the click. Vienna stuff gets so latent that you have to drag the midi a 16th note before the downbeat in order for anything to match up with click. This is a disaster for workflow and editing since after doing this for five or six tracks EVERYTHING is off the grid and it's a huge mess.

What can I do to sequence at a lower buffer size in Pro Tools (10 or 11, neither one seems to work better for getting Vienna to behave)? What gear do I need to buy? An interface that can handle VE's latency? Right now with VE everything just feels so messy when trying to write.

Is there any way to run at 512 or less withOUT getting inundated with clicks and pops? 

Still having the same issue.. bump

I've done some searches and I've found other threads with the same issue, but there hasn't been any answer as to whether there's a solution. See threads here: http://community.vsl.co.at/forums/p/29888/192076.aspx      -        http://community.vsl.co.at/forums/p/31191/198885.aspx

For me it definitely is related to the number of VE instances in my sequencer. With no instances connected, CPU usage in activity monitor on my slave is normal. For each instance I connect, it jumps quite a bit. With 6 instances connected (one each for strings, winds, brass, perc, pads, etc), VE's idle CPU usage is around 50%. I'm using Pro Tools 10.3.9 and an Mbox Pro 3 but as far as I can tell people have experienced this with all kinds of DAWs. And I'd be okay with cutting down to one mega-instance but Pro Tools only allows 16 midi ports per instance, so I would need at least 3 anyway.

Here's a screenshot of the CPU before and after connecting to Pro Tools: http://i.imgur.com/Fky4ZEO.png

Okay, well Pro Tools wasn't the issue. Downloaded the Cubase 7.5 trial, duplicated my PT template into Cubase, and still get the same crackle issues. In fact upping the buffer size in Cubase didn't really have an effect while at least at 1024 in PT it's a little better. Really stumped here. If it's not CPU (according to activity monitor), and it's not drive speed (SSD), not RAM (64 GB 1600 Mhz), what is it? VE?

Is that the one on the VE Pro plugin inside the DAW? (where it there are the options for 1 buffer, 2, 3, and 4?)

How sure are you that Pro Tools could be the problem? The reason I ask is that I've been eyeing up Cubase 7 for a while and if you're pretty sure that I could run at 256 or 512 in Cubase then that would be good enough for me.

What do you mean? The only menu I can find that is similar to that is the Vienna Ensemble Pro -> Preferences tab, which I've tried putting the multiprocessing option to many different settings. Is that what you are talking about or is there a different window where you can tweak this? If so I can't find it. Mine doesn't have the option for "Use Preferences Settings".

Right, I have 8 possible threads and 5 instances, so I originally had it set to two per instance. I've tried setting this to 2, 4, 6, 8 -- nothing seems to really make much of a difference.

I'm using DHCP with manual IP address on both machines.

I can't figure out why I can't just get my template to play cleanly without any drop outs or crackles in thickly orchestrated places. I have a brand new slave: Mac Pro, 3.8 Ghz Quad Core i7, OSX Mavericks 10.9.1, 32 gigs of 1600 Mhz RAM, VEP5, and a 1TB Samsung 840 Evo SSD streaming samples. This connects to my other Mac, a less powerful 2.4 Ghz Quad Core i7 sequencer on 10.9.1 with 16 GB of RAM, that is purely dedicated to Pro Tools 10.3.6 (also tried PT 11.1 which didn't provide better or worse results).

I'm not brand new to these kind of setups so I've tried a few things, but I just can't get everything to work as well as it should given what I've just invested in in terms of specs. My samples are all kontakt libraries, and again, streamed from a very fast SSD. I connect to them through 5 instances of VE Pro 5 (Master, Strings, Brass, Winds, Perc). Most of the time it plays fine, but at dense parts it can crackle and drop out (at 512 buffer size). If I bump it up to 1024 then it plays cleaner, but at that point the latency is just unmanageable in terms of playing things in.

I'm not sure why I can't get 512 to work consistently. Sometimes it's fine, other times it struggles. When I play a sequence and look at the activity monitors for both computers, the CPU on the sequencer hovers at about 4-5% (it's just receiving audio), and the slave/sampler runs at about 25%. So I don't think it's CPU, and with an SSD it's unlikely to be disk speed either. What's the problem here? Is there anything I can do to optimize my setup?

Some additional information: Delay compensation in Pro Tools is ON; I'm connecting to each instance with a VEP RTAS set at 2 buffers (changing that to 4 doesn't seem to make a difference), and the threads of my slave are set to 4 thread per instance (again, changing these settings doesn't seem to make a difference to the CPU in activity monitor). If I can optimize any of these settings to get a better setup, please let me know.

Okay so I have two macs (both on 10.9 Mavericks), and I'm trying to set them up with VE Pro, where I have the slave mac streaming samples to the sequencer/master mac (which uses Pro Tools). When I open a VE Pro plugin in pro tools and click on connect, I don't see any metaframes -- even if I have 5 metaframes open on my slave. Then, if I enter the IP address of my slave into the address box and hit connect, it DOES connect and it opens a new, blank metaframe on the slave side.

I'm wondering if anyone can help me get this set up properly. I've been on rigs with VE Pro over the network before and I know that when you open the plugin , you should see open metaframes and the IP address of the machine that each metaframe is on.

Granted, I'm not sure if I've set up my "network" properly. I have the two computers connected via cat 6 ethernet cable, but aside from that I'm not sure what I have to do make the two computers networked together. The IP address that I can find for my slave is 192.168.1.8 -- wondering if that's what it should be. Is there another address that I should have for it? Because I know that 192.168.x.x is assigned by the router, right? What am I doing wrong?

bump

This feature allows you to reduce the amount of samples loaded into RAM. But when I activate it and reduce the buffer to something lower like 30 kb (default is 60), the loaded RAM doesn't change. However, in a Kontakt instance inside a DAW, changing the buffer size automatically reduces the amount of RAM loaded (you can see the instrument's RAM usage drop from 300 MB to 150 MB, for example). Can you do this in VE Pro? Right now I can't tell that it's working.

problem just started again, audio gets lost on it's way to the master bus.

Kontakt -> input 1 -> Master bus

The input 1's metering is getting audio, but the master bus is not. If I restart VE and Pro tools sometimes this problem doesn't happen.

I have never experienced this before until yesterday. It's a horrible issue and has cost be a ton of work time. Basically I normally run with 5 viframes in one metaframe, all connecting into Pro Tools 11. All of a sudden, sometimes when I open my session, one of the sections (It's always the Strings frame) just won't create sound. Here's the strange part -- the audio is getting lost somewhere INSIDE Vienna Ensemble Pro. If I press play, I can see the midi data coming into the Strings frame, going to the strings in Kontakt, out to an input in VE (I can see the audio in the meter), and then it disappears. I have that input going to the master bus inside VE, and it's just vanishing. The input channel strip's output is set to 22 Master Bus, but when I look at the 22 Master Bus track in VE, there is no audio peaking the meter.


I tried just bypassing the Master Bus and setting the input channel's output to OUT 3/4 (which connects to an aux in Pro Tools received on VE Plugin X 3/4. But the audio still disappears. I have no idea what's going on.


I figure it HAS to be the software because if I completely shut down Pro Tools and Vienna, sometimes it will work again, loading the exact same saved metaframe and session. Suddenly I hear the strings upon reloading everything, but it's not consistent. Normally I would chalk this up to a Pro Tools problem -- especially because it's a new version (11), but the fact that the audio is not making it from Strings Input to the Master Bus in VE leads me to believe it's a VE issue.

Any idea what's going on here?

Some spec info: this is with the two most recent versions of VEP (tried updating in order to fix the problem), with 10.7.5 Lion.

Basically what I'm wondering is if there is a way to have 17 midi channels in Kontakt, in one Vienna Ensemble project viframe. Is this possible to do with Kontakt? I would like to use a second midi port but in Kontakt Port B, C, and D are all marked as unavailable. I'm using Pro Tools as my DAW and I would love to be able to use midi ports in VE to have more than 16 instruments in one viframe.

Is there a way to do this?

Is this possible? I've found tutorials on Youtube and followed the directions exactly (this video in particular: http://www.youtube.com/watch?v=3edatjdUXu0), but I get the following error messages in the bottom left corner of Kontakt 5:

SCRIPT WARNING: wrong group index in allow_group!

SCRIPT WARNING: get_engine_par_disp() non-existent group!

I was trying to get LA Scoring strings to keyswitch in Kontakt but so far I haven't had any luck. Anyone know what's going on? I'm guessing it has to do with the method of copying groups of samples, such as the staccato groups from a staccato patch, and then pasting them into the main group of the legato instrument -- I've made sure to set each set of articulation samples to a different keyswitch but something must be wrong with some scripts as I keep getting those messages.

Anyone know what is going on? Help would be greatly appreciated.

that was it, thanks!

As far as I know I have the latest version of Vienna Instruments/Ensemble. The version of Ensemble that I am running is 4.1.11515. I am on Mac OSx 10.7.4 by the way.

I can load Vienna Ensemble in Pro Tools just fine. And if I go to the /application support/library/audio/plugins folder I can see ViennaEnsemble.component, ViennaEnsemble.vst, and ViennaEnsemble.vst3 in their respective folders.

So I think the plugins are on my system I just can't get Sibelius to see them. I've tried using a previous version of Sibelius 7 and then I just updated to 7.1.3 last night and tried again and still nothing.

Hi. I've looked around the internet and determined that to use VSL in Sibelius I need to set the playback device to Vienna Ensemble. However, Vienna Ensemble is nowhere to be found in my audio devices. Instead I have Kontakt, Default Midi, and Vienna Instruments. I'm confused as to why Vienna Instruments would be there but Ensemble isn't. Anyway I think I know the subsequent steps to get it working but I'm roadblocked by my inability to make Ensemble show up in Sibelius's devices. Does anyone know how to fix this? I've tried reinstalling Vienna Instruments but that didn't help. I've also already pasted the sound set files into the sibelius directory, as well as the house style file.