Did this latest version brake PLAY functionality again? I can't seem to instantiate a PLAY instance, prompting the old error "Could not create plugin play_VST_x64". 

Am I missing something?

Yes, you're trying to instantiate a 32-bit plug-in as a 64-bit one.

Fixed by updating PLAY to the latest version.

All working now. Well, with the exception of the CPU spikes and dropouts on the Mac...

Thanks Paul,

I am so looking forward to being able to have VI Pro integrated with Vienna Ensemble.

Thanks to all of the vsl team for this.

best,

Steve[:D]

Well, thought it was fixex, but it isn't. Here's what's happening:

There seems to be a timeout issue with PLAY initializing in VE PRO. This happens with PLAY 2.0.25 on a Windows XP64 system, running VE PRO build 7043.

When the workstation first boots, VE PRO starts and a metaframe is loaded that contains an instance of PLAY, VE PRO will return an error stating that "Could not create plugin play_VST_x64". However, shutting down VE PRO and manually starting up a standalone PLAY instance will remedy the issue, as PLAY will take a long time to start up, but eventually will show the standalone window. After that VE PRO will also instantiate PLAY instances.

Above would be the workaround to get PLAY to work in the latest version of VE PRO. Would be nice though if we could have this addressed quickly. :)

Thanks,

JB

@Jack Weaver said:

Paul,

I still get the 404 error.

I am seeing the 404 as well for the VI Pro changelog (english)

 Sorry, this changelog was updated, it should work now.

best

Herb

@Jurgen Beck said:

Well, thought it was fixex, but it isn't. Here's what's happening:

There seems to be a timeout issue with PLAY initializing in VE PRO. This happens with PLAY 2.0.25 on a Windows XP64 system, running VE PRO build 7043.

When the workstation first boots, VE PRO starts and a metaframe is loaded that contains an instance of PLAY, VE PRO will return an error stating that "Could not create plugin play_VST_x64". However, shutting down VE PRO and manually starting up a standalone PLAY instance will remedy the issue, as PLAY will take a long time to start up, but eventually will show the standalone window. After that VE PRO will also instantiate PLAY instances.

Above would be the workaround to get PLAY to work in the latest version of VE PRO. Would be nice though if we could have this addressed quickly. 😊

Thanks,

JB

There is no timeout in VE Pro with regards to creating plugins. This seems to be a problem with Play, so I recommend to report it to East West.

In ensamble pro 70 43 I It looks like it can load the instruments properlly, Doesn not start.

@Jack Weaver said:

Paul,

I still get the 404 error.

I am seeing the 404 as well for the VI Pro changelog (english)

well, on my macs, they all (in applications, audio>plugins>components, VST, VST3) read: 4.1.7043. 'Build' = 'version'.

'

The version number is structured as such: <MajorVersion>.<MinorVersion>.<RevisionNumber>.

I am receiving the following after upgrading to ViennaEnsemblePro-OSX-4.1.7043. (See Error Listed below

• In windows there is a VST settings button available to set folder location and scan for changes. Is this not available on MAC
• No effects are showing up except Apple's AU, 
• 32 bit version is working and all effects are showing up and working properly. 
• Does Vienna Pro have VST support none is showing up in my setup. Am I doing something wrong?
• Is there support for cubase VST3 plugs effects on either WIN7 or OSX 10.6
• Will there be a bridge built in future for 32 bit support in 64 bit app?

Thanks for any input, I have purchased Pro but before I spend time with it, trying to see if this will work for me...

Kenny

On a Mac, VEP does not see .vst, only the AU .component. AFAIK Cubase plugs are completely proprietary ie., work only in Cubase.

If you see only the Apple AUs in the 64-bit VEP, it means you probably have no other 64-bit fx for VEP to see.

Oh well, I guess another waste of time and money. Funny all software I use is VST based...or can use VST on my mac

Software here is great concept but it seems only to work properly on PC, on mac the only thing I can use it with so far is VSL and no 3rd party plugs. My reason for getting was to use both MAC and PC together. Anyone know of software like FX Teleport that can be used to link Mac and PC computers? Or is there a wrapper that is supported by VSL (exp FXpansion wrapper that is used by Pro Tools and Digital Performer)....

Thx,

Kenny

VE Pro hosts AU's on Mac and VST's on Windows, seeing as this covers 99% of plugins out there. You can indeed only run 32bit plugins in a 32bit VE Pro, and 64bit plugins in a 64bit VE Pro. Note that you can run the 32bit and 64bit VE Pro Server side by side without problems though. On Windows you can also use a third party bit bridge like jBridge.

I am using a number of Native Instruments, BFD2, Play, IKMM TRackS and Amplitube2 (Jimi Hendrix, Metal, Fender etc) with no issues currently as AU.

It would be stupid to use FX teleport if you own a VEP license. Use the windows box for the things that don't provide AU versions and the Mac for the ones that do.  VEP works [&]

@kzarider said:

Software here is great concept but it seems only to work properly on PC, on mac the only thing I can use it with so far is VSL and no 3rd party plugs. 

Kenny,

There are COUNTLESS .au instruments. Spectrasonics, Native Instruments, and a slew of others...

What instruments do you use on the mac that are only VST ? Have you checked to see if the developer makes an AU version?

This really is not an issue since most all commercial instruments are cross platform.

Please be specific..

J

I would be interested to know which Mac plugins come as VST only.