[Bug 59778] New: VOCALOID6 VST3 doesn't load
http://bugs.winehq.org/show_bug.cgi?id=59778 Bug ID: 59778 Summary: VOCALOID6 VST3 doesn't load Product: Wine Version: 11.8 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: ole32 Assignee: wine-bugs@list.winehq.org Reporter: dominikgx@gmail.com Distribution: --- While the VOCALOID6 standalone version works, the VST3 version doesn't. It doesn't show up in Bitwig Studio, while using yabridge. In the logs I found this error message: 02:27:55 [vocaloid] [STDERR] 002c:err:ole:com_get_class_object class {8c63aa6f-cd14-4c55-b8ad-e5c9aa15e003} not registered 02:27:55 [vocaloid] [STDERR] 002c:err:ole:com_get_class_object class {8c63aa6f-cd14-4c55-b8ad-e5c9aa15e003} not registered 02:27:55 [vocaloid] [STDERR] 002c:err:ole:create_server class {8c63aa6f-cd14-4c55-b8ad-e5c9aa15e003} not registered 02:27:55 [vocaloid] [STDERR] 002c:fixme:ole:com_get_class_object CLSCTX_REMOTE_SERVER not supported 02:27:55 [vocaloid] [STDERR] 002c:err:ole:com_get_class_object no class object {8c63aa6f-cd14-4c55-b8ad-e5c9aa15e003} could be created for context 0x17 More info: https://github.com/robbert-vdh/yabridge/issues/479 -- 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.
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.
http://bugs.winehq.org/show_bug.cgi?id=59778 --- Comment #2 from Stian Low <wineryyyyy@gmail.com> --- (In reply to Stian Low from comment #1)
I will open a separate bug to address VOCALOID6 standalone crashing for new WOW64 and link it here for reference.
https://bugs.winehq.org/show_bug.cgi?id=59788 -- 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.
http://bugs.winehq.org/show_bug.cgi?id=59778 --- Comment #3 from dominikgx@gmail.com --- I require your assistance. I disabled DXVK and switched to GL. VOCALOID6 now fails to load with Kron4ek-11.8 in combination with latest yabridge and Bitwig. I attach another log. -- 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.
http://bugs.winehq.org/show_bug.cgi?id=59778 --- Comment #4 from dominikgx@gmail.com --- Created attachment 81016 --> http://bugs.winehq.org/attachment.cgi?id=81016 Logfile of VOCALOID6 after changing to GL and DXVK disabled -- 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.
http://bugs.winehq.org/show_bug.cgi?id=59778 --- Comment #5 from Stian Low <wineryyyyy@gmail.com> --- (In reply to dominikgx from comment #4)
Created attachment 81016 [details] Logfile of VOCALOID6 after changing to GL and DXVK disabled
Looks like DirectX dlls are missing based on these err for your log: 20:24:15 [VOCALOID VSTi-FOWlmpux] [Wine STDERR] 01f4:err:module:import_dll Library d3d10core.dll (which is needed by L"C:\\windows\\system32\\d3d10_1.dll") not found 20:24:15 [VOCALOID VSTi-FOWlmpux] [Wine STDERR] 01f4:err:module:import_dll Library dxgi.dll (which is needed by L"C:\\windows\\system32\\d3d10_1.dll") not found 20:24:15 [VOCALOID VSTi-FOWlmpux] [Wine STDERR] 01f4:err:module:import_dll Library d3d10_1.dll (which is needed by L"C:\\windows\\system32\\d2d1.dll") not found How did you go about "changing to GL and DXVK disabled"? I'm less familiar with bottles than vanilla wine but dxvk typically replaces those directx dlls with its own copies which act as 3rd party alternatives to wine's versions of those dlls. Therefore it seems as if however you disabled DXVK removed it's copy of those dlls and may not have restore wine's original versions of those files. Also, how did you enable GL? I switch between gl and vulkan for vanilla wine via command line such as: WINE_D3D_CONFIG=renderer=gl WINEPREFIX=/home/any/wine_stianlow_wow64_old_pfx ~/Downloads/bitwig-studio-6.0.6/opt/bitwig-studio/bitwig-studio For DXGI, I use winetricks which overwrites wine's dlls so I typically create a separate WINEPREFIX that separates DXVK or nuke the DXVK WINEPREFIX and recreate which initializes it back to wine's original dlls. -- 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.
http://bugs.winehq.org/show_bug.cgi?id=59778 --- Comment #6 from dominikgx@gmail.com --- Created attachment 81019 --> http://bugs.winehq.org/attachment.cgi?id=81019 Logfile of VOCALOID6 after changing to GL and DXVK disabled I got a little bit closer to run V6 in Bitwig. In Bitwig I entered CTRL + ENTER and searched for "advanced" option to run Bitwig in OpenGL. I restarted the program and ran V6. Now I see the logo with the info " VOCALOID module initialization failed" Any idea? -- 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.
http://bugs.winehq.org/show_bug.cgi?id=59778 --- Comment #7 from dominikgx@gmail.com --- The OpenGL is working now after switching the runner back and forth. Also DXVK is disabled. -- 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.
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.
http://bugs.winehq.org/show_bug.cgi?id=59778 --- Comment #9 from dominikgx@gmail.com --- (In reply to Stian Low from comment #8)
(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.
In bottles I can select the runner (sys-wine11 and kron4ek-11.8). I switched from kron4ek 11.8 to sys-wine11 and back. Then the error messages were solved.
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.
I updated to kron4ek 11.9 today and tried running it, without success. VOCALOID6 VST3 does not connect to the standalone version. I think it might be related to the flatpak sandbox? Or maybe the GPU acceleration? I update the logs. -- 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.
http://bugs.winehq.org/show_bug.cgi?id=59778 dominikgx@gmail.com changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #81016|0 |1 is obsolete| | Attachment #81019|0 |1 is obsolete| | --- Comment #10 from dominikgx@gmail.com --- Created attachment 81030 --> http://bugs.winehq.org/attachment.cgi?id=81030 Logfile of VOCALOID6 VST3 with "VOCALOID module initialization failed" error message -- 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.
http://bugs.winehq.org/show_bug.cgi?id=59778 --- Comment #11 from Stian Low <wineryyyyy@gmail.com> --- (In reply to dominikgx from comment #10)
Created attachment 81030 [details] Logfile of VOCALOID6 VST3 with "VOCALOID module initialization failed" error message
With VST rendering is fixed, it seems the remaining bugs to fix may involve these logs included for your first report which still remain: 18:46:08 [VOCALOID VSTi-4RYfuvwy] [Wine STDERR] 0724:err:ole:com_get_class_object class {8c63aa6f-cd14-4c55-b8ad-e5c9aa15e003} not registered 18:46:08 [VOCALOID VSTi-4RYfuvwy] [Wine STDERR] 0724:err:ole:create_server class {8c63aa6f-cd14-4c55-b8ad-e5c9aa15e003} not registered 18:46:08 [VOCALOID VSTi-4RYfuvwy] [Wine STDERR] 0724:fixme:ole:com_get_class_object CLSCTX_REMOTE_SERVER not supported 18:46:08 [VOCALOID VSTi-4RYfuvwy] [Wine STDERR] 0724:err:ole:com_get_class_object no class object {8c63aa6f-cd14-4c55-b8ad-e5c9aa15e003} could be created for context 0x17 VST may need CLSCTX_REMOTE_SERVER to communicate with VOCALOID6 standalone Editor but that mechanism seems not very well supported for wine yet given this block of code responsible for creating that log: /* Finally try remote: this requires networked DCOM (a lot of work) */ if (clscontext & CLSCTX_REMOTE_SERVER) { FIXME ("CLSCTX_REMOTE_SERVER not supported\n"); hr = REGDB_E_CLASSNOTREG; } The comment suggests that it may be "a lot of work" to support it but I'll try to get something working. -- 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.
http://bugs.winehq.org/show_bug.cgi?id=59778 Zeb Figura <z.figura12@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |z.figura12@gmail.com --- Comment #12 from Zeb Figura <z.figura12@gmail.com> --- I would be very surprised if it needs CLSCTX_REMOTE_SERVER. Probably those messages are a red herring entirely. -- 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.
http://bugs.winehq.org/show_bug.cgi?id=59778 --- Comment #13 from dominikgx@gmail.com --- Created attachment 81037 --> http://bugs.winehq.org/attachment.cgi?id=81037 The better logfile of VOCALOID6 with explanation ### I was getting rid of the EGL error messages by changing my flatpak's config. Now it looks like this (for documentation purposes): $ flatpak override --user --show com.bitwig.BitwigStudio [Context] devices=dri filesystems=xdg-run/yabridge*;/var/home/user/.vst;/var/home/user/.local/bin;/var/home/user/.vst3;/var/home/user/.var/app/com.usebottles.bottles:ro;/var/home/user/.clap;/var/home/user/.local/share/yabridge:ro;/var/home/user/.config/yabridge [Environment] LD_LIBRARY_PATH=/var/home/user/.local/share/yabridge:/run/host/usr/lib __EGL_VENDOR_LIBRARY_FILENAMES=/usr/lib/x86_64-linux-gnu/GL/glvnd/egl_vendor.d/10_nvidia.json PATH=/app/bin:/usr/bin:/var/home/user/.local/share/yabridge:/var/home/user:/run/host/usr/bin WINELOADER=/var/home/user/.local/bin/wineloader.sh YABRIDGE_DEBUG_FILE=/var/home/user/debug.log __GLX_VENDOR_LIBRARY_NAME=nvidia ### After I made the changes for OpenGL support to my system, the logo doesn't render anymore. But there were also some rendering issues beforehand (it was only shown when I ran the VST3 multiple times.) The OpenGL compositor is not working for this application (?). I believe the CLSCTX_REMOTE_SERVER error is not the major problem here, as it disappeared inside this new log. -- 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.
http://bugs.winehq.org/show_bug.cgi?id=59778 --- Comment #14 from dominikgx@gmail.com --- In OpenGL and DXVK this is the actual function which seems to be missing? I found it in both logs. 07b0:fixme:ole:CoCreateInstanceEx no instance created for interface {00000000-0000-0000-c000-000000000046} of class {8c63aa6f-cd14-4c55-b8ad-e5c9aa15e003}, hr 0x80131604. -- 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.
http://bugs.winehq.org/show_bug.cgi?id=59778 dominikgx@gmail.com changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #81030|0 |1 is obsolete| | Attachment #81037|0 |1 is obsolete| | --- Comment #15 from dominikgx@gmail.com --- Created attachment 81038 --> http://bugs.winehq.org/attachment.cgi?id=81038 WINEDEBUG VOCALOID 6 VST3 plugin fails to initialize GUI with yabridge under Wine due to .NET COM/OLE instantiation failure (CoCreateInstanceEx error for CLSID_CorRuntimeHost). Can someone fix this? :) -- 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.
http://bugs.winehq.org/show_bug.cgi?id=59778 dominikgx@gmail.com changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|VOCALOID6 VST3 doesn't load |VOCALOID 6 VST3 crash on | |GUI initialization | |(.NET/OLE fixme error under | |Wine) -- 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.
http://bugs.winehq.org/show_bug.cgi?id=59778 --- Comment #16 from Nikolay Sivov <bunglehead@gmail.com> --- From your log a more likely reason is this: 19:49:01 [VOCALOID VSTi-146BKNZu] [Wine STDERR] wine: Call from 00006FFFFE219628 to unimplemented function dxgi.dll.DXGID3D10CreateDevice, aborting 19:49:01 [VOCALOID VSTi-146BKNZu] [Wine STDERR] 053c:err:seh:user_callback_handler ignoring exception 80000100 -- 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.
http://bugs.winehq.org/show_bug.cgi?id=59778 --- Comment #17 from Stian Low <wineryyyyy@gmail.com> --- Created attachment 81039 --> http://bugs.winehq.org/attachment.cgi?id=81039 Screenshots for 8c63aa6f-cd14-4c55-b8ad-e5c9aa15e003 registry missing bug and fixes (In reply to dominikgx from comment #14)
In OpenGL and DXVK this is the actual function which seems to be missing? I found it in both logs.
07b0:fixme:ole:CoCreateInstanceEx no instance created for interface {00000000-0000-0000-c000-000000000046} of class {8c63aa6f-cd14-4c55-b8ad-e5c9aa15e003}, hr 0x80131604.
This log indeed is problematic and may be caused by ongoing installer bugs that still need to be fixed: 07b0:fixme:ole:CoCreateInstanceEx no instance created for interface {00000000-0000-0000-c000-000000000046} of class {8c63aa6f-cd14-4c55-b8ad-e5c9aa15e003}, hr 0x80131604. VOCALOID6 installer errors have been reported so despite it seemingly working for some test cases, it should probably not be assumed stable/reliable for wine yet: https://bugs.winehq.org/show_bug.cgi?id=59788 https://bugs.winehq.org/show_bug.cgi?id=56482 Wine ./pfx/system.reg is missing CLSID entry for 8c63aa6f-cd14-4c55-b8ad-e5c9aa15e003 which exists for Windows registry (screenshot) as "Yamaha.VOCALOID.VST.VSTPluginController" which is probably missing because of the installer bugs. Install err logs which may cause registry update to fail: 02e8:fixme:kernelbase:AppPolicyGetProcessTerminationMethod FFFFFFFFFFFFFFFA, 00007FFFFE20FE80 026c:err:ole:std_release_marshal_data could not map object ID to stub manager, oxid=2680000026c, oid=2 026c:err:ole:CoReleaseMarshalData StdMarshal ReleaseMarshalData failed with error 0x8001011d Manually creating missing registry entries partially fixes for Windows Bitwig via wine which allows VST to successfully open VOCALOID6 editor (screenshot). These lines were added to wine prefix system.reg to fix the logs and have the VST attempt to launch the Editor: [Software\\Classes\\CLSID\\{8C63AA6F-CD14-4C55-B8AD-E5C9AA15E003}] 1779694646 #time=1dcec19555275cc @="Yamaha.VOCALOID.VST.VSTPluginController" [Software\\Classes\\CLSID\\{8C63AA6F-CD14-4C55-B8AD-E5C9AA15E003}\\InprocServer32] 1779694646 #time=1dcec19555275cc @="C:\\Program Files\\VOCALOID6\\Editor\\VOCALOID6Plugin.comhost.dll" "ThreadingModel"="Both" [Software\\Classes\\CLSID\\{8C63AA6F-CD14-4C55-B8AD-E5C9AA15E003}\\ProgId] 1779694646 #time=1dcec19555275cc @="Yamaha.VOCALOID.VST.VSTPluginController" Linux Bitwig VST fails to open VOCALOID6 Editor and crashes the plugin. Clicking reload plugin button within Bitwig just repeats this fail indefinitely. Linux Ardour succeeds in opening VOCALOID6 Editor but the app goes into not responding state. Windows Ardour via wine crashes when opening VOCALOID Editor. Because Windows Bitwig via wine seems most compatible with VOCALOID6, it may be worth testing first and building off of it since yabridge may be a factor for Linux-based DAW bugs. Just keep in mind that since Windows Ardour crashes also, Windows Bitwig may have additional issues that may require installer fixed first. Also, until causes of VOCALOID6 crashes for new vs old WoW64 is resolved, old seems recommended for progress testing VOCALOID6 support by wine: https://bugs.winehq.org/show_bug.cgi?id=59788 Continuing to work these issues. -- 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.
http://bugs.winehq.org/show_bug.cgi?id=59778 --- Comment #18 from Stian Low <wineryyyyy@gmail.com> --- (In reply to Nikolay Sivov from comment #16)
From your log a more likely reason is this:
19:49:01 [VOCALOID VSTi-146BKNZu] [Wine STDERR] wine: Call from 00006FFFFE219628 to unimplemented function dxgi.dll.DXGID3D10CreateDevice, aborting 19:49:01 [VOCALOID VSTi-146BKNZu] [Wine STDERR] 053c:err:seh:user_callback_handler ignoring exception 80000100
Indeed it seems whatever bottle methods being used to enable/disable renderering are nuking d3d dlls as I pointed out earlier: https://bugs.winehq.org/show_bug.cgi?id=59778#c8 Once missing d3d dlls is fixed again then missing registry entries for 8C63AA6F-CD14-4C55-B8AD-E5C9AA15E003 become relevant. -- 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.
http://bugs.winehq.org/show_bug.cgi?id=59778 --- Comment #19 from dominikgx@gmail.com --- Thank you very much for your detailed information on the current state of the wine compatibility layer and your support. I suspect this is not going to be done in the foreseeable future? (by means, it depends?) I really intended creating music on Linux using V6 and I'm sure more people are out there. d3d dlls and support for the installer. Is this bug report now set on freeze by now? Or can you elaborate, if you continue to work on supporting the program? -- 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.
http://bugs.winehq.org/show_bug.cgi?id=59778 --- Comment #20 from Stian Low <wineryyyyy@gmail.com> --- (In reply to dominikgx from comment #19)
I suspect this is not going to be done in the foreseeable future? (by means, it depends?)
d3d dlls and support for the installer. Is this bug report now set on freeze by now? Or can you elaborate, if you continue to work on supporting the program?
d3d dll issues with you report seem more a problem caused by whatever bottles mechanism you are using vs a wine so d3d hardly seems a problem for this bug overall so far. Rather the installer not fully working seems to be the first major bug to solve so that manual registry edits are not required. I don't consider this issue frozen and will continue working to fixing the installer. You should be aware that many yabridge users are stuck using wine 9.21 due to a bug that emerged after that version: https://bugs.winehq.org/show_bug.cgi?id=58552 https://github.com/robbert-vdh/yabridge/issues/382 Wine had a bug for 9.21 and prior that yabridge was dependent upon so when it was fixed it broke yabridge causing GUI offset bugs and their dev team seem not to know how to fix it for compatibility with versions of wine later than 9.21. Unclear if bugs that cause yabridge users to revert to 9.21 are relevant for VOCALOID6 because it only effects VST GUI offsets but VOCALOID6 VST has no GUI components and instead just acts as a placeholder/bridge to the VOCALOID standalone Editor which seems to behave as a regular app rather than a VST. However, if you intend to use other VSTs along with VOCALOID via yabridge, then you'll likely encounter GUI offset bugs. It's an unfortunate but if yabridge compatibility issues are too difficult to resolve then perhaps a new bridge project more aligned with wine should be created to better handle VST compatibility with latest wine releases. -- 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.
http://bugs.winehq.org/show_bug.cgi?id=59778 --- Comment #21 from dominikgx@gmail.com ---
I don't consider this issue frozen and will continue working to fixing the installer.
I'm very glad! Thank you for your effort!
Wine had a bug for 9.21 and prior that yabridge was dependent upon so when it was fixed it broke yabridge causing GUI offset bugs and their dev team seem not to know how to fix it for compatibility with versions of wine later than 9.21.
Indeed, there was this bug, which I don't encounter anymore. The development version (available in Githubs Automatic Build section; newest version here https://github.com/robbert-vdh/yabridge/actions/runs/25067934796) fixed it already. Currently they seem to work on Ara2 support. Not sure, why they did not release the changes yet. -- 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.
participants (1)
-
WineHQ Bugzilla