[Bug 44827] New: FL Studio: 32-bit/ 64-bit VST plugin bit bridging soft locks the host

wine-bugs at winehq.org wine-bugs at winehq.org
Sun Mar 25 23:33:20 CDT 2018


https://bugs.winehq.org/show_bug.cgi?id=44827

            Bug ID: 44827
           Summary: FL Studio: 32-bit/64-bit VST plugin bit bridging soft
                    locks the host
           Product: Wine
           Version: 3.4
          Hardware: x86-64
                OS: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: -unknown
          Assignee: wine-bugs at winehq.org
          Reporter: ajduck at outlook.com
      Distribution: ---

Trying to bridge a 32-bit VST plugin in FL Studio 64-bit, or bridge a 64-bit
VST plugin in FL Studio 32-bit, leads to this being outputted:

003c:err:ntdll:RtlpWaitForCriticalSection section 0x1ac6028 "?" wait timed out
in thread 003c, blocked by 002a, retrying (60 sec)

And the DAW soft locks with a loading cursor as it blocks the UI until the
plugin's loaded, forever trying to bridge the plugin.

(By "soft lock", I mean that FL Studio itself is still responsive, but you're
completely blocked from doing anything and the only way to get out of it is to
kill the process.)

======

Steps to reproduce:

  1. Download and install FL Studio 12 Demo:
https://support.image-line.com/redirect/FLStudio_Installer_Google

The demo and the full version are the same executable.

You will need the Arial font or any ttf named as arial.ttf in
"C:/Windows/fonts/". If you have Winetricks just run "winetricks corefonts"
(you will need the cabextract package).

  2. Download any 32-bit or 64-bit VST to test.

This is the one I tried, a 32-bit plugin (http://veg.by/en/projects/syxg50/).
The plugin itself is working perfectly. You can use any VST you want, as long
as you know whether it's 32-bit or 64-bit.

Put the dll file in "~/.wineprefix/drive_c/Program Files
(x86)/Steinberg/VstPlugins/".

  3. Open the FL Studio version which DOESN'T match the instruction set of the
VST you're using. If you're using a 32-bit VST plugin, open FL Studio 12
(64-bit). If you're using a 64-bit VST plugin, open FL Studio 12 (32-bit). (If
you're using the VST I linked to, open FL Studio 12 (64-bit))

  4. When FL Studio is launched for the first time, a featured project file is
automatically loaded. Click "File" in the top left corner and then "New" to
create an empty project.

  5. Click "Options" > "Manage Plugins"

  6. Click the "Start scan" button with "Verify plugins" enabled (make sure the
light is red). Let it scan for plugins.

  7. Close the window, click "Add", and then "More plugins..." (under System)

  8. Find and select "S-YXG50" (or if you used another VST, pick that).

  9. Because the instruction set of the VST plugin doesn't match the host
program's (FL Studio), FL Studio will try to run the VST plugin under a
"bridge" (which uses ilbridge.exe, the bridging program installed as part of FL
Studio). However, the plugin never loads. The UI blocks any interaction while
plugins are being loaded so FL Studio is effectively soft locked.

-- 
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.



More information about the wine-bugs mailing list