![Profile picture for user tedivarius](/sites/default/files/styles/avatar/public/avatars/picture-5549.jpg?itok=mveWEU9l)
Posted
The EWQL Play engine (v4) seems to cause problems/crashes in 64-bit mode. As a workaround I could edit the 32-bit version in Synfire Engine 1 (32-bit) and then put it inside a Drone in Cubase. After which editing Play in Cubase was impossible because it would only show a blank screen - nothing strange there. The 64-bit Play would crash when loading instruments, even without using Cubase (using Synfire Enigine 2 (64-bit) only).
This is probably EWQL's problem since their engine also caused problems in Cubase 6. Although that is just guessing. The workaround from EWQL for that also works here: reverting back to Play engine v3. Not the greatest solution maybe, but after some quick testing it seems stable and at least allows for a normal workflow.
EDIT: This is definitely something that has to do with the Play engine and has nothing to do with Synfire. The 64-bit AU (Play v4) crashes when loading instruments in Synfire and the 64-bit VST (v4) shows a black screen. Added to that is the fact that the only way to not crash Cubase on exiting when using Play v3 is disabling the Cubase video engine by deleting videoengine.bundle. (This is only an option for those of us not using video in Cubase.)
Sa., 12.09.2015 - 14:46 Permalink
UPDATE: It seems, after some quick testing, that the latest version of EWQL Play (v4.2.35) works without problems inside a drone (SFP v1.7.13) in Cubase Pro v8.0.30 (everything 64-bit).