Thanks a lot por this audio application. I have started the learning of Ardour recently. In my trials, adding a Yoshimi synth track freezes Ardour until I kill the process. I use Wayland.
Other scenario where it works: if I launch Ardour with FLTK_BACKEND=x11, the track is added and Yoshimi works well, but it is launched in X11 mode with XWayland.
I think a few months ago I added a Yoshimi track without changing FLTK_BACKEND environment variable, but I am not sure.
That bug seems to involve running Yoshimi stand alone under Wayland. Ardour always runs in XWayland on a Wayland desktop, so seems odd that it could show up as a plugin running in XWayland.
Also, this description is a little worrying if it applies to the plugin as well:
“In this release we no longer make any direct use of gtk. However we suspect
problem is fltk’s use of gtk modules.”
Yoshimi problem is solved in Debian now. In fact, when I launch it without Ardour, it works in Wayland without problem. Only adding a track on Ardour seems problematic.
Tried to launch yoshimi in CachyOS, Plasma Wayland:
yoshimi
yoshimi 2.3.6.2 is starting...
Start-up Synth-Instance(0)...
-----Connect-attempt----(jack_audio/alsa_midi)----
finding manual
-----Connect-SUCCESS-------------------
Using jack_audio for audio and alsa_midi for midi
manual found
Found 3131 instruments in 80 banks
Root 20. Bank set to 125 "SynthPiano"
Set jack session callback failed
Alsa midi priority is 1
WARNING: Yoshimi forced to X11 due to missing Cairo support in FLTK
Build Number 2422
Clientname: yoshimi
Audio: jack -> 'default'
Midi: alsa -> 'default'
Oscilsize: 512
Samplerate: 48000
Period size: 256
Yay! We're up and running :-)
yoshimi> Failed to load plugin 'libdecor-gtk.so': failed to init
Main Engine initialised
fish: Job 1, 'yoshimi' terminated by signal SIGSEGV (Adressbereichsfehler)
Did a search for the libdecor-gtk error:
The error message “Failed to load plugin ‘libdecor-gtk.so’: failed to init” indicates that the application is unable to initialize the libdecor plugin, which is often related to issues with the Wayland display server. To resolve this, you may need to ensure that the libdecor-gtk plugin is properly installed and configured for your environment.
Issues with stand-alone Yoshimi would be different, and not really relevant to the Ardour forums.
At least I assume that when the original poster wrote “adding a Yoshimi synth track” that meant adding a MIDI track with Yoshimi LV2 plugin added as an instrument plugin.
Currently I would consider the Yoshimi LV2 build process very broken. I just downloaded the 2.3.6.2 source code, and using the default build process I got a yoshimi_lv2.so which not only referenced system libraries rather than linking statically, it even linked to libwayland-egl.so.1, libwayland-client.so.0, and libwayland-cursor.so.0.
As far as I know LV2 does not support Wayland, so possibly that is being pulled in by linking to the FLTK libraries.
The LV2 plugin also is linked to libblkid, libmount, and libselinux. Maybe there is an argument to be made that the plugin needs libselinux to create and edit preset files (although I think that would probably be covered by whatever permissions the host application has), but I don’t see any situation in which an LV2 plugin would need to access raw block devices and attempt to mount any filesystems from block devices.
I will file an issue on the Yoshimi github page, but I don’t use the Yoshimi plugin myself, so if you are interested in progress you can check:
Not very many dynamically linked libraries. Is it OK to dynamically link the math and FFT libraries? libm is installed with glibc, so maybe OK, but I thought FFTW was supposed to be statically linked in plugins.
libfftw3 is indeed potentially problematic, but that has been API and ABI stable for a while.
No idea why it’s dynamically linked, maybe some licensing issues for official binaries.
