I have come to the conclusion that ilok is superior in Mac over eLicenser. eLicenser does much better in windows, but it really does suck large stinkin rotten eggs in mac. I constantly have to reinstall it, about every few months or so. Never have to do that with ilok - never, not even once. 

Heads up to all those using DP/DAE with VEPro, with the latest version of VEPro v4.o.6150, VSL trimmed the MIDI naming down for RTAS (which was really long)

This has inadvertently fixed the MIDI port naming issue where DP could not distinguish the different ports of a given VEPro instance. 

So, now when using VEPro with DP/DAE, all the correct ports are displayed in DP's MIDI selection.

Thank you VSL!

I use PTHD with VeP all the time, no such issue here. It's a stab in the dark, but you might want to take a look at what other plugs you have installed. I would try taking out all third party plugs, leave VE in and see if you get the same results. Could be a conflict between VEP and another plug. 

Because in this day and age of piracy, that's the price you pay for owning audio plugs and apps. Think of it like this: you need to buy a computer to run this stuff, you also need to buy hard drives, monitors and keyboards. They are not included in the app either. 

William, you forget your meds or just having a bad day? I happen to prefer LASS to VSL for a number of things. Quite a few VSL users I know feel the same. Doesn't make VSL bad, just preferred in some situations. I still use VSL all the time, but I also use LASS. 

I guess that makes us all shills, because I don't think any of us are brain dead. Although sometimes I wonder if you are when you go off like that. 

I have PLAY working in VE Pro on one of my PC slaves, but I've only use one instance of it for the piano. It's been stable without issue, unless I try to load more than one piano into it. I wouldn't even attempt to run more than one instance or even just one fully loaded instance. The more you have to access the Play GUI, the great the chances of a crash. 

One of my VE Pro slaves is X64. I don't have that problem. I have K3.5 on it and it loads the Mframe every time. The only problem with that one is that it stalls out for a long time between loading instances of Kontakt. It will load the first one (rather large) then it pauses for about 4 minutes before it will begin loading the second one. 

I also have Win7 on another VE Pro Slave. I have had some occasional issues were the Mframe wouldn't load at all on that one. I would end up having to open an empty VE Pro and then load the project from there. But the Win7 slave doesn't stall out between Kontakt instances. 

Fantastic, thanks! Any ideas when the next update will be rolled out? 

+1 here as well

7 here

Just discovered that you can't type in any names when saving VS presets on Mac using VST. 

It works fine with AU but not the VST version in Bidule.

10.5.8 8 core, Bidule 9695, Vienna Suite 1.2 (latest version) 

Is this a known issue? 

XP64 with latest Ve Pro beta - I have a large slave session with 2 instances of K3.5. When booting up VE the first instance starts loading right away. But it hangs forever with the second one. The 2nd Kontakt load window comes up right away, but loading activity deosn't even start until after about 5 minutes. It's been this way with all the versions of VE. Just wondering if there might be a solution for this.

Thanks. 

No, sorry it's a 1.86Ghz core2duo, one of the early ones and one of my older slaves. But it's still very functional as a slave. I've been using it daily for several years and haven't had an issues with it until using VE Pro. I think you are right, I need to get a graphic card. 

Thanks for the help. 

Latency is 512

Thread is 2

Graphics is built in intel graphics accelerator driver - Intel Core 2 @ 1.68Ghz, 8 gigs ram, graphics set to 256 meg in bio

I don't have a graphics slider (at least I haven't found one) but I did go back yesterday and change the performance to "best" in the system prefs. It does have various choices for the 3D and video settings in the Intel graphics. I'm not sure what of those are significant to VE. It's OpenGL. Here is the list of the choices:

Asynchronous filp - on/off

Triple Buffereing - on/off

Flipping Policy - flip/blit

Depth Buffer Bit Depth  - default/16 Bit / 24 Bit

Force S3TC texture Compression - on/off

Force FXT1 Texture Compression - on/off

Driver Footprint memory - normal/low/high

Texture Color Depth - Desktop Color Depth/16 bit per texel / 24 bit per texel

Anisotropic Filtering - application control / on / off

Video Quality Section:

Enable Film Mode detection

Sharpness Enhancement - enable application settings override (with silder min to max)

Noise reduction - enable application setting override

Any of those settings have a bearing on VE or am I going to have to get a dedicated graphics card? 

No, not even close. I get this on a session that is using about 3.98 total gigs out of 8 gigs. I can hold down a single 4 voice sustained string chord and it will have glitches. Watching the CPU usage in the task manager while I hold down the chord, it's showing anywhere from 26% for 4 notes up to 50 or 60% if I hold like 24 notes at once. But, it will have glitches even with 4 notes at 30%. Once in a while it will suddenly shoot up to 80% for a fraction of a second, then come back down. But the glitches happen even when the CPU usage is holding steady at 30%. 

Also, I can run the exact same multi set up and patches playing many tracks at once in Bidule (through my audio card) without any issues at all. So, it's not that I'm running close to max. I never had an issue until trying to use VE Pro. 

And I don't use remote desktop so it wouldn't be that. 

What else would cause it? 

I've had this happen a few times to me in Protools. To answer DG's question - I run VE decoupled most of the time because of the save times, but I've still ended up with the problem on several occasions. The decoupling doesn't disconnect VE, so if you crash your DAW, VE slaves can still think they are connected. 

There have been other posts about this, the solution would be to have the ability to disconnect on the slave end as well. 

I have VE on two PC's and my main Mac daw. Everything works well, except on one PC I'm getting random audio drops, crackles and glitches. It's on a 2core Duo with Win7. Nothing running on it except VE Pro. One thing I noticed, and I've noticed this with some of the later versions of VE2 on my other machines - the graphics in VE can be related to the audio glitches. There is definitely something going on that is graphic related. 

Since I have an ongoing issue with graphics with VE2 on another machine, a P4 3.0, I tried the same thing that I have to use in that one - which is close or hide any VE graphic while playing back. I tried the same on the VE Pro/ 2core  duo machine, and all the glitches went away. 

Also, when I open the GUI of any Vienna suite plug inside of the VE Pro slave, the audio drop outs get significantly worse, unplayable at that point. Close the plug GUI's and the glitches reduce greatly, though still occasionally there. Hide all VE GUI's and the glitches go away completely. 

It makes me wonder if others that are having audio glitches are running into the same thing. 

Any ideas on how to solve this?   

I'm crashing in 64pc with 64 server. 

Yeah, it happened again today. I booted up the studio and it loads my first of two kontakts fine. Then it hangs for 15 minutes before it starts loading the second kontakt in the VE instance. Then it hangs again for several minutes. Once it is all finally loaded, it was up for a few seconds before it crashed.

Last night when I shut down the studio, I made sure that I recoupled all the slaves and saved the project, just to see what would happen when I started up today. I didn't manually load a metaframe today. I just started up the VE servers and then launched my project in the DAW. 

I've had the same thing happen. On one of my PC slaves, the metaframer will load about 2/3's of the way and then crash. I had saved it as a project, and that reloads fine, but if I try to open the metaframe it crashes. 

It was fine until I upgraded to the latest version. 

Great!

Something has to be done about these eLicenser issues. I just lost about an hour of work...again...because on my Mac I constantly get "can't find the license" error. I get them on both Leopard and Tiger boots, I get them about every other day. Sometimes I can just quit VE and it will work the next time. Other times I have to reboot to get it to work, which means 20 minutes of sample loading. It's really a pain. 

I've been using the last version, just downloaded the very latest version, installed and booted, VE is up now, but I'm not to confident that I won't have an issue tomorrow or the next day. I always install the latest version of eLicenser and the problem has yet to go away. 

Hey Paul, I'm in contact with DP. I'll report back here when I hear back from them. 

Thanks.

Hi Paul,

I wish I could use AU, but my main daw is RTAS/DAE based. I would have to give up too much in terms of hardware I/O and certain plugs that I can't live without. 

I'm not sure where to steer this, because I'm discovering more as I try to find the solution. It appears that there is a sync issue at least with a few plugs in DP7/RTAS on Leopard, (i.e Kontakt and Spectrasonics stuff) but only on Leopard, they work fine in Tiger. I also found that though that a few VI do sync fine inside of DP7/RTAS on Leopard, (i.e. EZ Drummer) but those that do work inside of DP, don't work with VE Pro. None of them work in VE Pro.  Maybe this is something that you could have your guys look into. While MOTU needs to address the issue as well, I think that even if they fix all the sync issues in DP7/RTAS, it will still be an issue with VE Pro, because currently none of them sync when using VE Pro.

Thanks.  

One more time: 

Hi guys, 

I have a question about the sync. In DP / RTAS the sync is not going through to the slaves. Sync works fine with all my plugs inside ot DP, but not with VE Pro.

Any possibility at all that you could look into it on your end? If the plug sync is working fine inside of DP, shouldn't it also work with VE, since VE Pro is hooking up inside of DP? 

The sync I am referring to is the midi clock that plugs like RMX, Kontakt etc use to lock to the DAW tempo.

Thanks