Thanks. That's very helpful information.

I'm rewriting this post. I just got the Overdrive Guitar and I was thinking that the legato wasn't working right because it sounds like there is an attack between notes in the legato. But then I got to thinking about it and realized that there would be an attack (or a pluck or pick sound in the case of the guitar) even between notes in sustained lead since that's how the guitar is played. But certain steps would not have a pluck if they are "hammered on" or a slide or fast runs that are like extended hammering. So  I guess I'm starting to figure this out a little. Any advice, tips, tricks that you know of how to use the articulations effectively would be very helpful. Or maybe someone has worked a tutorial on this somewhere.

OK. VSL figured it out. Turns out the instrument wasn't actually installed. I think I got thrown off by the fact that it was a downloadable instrument.

Paul, 

I did all that. The software is build 8008. Plus I erased and added the folders again.

I'm using  a Mac  with OS X 10.6.7

I already went and got the latest version of the elicenser6.3.1.1066. So I'm ok there. Also the OD shows up in the license control software and it shows up on the left side of an instance of Vienna Instrument Player as a license that is installed on this computer. It just doesn't show up on the right where you choose presets, matrixes or patches.

 I just bought overdrive guitar, downloaded it, installed it. But it won't show up as a choice when I open an instance of Vienna Instruments player. Why is this? It shows up in the Directory Manager and the path appears correct. As far as I can tell everything says it's installed and available yet it's not showing up like all the other instruments I have installed in the same place. Can somebody please help me?

Karel. Thanks for speaking up and making that clear to me. I've been using Pro Tools 8 LE all this time which didn't have automatic delay compensation built into it. I think I got thrown off by the VE Pro manual where it says, ”The Vienna Ensemble
PRO Server Interface plug-in automatically compensates the latency in playback” because it didn't also say, "assuming your host has the ability to do delay compensation". Of course ProTools 9 does have it now so everything is making sense.

I really do need to get some answers on this subject. Especially since ProTools 9 now has automatic delay compensation also. I need to know what's doing what. Is the VEPro plugin compensating AND ProTools or what? And I need an answer to the question from my previous post as well.  Could somebody from VSL speak up about this?  (And why does "Normal 0" show up at the top of my posts?)

Normal
0

Thanks for your explanation. I’m still confused though. What
you described to me sounded like the explanation of how latency compensation is
done by the DAW software like my new ProTools 9 (which now performs automatic
delay compensation finally). This I think I understand how that it finds the track with
the most latency and then makes sure all the other tracks are delayed just as
much so everything plays in sync. This I can understand because ProTools (or Cubase or DP) has control of all the different tracks.

But my question was not how does ProTools do this but rather
how does the Vienna Ensemble PRO Server Interface plug-in do this? Again the
manual says,”The Vienna Ensemble PRO Server Interface plug-in automatically compensates the latency in playback.” So how does it do this?  Is the plugin so smart that it can look at
all the other tracks playing and slow them down by the amount needed so that
everything plays in sync? If so that seems very impressive to me. Or maybe I just don’t understand so well. Tell me more please.

Normal
0

I’ve never totally understood latency compensation in VEPro
and now with the new Pro Tools 9 which finally has automatic delay compensation I’m even a little more confused. I think I have a few questions but I'll start by asking one and see if I can get someone to respond:

The VE PRO manual says,”The Vienna Ensemble
PRO Server Interface plug-in automatically compensates the latency in
playback”.  Can someone tell me then – Does that mean
that, during playback, the plugin knows what notes are going to be played
before hand and triggers the notes early by the amount of the latency setting?
And if that is so – does it trigger them early by the amount of the buffers added or also the amount of the soundcard latency setting?

I'm a Pro Tools 8 user. I see Pro Tools 9 is out now and I'd like to get some opinions about it's use with Vienna stuff, in my case VEPro and the VI Pro.

The main thing I was interested in was the new automatic delay compensation that is now built into the software. You don't need the HD version to get it like before.  I heard that it even compensates for midi virtual instruments. I'd like to know to what degree that is true. Any thoughts?

 ...and thanks, DG. You slid in your response while I wasn't looking.

 Thanks Tom. So I'm going to conclude that even though VI Pro can do many thoroughly wonderful things this isn't one of them except the way I'm already doing it with 2 instances of VI.

For anyone reading this, if you don't understand the benefit of using velocity to control vel XF. Here's the idea: Normally a patch only has however many velocity layers it has and it jumps from one to the other as the velocity crosses set threshholds. But with velocity controlling vel XF you have about 127 velocity layers or it seems that way.

Feature request: If VSL could figure out a way to do this (hint,hint), automatically switch between what controller controls vel XF within an instance of VI that would be way cool.

 Hi Mich,

That's a real handy trick and I think I will use that. It doesn't solve what I still need to figure out though. When I'm doing a lot of short repetition notes I like to have real subtle velocity changes between the notes sometimes. I can do that with velocity XF cc changes for every note which looks like a stairstep graph in my DAW. But it's alot nicer if the velocity can control the velocity xfade since it lands at the beginning of each of these short notes. So, in my pieces, when an instrument is playing long notes I use a continuous controller to gradually sweep the volume of the instrument up and down as I wish. When the instrument changes to short repetitions I need  maybe subtle but abrupt volume changes at the beginnings of notes. That's when I wish I could send a message to change the controller of the velocity XF from a cc knob or slider to velocity. But I can't figure out a way to do it except for the method I'm already using which uses 2 separate VIs. Does this make sense? 

 With the old VI I had a setup where I could switch between controlling which controller effected the velocity crossfade. One way I controlled it with  a CC number and a knob. The other way I controlled it by velocity. The caveat was that I had to set up 2 different VI instruments each with 2 matrixes. It was complicated but it worked. Is there a way to do it all within one instance of VI Pro? If so I can't figure it out. I see something in the slot edit section to override the global vel XF setting. But it appears that it just allows it to be on or off, not to change the choice of controllers. Do I understand correctly or is there a way to do it?

 Yeah, but not for the demo version - just one. That's all I got.

 Got it. Thanks Karel.

 The activation code is just for one computer right?

 I have a very similar problem and some others too. I never know whether Pro Tools will connect with the decoupled instance or if it will start a new one. This is true for all 3 slaves but one most commonly. Also sometimes ProTools shuts down on startup for no known reason. I do a lot of shutting down everything and restarting or rebooting until everything wants to cooperate. It takes up a great deal of time sometimes.

I'm running Pro Tools 8.03 on a Mac Pro, Snow Leopard. My VEP is 5436. I'll get the newer one if it will help. But will it?

 Dennis,

Thanks for replying. Too bad about your experience with Pro Tools. I actually enjoy PT 8 very much and I use the 003 rack. I hope the kind of problems you have with it aren't something I will also have if/when I get a Mac Pro ( I use a quad core PowerPC Mac now.)

Thanks for the clarification, Sergino.

I was checking some of the FAQs for Digidesign's latest release of Pro Tools (8.0.3) which is their first release that's fully certified with Snow Leopard.  They did say in there, "Pro Tools already employs a modern multi-threaded processing engine that is fully compatible with many-core CPUs" which I was glad to read.

Concerning the use of 64 bit technology the FAQs said, "Pro Tools 8.0.3 is not qualified with Snow Leopard’s 64-bit kernel mode at this time." It also said, "Pro Tools 8.0.3 is a 32-bit application. We are investigating 64-bit support and have no release plans to share at this time."

I am assuming this doesn't keep Vienna Ensemble Pro from working in 64 bit right? Can anybody verify this for me?

 Good point DG. I'm sure there will be a huge step up even with the Xeon which is all I need to know. BUT - Here's my 3 major concerns (which are probably due to lack of understanding) - Are all Intel Xeon Macs fully 64 bit capable hardware-wise?  If not I have to know which ones are. Will I be able to decrease my soundcard buffer? The buffer I have to use is probably the most annoying thing about my system right now. It's set at 1024 right now. And 3rd - Is there a big jump in speed from 4 core to 8 core using Pro Tools 8?

 My trouble is I don't know if I can wait for the latest model or afford it. Like I started off saying, my current Mac, a quad core PowerPC with 7.5 gig ram is working very well for me. I run ProTools on it and 1 instance of Vienna Ensemble then network to a PC with 2 instances and an older G5 with 1 instance. 

I see I could pick up a used 8 core Intel Xeon Mac for about $2500 on Ebay and then sell my quad G5 before it looses all it's value. I'm just wondering if that would be fine for me. Or is there something I'm going to be real disappointed about with it? I can switch to Snow Leopard - right? I can use the 64 bit instead of the 32 bit - right? Is there a problem with the usage of RAM?  I don't necessarily need the latest/greatest.

 Thanks for speaking up. I probably won't be using MIR real soon though and will stick with the Mac rather than a PC.