BFD2 has been a nightmare in VE Pro. To use it entails having to quit before and after and restart the computer, or else the other instances using other plugins either: crash at a certain point while loading with the project they are preserved with, or BFD2 will fail to load the full BFD2 preset I have saved no matter what. VE Pro does not recall that preset in the VEP project and it has to be loaded manually each time. With a restart both ways loading is possible but awkward. The use of BFD2 in VEP seems to have messed up the whole way instances load with a Cubase project; the project takes more time to load than it did when instances of VEP loaded with the project than it does now, which does not connect with VEP, and then I'm loading the instances. Once everything is up, it's great, but loading/unloading is a PITA.

In any case, I'm using it alone and have decided for now not to bother with it under VE Pro, it just isn't playing nice with VEP or vice versa. Going back and forth to run it in Cubase on the slave machine vs my usual workflow is less of a workaround than this stuff I'm doing now.

Trillian Disaster! -- I had a major day of crash-y, stuttery, glitchy, very frustrating behavior.  It was the first time I've used Trillian in a session.  I seem to have resolved the problem by opening the same patch in Omnisphere.  All problems gone now.

Details:  Trillian v1.1.4c (Omnisphere 1.1.4c) in VE Pro build 4686, Pro Tools 8.0.1cs1, OS 10.5.8, Mac Pro 2x2.6 Dual Core.

Great software.

Superior drummer 2 and EZ drummer groove browser doesn't work properly for me in VE pro.  You can only loop about one beat of the groove when previewing.

Also hypersonic 2 doesn't work at all.

Play keeps not working under Windows XP 32bit.

I tried the following interfaces: Symphonic Choirs, Voice of Passion and Ministry of Rock.

None of them properly works under VE Pro. The interface partially loads and the user can't interact with it (when I click inside the play panel the entire window of VE Pro loses the focus, while it gets back the focus when I click on toolbars or other element of the VE Pro window).

I can also assure that the Play engine didn't work properly under many other circumstances. I'm still using it through FX Teleport, but the interface exposes THOUSANDS of issues! At EastWest they are always trying to grab some money from us with new sounds, new libraries, new products.

And while they are counting down for the release of the new Hollywood Strings... we are still counting down for a stable, safe and rock solid version of play, which can run as smoothly as Vienna Instrument does!!!

@Elias57 said:

With the new beta from 18.12.2009 on my Macs all IK-Multimedia CSR Hall Plugins are shown with a white GUI. Clicking on this white GUI shows the element under the clicked area.

Steinberg The Grand 2- please, it wold be great if this worked. It loads and responds to "midi" but not sounds.

The Grand 3 DOES work but, in my opinion, has inferior piano sounds. Amazingly Steinberg have dropped the very useful and very beautiful Steinway model from The Grand3.

thanks

After a lot of use .there may be issues with Refx Nexus,im getting the occasional crash and a few times i've had a message saying i should move remove a plugin,although it doesn't tell me which one.When i look a the GUI of Nexus,the colours are all messed up.A restart fixes it.Most of the time however it is working fine

BFD2 has been godawful here. By itself, with absolutely nothing else in the network, I can get it to work if I set BFD2 to load with that preset as if a default. But loading new kit pieces, WILL crash VEP; or, with 'load nothing' as a preference, loading a preset or kit will fail to load most of it, and 'loading new kit pieces WILL crash...'. Generally I'm working around it, Cubase on the slave machine, BFD or BFD2 as a regular plugin.

'On a Mac', well I'm using a macpro octocore under OSX.6.2 with these issues. I think I will compile some crash reports per this 'loading causes crash in every case' and submit. With 'load preferred preset at startup' it's ok, but typically I pick a kit according to the demands of the piece's other orchestration, so this is a real problem for me.

@BenjaminCS said:

I just tried VE Pro with EastWest's PLAY and it seems to work, I am very surprised (in a good way obviously) since the compatibility list says it doesn't. PLAY version 1.2.05, VE Pro version 4.0 build 4881, Cubase x64 5.1.1, Windows 7 x64 on Core i7 12GB. Apparently great news (?)... but why does http://vsl.co.at/en/211/497/1685/1693/1742/1369.htm explicitly say it doesn't work?

Because it works with some versions of the software (on Windows) and not others. there is guarantee that ti will work with future versions. this is why I J-Bridge PLAY, so that I don't have to worry about future updates of VE Pro not working with PLAY.

DG

I've played a bit with Korg Analog on both Mac and Windows, and I couldn't reproduce this behavior. Could you perhaps give some exact steps on how to get it to behave like this?