Is that really true?
http://www.soundsonline-forums.com/showthread.php?t=23845
Would be very, very disappointing!
-Andreas
194,142 users have contributed to 42,912 threads and 257,924 posts.
In the past 24 hours, we have 2 new thread(s), 15 new post(s) and 79 new user(s).
Is that really true?
http://www.soundsonline-forums.com/showthread.php?t=23845
Would be very, very disappointing!
-Andreas
@andreas_6739 said:
Is that really true?
http://www.soundsonline-forums.com/showthread.php?t=23845
Would be very, very disappointing!
-Andreas
I think that the important part is yet.
DG
I have (almost) no problems using Play with VE Pro.
Case 1) Adding a "Vienna Ensemble Pro" VSTi in the sequencer, then creating a new instance and inserting "Play" works fine. Though I see a warning message, you can ignore this.
Case 2) Add an instance before connecting it to the sequencer and then inserting "Play" makes problems. I don't see the "Play"-interface. But there exists an workaround: Insert "Play" like I explained in case 1) and save this as "Project" in VE Pro. Then when you want to insert "Play" like I wrote in Step 2) you can load this project and it should work.
Best regards,
Peter
Has there been any careful estimations if:
a) VE-PRO will be supporting EW Play at all?
b) in what kind of timeframe we could expect this to happen?
I was looking forward to VE-PRO as the opener of doors to the 64-bit world for me, replacing FX teleport (being the only piece in the puzzle holding me back), but 50% of my rig being in PLAY format, it doesn't really help. Running FX teleport AND VEP alongside each other doesn't really sound like a good idea does it?