keeping Jack from stopping

Optimize your system for ultimate performance.

Moderators: khz, MattKingUSA

Re: keeping Jack from stopping

Postby oNNogitaar » Sun Apr 17, 2011 5:57 pm

...succesfully downgraded the firmware from 5.5 to 4.8.
This is what I get starting Jack:
Code: Select all
19:51:57.622 Patchbay deactivated.
19:51:57.629 Statistics reset.
19:51:57.663 ALSA connection change.
19:51:57.698 ALSA connection graph change.
19:52:37.573 JACK is starting...
19:52:37.574 /usr/bin/jackd -v -P70 -dfirewire -r44100 -p128 -n12
jackd 0.120.1
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    2724522
getting driver descriptor from /usr/lib/jack/jack_firewire.so
19:52:37.610 JACK was started with PID=2991.
no message buffer overruns
getting driver descriptor from /usr/lib/jack/jack_dummy.so
getting driver descriptor from /usr/lib/jack/jack_freebob.so
getting driver descriptor from /usr/lib/jack/jack_oss.so
getting driver descriptor from /usr/lib/jack/jack_net.so
getting driver descriptor from /usr/lib/jack/jack_alsa.so
JACK compiled with System V SHM support.
server `default' registered
registered builtin port type 32 bit float mono audio
registered builtin port type 8 bit raw midi
clock source = system clock via clock_gettime
loading driver ..
start poll on 3 fd's
new client: firewire_pcm, id = 1 type 1 @ 0x90c1578 fd = -1
new buffer size 128
resizing port buffer segment for type 0, one buffer = 512 bytes
resizing port buffer segment for type 1, one buffer = 512 bytes
libffado 2.999.0- built Jan 24 2011 10:57:58
00085520160: Warning (fireworks_session_block.cpp)[ 257] loadFromMemory: size not correct: got 13392, should be -4 according to data
firewire MSG: Streaming thread running with Realtime scheduling, priority 70
firewire MSG: Registering audio capture port C0_001486016bf52dca_Unknown
registered port system:capture_1, offset = 512
firewire MSG: Registering audio capture port C1_001486016bf52dca_Unknown0
registered port system:capture_2, offset = 1024
firewire MSG: Registering audio capture port C2_001486016bf52dca_Unknown1
registered port system:capture_3, offset = 1536
firewire MSG: Registering audio capture port C3_001486016bf52dca_Unknown2
registered port system:capture_4, offset = 2048
firewire MSG: Registering audio capture port C4_001486016bf52dca_Unknown3
registered port system:capture_5, offset = 2560
firewire MSG: Registering audio capture port C5_001486016bf52dca_Unknown4
registered port system:capture_6, offset = 3072
firewire MSG: Registering audio capture port C6_001486016bf52dca_Unknown5
registered port system:capture_7, offset = 3584
firewire MSG: Registering audio capture port C7_001486016bf52dca_Unknown6
registered port system:capture_8, offset = 4096
firewire MSG: Registering audio capture port C8_001486016bf52dca_Unknown7
registered port system:capture_9, offset = 4608
firewire MSG: Registering audio capture port C9_001486016bf52dca_Unknown8
registered port system:capture_10, offset = 5120
firewire MSG: Registering audio capture port C10_001486016bf52dca_Unknown9
registered port system:capture_11, offset = 5632
firewire MSG: Registering audio capture port C11_001486016bf52dca_Unknown10
registered port system:capture_12, offset = 6144
firewire MSG: Registering midi capture port C12_001486016bf52dca_Unknown11
registered port firewire_pcm:C12_001486016bf52dca_Unknown11, offset = 512
firewire MSG: Registering audio playback port P0_001486016bf52dca_Unknown
registered port system:playback_1, offset = 0
firewire MSG: Registering audio playback port P1_001486016bf52dca_Unknown0
registered port system:playback_2, offset = 0
firewire MSG: Registering audio playback port P2_001486016bf52dca_Unknown1
registered port system:playback_3, offset = 0
firewire MSG: Registering audio playback port P3_001486016bf52dca_Unknown2
registered port system:playback_4, offset = 0
firewire MSG: Registering audio playback port P4_001486016bf52dca_Unknown3
registered port system:playback_5, offset = 0
firewire MSG: Registering audio playback port P5_001486016bf52dca_Unknown4
registered port system:playback_6, offset = 0
firewire MSG: Registering audio playback port P6_001486016bf52dca_Unknown5
registered port system:playback_7, offset = 0
firewire MSG: Registering audio playback port P7_001486016bf52dca_Unknown6
registered port system:playback_8, offset = 0
firewire MSG: Registering audio playback port P8_001486016bf52dca_Unknown7
registered port system:playback_9, offset = 0
firewire MSG: Registering audio playback port P9_001486016bf52dca_Unknown8
registered port system:playback_10, offset = 0
firewire MSG: Registering audio playback port P10_001486016bf52dca_Unknown9
registered port system:playback_11, offset = 0
firewire MSG: Registering audio playback port P11_001486016bf52dca_Unknown10
registered port system:playback_12, offset = 0
firewire MSG: Registering midi playback port P12_001486016bf52dca_Unknown11
registered port firewire_pcm:P12_001486016bf52dca_Unknown11, offset = 0
++ jack_sort_graph
++ jack_rechain_graph():
-- jack_rechain_graph()
-- jack_sort_graph
19:52:40.515 JACK connection change.
19:52:40.518 Server configuration saved to "/home/onno/.jackdrc".
19:52:40.520 Statistics reset.
19:52:41.031 Client activated.
19:52:41.044 Buffer size change (0).
server thread back from poll
new client: qjackctl, id = 2 type 2 @ 0xb6dc7000 fd = 50
start poll on 4 fd's
server thread back from poll
new client qjackctl using 51 for events
start poll on 4 fd's
server thread back from poll
start poll on 4 fd's
server thread back from poll
start poll on 4 fd's
server thread back from poll
start poll on 4 fd's
server thread back from poll
start poll on 4 fd's
server thread back from poll
start poll on 4 fd's
server thread back from poll
start poll on 4 fd's
server thread back from poll
start poll on 4 fd's
server thread back from poll
start poll on 4 fd's
server thread back from poll
start poll on 4 fd's
server thread back from poll
start poll on 4 fd's
server thread back from poll
start poll on 4 fd's
server thread back from poll
start poll on 4 fd's
server thread back from poll
start poll on 4 fd's
server thread back from poll
++ jack_sort_graph
++ jack_rechain_graph():
-- jack_rechain_graph()
client event poll on 51 for qjackctl starts at 88030613
back from client event poll after 13 usecs
client event poll on 51 for qjackctl starts at 88030645
back from client event poll after 11 usecs
-- jack_sort_graph
client event poll on 51 for qjackctl starts at 88030747
back from client event poll after 11 usecs
client event poll on 51 for qjackctl starts at 88030854
back from client event poll after 11 usecs
client event poll on 51 for qjackctl starts at 88030901
back from client event poll after 11 usecs
start poll on 4 fd's
server thread back from poll
start poll on 4 fd's
server thread back from poll
start poll on 4 fd's
server thread back from poll
start poll on 4 fd's
server thread back from poll
start poll on 4 fd's
server thread back from poll
start poll on 4 fd's
server thread back from poll
start poll on 4 fd's
server thread back from poll
start poll on 4 fd's
server thread back from poll
start poll on 4 fd's
server thread back from poll
start poll on 4 fd's
server thread back from poll
start poll on 4 fd's
server thread back from poll
start poll on 4 fd's
server thread back from poll
start poll on 4 fd's
server thread back from poll
start poll on 4 fd's
firewire ERR: Could not start streaming threads: -1
DRIVER NT: could not start driver
cannot start driver
starting server engine shutdown
19:52:49.217 JACK connection graph change.
server thread back from poll
stopping driver
unloading driver
client event poll on 51 for qjackctl starts at 94689150
back from client event poll after 45 usecs
client event poll on 51 for qjackctl starts at 94689275
back from client event poll after 54 usecs
client event poll on 51 for qjackctl starts at 94689406
back from client event poll after 39 usecs
client event poll on 51 for qjackctl starts at 94689520
back from client event poll after 39 usecs
client event poll on 51 for qjackctl starts at 94689632
back from client event poll after 39 usecs
client event poll on 51 for qjackctl starts at 94689752
back from client event poll after 39 usecs
client event poll on 51 for qjackctl starts at 94689879
back from client event poll after 40 usecs
client event poll on 51 for qjackctl starts at 94689994
back from client event poll after 74 usecs
client event poll on 51 for qjackctl starts at 94690143
back from client event poll after 39 usecs
client event poll on 51 for qjackctl starts at 94690255
back from client event poll after 39 usecs
client event poll on 51 for qjackctl starts at 94690382
back from client event poll after 39 usecs
client event poll on 51 for qjackctl starts at 94690494
back from client event poll after 39 usecs
client event poll on 51 for qjackctl starts at 94690605
back from client event poll after 38 usecs
client event poll on 51 for qjackctl starts at 94690718
back from client event poll after 39 usecs
client event poll on 51 for qjackctl starts at 94690828
back from client event poll after 52 usecs
client event poll on 51 for qjackctl starts at 94690953
back from client event poll after 39 usecs
client event poll on 51 for qjackctl starts at 94691108
back from client event poll after 43 usecs
client event poll on 51 for qjackctl starts at 94691233
back from client event poll after 45 usecs
client event poll on 51 for qjackctl starts at 94691359
back from client event poll after 62 usecs
client event poll on 51 for qjackctl starts at 94691504
back from client event poll after 42 usecs
client event poll on 51 for qjackctl starts at 94691623
back from client event poll after 41 usecs
client event poll on 51 for qjackctl starts at 94691741
back from client event poll after 41 usecs
client event poll on 51 for qjackctl starts at 94691858
back from client event poll after 55 usecs
client event poll on 51 for qjackctl starts at 94691990
back from client event poll after 65 usecs
client event poll on 51 for qjackctl starts at 94692134
back from client event poll after 40 usecs
client event poll on 51 for qjackctl starts at 94692251
back from client event poll after 41 usecs
19:52:49.373 JACK connection change.
no message buffer overruns
freeing shared port segments
stopping server thread
stopping watchdog thread
last xrun delay: 0.000 usecs
max delay reported by backend: 0.000 usecs
freeing engine shared memory
max usecs: 0.000, engine deleted
cleaning up shared memory
cleaning up files
unregistering server `default'
cannot read server event (Success)
cannot continue execution of the processing graph (Bad file descriptor)
cannot continue execution of the processing graph (Bad file descriptor)
cannot continue execution of the processing graph (Bad file descriptor)
cannot continue execution of the processing graph (Bad file descriptor)
cannot continue execution of the processing graph (Bad file descriptor)
cannot continue execution of the processing graph (Bad file descriptor)
cannot continue execution of the processing graph (Bad file descriptor)
cannot continue execution of the processing graph (Bad file descriptor)
cannot continue execution of the processing graph (Bad file descriptor)
cannot continue execution of the processing graph (Bad file descriptor)
cannot continue execution of the processing graph (Bad file descriptor)
cannot continue execution of the processing graph (Bad file descriptor)
cannot continue execution of the processing graph (Bad file descriptor)
cannot continue execution of the processing graph (Bad file descriptor)
cannot continue execution of the processing graph (Bad file descriptor)
cannot continue execution of the processing graph (Bad file descriptor)
cannot continue execution of the processing graph (Bad file descriptor)
cannot continue execution of the processing graph (Bad file descriptor)
cannot continue execution of the processing graph (Bad file descriptor)
cannot continue execution of the processing graph (Bad file descriptor)
cannot continue execution of the processing graph (Bad file descriptor)
cannot continue execution of the processing graph (Bad file descriptor)
cannot continue execution of the processing graph (Bad file descriptor)
cannot continue execution of the processing graph (Bad file descriptor)
cannot continue execution of the processing graph (Bad file descriptor)
cannot continue execution of the processing graph (Bad file descriptor)
cannot continue execution of the processing graph (Bad file descriptor)
cannot continue execution of the processing graph (Bad file descriptor)
cannot continue execution of the processing graph (Bad file descriptor)
cannot continue execution of the processing graph (Bad file descriptor)
cannot continue execution of the processing graph (Bad file descriptor)
19:52:49.532 Client deactivated.
cannot continue execution of t
19:52:49.534 JACK was stopped successfully.

...so the "flash read failed" error is gone.
But the device won't run
User avatar
oNNogitaar
Establlshed Member
 
Posts: 164
Joined: Thu Oct 14, 2010 7:24 pm
Location: Berlin / Amsterdam

Re: keeping Jack from stopping

Postby oNNogitaar » Tue May 03, 2011 11:06 am

nobody??
User avatar
oNNogitaar
Establlshed Member
 
Posts: 164
Joined: Thu Oct 14, 2010 7:24 pm
Location: Berlin / Amsterdam

Re: keeping Jack from stopping

Postby oNNogitaar » Thu Aug 18, 2011 7:59 am

Hi there,
well, as you probably guessed, I gave up for a while.
But now as Ubuntu promisses With the release of 11.04, the migration to the new FireWire driver stack is complete. No extra configuration steps are required beyond what is needed for running any other soundcard with JACK in realtime mode. If a lowlatency kernel is installed, and the 'audio' group is set up with proper security and user settings, it should 'just work'. I decided to give it another shot.
Code: Select all
09:51:48.493 Patchbay deactivated.
09:51:48.494 Stati09:51:48.493 Patchbay deactivated.
09:51:48.494 Statistics reset.
09:51:48.521 ALSA connection change.
Cannot connect to server socket err = No such file or directory
Cannot connect to server socket
jack server is not running or cannot be started
09:51:48.529 ALSA connection graph change.
09:52:21.740 JACK is starting...
09:52:21.741 /usr/bin/jackd -r -dfirewire -dhw:0 -r44100 -p1024 -n3
Cannot connect to server socket err = No such file or directory
Cannot connect to server socket
jack server is not running or cannot be started
no message buffer overruns
no message buffer overruns
jackdmp 1.9.7
Copyright 2001-2005 Paul Davis and others.
Copyright 2004-2010 Grame.
jackdmp 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
JACK server starting in non-realtime mode
09:52:21.886 JACK was started with PID=2002.
libffado 2.999.0- built Mar 28 2011 17:44:19
firewire ERR: FFADO: Error creating virtual device
Cannot attach audio driver
JackServer::Open() failed with -1
no message buffer overruns
Failed to start server
09:52:22.094 JACK was stopped with exit status=255.
09:52:23.889 Could not connect to JACK server as client. - Overall operation failed. - Unable to connect to server. Please check the messages window for more info.
Cannot connect to server socket err = No such file or directory
Cannot connect to server socket
jack server is not running or cannot be startedstics reset.
09:51:48.521 ALSA connection change.
Cannot connect to server socket err = No such file or directory
Cannot connect to server socket
jack server is not running or cannot be started
09:51:48.529 ALSA connection graph change.
09:52:21.740 JACK is starting...
09:52:21.741 /usr/bin/jackd -r -dfirewire -dhw:0 -r44100 -p1024 -n3
Cannot connect to server socket err = No such file or directory
Cannot connect to server socket
jack server is not running or cannot be started
no message buffer overruns
no message buffer overruns
jackdmp 1.9.7
Copyright 2001-2005 Paul Davis and others.
Copyright 2004-2010 Grame.
jackdmp 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
JACK server starting in non-realtime mode
09:52:21.886 JACK was started with PID=2002.
libffado 2.999.0- built Mar 28 2011 17:44:19
firewire ERR: FFADO: Error creating virtual device
Cannot attach audio driver
JackServer::Open() failed with -1
no message buffer overruns
Failed to start server
09:52:22.094 JACK was stopped with exit status=255.
09:52:23.889 Could not connect to JACK server as client. - Overall operation failed. - Unable to connect to server. Please check the messages window for more info.
Cannot connect to server socket err = No such file or directory
Cannot connect to server socket
jack server is not running or cannot be started

no succes...
Any ideas about what is going wrong?
Thanks!
User avatar
oNNogitaar
Establlshed Member
 
Posts: 164
Joined: Thu Oct 14, 2010 7:24 pm
Location: Berlin / Amsterdam

Re: keeping Jack from stopping

Postby Pablo » Mon Aug 29, 2011 1:44 pm

Hi,

I don't know much about jack with firewire audio devices but you shouldn't run jack in non-realtime mode.

Cheers, Pablo
Pablo
Establlshed Member
 
Posts: 833
Joined: Thu Apr 17, 2008 9:57 pm

Re: keeping Jack from stopping

Postby oNNogitaar » Tue Aug 30, 2011 10:09 am

Pablo wrote:you shouldn't run jack in non-realtime mode.

Thank you Pablo,
that helped at least a bit. It did not crash right away.... These are my settings
Image
These are the messages.
Code: Select all
10:17:48.567 Patchbay deactivated.
10:17:48.576 Statistics reset.
10:17:48.983 ALSA connection change.
Cannot connect to server socket err = No such file or directory
Cannot connect to server socket
jack server is not running or cannot be started
10:17:48.989 ALSA connection graph change.
10:24:20.009 JACK is starting...
10:24:20.009 /usr/bin/jackd -dfirewire -dhw:0 -r44100 -p1024 -n3
Cannot connect to server socket err = No such file or directory
Cannot connect to server socket
jack server is not running or cannot be started
10:24:20.056 JACK was started with PID=2159.
no message buffer overruns
no message buffer overruns
jackdmp 1.9.7
Copyright 2001-2005 Paul Davis and others.
Copyright 2004-2010 Grame.
jackdmp 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
JACK server starting in realtime mode with priority 10
libffado 2.999.0- built Mar 28 2011 17:44:19
01388442307: Warning (fireworks_session_block.cpp)[ 257] loadFromMemory: size not correct: got 13392, should be -4 according to data
10:24:24.808 JACK connection change.
10:24:24.809 Server configuration saved to "/home/onno/.jackdrc".
10:24:24.809 Statistics reset.
10:24:24.818 Client activated.
10:24:24.850 JACK connection graph change.
JackPosixMutex::Unlock res = 1
10:24:27.411 XRUN callback (1).
JackPosixMutex::Unlock res = 1
10:24:47.775 XRUN callback (2).
JackPosixMutex::Unlock res = 1
10:25:06.705 XRUN callback (3).
JackPosixMutex::Unlock res = 1
10:25:10.571 XRUN callback (4).
JackPosixMutex::Unlock res = 1
10:25:26.613 XRUN callback (5).
10:25:40.507 XRUN callback (6).
JackPosixMutex::Unlock res = 1
10:25:48.700 XRUN callback (7).
JackPosixMutex::Unlock res = 1
JackPosixMutex::Unlock res = 1
10:25:49.706 XRUN callback (1 skipped).
JackPosixMutex::Unlock res = 1
10:26:20.844 XRUN callback (9).
JackPosixMutex::Unlock res = 1
10:26:50.889 XRUN callback (10).
JackPosixMutex::Unlock res = 1
10:26:53.630 XRUN callback (11).
10:27:20.881 XRUN callback (12).
JackPosixMutex::Unlock res = 1
JackPosixMutex::Unlock res = 1
10:27:35.118 XRUN callback (13).
JackPosixMutex::Unlock res = 1
10:27:37.787 XRUN callback (14).
JackPosixMutex::Unlock res = 1
10:27:45.600 XRUN callback (15).
JackPosixMutex::Unlock res = 1
10:27:46.852 XRUN callback (16).
JackPosixMutex::Unlock res = 1
10:28:16.898 XRUN callback (17).
10:28:32.165 XRUN callback (18).
JackPosixMutex::Unlock res = 1
JackPosixMutex::Unlock res = 1
10:28:42.651 XRUN callback (19).
JackPosixMutex::Unlock res = 1
10:28:46.892 XRUN callback (20).
JackPosixMutex::Unlock res = 1
10:29:14.886 XRUN callback (21).
JackPosixMutex::Unlock res = 1
10:29:20.834 XRUN callback (22).
JackPosixMutex::Unlock res = 1
JackPosixMutex::Unlock res = 1
10:29:31.689 XRUN callback (24).
JackPosixMutex::Unlock res = 1
10:29:36.003 XRUN callback (25).
JackPosixMutex::Unlock res = 1
10:29:37.380 XRUN callback (1 skipped).
JackPosixMutex::Unlock res = 1
10:29:40.645 XRUN callback (27).
10:30:10.893 XRUN callback (28).
JackPosixMutex::Unlock res = 1
JackPosixMutex::Unlock res = 1
10:30:40.904 XRUN callback (29).
JackFFADODriver::ffado_driver_wait - unhandled xrun
firewire ERR: wait status < 0! (= -1)
JackAudioDriver::ProcessAsync: read error, stopping...

after an hour and a half it still did not actualy stop...
User avatar
oNNogitaar
Establlshed Member
 
Posts: 164
Joined: Thu Oct 14, 2010 7:24 pm
Location: Berlin / Amsterdam

Re: keeping Jack from stopping

Postby oNNogitaar » Fri Sep 23, 2011 10:29 am

anyone?
User avatar
oNNogitaar
Establlshed Member
 
Posts: 164
Joined: Thu Oct 14, 2010 7:24 pm
Location: Berlin / Amsterdam

Re: keeping Jack from stopping

Postby oNNogitaar » Fri Dec 16, 2011 4:28 pm

for anyone interested:
it is running and has not stopped by itself for about 10mins
i run it from terminal as sudo (and ardour too)
if i play back my project there is even sound trough the speakers
:D
i am pretty happy for the moment, that took over a year to accomplish
User avatar
oNNogitaar
Establlshed Member
 
Posts: 164
Joined: Thu Oct 14, 2010 7:24 pm
Location: Berlin / Amsterdam

Re: keeping Jack from stopping

Postby Pablo » Fri Dec 16, 2011 7:27 pm

I have always read from the gurus that if you can run jack as sudo but not as a normal user, you have a bad configuration somewhere. But... as long as it works for you... at last! I suppose you don't feel like removing the magic word.

Congratulations!
Pablo
Establlshed Member
 
Posts: 833
Joined: Thu Apr 17, 2008 9:57 pm

Re: keeping Jack from stopping

Postby oNNogitaar » Thu Dec 22, 2011 7:33 pm

Thanks!
Pablo wrote:I have always read from the gurus that if you can run jack as sudo but not as a normal user, you have a bad configuration somewhere
i guess so yes
Pablo wrote:I suppose you don't feel like removing the magic word.
well actualy i do, and i have found something about permissions on Autostatics pages. So i might give it a try later. First i want to find out if i can realy start working now.
User avatar
oNNogitaar
Establlshed Member
 
Posts: 164
Joined: Thu Oct 14, 2010 7:24 pm
Location: Berlin / Amsterdam

Re: keeping Jack from stopping

Postby slowpick » Fri Dec 23, 2011 12:38 am

Pablo wrote:I have always read from the gurus that if you can run jack as sudo but not as a normal user, you have a bad configuration somewhere. But... as long as it works for you... at last! I suppose you don't feel like removing the magic word.

Congratulations!
Do you know if the setting of qjackctl Periods/Buffer as 3 for usb devices
also holds true for firewire?
slowpick
Establlshed Member
 
Posts: 457
Joined: Mon Apr 25, 2011 10:09 am

Re: keeping Jack from stopping

Postby Pablo » Fri Dec 23, 2011 11:06 pm

Do you know if the setting of qjackctl Periods/Buffer as 3 for usb devices
also holds true for firewire?


It could be. I am not sure.

Cheers! Pablo
Pablo
Establlshed Member
 
Posts: 833
Joined: Thu Apr 17, 2008 9:57 pm

Re: keeping Jack from stopping

Postby StoneCut » Wed Dec 28, 2011 9:17 am

Are you in the "audio" group ? I had issues with Jack when I wasn't ...
StoneCut
Establlshed Member
 
Posts: 42
Joined: Tue Dec 20, 2011 8:15 am

Re: keeping Jack from stopping

Postby oNNogitaar » Tue Jan 10, 2012 8:07 pm

I have been fidling around for a while but i get too many xruns at 8mS latency.
16ms is not realy workable but even than there too many to be able to record...
should i try to get a rt-kernel?
i run Ubuntu 11.10 at the moment...
thank you all!!

btw: i have not worked on the root thingy yet, my first goal is to get it working :D
btw2: how can i tell if i am in the audio group? i do not find this window i used to have in ubuntustudio, but i am sure one can find out in the terminal, right?
User avatar
oNNogitaar
Establlshed Member
 
Posts: 164
Joined: Thu Oct 14, 2010 7:24 pm
Location: Berlin / Amsterdam

Re: keeping Jack from stopping

Postby Capoeira » Tue Jan 10, 2012 8:16 pm

oNNogitaar wrote:I have been fidling around for a while but i get too many xruns at 8mS latency.
16ms is not realy workable but even than there too many to be able to record...
should i try to get a rt-kernel?
i run Ubuntu 11.10 at the moment...
thank you all!!

btw: i have not worked on the root thingy yet, my first goal is to get it working :D
btw2: how can i tell if i am in the audio group? i do not find this window i used to have in ubuntustudio, but i am sure one can find out in the terminal, right?


have you tried a light desktop environment like LXDE? better even adicionaly to this a lightweight window manager like lxdm, slim
User avatar
Capoeira
Establlshed Member
 
Posts: 1112
Joined: Tue May 12, 2009 1:01 pm
Location: Brazil

Re: keeping Jack from stopping

Postby Pablo » Tue Jan 10, 2012 9:32 pm

btw2: how can i tell if i am in the audio group? i do not find this window i used to have in ubuntustudio, but i am sure one can find out in the terminal, right?


Yes. Type:

groups

You will see the groups your user belongs to. If you don't see "audio" between them, type:

sudo adduser onnogitaar audio

assuming onnogitaar is your user name. Change it for the real one.

Cheers, Pablo
Pablo
Establlshed Member
 
Posts: 833
Joined: Thu Apr 17, 2008 9:57 pm

PreviousNext

Return to System Tuning and Configuration

Who is online

Users browsing this forum: No registered users and 1 guest