Main menu
You are here
Fluidsynth in DSSI plugin menu
1 April, 2024 - 12:09 — ElyHarsh
Further to my Ryzen 7 issues vis-à-vis qtractor, ardour and rosegarden, I finally resolved it by installing Ubuntustudio 20:04. Qtractor now runs fast with no problems. The only downside is that ubuntustudio 20:04 only has fluidsynth as a stand alone, whereas I was used to it being available WITHIN the dssi plugin menu in qtractor, which was the default behavior in Ubuntustudio 21:10 onwards. Is there any way for me to make qtractor find it as a plugin?
Forums:
re. Fluidsynth in DSSI plugin menu...
hi,
you certainly have to install it for your new system, otherwise qtractor won't find it anywhere nor anything else eg. rosegarden. afaict. fluidsynth-dssi is available from the ubuntu 20.04lts (focal) universal repo, so why don't you just install it as you should?
byee
It is already installed . . .
It is already installed . . . as a standalone . . .
re. It is already installed . . .
fluidsynth-dssi is no standalone , it's the original DSSI plugin for libfluidsynth, the same back-end library that is behind fluidsynth command-line front-end (which I think you're confusing as the standalone).
Fair enough. So what do I do
Fair enough. So what do I do then? Its installed, but not detected as per the attached . . .
re. Its installed....
please verify that it's actually installed:
does
fluidsynth-dssiappear on the output?ps. if it's actually installed, ie. has the
iiprefix above then I suspect it's packaged on non-standard DSSI plugin system paths; it should be under/usr/lib/dssi/or/usr/local/lib/dssi; check withdpkg -S fluidsynth-dssithe whereabouts offluidsynth-dssi.soand add it to DSSI plugin search paths in qtractor > View > Options.... > Plugins > Paths); don't blame me nor qtractor: that's one original canonical/debian blunder :)Wow. Its not there . . . in
Wow. Its not there . . . in either place. I'm gonna uninstall and reinstall. Thanks for your time. And stop suggesting that I blame you or qtractor for anything . . . qtractor has been my very best recording experience in 35 years - which makes you the best programmer ever in my eyes . . . and its only my eyes I care about
re. Wow. Its not there . . .
thanks
so, you do have fluidsynth-dssi installed but perhaps the reason is that it's installed in somewhere non-standard...
and add the output path, if any, to DSSI plugins search path (in View > Options... > Plugins > Paths > DSSI).
hth.
THAT'S IT . . . SORTED!!!
THAT'S IT . . . SORTED!!!
Rui, that code you told me to put in told me where it was and I copied it into qtractor . . . totally worked!!
It even carried over to the appimage of qtractor without me having to put it in twice - (I don't question how that's possible - you're a genius dude)!
Before my upgrade motherboard and CPU, qtractor worked great but musescore dithered because my PC wasn't powerful enough. I upgraded in December with great musescore but no qtractor due to my soundcard not working in modern Ubuntu studio . . . now I have both . . . the perfect recording studio - there's nothing I can't do now . . . this marks the very first time that I have everything I need. I can't thank you enough. I know the solution was bread and butter to you, but there's no way I could have ever found the solution on my own . . . I know nothing.
G3N-ES - thanks so much for your advice . . . I now use fluidsynth as per your gif which works brilliantly and totally sorts out instrument persistence . . . cheers dude.
Got the attached error when
Got the attached error when typing that in. But I have opened it from the Audio menu and selected sf2s - so it is there. I have no idea what any of that error message means . . .
re. attached error...
you misspelled the lowercase case L (
-l):)
Oops. Still have no way of
Oops. Still have no way of knowing where it is. I'll let you know when sorted . . . thanks dude . . .
I have encountered that same problem.
PROBLEM
It arises because plugin installation paths vary between distributions.
Sometimes the same distribution changes the path in updates.
Related topics have been discussed in this forum.
My perception on this matter is that plugins should never be installed in the administrative (opaque) part of the operating system, but in the user folder (where the person has complete control).
When you install plugins from developer websites, some are already starting to take this approach.
MY SOLUTION:
Create local folders in the user path and host the plugins there:
.lv2
.dssi
.clap
This way I always know which plugins I want to be available (since many times plugins are installed that we never use and should not be available) and where to find them.
Then in Qtractor options I add these routes in options.
Some LV2 plugins may not work with this approach. Rui took measures so that LV2 could also function like this. I don't know if he finally achieved it, because it depended on the format developers.
DSSI is a format that should work by locating where the binary is.
So I'm attaching it to you in case you have problems locating it within the opaque administrative part of the system.
Wow, thanks for that! I don
Wow, thanks for that! I don't have the permission to put it in the folders Rui stated. If I create the folders as you suggest, does it matter where? I just tried it in my home folder and was able to add it in options in qtractor, but it didn't give me the GUI in order to select the sf2 . . .
sudo apt-get -y install fluidsynth-dssi
I don't know what could be happening.
Try reinstalling it from the console.
Maybe the binary points to dependencies that should be pre-installed.
(There should be no need to move the plugin from .dssi. It works correctly for me as I have indicated.)
I also provide you with this thread where different ways of working with sf2 in different plugins are discussed.
https://www.rncbc.org/drupal/node/2577
That's very helpful, thanks.
That's very helpful, thanks. Rui, is right, there seems to be an issue with this distro in respect of fluidsynth. I have to stick with it though because I'm using a PCI to pcie adapter for my Edirol DA 2496 soundcard/interface, and none of the later distros accept it. I can get sound, but the midi engine only works in 20:04. So everything is gorgeous now that qtractor is working again, I just need to learn more about my options, which the thread you've attached massively helps with. When I suss it I'll update this forum. Thanks so much for your time . . .
Add new comment