Is VE Pro 64 only able to load 64 bit VIs? It's not recognizing Omnisphere after rescanning of VST directories. I did have a crash when I first loaded Kontakt 3.5 with an older gig file. Loaded Kontakt first, then loaded Solo Strings staccato and it froze. Restarted the program and it hasn't crashed it but I'm still fiddling around.
Thanks
-
-
hey! I didn't even think about it like that! Think they'll both run at the same time? I'll try it. Report back in a few.. gotta let the dogs out and smoke a cig. Good idea dude!@cgernaey said:
I don't know the answer to that question however, have you tried using "both" at the same time (a session of 32-bit and a session of 64-bit)? Put your 64-bit plugs in that and your 32-bit ones inside a 32-bit. I would be really interested in hearing if that worked or not.
Maestro2be
-
Yep. It works. Got both 32 and 64 bit running at the same time. Somebody earlier in the thread said they got PLAY working but only in 32 bit? Is this true? I'm installing all the 32 bit version of my PLAY libraries and they're not working in 32 VE Pro. I haven't updated to 1.2.5 yet cause I can't seem to download it right now. Keeps finishing at around 3 mb when the update is like 170.
-
Hey Paul, I was able to load my EW Play 64 version into VE Pro. I never tried loading the 64bit versions because it was said that it's not compatible. I assumed the 32 bit worked because someone here said it worked for them. I couldn't get the 32bits to work. Anyways after several hours of playing around with the the new features, I said what the heck... let's load one and see what it says. A pop up titled "Could not find default plugin" appeared. In the body of the message read: "Play could not find its default libraries on your system. Please download the latest Play update at http://support.soundonline.com/play" I clicked OK and boom! The gui loaded up. I said to myself "This can't be right". So I clicked on the browser and started loading instruments. I loaded 7 Play instruments on the slave machine and had them routing back into Pro Tools. Placed random midi notes and looped it to see if I would get errors upon playback. Didn't get any. Odd thing was that I couldn't assign "Plugin Input 13/14" in Pro Tools. It wouldn't let me. I would select it but nothing would happen. So I just skipped it and went with 15/16. The only problem I encountered: Pro Tools all of a sudden froze when it was trying to Save a back up file. I rebooted and opened up the same session again. I tested out the 13/14 input thing and it still wouldn't let me. I cleared out all the inputs and did the track select CTRL+ALT+SHIFT input method hopnig all inputs would be assigned in sequential order. It stopped at 11/12. I tried to select input 15/16 (Because 13/14 just wouldn't work) and now 15/16 can't be selected. Weird. So I skipped that and selected 17/18. Played the loop again... Ctrl S several times while it was playing. Didn't crash. I started zooming in and out as it was playing and hit Ctrl S and it froze again. Apologies if this should go straight to support or whatever, but I thought I'd let you and the community know... Thanks@Paul said:
Hi jazzhole,
it is really unfortunate that we do not currently support EastWest PLAY in Vienna Ensemble PRO.
We are working on a solution for this, together with our colleagues from EastWest. Thanks for your patience!
Best,
Paul
-
Do you have both 32 and 64 bit version of Play installed? Im trying it out right now but it's not working for me.@morphlite said:
Yeah I got that error message with EWQL Play. Works in the 32bit VE Pro verson for me though, just not 64bit.
Paul
If I remember rightly I specifically ticked to install both 32bit and 64bit VST's when I installed the Choir and EQWL Orchestra. (I'm using this on a 64bit Vista Core i7 Slave btw) It does always give the "Can't find default libraries" on start up though
Cheers
Paul
-
@Johannet said:
Using the 64-bit Server i can only load some apple effects, not the Vienna Suite ones, which according to the manual, should be 64-bit.
The released version of the Vienna Suite does not contain any 64-bit architecture plugins for Mac. We are currently testing the new Suite release for Mac, which includes the 64-bit architecture. It should be available any day now. Remember - before VE Pro there has been no host that supports 64-bit on Mac.
-
@FredB said:
Congratulation to VSL for this amazing piece of software. I'm just wondering if it's possibleto send automation data from VE Pro to Logic, in touch, latch or write mode. Automation works as expected from the host to VE Pro and It's far better than the last version wich whas not automateble. I understand that we can't have every special features in the first built. Are you planning to offer feature? Or is it only in Logic that it dose'nt work?
Thanks for the kind words!
Regarding automation, we currently do not support the "touch" mode automation. The automation parameters are just sent to VE Pro, there is no communication channel going back from VE Pro regarding the touch of sliders etc. Since we have to transport all of this information over network, it gets a bit more complicated than for a simple AU plugin 😊
We are looking into getting this done for a future release however.
-
@cgernaey said:
I don't know the answer to that question however, have you tried using "both" at the same time (a session of 32-bit and a session of 64-bit)? Put your 64-bit plugs in that and your 32-bit ones inside a 32-bit. I would be really interested in hearing if that worked or not.
This is exactly how we intended it to work. A video should be up very soon, explaining some of the more advanced tricks of VE Pro.
-
-
Hello all,
Couple of things...
(1) I had EWQLPianos playing just fine last night on my slave PC Vista 64 bit and no major problems except the initial missing plug in screen.
(2) I'm also running a mac laptop slave (Intel 2.0 ghz with 2 gig ram - Snow Leopard) and I'm not using a sound card, just the built in apple sound card. Is this a bad idea? I did have some problems last night running Reaktor (Native Instruments) as the sound after a while would crackle and then the sound would not stop, I had to close the channel to get it to stop. So... can I use the built in apple sound card or should I use a firewire audio interface like a motu 828 (which I have an extra of)?
Thanks for including the older macs in this software! That was a big help.
-
I am currently using my internal soundcard because there is no driver for my studio card yet for Snow Leopard and it performs like a champ. I have used the internal card many times over the years. Apple did a great job with that internal sound card. However, if you have an extra Motu you might like that better for latency etc. I would try both and see the results. For me, I didn't see much difference in performace but I got lots of additional control through the mixer software that my external came with. It made channel routing simplistic compared to internal routing.
Either way they will both work.
Maestro2be
-
To finish up my posts from earlier. So far everything works! (Except the minor bug about not being to use plugin inputs 13/14) Play runs fine in VE Pro slave machine. The crash in Pro Tools mentioned ealrier has been resolved. No more crashes. Everything's butter! This is what I'm talkin about! Woo Hoo.
-
Everything seems to work Perfectly here.
Still I wonder, In my host mixer i'm getting two band of audio output for each pair. So instead of having say 1-2 has a one stereo band, i'm getting 1 and 1.5 on two bands. this is really crowding up my mixer (double all the bands).
Sorry for the lack of proper terminology btw. But is there anyway of setting up something to have stereo band back. (My usual VSL ensemble gave my one stereo band for every two output).
Just wondering..
