Add new comment

As I indicated before, each plugin works in a different way.

Fluidsynth-dssi, at least in my experience, does not support multichannel, which is necessary to use it on BUS.

The only one that works correctly in BUS with the method that I have indicated (configuring from track and not from plugin) is "ACE Fluidsynth LV2". However, I can't find it for download. It came preinstalled in AVLinux.

I consider it to be (configuring from track) the most suitable method because it is the standard and therefore compatible with hardware synths. But if the plugin only allows it to be configured from its interface, and this does not create problems, it is also an option.

As I also indicated before, Calf Fluid does support multichannel, but it is managed from the plugin interface, not from the track.
You just have to add an instance (only one) of Calf Fluid on every bus you need, load a soundfont, and from the plugin interface assign each instrument to each midi channel. As you know, you have 16 instruments (channels) per BUS.

The only problem with Calf Fluid is that you lose the sf2 file name, but it will work correctly. It can be easily solved by writing down the name anywhere :).

However it is not necessary to work with buses. The only advantage of working by bus is performance. But generally with a machine that is 10 years old or less (which is not exactly new) and more than 4 gigabytes (which is not something unusual nowadays) it is not worth working by bus (I disagree here with Rui).

The advantage of working on separate tracks is that you can EQ, mix and apply effects to each instrument separately.
You can also automate these effects separately.

Losing all that for a minimal performance improvement I don't see the point. But it is good that we know the two ways of working, their pros and cons.
Logically, if you have dozens of instruments you take the risk of running out of RAM, that also depends on the weight of the SF2.
Each project must be valued.

Concluding:
For me, continuing to work on separate tracks with fluidsynth DSSI controlled from the track properties is the best option.
If I needed many many instruments (seeing that fluidsynth-dssi only supports 15), I would play with several plugins (Calf, ACE, DIE...)
If I ran out of ram I would change strategy to plugins in BUS.

As far as I know we have the following plugins, and we can combine them in a session.
In principle they should work well from their own interface. It's a matter of trying them and seeing how best to configure each one of them, whether from the interface itself or from the track. See their behaviors, whether or not they cause problems, etc.

Fluidsynth-DSSI
Calf Fluidsynth
ACE Fluidsynth
DIE Fluidsynth: https://github.com/DISTRHO/DIE-Plugins
FLUIDA: https://github.com/brummer10/Fluida.lv2/