30 Jan
2008
30 Jan
'08
7:35 p.m.
Hi everyone!
I narrowed my recent problem down to not being LinuxSampler, but either jack
or its interaction with the kernel.
So: Does any of you use 2.6.23.1-rt11 or 2.6.24-rt1 in conjunction with
jack?
How well does it work? Is it easy to make connections when the system is
working nicely (with a good deal of memory in use)?
I still have trouble connecting my linuxsampler when I've loaded my 1.3gig
sample (32768 samples in RAM) or when I use fluidsynth with a very big
soundfont (200M). It's all much too instable?
Suggestions anyone? What to test? Where to start?
Kindest regards
Julien
--------
Music was my first love and it will be my last (John Miles)
======== FIND MY WEB-PROJECT AT: ========
http://ltsb.sourceforge.net
the Linux TextBased Studio guide
======= AND MY PERSONAL PAGES AT: =======
http://www.juliencoder.de
30 Jan
30 Jan
8:09 p.m.
Hi folks!
OK beat me round the head with a rubber-bat. I gave /dev/shm as jack's
tmpdir. Not good. Now LS runs fine. BUT!!!
But still when I do the following - and this is repeatable:
start fluidsynth like this:
fluidsynth -a jack -j -r 48000 nd_bass_guitar.sf2
Start ecasound and use it:
ecasound -B:rtlowlatency -b:64 -r 30 -c -a:1 -i jack_auto,fluidsynth \
-o test.wav -a:2 -i null -pn:met,120 -a:3 -i monitor.wav -a:2,3 -o jack_alsa
And then after working finish ecasound. Fluidsynth looses its connection
because JACK simply dies, saying:
jackd watchdog: timeout - killing jackd
Aborted
This is not nice, though sufferable. But as sufferable still contains "to
suffer", it would be nice to abolish it.
Can anyone help here?
Kindest regards
Julien
--------
Music was my first love and it will be my last (John Miles)
======== FIND MY WEB-PROJECT AT: ========
http://ltsb.sourceforge.net
the Linux TextBased Studio guide
======= AND MY PERSONAL PAGES AT: =======
http://www.juliencoder.de
1 Feb
1 Feb
1:59 p.m.
On Thursday 31 January 2008, Julien Claassen wrote:
Hi folks!
OK beat me round the head with a rubber-bat. I gave /dev/shm as jack's
tmpdir. Not good. Now LS runs fine. BUT!!!
But still when I do the following - and this is repeatable:
start fluidsynth like this:
fluidsynth -a jack -j -r 48000 nd_bass_guitar.sf2
Start ecasound and use it:
ecasound -B:rtlowlatency -b:64 -r 30 -c -a:1 -i jack_auto,fluidsynth \
-o test.wav -a:2 -i null -pn:met,120 -a:3 -i monitor.wav -a:2,3 -o
jack_alsa
And then after working finish ecasound. Fluidsynth looses its connection
because JACK simply dies, saying:
jackd watchdog: timeout - killing jackd
Aborted
This is not nice, though sufferable. But as sufferable still contains "to
suffer", it would be nice to abolish it.
Can anyone help here?
Kindest regards
Julien
I'm not sure this is a jack problem. The dependence on the size of the loaded
data files rather hints at problems in the clients that only show in realtime
mode.. Maybe try
a] allowing apps to mlock more memory
b] using a longer timeout for jack [see manpage]
/dev/shm is actually a rather good choice for the jack temp directory.. [when
there's a shmfs mounted there]
Flo
--
Palimm Palimm!
http://tapas.affenbande.org
2:22 p.m.
On Fri, Feb 01, 2008 at 06:59:13PM +0100, Florian Schmidt wrote:
/dev/shm is actually a rather good choice for the jack
temp directory.. [when
there's a shmfs mounted there]
I'm not sure if Julien wanted to say it was the solution
or the problem... his words leave open both possibilities.
AFAIK, /dev/shm is the also default jack tmpdir in 0.109.
--
FA
Laboratorio di Acustica ed Elettroacustica
Parma, Italia
Lascia la spina, cogli la rosa.
6173
days inactive
6175
days old
linux-audio-user@lists.linuxaudio.org
3 comments
3 participants
participants (3)
-
Florian Schmidt -
Fons Adriaensen -
Julien Claassen