lol And Doug Rogers just flamed me not too long ago over at Gearslutz for saying that Play was buggy and not surprising it doesn't work in VE Pro as it doesn't work too well in a lot of DAWs even. He said the Vienna developers had just admiited it was a VE Pro problem.
-
To be fair, Doug's comments on this latest update state that to fix this incompatibility it required work on both sides.
-
@inwinterhesleeps said:
To be fair, Doug's comments on this latest update state that to fix this incompatibility it required work on both sides.
To be fair, Doug initially swore up and down that everything was just fine on the EW side and that it was totally Vienna's fault and that it would require a fix from Vienna and EW didn't need to do anything about it. I hope he remembers this next time there's an issue and is more diplomatic instead of immediately blaming everyone but his own company.
-
So Karel, you are stating that absolutely nothing has been done by VSL to make things work? Or is it just that the VSL team implemented their side of the fix a lot quicker?
-
Anyone want to try the latest PLAY with earlier versions of VEP? It would be interesting to see how long it has been fixed on the vienna side.
-
-
Does that mean all as in recent versions, or all as in since the very first release of VEP?
-
My own experiences with Play as VSTi in Cubase are not good: frequent crashes or no sound output when using Play, also some graphic errors sometimes. I try to use my older Kontakt versions of EW instead when ever possible.
So I would definetely believe that this is an EW problem - not a Vienna problem.
-
I did see a post elsewhere from someone who tried running the new PLAY with an older version of VEP - it ran but there were some functionality bugs which went away when he updated to a newer version of VEP. So it does look like there were some fixes made on the vienna side that helped PLAY work better.
-
There were some overall improvements to plugin hosting in VE Pro updates, which could indeed also affect Play. No Play specific fixes were ever done for the hosting of Play in VE Pro however. I think this is not a matter of pointing fingers though. Let's just be happy that the compatibility problem is resolved and get on with our lives ;)
-
It's only been a few days and I haven't pushed it (I normally only use a few EW sounds at a time anyway), but it's working great for me so far. It's a HUGE relief. Before, I had all my VSL libraries on a Mac Pro slave with VE Pro, working great, with Play alongside Sonar on my Windows XP master, and was constantly having trouble with Play taking over CPU resources, missing notes or sustains on export, etc. Whether it's just finally getting Play onto a slave rather than the master computer, getting it onto a Mac rather than PC, or some other improvements they've done, it's totally working great. There's been much less swearing in my studio this week. :)
Of course, to stay on topic, it's thanks to VSL and VE Pro that I can do it! And VSL is still the vast majority of my sound. I pretty much only use EW for instruments VSL doesn't offfer.