Re: [Line6linux-devel] UX2 - sysinfo
Status: Pre-Alpha
Brought to you by:
mgrabner
From: Stefan H. <ste...@gm...> - 2011-12-07 08:12:08
|
On Wed, Dec 7, 2011 at 7:03 AM, "Maciej Łoziński" <loz...@o2...> wrote: > On Tue, December 6, 2011 10:43 pm, Stefan Hajnoczi wrote: >> 2011/12/6 Maciej Łoziński <loz...@o2...>: >>> >>> I installed latest version from ux2 branch (rev.896) and it indeed has >>> input source select (my bad, sorry). >>> >>> But I didn't manage to record anything from any input (I was using >>> Audacity 1.3.13 and Arch linux with 3.1.1 kernel). Also JACK was >>> disconnecting about 30 seconds after connecting, and it wasn't possible >>> to record with Ardour+JACK. I also encountered a kernel panic once when >>> plugging in a device. >> >> If you have problems with jack please send the debug messages (with >> qjackctl you can get them by clicking on "Messages"). >> >> Stefan >> > > Here is the output from qjackctl. There are some polish messages - > "Sukces" means 'Success' and "Błędny deskryptor pliku" means 'Invalid > file descriptor'. > > cheers > Maciek > > 07:56:48.270 Patchbay deactivated. > 07:56:48.292 Statistics reset. > 07:56:48.346 ALSA connection change. > 07:56:48.433 ALSA connection graph change. > 07:57:11.811 JACK is starting... > 07:57:11.812 /usr/bin/jackd -r -dalsa -dhw:1 -r44100 -p1024 -n2 > jackd 0.121.3 > 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 > 07:57:11.857 JACK was started with PID=1927. > could not open driver .so '/usr/lib/jack/jack_firewire.so': libffado.so.2: > cannot open shared object file: No such file or directory > could not open driver .so '/usr/lib/jack/jack_net.so': libcelt0.so.2: > cannot open shared object file: No such file or directory > JACK compiled with System V SHM support. > loading driver .. > apparent rate = 44100 > creating alsa driver ... hw:1|hw:1|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: 16bit little-endian > ALSA: use 2 periods for capture > ALSA: final selected sample format for playback: 16bit little-endian > ALSA: use 2 periods for playback > 07:57:14.088 JACK connection change. > 07:57:14.121 Server configuration saved to "/home/maciek/.jackdrc". > 07:57:14.122 Statistics reset. > 07:57:14.126 Client activated. > 07:57:14.135 Buffer size change (1024). > ALSA: poll time out, polled for 34860373 usecs Not an error I'm familiar with but it could mean jack was trying to read/write to the device but gave up after 34 seconds. Using arecord(1) or audacity with ALSA is a good first step at troubleshooting. Adding jack or PulseAudio to the picture can make it harder to see what is going on. Perhaps you'll get more clues by running arecord(1) or audacity. For audacity you can check .xsession-errors to see error messages if you started it from a GUI, if you start it from a terminal then the error messages get printed to the terminal. Stefan |