http://bugs.winehq.org/show_bug.cgi?id=59778 --- Comment #8 from Stian Low <wineryyyyy@gmail.com> --- (In reply to dominikgx from comment #7)
The OpenGL is working now after switching the runner back and forth. Also DXVK is disabled.
I'm not sure how you resolved the previous errors regarding missing DirectX dlls by toggling the Bitwig OpenGL advanced option but the missing dlls seem resolved and D3D calls seem to be working now based on your latest logs. By switching to renderer=gl (wined3d) vs vulkan (dxvk), I did not mean changing Bitwig to OpenGL, but rather for wine/yabridge which is done via the command line option I posted. Linux Bitwig should have no effect on wine/yabridge and only interaction between them is via yabridge generated *.so files which call wine. Regardless whatever you did seems to have fixed the rendering issues because "VOCALOID module initialization failed" is the same message that appears for Ardour for the screenshot I attached previously (last screen). Oddly I don't see any of those VST messages for the first screenshot for Bitwig but we seem to now be in a very similar state now. I believe the remaining bug to fix is "module initialization failed" which may be what is preventing VOCALOID6 standalone from launching automatically by the VST. Please try to manually launch VOCALOID6 standalone while VST is loaded to see if they are able to connect and interact as a workaround. If that does not work then errors for your new logs may hint at what else needs to be fixed to get VOCALOID standalone to launch via VST and connect and interoperate as expected. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.