I use the great sampler SL on GNU/Linux (Ubuntu 10.04) for live stage of theater... it's the greatest free software I know for do that and I am really proud to use it for professional use...
But... there is a "but"... I had a terror feeling yesterday during run-through... Sooper Looper froze! I don't know the good word to say that : no more spent it! May be it was the graphical layer which stops, I didn't have the time to verify it with the system monitor, I just forced to quit and restarted as fast as possible (2 minutes with the connexion to Jack, very very too long for real-time effect!)
I remember it happends other times (2 or 3 times in 3 years!) but I can't make the connexion with the different cases.
I use 4 stereo loops with personnal sounds I load during the play. The "memory duration" of each of my four loops is 12 minutes 40 s...
I read on my system monitor that the software (with 4 stereo loops) use 1Go of memory and my computer configuration is : "Intel Centrino Core 2 Duo T7200 2 GHz" as CPU and 2 Go of DDR II SDRAM (1Go as Swap)
I'm not sure there is any informations in Jack messages but, in case of... (partially in french...)
Code: Select all
18:27:15.400 Changement du graphique des connexions JACK.
subgraph starting at qjackctl timed out (subgraph_wait_fd=16, status = 0, state = Running, pollret = 0 revents = 0x0)
bad status (1) for client sooperlooper handling event (type = 8)
**** alsa_pcm: xrun of at least 0.909 msecs
18:27:15.449 Changement des connexions JACK.
18:27:49.310 Changement du graphique des connexions ALSA.
18:27:49.483 Changement des connexions ALSA.
18:27:54.430 Changement du graphique des connexions JACK.
18:27:54.497 Changement des connexions JACK.
18:27:54.876 Changement du graphique des connexions JACK.
18:27:55.726 Changement du graphique des connexions ALSA.
18:27:55.907 Changement des connexions ALSA.
My questions :
Would it be more sure to run with the terminal way (sooperlooper then slgui) instead of the slgui launcher?
Is my harware configuration strong enough?
Is my Jack configuration appropriate? (500ms timeout could be too short?)
Code: Select all
jackd 0.118.0
Copyright 2001-2009 Paul Davis, Stephane Letz, Jack O'Quinn, Torben Hohn and others.
jackd comes with ABSOLUTELY NO WARRANTY
This is free software, and you are welcome to redistribute it
under certain conditions; see the file COPYING for details
Memory locking is unlimited - this is dangerous. You should probably alter the line:
@audio - memlock unlimited
in your /etc/limits.conf to read:
@audio - memlock 1539312
no message buffer overruns
JACK compiled with System V SHM support.
09:44:44.792 JACK a été démarrer avec le PID=2417.
loading driver ..
apparent rate = 44100
creating alsa driver ... hw:1,0|hw:1,0|1024|2|44100|0|0|nomon|swmeter|-|32bit
control device hw:1
configuring for 44100Hz, period = 1024 frames (23.2 ms), buffer = 2 periods
ALSA: final selected sample format for capture: 32bit integer little-endian
ALSA: use 2 periods for capture
ALSA: final selected sample format for playback: 32bit integer little-endian
ALSA: use 2 periods for playback
Thanks a lot for any suggestions!!!
Amélie
PS : sorry for the french accent...