Forums
Greetings. When I try to run qsynth-0.9.7-51.4.x86_64.AppImage, it tells me:
qsynth: error while loading shared libraries: libpulsecommon-13.0.so: cannot open shared object file: No such file or directory
I'm running Mint 20.3. On my system, I have /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-13.99.so, so I symlinked that to libpulsecommon-13.0.so, but it still reports the same error. Is it supposed to be bundled inside the appimage?
---scott
Appimage build system?
May I ask what distribution/version the Appimages are built on?
re. Appimage build system?
All AppImages are built on OBS with distro and toolchain being based on openSUSE Leap 15.2.
qsynth-0.9.7-51.4.x86_64.AppImage in particular is actually broken, due to missing rpath setting to /usr/lib64/pulseaudio for instance...
that's hopefully fixed if you download the latest snapshot.
please try and tell
cheers
re: qsynth-0.9.7-51.4.x86_64.AppImage missing libpulsecommon...
Nah, I have too many dependencies that lag behind to build it without going crazy. That's why I wanted to use the Appimage. I'll wait. Thanks.
---scott
re. qsynth-0.9.7-51.4.x86_64.AppImage missing libpulsecommon...
please do try qsynth-latest-x86_64.AppImage, it was broken before, maybe not anymore
cheers
ps. remember to make it executable (eg.
chmod a+x qsynth-latest-x86_64.AppImage;)The AppImage works on Q4OS 4
The AppImage works on Q4OS 4.8, but this version of QSynth is not working well with Igor Engraver via Wine: instrument parts are poorly synchronized and balanced in playback. This was never a problem with QSynth 0.5.0.
Regards,
Magnus
re. not working well with Igor Engraver via Wine
maybe an issue with the soundfont in particular and/or in general to libfluidsynth >= 2 ?
qsynth v0.5.0 is pretty much ancient (5y+?) and most surely won't have any love around here anymore, sorry
cheers
OK, so libfluidsynth 2 may be
OK, so libfluidsynth 2 may be the cause. What can I do to resolve this issue?
re. Igor Engraver
no idea
I don't really know why that thing is not doing it right (through wine? really? :S)
if qsynth v0.5.0 (and fluidsynth < 2) works for you then keep'em--you're are on your own, sorry
byee
byee
OK. I have now submitted a
OK. I have now submitted a bug report at https://github.com/FluidSynth/fluidsynth/issues/1102. Let's see if it can be sorted out.
Bye for now!
re. OK. I have now submitted a
maybe it would be more concise if you state which audio and midi driver you have set in qsynth/fluidsynth (and whether you tried something else in that regard:))
just 2c.
Add new comment