Any news regarding PLAY compatibility? I try to run PLAY on a Vista 64 PC (Slave) and although somebody is running PLAY successfully, it only has worked once in VE Pro 32bit and now it's crashing VE Pro completely...
Andreas
-
What's the status on PLAY?
-
Ok, I re-installed PLAY and it's kind of working now. At first startup I was able to see the GUI.
Before that I got an Runtime Error Message R6025 pure virtual function call in the VE 64bit Server.
Edit: Worked, now I got the message back. And strange enough PLAY is working on the 32bit VE Pro Server...I'm pretty sure I only installed 64bit PLAY ??? How can this be?
-
Snow Leopard, Play will not load in VE Pro in local host network, GUI wont load. Reinstalled and fully updated Play, no change. Haven't tested on slave.
-
I'm really beginning to miss those PC days -- dealing with viruses, incompatible hardware, loose operating system, etc, etc, etc, -- but at least the software worked as advertised most of the time......
-
@MS said:
Play does not work in VE Pro on Mac, it will also not work in the upcoming update. A solution is in the works, but I can not give you any promises or dates.
So, does VE Pro currently, works fine with PLAY on a PC ?
Well, It's beginning to sound like the VE Pro, and Mac issue might not be that simple to fix, after reading your feedback, I'm sensing a lot of uncertainty as far as the fix goes, which worries me.
I hope this will be sorted out in the very near future. There are lots of Mac PLAY users who would like to enjoy VE Pro's benefits.
-
-
Actually, I find it very strange that PLAY is the 'only' format that does not currently work with VE-Pro, although it's supposed to be a standard VST and AU format virtual instrument.
How different did EW code PLAY if it is supposed to be a standard VST, or AU Virtual Instrument ? Aren't 'VST' and 'AU' supposed to be standards to be used by this industry, mainly to avoid these compatibility issues (i.e. if a host can run VST, then all VST's should work, and same with AU's ? It seems like things are still messy, although we have some standard formats to work with.
Which makes it very annoying ! A Standardization of format (VST) or (AU) should be more like using 110 Volt appliance vs 220 V appliance, if you have 110 V appliance, you plug it into 110 V power outlet, it should work ! Too bad this is NOT the case with VST/AU formats on Mac and PC.
-
Unfortunately there are many thousand points where an AU or VST plugin can become incompatible to a specific host. Thus you cannot reduce such a complex problem down to this level of logic.
We have spent countless hours the past few weeks making exceptions and workarounds for various plugins which do not follow all standards or otherwise behave in ways which we did not predict beforehand.
-
I think the real problem is we have a 'Weak Standard' as far as plug-ins are concerned.
A 'Standard' means nothing if each plug-in needs a specific tweak to get it to work ! At least that's my perspective on this topic, be it complex, or simple... A standard should mean one thing .... 'A Real Standard' , rather than a 'hypothetical-Standard' or 'weak-standard'.
-
east west with play have their own approach to deal with ram-shortcomings in OSses. that means, they do things apart from apples AUspecs etc. in order to make things work. the viennas,i believe do the same OR are in closer contact to apple, which i start to believe, cause things are running very, very well on this side, what i tend to believe must be due to some "under-the-hood" tweakings that only can be done by apple. one might think as EWQL is a competitor to vienna, they don´t really want to deal with it. hmmm... i hope that isn´t the case and i don´t think so. they might try to get a little advantage out of the situation for some time beeing, but they earn it. ;) i really hope, that play will work soon in VEpro, but with all i get from VEpro, i might have enough ramspace left, to run EW-stuff from my sequencers memory. (if they get to work spectrasonics stuff properly, but i´ll start a new topic on this issue right now....
-
@muziksculp said:
I think the real problem is we have a 'Weak Standard' as far as plug-ins are concerned.
A 'Standard' means nothing if each plug-in needs a specific tweak to get it to work ! At least that's my perspective on this topic, be it complex, or simple... A standard should mean one thing .... 'A Real Standard' , rather than a 'hypothetical-Standard' or 'weak-standard'.
If you would create a standard that would specify every requirement into such minute details (processing rules, gui handling etc), the standard would be overspecified and complex to implement, and would thus probably not gain many adopters. Steinberg are even having a hard time getting dev's to adopt VST3, which is actually a rather nice plugin standard.
-
So is this PLAY incompatibility somewhere in BIG LETTERS on the download/purchase page? I just bought and downloaded VE PRO thinking it would pull me out of a current jam I'm in on a big film score with Logic. I've actually been waiting on the availability for over a month thinking it would be the total fix of my multicomputer setup.
Did I miss this compatibility list somewhere?
And now you have no idea when it will be fixed?
I am amazingly disappointed at this point!! As well as frustrated at the 2 hours I just spent trying to get VE PRO happy in my setup!!!
If the incompatibility is listed somewhere EASY to see, then my fault. If not, GET IT ON THE BUY page asap!
-
I think VE-Pro and PLAY are OK on PC, at least I remember reading something about this.
So, if your farm computers are PCs, you might be able to use VE Pro to host PLAY. Hopefully VE Pro and PLAY on the Mac will be finally fixed in the near future.
I have decided to wait for PLAY and VE pro on the Mac to be fixed, before purchasing VE Pro. I feel waiting a bit longer is my best option, but, sadly, not the option that I was looking forward to.
Can someone using VE Pro confirm if PLAY works on PCs ?
Thanks.
