[Bug 44827] FL Studio: Soft locks forever when attempting to load the GUI of a "bit-bridged" 32-bit/64-bit VST plugin

[wine-bugs at winehq.org]

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

--- Comment #6 from ajduck at outlook.com ---
I've discovered an even better workaround that doesn't even require jBridge!
It's so much better! (This workaround supersedes the workaround in the previous
comment.)

FL Studio has the option to show an external window for the GUI for a bridged
plugin. It turns out that FL shows the GUI of a bit-bridged plugin absolutely
fine when it's shown in an external window (I think the external window might
be from the ilbridge.exe process itself).

The hanging problem seems to be specifically when FL tries to show a
bit-bridged plugin's GUI in the internal FL Studio window representing the
plugin.

To workaround this without any external programs, all you need to do is this:

  1. Open FL, go to Options > Manage plugins and find the plugins you're coming
across this Wine bug with. Find out whether they're 32-bit or 64-bit only.
  2. Open the FL version with the same bit size as the plugin you want to get
working in the other bit version. Open FL 32-bit for 32-bit plugins and FL
64-bit for 64-bit plugins.
  3. For each plugin you want to workaround the Wine bug with, open the plugin
and go to the VST wrapper settings*. Then click on the "Processing" tab at the
top and enable "External window" under the top-most section ("Compatibility
options").

* Click on the cog icon in the plugin window's headerbar if it's not green and
then click on the plug & cog icon in the bar below the headerbar

Now when you show the GUI of that plugin in the other bit version of FL, it
won't hang.

--------

By the way, in the case you accidentally cause FL to lock up from this specific
Wine bug  and you really want to release FL from it (e.g. you really want to
save the project file), you _can_ actually release FL from it. You need to end
the ilbridge.exe process that FL is waiting for.

You can either use Wine's taskmgr or a native process manager:

- Native process manager: Go to a native process manager that shows PIDs and
end the ilbridge.exe process that has the highest PID.
- Wine taskmgr: End the ilbridge.exe process that shows 0:00:00 CPU time.

FL will be responsive again. You won't be able to reload the plugin without
triggering the hanging again though (because the only way to load the GUI of
the plugin is to click the button in the plugin window). The project file will
save fine though and you won't lose the plugin or it's settings.

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