I use FL Studio to do the majority of my sequencing. Recent versions of FL Studio (I believe 10.x) has a feature to bridge plugins into their own memory space. This is hugely helpful for RAM hungry plugins such as BFD. LS works great in FL, but when I attempt to bridge it, it crashes.

This is not a priority item, or even needed for LS functionality, but it would be great if LS could be compatible with bridging in FL Studio.

I do not know about the technical details of bridging a VST, however, Frederic (a.k.a. reflex) at FL Studios has kindly offered to answer any questions. He can be contacted at: frederic AT flstudio DOT com

When I saw the other FL Studio post in the forum a while ago, I tried the FL Studio 10 demo (v10.0.9), and yes, I get a crash when I load the 64 bit linuxsampler vst. The 32 bit version loads OK. FL Studio seems to be a 32 bit program, so I guess the bridge (ilbridge.exe) is a solution to use 64 bit vst plugins from FL Studio.

I debugged the issue a bit, and I found that if I revert the increase of number of programs from 128 to 16384 that were made in LS 2012-09-22, the crash disappears. You can maybe verify this by testing the linuxsampler_20120919_setup.exe version? It it works, we should discuss with your FL contact if there is a max number of programs in ilbridge, and if it's ilbrigde or LS that should be changed.

Then I was sidetracked when I noticed that only some of the instruments in the gig I was testing with worked in FL Studio, the others gave no sound at all. Very strange. I haven't looked any further into this yet.edit: The problem with silent instruments is solved by turning on "Use fixed size buffers" in the plugin wrapper "processing" settings in FL Studio.

Andreas wrote:FL Studio seems to be a 32 bit program, so I guess the bridge (ilbridge.exe) is a solution to use 64 bit vst plugins from FL Studio.

Indeed you are right that ilbridge provides a solution for 64bit VST. It is also very useful for 32bit VST to overcome the 2G RAM limitation. I am using the 32bit LS in WinXP.

Andreas wrote:I debugged the issue a bit, and I found that if I revert the increase of number of programs from 128 to 16384 that were made in LS 2012-09-22, the crash disappears. You can maybe verify this by testing the linuxsampler_20120919_setup.exe version?

The test plugin I made confirmed that the current ilbridge couldn't handle more than 2048 programs in a VST. But it also confirmed that this bug was already solved in the next version of ilbridge, so I guess we were content with that.

The developer also told me that the linuxsampler installer once had messed up his Windows, by removing every entry in the PATH environment variable. I found a hint that NSIS (the system we use to create the linuxsampler installer) installers could do that if the value of PATH is long. The solution is to rebuild the makensis program with a special option. I did that, so from linuxsampler_20130208_setup.exe and onwards that problem is solved.

Andreas wrote:The test plugin I made confirmed that the current ilbridge couldn't handle more than 2048 programs in a VST. But it also confirmed that this bug was already solved in the next version of ilbridge, so I guess we were content with that.

The developer also told me that the linuxsampler installer once had messed up his Windows, by removing every entry in the PATH environment variable. I found a hint that NSIS (the system we use to create the linuxsampler installer) installers could do that if the value of PATH is long. The solution is to rebuild the makensis program with a special option. I did that, so from linuxsampler_20130208_setup.exe and onwards that problem is solved.

For those still interested, LS VST is now fully bridge compatible with FL Studio 11 (recently released) and works very well.