[Bug 44827] FL Studio: Soft locks forever when attempting to "bit bridge" a 32-bit/64-bit VST plugin

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

--- Comment #5 from [e-mail] ---
Also if anyone is looking for a workaround to this issue, you can use jBridge
(though the author does not give it out gratis). It only works with VST1 and
VST2 though.

You have to use it in separated GUI mode however because the integrated GUI
mode causes the plugin GUI to be glitchy and it will usually hang FL when you
try to close the GUI (probably some separate Wine issue, don't have a Windows
installation to test on). The hang can be fixed with a config change but the
glitching can't.

jBridge creates a .dll and config file for each plugin you want to use jBridge
with, and there seems to be no global settings or override or anything (and the
default config text file doesn't seem to work correctly), so you have to set
this per plugin. Here's a short fish script to set all the jBridge plugin
configs to separated GUI mode (and some other settings that make the mode
easier to use) after you create them with the jBridge tool:

#!/usr/bin/env fish
for cfg in "$HOME/Documents/jBridge/SettingsFilesFor32BitPlugins/"*".jBridge"
  string replace "USE_SEPARATED_GUI 0" "USE_SEPARATED_GUI 1" < "$cfg" > "$cfg"
  # The below are optional and may already be on by default but I recommend
them
  string replace "GUI_WINDOW_ALWAYS_ON_TOP 0" "GUI_WINDOW_ALWAYS_ON_TOP 1" <
"$cfg" > "$cfg"
  string replace "GUI_AUTOCLOSE 0" "GUI_AUTOCLOSE 1" < "$cfg" > "$cfg"
end
for cfg in "$HOME/Documents/jBridge/SettingsFilesFor64BitPlugins/"*".jBridge"
  string replace "USE_SEPARATED_GUI 0" "USE_SEPARATED_GUI 1" < "$cfg" > "$cfg"
  # Ditto
  string replace "GUI_WINDOW_ALWAYS_ON_TOP 0" "GUI_WINDOW_ALWAYS_ON_TOP 1" <
"$cfg" > "$cfg"
  string replace "GUI_AUTOCLOSE 0" "GUI_AUTOCLOSE 1" < "$cfg" > "$cfg"
end

You have to scan for plugins again in FL once you've created the jBridge dlls.
Even though the jBridged plugin .dll will show up separately in the plugin
database with [jBridge] prepended to the name, it will load in place of the
32-bit version if you try to load it in FL64 (and vice versa).