21 May
2005
21 May
'05
11:49 p.m.
I am trying to use qsynth to play midi files through jack. I have
tried 3 different sound fonts. 2 make no sounds and the GM font just
crashes with output 'Killed'. fluidsynth does the same when using
that font. When I play the midi with pmidi -p 129:0 file.mid I see
green lights flash and such, but no sound comes out. I turned up gain
but nothing happens. Using Qjackctl I see that the connections are
right, it should be making noise. Pmidi seems to be ok with it...
But nothing comes out. I have tried 3 different fonts and 2 different
files having totally different content (one heavy metal the other
piano music). I don't know what to try next.
Thanks for any help.
22 May
22 May
12:22 a.m.
Noah Roberts wrote:
I am trying to use qsynth to play midi files through
jack. I have
tried 3 different sound fonts. 2 make no sounds and the GM font just
crashes with output 'Killed'. fluidsynth does the same when using
that font. When I play the midi with pmidi -p 129:0 file.mid I see
green lights flash and such, but no sound comes out. I turned up gain
but nothing happens. Using Qjackctl I see that the connections are
right, it should be making noise. Pmidi seems to be ok with it...
But nothing comes out. I have tried 3 different fonts and 2 different
files having totally different content (one heavy metal the other
piano music). I don't know what to try next.
Noah, how are you starting qsynth ? Specifically, what fonts have you
tried ? I think fluidsynth has some troubles with large soundfonts, at
least I've been unable to use qsynth with the Fluid_R3 font. Works fine
with Creative's 8mbgmsfx.sf2 though.
Youve connected qsynth's audio output to alsa_pcm in the Qjackctl audio
connections panel ? Volume is up on the mixer ?
Please let me know what fonts you've tried. Details help. :)
Best,
dp
1:05 a.m.
On 5/21/05, Dave Phillips <dlphillips(a)woh.rr.com> wrote:
Noah Roberts wrote:
Using these soundfonts crashes qsynth immediately upon play:
Hollywood.SF2
8Rock11e.sf2
This one I just tried crashes after a few seconds upon play:
Vintage Dreams Waves v2.sf2
These ones don't output any sound:
Chris_Percussion2.sf2
Saber_5ths_and_3rds.sf2
All but Vintage Dreams come from hammersound.net.
I think it is actually fluidsynth that crashes. I try using it also
and it just says "Killed".
In gdb I get a segfault:
(gdb) run -m alsa_seq -a jack -j -i
/home/nroberts/Music/soundfonts/8Rock11e.sf2
/home/nroberts/Music/midi/holy_wars.mid
Starting program: /usr/bin/fluidsynth -m alsa_seq -a jack -j -i
/home/nroberts/Music/soundfonts/8Rock11e.sf2
/home/nroberts/Music/midi/holy_wars.mid
(no debugging symbols found)...(no debugging symbols found)...[Thread
debugging using libthread_db enabled]
[New Thread 16384 (LWP 10101)]
fluidsynth: warning: Ignoring sample *DlcmrC3: can't use ROM samples
fluidsynth: warning: Ignoring sample *Vibraloop: can't use ROM samples
fluidsynth: warning: Ignoring sample *BockClave: can't use ROM samples
fluidsynth: warning: Ignoring sample *XyloE4Looped: can't use ROM samples
fluidsynth: warning: Ignoring sample *ChanterAx1: can't use ROM samples
fluidsynth: warning: Ignoring sample ShakuA2 #02: can't use ROM samples
fluidsynth: warning: Ignoring sample RecorderAx2: can't use ROM samples
fluidsynth: warning: Ignoring sample *SikuE2: can't use ROM samples
fluidsynth: warning: Ignoring sample *HarmonicaA3: can't use ROM samples
fluidsynth: warning: Ignoring sample *SynthStringsC4: can't use ROM samples
fluidsynth: warning: Ignoring sample GunShot: can't use ROM samples
fluidsynth: warning: Ignoring sample SineWave #10: can't use ROM samples
[New Thread 32769 (LWP 10102)]
[New Thread 16386 (LWP 10103)]
fluidsynth: warning: Couldn't set high priority scheduling for the MIDI input
[New Thread 32771 (LWP 10104)]
[New Thread 49156 (LWP 10105)]
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 16386 (LWP 10103)]
0x00002aaaaabfef52 in fluid_voice_write () from /usr/lib/libfluidsynth.so.1
(gdb) bt
#0 0x00002aaaaabfef52 in fluid_voice_write () from /usr/lib/libfluidsynth.so.1
#1 0x00002aaaaabf8b13 in fluid_synth_one_block ()
from /usr/lib/libfluidsynth.so.1
#2 0x00002aaaaabf83dc in fluid_synth_write_float ()
from /usr/lib/libfluidsynth.so.1
#3 0x00002aaaaabd6737 in fluid_jack_audio_driver_process ()
from /usr/lib/libfluidsynth.so.1
#4 0x00002aaaaafb82c2 in jack_port_type_size () from /usr/lib/libjack.so.0
#5 0x00002aaaab543e05 in pthread_start_thread () from /lib/libpthread.so.0
#6 0x00002aaaab543e9d in pthread_start_thread_event ()
from /lib/libpthread.so.0
#7 0x00002aaaab79dc00 in thread_start () from /lib/libc.so.6
#8 0x00002aaaac371a40 in ?? ()
(gdb)
What I really don't get is the "Can't set high priority..." I have RT
limits and jack is able to go realtime. Could its inability to do
that be causing the troubles?
Yes, volume is up and the connections seem to be made on their own.
qjackctl connect dialog shows the connections established. Other jack
stuff can output sound.
I'll google for 8mbgmsfx and see what happens...
I am trying to use qsynth to play midi files
through jack. I have
tried 3 different sound fonts. 2 make no sounds and the GM font just
crashes with output 'Killed'. fluidsynth does the same when using
that font. When I play the midi with pmidi -p 129:0 file.mid I see
green lights flash and such, but no sound comes out. I turned up gain
but nothing happens. Using Qjackctl I see that the connections are
right, it should be making noise. Pmidi seems to be ok with it...
But nothing comes out. I have tried 3 different fonts and 2 different
files having totally different content (one heavy metal the other
piano music). I don't know what to try next.
Noah, how are you starting qsynth ? Specifically, what fonts have you
tried ? I think fluidsynth has some troubles with large soundfonts, at
least I've been unable to use qsynth with the Fluid_R3 font. Works fine
with Creative's 8mbgmsfx.sf2 though.
Youve connected qsynth's audio output to alsa_pcm in the Qjackctl audio
connections panel ? Volume is up on the mixer ?
Please let me know what fonts you've tried. Details help. :) 
2:05 a.m.
On Sat, 2005-05-21 at 20:05 -0700, Noah Roberts wrote:
What I really don't get is the "Can't set
high priority..." I have RT
limits and jack is able to go realtime. Could its inability to do
that be causing the troubles?
I think that we are seeing a problem with some apps that don't work with
the RT limits patch because they assume if one RT priority is available,
they all are, as with the realtime LSM. Probably it tries to create the
thread at RT priority 99 or something. Audacity seems to do the same
thing.
This could be responsible for the bug, if it does not handle this error
correctly.
Lee
3 a.m.
On 5/21/05, Lee Revell <rlrevell(a)joe-job.com> wrote:
On Sat, 2005-05-21 at 20:05 -0700, Noah Roberts
wrote:
Can I solve the problem without diving into source?
What I really don't get is the
"Can't set high priority..." I have RT
limits and jack is able to go realtime. Could its inability to do
that be causing the troubles?
I think that we are seeing a problem with some apps that don't work with
the RT limits patch because they assume if one RT priority is available,
they all are, as with the realtime LSM. Probably it tries to create the
thread at RT priority 99 or something. Audacity seems to do the same
thing.
This could be responsible for the bug, if it does not handle this error
correctly.
3:10 a.m.
On Sat, 2005-05-21 at 22:00 -0700, Noah Roberts wrote:
On 5/21/05, Lee Revell <rlrevell(a)joe-job.com>
wrote:
Try setting the max RT priority to 99 in /etc/security/limits.conf.
On Sat, 2005-05-21 at 20:05 -0700, Noah Roberts
wrote:
Can I solve the problem without diving into source?
What I really don't get is the
"Can't set high priority..." I have RT
limits and jack is able to go realtime. Could its inability to do
that be causing the troubles?
I think that we are seeing a problem with some apps that don't work with
the RT limits patch because they assume if one RT priority is available,
they all are, as with the realtime LSM. Probably it tries to create the
thread at RT priority 99 or something. Audacity seems to do the same
thing.
This could be responsible for the bug, if it does not handle this error
correctly.
1:11 a.m.
8:54 a.m.
New subject: [linux-audio-user] Re: unable to use qsynth
Noah Roberts wrote:
you can get it from here:
http://www.alsa-project.org/~james/sound-fonts/8MBGMSFX.SF2
Rossen
Noah, how are
you starting qsynth ? Specifically, what fonts have you
tried ? I think fluidsynth has some troubles with large soundfonts, at
least I've been unable to use qsynth with the Fluid_R3 font. Works fine
with Creative's 8mbgmsfx.sf2 though.
I don't have this font and apparently it only comes with the card or
something. Where is a good font to try with qsynth that is known to
be pretty stable?
7154
days inactive
7155
days old
linux-audio-user@lists.linuxaudio.org
7 comments
4 participants
participants (4)
-
Dave Phillips -
Lee Revell -
Noah Roberts -
rossen