http://bugs.winehq.org/show_bug.cgi?id=59778 Stian Low <wineryyyyy@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |wineryyyyy@gmail.com --- Comment #1 from Stian Low <wineryyyyy@gmail.com> --- Created attachment 81011 --> http://bugs.winehq.org/attachment.cgi?id=81011 Screenshots for VOCALOID6 VST3s for Bitwig/Ardour (Linux) via yabrige for wine-11.9-202b45dd9aa (WINED3D/gl and DAMAVAND/vk and Windows for comparison) gl renderer (WINED3D) supports VOCALOID6 VST3s for Bitwig and Ardour with same graphics as Windows and it supports the VOCALOID6 standalone. vulkan renderer (DAMAVAND) renders VOCALOID6 VST3s as blackscreens for both Bitwig and Ardour but it supports VOCALOID6 standalone. Therefore WINED3D/gl renderer seems most reliable for all VOCALOID6 use cases. Unclear why vulkan/DAMAVAND renderer does not work for VOCALOID VST3s despite working for standalone. MangoHUD overlay is not even visible which is odd because MangoHUD typically appears for other blackscreen cases and at least indicates DAMAVAND. Also, despite VSTs being loaded and WINED3D rendering same graphics as Windows, VOCALOID6 standalone is not launched when loading VOCALOID6 VSTs which is triggered for Windows Bigwig. I haven't noticed any logs that indicate an obvious error that prevents standalone from launching and unclear if it causes other usage issues/bugs or if standalone may be launched manually as a workaround. This still needs to be tested which I skipped because I'm not familiar enough with the apps yet. For yabridge link, it reports logs for DXVK which is tailored for games so as suggested it is probably better to run the app without DXVK: https://github.com/robbert-vdh/yabridge/issues/479#issuecomment-4509254761 DXVK test via GE-Proton10-32 crashed for standalone which seems to confirm that its probably less reliable for running VOCALOID6. Note VOCALOID6 standalone seems broken for new WOW64 vs old WOW64 which recently became clear while reporting successful tests which caused this bug to be closed as fixed: https://bugs.winehq.org/show_bug.cgi?id=56482 Bug originally reported for wine wine-9.3 (Staging) x86_64 (guest: i386) which seems to use old WOW64 so closing it as fixed seems valid but important to note that it apparently only applies for old WOW64 and not new WOW64. I will open a separate bug to address VOCALOID6 standalone crashing for new WOW64 and link it here for reference. Tested with practically same results for x11 and wayland and with and without emulate virtual desktop. -- 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.