Hi Julien,
My guess is you are running out of memory and when you start jack
perhaps due to memory locking something goes wrong. (does jackd normally exit in case it cannot lock memory ?)
You could try to decrease the preload size in LS, recompile it and see if it loads the big piano.
keep in mind that making the preload size too small will reduce the polyphony as it puts lots of stress on the disk.
I'd use min voices = 2 or 4 in the configure parameter when using smaller sample preload numbers.
the default preload is 32768 samples, you could try to decrease it to 24k or even 16k.
cheers,
Benno
http://www.linuxsampler.org
2008/1/30, Julien Claassen <julien@c-lab.de>:
Hi everyone!
I've still got some problems with my LS. I can load smaller gigsampler (upto
650M for sure) and even larger ones, bUT...
But when I load my Old Lady Grand (1.3G) it loads perfectly, but when I try
to connect LS to JACK the following happens:
[Linuxampler console]
[copeous output]
Caching initial samples...OK
cannot complete execution of the processing graph (Resource temporarily
unavaila
ble)
zombified - calling shutdown handler
Killed
[JACK console]
[copious output]
Noise-shaped dithering at 16 bits
jackd watchdog: timeout - killing jackd
Aborted
what's the trouble. I just compiled JACK 0.109.1 (svn from 29.01.2008) and
LS
0.5.1 (tarball). My kernel is:
host # uname -a
Linux bach 2.6.23.1-rt11 #2 PREEMPT RT Sun Dec 30 22:43:22 CET 2007 i686
GNU/Linux
I've got 512M RAM (no Xserver running), so mostly unused.
I compiled my LS with 8 diskstreams min and 140 max, and max 128 voices, the
rest was decided by the configure script. I even tried reverting the
disk-stream options and the voices to normal.
Jack was compiled without a lot of drivers I don't need, and with
--enable-resize --enable-timestamps --enable-sse --enable-mmx
--enable-optimization-by-compiler
I start my jackd with:
jackd --timeout 4000 -R -d alsa -d hw:1 -r 48000 -H -M -p 256 -z shaped
I've got a 1.8Ghz CPU and my soundcard is an MAudio Delta 1010LT.
One last note: I checked memory sage with top: Even with the big gigasample
it only takes 41% and CPU-usage is marginal.
So where would you suspect the most possible source for my problem?
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
_______________________________________________
Linux-audio-dev mailing list
Linux-audio-dev@lists.linuxaudio.org
http://lists.linuxaudio.org/mailman/listinfo/linux-audio-dev