22 Feb
2005
22 Feb
'05
5:24 p.m.
Has anybody had problems with FluidSynth lately? I think the midi
portion is working correctly, but the audio output is spewing a bunch of
NAN garbage.
-Reuben
23 Feb
23 Feb
5:39 a.m.
On Tue, Feb 22, 2005 at 03:27:59PM -0600, Reuben Martin wrote:
Has anybody had problems with FluidSynth lately? I
think the midi
portion is working correctly, but the audio output is spewing a bunch of
NAN garbage.
Running FluidSynth example in GDB yields the following for me:
[New Thread 16384 (LWP 1217)]
fluidsynth: ALSA driver: Using format s16, rw, interleaved
[New Thread 32769 (LWP 1311)]
fluidsynth: warning: Couldn't set high priority scheduling for the audio output
[New Thread 16386 (LWP 1312)]
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 16386 (LWP 1312)]
0xb7fcbd50 in fluid_voice_write () from /usr/local/lib/libfluidsynth.so.1
(gdb) info stack
#0 0xb7fcbd50 in fluid_voice_write () from /usr/local/lib/libfluidsynth.so.1
#1 0x462c633e in ?? ()
#2 0xb7fc4134 in fluid_synth_one_block ()
from /usr/local/lib/libfluidsynth.so.1
#3 0xb7fc452e in fluid_synth_write_float ()
from /usr/local/lib/libfluidsynth.so.1
#4 0xb7fc45c2 in fluid_synth_process () from /usr/local/lib/libfluidsynth.so.1
#5 0xb7fa3f66 in fluid_alsa_audio_run_s16 ()
from /usr/local/lib/libfluidsynth.so.1
#6 0xb7cc9591 in pthread_start_thread (arg=0xb7c26be0) at manager.c:301
#7 0xb7cc9695 in pthread_start_thread_event (arg=0xb7c26be0) at manager.c:324
Perhaps this should be sent to FluidSYnth development list.
I have alsa-lib-1.0.8rc2, kernel 2.6.9 and FluidSYnth-1.0.5.
--
Tapio
24 Feb
24 Feb
12:44 a.m.
Tapio Kelloniemi wrote:
On Tue, Feb 22, 2005 at 03:27:59PM -0600, Reuben
Martin wrote:
I don't get a segfault, but all I hear out of it after first connecting
is a loud pop. Jack-bitscope shows it producing a constant stream of Not
A Number crap.
It used to work. I'm not sure what made it stop working. Some dependency
I've updated recently must have screwed it up. Recompiling it doesn't
fix the problem.
Has anybody had problems with FluidSynth lately? I
think the midi
portion is working correctly, but the audio output is spewing a bunch of
NAN garbage.
Running FluidSynth example in GDB yields the following for me:
[New Thread 16384 (LWP 1217)]
fluidsynth: ALSA driver: Using format s16, rw, interleaved
[New Thread 32769 (LWP 1311)]
fluidsynth: warning: Couldn't set high priority scheduling for the audio output
[New Thread 16386 (LWP 1312)]
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 16386 (LWP 1312)]
0xb7fcbd50 in fluid_voice_write () from /usr/local/lib/libfluidsynth.so.1
(gdb) info stack
#0 0xb7fcbd50 in fluid_voice_write () from /usr/local/lib/libfluidsynth.so.1
#1 0x462c633e in ?? ()
#2 0xb7fc4134 in fluid_synth_one_block ()
from /usr/local/lib/libfluidsynth.so.1
#3 0xb7fc452e in fluid_synth_write_float ()
from /usr/local/lib/libfluidsynth.so.1
#4 0xb7fc45c2 in fluid_synth_process () from /usr/local/lib/libfluidsynth.so.1
#5 0xb7fa3f66 in fluid_alsa_audio_run_s16 ()
from /usr/local/lib/libfluidsynth.so.1
#6 0xb7cc9591 in pthread_start_thread (arg=0xb7c26be0) at manager.c:301
#7 0xb7cc9695 in pthread_start_thread_event (arg=0xb7c26be0) at manager.c:324
Perhaps this should be sent to FluidSYnth development list.
I have alsa-lib-1.0.8rc2, kernel 2.6.9 and FluidSYnth-1.0.5.
7217
days inactive
7218
days old
linux-audio-user@lists.linuxaudio.org
2 comments
2 participants
participants (2)
-
Reuben Martin -
Tapio Kelloniemi