Did this become a VEP8 feature or what happened? It’s hard to think of a feature both as powerful and easy to implement as this.

My M.2 SSD shows a speed of 624.9 MB/s but results in 3072 Preload Size so there's something a bit off with the algorithm. Also a Default Preload Size of 1024 (or less) might be in order with the new speedier drives.

Do I have to buy all licenses at the same time or will the price be the same (45 €) for additional licenses if I decide to get more during the introductory offer?

I know fixed IP would be better for VEP but that would either prevent me from accessing internet or force me to buy a router. I've been using this exact setup for almost a year now and haven't run into this problem.

It seems that VEP stopped broadcasting the slave instances for no apparent reason. I can connect manually but that is a pain with dynamic addresses and several instances. Any suggestions?

i'm in the middle of a project and suddenly the server can't see the slave in VEP. Network sharing works as usual and both can access internet. What should I try? I'm using Cubase 7.5 on Windows 8.1 and the slave has Windows 7.

It seems that Windows remembers the location of the Server but the problem remains that the Server creates the VEP instances on the wrong screen and there currently doesn't seem to be a way around it. This can't be random. There should be some kind of "Save GUI positions" setting.

I also disabled my secondary and tertiary display forcing VEP to open on the primary display. Even after that and a reboot VEP is back on the third display. This I tested without Cubase adding the VEP instance from the server. Even the window position is exactly the same so this is clearly an issue with the VEP and not Cubase.

I'm having the same issue. I'm using Windows 8 and Cubase 7 but no matter what I do VEP always opens on my third display. I want VEP instances to hide behind the project window on my main display instead of cluttering the third display that is reserved for mastering and analysis plugins. I've tried everything I can think of in both VEP and Cubase but can't seem to be able to fix the problem.

Yes, checking the license in installation is really shortsighted especially from a company that helps us use slave computers. We have computers without internet connections, without keyboards, without displays etc. and the computer used to extract or install the downloaded software isn't necessarily the computer used to run the software. No other company I know of does that and I'm disappointed that VSL would do something like this. If you trust the dongle then trust it. If you don't then don't make us use it.

Switch to Vienna Ensemble Pro, way better than FXT.

Yes, this fixed the crash on XP32. Thanks for the quick patch!

Exactly. It doesn't make much sense to me to make the VIP better than VI in some cases. It should be better. Period. It should be lighter or at least similar to the VI when loading VI programs and then offer all the power in the world when needed with modularily rising resource requirements. Kontakt can do that, why can't VIP?

Are you thinking that VIP is included as a part of VEP which isn't the case? VIP is a plugin that can be used in VEP or in a sequencer. Why would you need the presets on a slave that isn't using VIP? The presets don't work in anything else than the VIP.

Ok. Thanks for the info. At the moment I can't even think of a reason why I would need 128 voices or multiple outputs but if some people do then could it be possible to get a slimmer version of the VIP or user definable performance options? All I want is to add the humanizing options, polyphonic legato and background loading to my current setup so that it takes more CPU for those instances that actually do more. Now I'm getting all sorts of unnecessary bells and whistles with a severe performance degradation. I understand that more features means need for more resources but do they all have to be active all the time? It's my fault that I didn't check but I took it for granted that the VIP would replace the VI as the basic workhorse plugin and just add more options but now it seems to be a luxury item that I can only afford to use every now and then.

I tried both VI and VIP with my template viframe. The VI version has 61 instances and I used the VEP converter to make the VIP version. I measured the time it takes for the VI to show the GUI and for the VIP to get through the progress bar and then looked at Task Manager. I booted between the tests.

VI:

Load time: 5 min 10 seconds

Memory usage: 3.88 gigs

Task Manager CPU usage: 2%

VIP:

Load time: 8 mins 45 seconds

Memory usage: 5.42 gigs

CPU: 9%

Is there a change in the buffering settings or why is VIP using 40% more memory? It takes 70% more time to load that 40% more so obviously VIP would also slower in loading the same amount of data. The CPU usage measurement is certainly very unscientific but still it's four times the load VI has. That's not good considering the amount of instances we need.

Could somebody try this out? My setup is Q6600, P5B-VM, 8 gigs, Vista 64.

No reverb. I have 61 VIs which I converted to VIPs with the VEP convert function, I didn't do anything else. In addition to using several times more CPU the VIP also loads aa looot sloooweeeer than the VI. With VEP crashing on my XP32 slave and VIP too heavy it seems that I have to go back to the previous VEP and postpone switching to VIP. I'm sure the next versions will work fine.

You said that you are using Vienna Instrument PRO and what I was pointing out is that VI PRO uses too much CPU. The regular Vienna Instrument is very easy on the CPU in my 64-bit environment. Did you say that the 32-bit version of VI PRO is lighter than the 64-bit version? I have to try that. Maybe there's a bug in the 64-bit version that causes the difference.

But Win XP32 is, right? Maybe it's the same thing that broke both XP32 and XP64.

I have Core 2 Quad running Vienna Instruments but one instance of VE PRO is using only one core so my VE PRO gets about the same amount of power as yours. I can't use VI PRO to replace VI at the moment because the CPU usage is high. It's nowhere near 80% with just a couple of instances though.

But that requires loading the VI PRO, loading the preset, removing the VI and routing everything again. The replacing feature is just perfect as it takes care of all that repetitive stuff.

The CPU core running the VE PRO instance went from 25% to 100% and the VE PRO CPU meter from 10-20% to 80-90% when I switched to the VI PROs. I couldn't play a single flute without hickups. The system is Vista 64, Q6600, Asus MB and 8 gigs of RAM. Doesn't get much more average than that.

Also the new VE PRO 4.1.6844 crashes on my only 32-bit XP slave. When I try to add an instance from the DAW or from the VE PRO on the slave it crashes. It worked fine with the previous version but that doesn't work with the latest version on other systems. I tried removing the VE PRO and reinstalling but that didn't help.

The "Convert to Vienna Instruments PRO" feature works very well. I was just wondering how on earth would I change all my VIs to VI PROs and the I read this announcement.

Would it be possible to get a "Convert single instance to VI PRO"
feature to the VE PRO to be used before the VI PRO gets ready to completely replace the basic VI? I have a problem with the VI PRO using too much CPU resources. I have a VE PRO instance with 61 VIs loaded at the moment. I converted the instance to VI PROs and it became unusable because of the considerably higher CPU usage. Everything went back to normal when I reloaded the old VIs. The slave has an Intel Core 2 Quad processor.

Are the high CPU requirements for VI PRO a known issue? I know it has a lot of features but at the moment it takes several times more CPU than the basic VI.

The flugelhorn was the first library that I used the download manager
with and I was disappointed to notice that the download manager checks
the dongle for license before installing. I can't figure how it would make anything safer for
VSL but it makes things more difficult for the legitimate users. My
slave that runs Vienna Instruments doesn't have a keyboard and I like to
download everything to a single folder on the DAW for easy backup. Because I have to use the download manager to extract the downloaded files and it asks for the dongle I have to move the dongle with the right license from the slave to the DAW for installing and then back to the slave for using.

I also can't understand why the flugelhorn doesn't have an installer. It seems that the download manager can only install software that it has downloaded, it doesn't seem to be able to open files downloaded with another computer. Do I have to download the samples again with the download manager to be able to install them to a new system? What if all my software required me to do that? I just did a full backup of my samples and that's 1.2 teras at the moment. Or can I just compress the files the download manager extracted and save those for further installs? Doesn't that make having the copy protection procedures in the download manager completely pointless?

Also the download manager itself is questionable even if it can be downloaded on any necessary system and even if the downloading worked very well. I'm not too happy with the scenario where I have to keep installing and using separate download managers for all the dozens of manufacturers I have bought software from instead of just browsing to their websites and getting what I need.

I really hope that you can keep using the good old-fashioned way of having an installer that can be run without a dongle or any external software and easily copied from system to system. We already have to use a dongle to use the software, that should be enough.

No, I meant !!!plugin!!! which is the way Cubase informs that the project includes a missing plugin.

But anyway, the problem is that I made my template in Cubase 5 x32 and now I can't load it in Cubase 5 x64. Is that simple enough?

The save time for my template in Cubase is over a minute so I think that qualifies. I aim to make a standard template that my two 8 gig slaves load automatically when they boot up. Isn't decoupling mandatory for that? Can't I just recouple them when necessary to make a backup of the whole thing at once so that I don't have to wonder which template version belongs to which piece in case I have to reopen something finished or use two different templates in two different projects?