Re: [LAU] Qsynth: Why oh why

Le Mercredi, 24 Dec 2009 15:38:10 +0000,
Rui Nuno Capela <rncbc@rncbc.org> a écrit :

> On 12/24/2009 03:28 AM, lanas wrote:
> > Le Mercredi, 23 Décembre 2009 13:25:11 -0500,
> > lanas <lanas@securenet.net> a écrit :
> >
> > Well, I compiled fluidsynth 1.1.1. and Qsynth 0.3.4 (nicely
> > segregated (at least to a certain point - this is not a thought
> > toolchain of any sort) from main Fedora system in /usr/local
> > configure's default) and connected the Axiom25 to it, loaded the
> > same soundfont and do not see the problem so far.
> >
>
> would you try with qsynth svn trunk as well? it's more suited to
> libfluidsynth >= 1.1.1 than anything else. you tell me

OK. After autoreconf, I compiled it to get the following config:

  Qsynth 0.3.4.14
  Build target . . . . . . . . . . . . . . . . . . .: release
  FluisSynth library support . . . . . . . . . . . .: yes
  FluisSynth server support . . . . . . . . . . . .: yes
  FluisSynth reset support . . . . . . . . . . . . .: yes
  FluisSynth bank offset support . . . . . . . . . .: yes
  FluisSynth channel info support . . . . . . . . .: yes
  FluisSynth unset program support . . . . . . . . .: yes
  System tray icon support . . . . . . . . . . . . .: yes

  Gradient eye-candy . . . . . . . . . . . . . . . .: yes
  Debugger stack-trace (gdb) . . . . . . . . . . . .: yes

I've added the gdb flag since it did not run. The GUI comes up but no
initialization occurs, then the GUI vanishes. After adding the debug
flag I got, only once:

Warning: no translation found for 'fr_FR' locale: /usr/local/share/locale/qsynth_fr_FR.qm

I also tried specifying the path to libfluidsynth.

So I looked into the regular ways to have more
info to help. /var/log/messages ? No output there. A '-d' flag for
console output ? None. '-v' does not provide more console output in
this case. So let's go with gdb. It provided an exit code that could
be useful.

Otherwise:

Starting program: /usr/local/bin/qsynth
[Thread debugging using libthread_db enabled]
[New Thread 140628974282496 (LWP 4897)]
[New Thread 1106684240 (LWP 4901)]
[Detaching after fork from child process 4902. (Try `set detach-on-fork off'.)]
[New Thread 1117174096 (LWP 4903)]
[New Thread 1127663952 (LWP 4904)]

Program exited with code 0177.

Missing separate debuginfos, use: debuginfo-install
alsa-lib.x86_64 celt.x86_64 e2fsprogs.x86_64 expat.x86_64
fluidsynth.x86_64 fontconfig.x86_64 freetype.x86_64 gcc.x86_64
glib2.x86_64 glibc.x86_64 jack-audio-connection-kit.x86_64
lash.x86_64 lcms.x86_64 libICE.x86_64 libSM.x86_64 libX11.x86_64
libXau.x86_64 libXcursor.x86_64 libXdmcp.x86_64 libXext.x86_64
libXfixes.x86_64 libXi.x86_64 libXinerama.x86_64 libXrandr.x86_64
libXrender.x86_64 libjpeg.x86_64 libmng.x86_64 libpng.x86_64
libsamplerate.x86_64 libtiff.x86_64 libxcb.x86_64 ncurses.x86_64
qt4.x86_64 readline.x86_64 zlib.x86_64

That could mean that the problem is elsewhere.

Since I've installed fluidsnyth by default in /usr/local/lib then I
specified:

./configure --with-fluidsynth=/usr/local/lib

But the outcome remains:

ldd qsynth | grep flui
libfluidsynth.so.1 => /usr/lib64/libfluidsynth.so.1 (0x00000035d2e00000)

So that might be the problem.

Remember, this is on a Fedora 8 x86_64 system. I would like to provide
more info, but no output in log file nor console. It's interesting,
but unfortunately I have other work to do. let me know if you'd liek
to run some quick test.

By the way, was this problem of obtaining an ugly glissando sound when
choosing another instrument a known bug ? Sounded (pun ? ;-) like a
wrong offset to a soundfount instrument loaded in memory or something
similar.

Cheers.

_______________________________________________
Linux-audio-user mailing list
Linux-audio-user@lists.linuxaudio.org
http://lists.linuxaudio.org/mailman/listinfo/linux-audio-user
Received on Thu Dec 24 20:15:06 2009