[ardour-users] Refugee from Windoze/Cubase -drowning in Linux/Ardour

Keith Smith kah.smith at shaw.ca
Tue Apr 19 14:21:19 PDT 2005


Thanks Mark, and sorry about the earlier direct reply. If I actually
opened my mail instead of just reading it in the browser, I might have
realized how this stuff works. Hmm. Maybe that's a clue about the rest
of my troubles(!). I pasted your reply to that message below this one.

Running Qjackctrl from the Gnome menu on a fresh boot, the GUI comes up
fine.
Going to setup Settings,  I have Server Path as jackd, Driver Alsa, no
realtime or other parameters checked in the first column,  Frames,44100,
2, Port Maximim 128, 
start delay 2 secs, Audio Duplex, Input Device hw:0, Output device:
hw:0,input channels 2, Output channels 2, dither Shaped, and Timeout
200msec.
Options (which I haven't messed with): Execute script on Startup: arts
shell -q terminate, Capture standard output, XRUN dedtection regex: xrun
of at least([0-9|\.]+) msec.
Display Transport time code
Misc Confirm Application close,Keep child windows always on top, Save
Jack audio server configuration to .jackdrc, confirm server shutdown

I hit start and eventually get the error window 'Could not connect to
Jack server as client.'
Here's the message list:

13:26:59.125 Patchbay deactivated.
13:26:59.557 Statistics reset.
13:26:59.663 MIDI connection graph change.
13:26:59.860 MIDI connection change.
13:26:59.862 MIDI connection graph change.
13:40:34.282 Startup script...
13:40:34.282 artsshell -q terminate
13:40:35.053 Startup script terminated with exit status=256.
13:40:35.056 JACK is starting...
13:40:35.057 /usr/local/bin/jackd -t200 -dalsa -r44100 -p1024 -n2 -D -
Chw:0 -Phw:0 -i2 -o2 -zs
13:40:35.077 JACK was started with PID=6262 (0x1876).
jackd 0.99.0
Copyright 2001-2003 Paul Davis 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
JACK compiled with System V SHM support
loading driver ..
apparent rate = 44100
creating alsa driver ... hw:0|hw:0|1024|2|44100|2|2|nomon|swmeter|-|
32bit
control device hw:0
configuring for 44100Hz, period = 1024 frames, buffer = 2 periods
ALSA: cannot set channel count to 2 for capture
ALSA: cannot configure capture channel
cannot load driver module alsa
13:40:35.269 JACK was stopped successfully.
13:40:37.093 Could not connect to JACK server as client.

Now at this point:

[root at S01060050da7307e1 ks]# /sbin/fuser /dev/snd/pcmC0D0p    
/dev/snd/pcmC0D0p:    6076  6076m
[root at S01060050da7307e1 ks]#
(Thanks Paul!!)

and 6076 is jackd

So the way the system sits right now, I can only get Ardour running if I
let it load jack, and that always ends up as 48kHz which is not what I'm
after. I hope that frames the question I'm really trying to ask. (I've
never felt quite so dim :) )

Also it seems clear that alsa isn't happy with the inputs and outputs on
these cards, yet when I have had Ardour up and running, Jack connect
shows i/o for the card and connections can be made. I don't get that at
all.

BTW: Does 'Quit' on the Qjackctrl GUI kill jack, or just Qjackctrl? It
seems to me jack is left running. Is there a kill jack command line
statement I can use to avoid all this rebooting? It seems I shouldn't
have to do this in Linux.

Thanks again,
k



Keith,
   (Did you want this response off list? If not then post and response
back to me through the list. Thanks!)

   The information is perfectly helpful. Your system is working
exactly like it should. This is good. JAck works correctly and you
have the right kernel and right version of Alsa.

   So apparently the two ICE1712 card in separate slots are using the
ICE1712 drivers. Are you getting sound using something like aplay
file.wav? I think you are, at least from card 0.

   Now, since everything is working that means we're probably dealing
with just confusion on your end about how the apps work.

   Can you concisely relate what problem you are having at this point?
The normal way to run Ardour would be:

1) Starrt qjackctl. GUI comes up.
2) Mess a bit with the setting dialog and then start JAck within QJC.
3) Start Ardour.
4) Create a session.
5) Record and playback.

Since you have two cards you may think that you are going to be able
to use them both with Jack. In general you cannot, or at least there
are limitations to doing this. We can cover that later when I
understand more about what hte problem currently is.

Good luck,
Mark

On 4/19/05, Keith Smith <kah.smith at shaw.ca> wrote:
> Hi Mark,
> Thanks for your effort here! You're absolutely right. I should have
> posted on day 1 with "What questions should I ask?" :)
> Here are the  lines from the terminal:
> 
> [ks at S01060050da7307e1 ~]$ uname -r
> 2.6.10-2.1.ll.rhfc3.ccrma
> 
> [ks at S01060050da7307e1 ~]$ cat /proc/asound/version
> Advanced Linux Sound Architecture Driver Version 1.0.9rc1.
> Compiled on Mar 22 2005 for kernel 2.6.10-2.1.ll.rhfc3.ccrma.
> 
> [ks at S01060050da7307e1 ~]$ cat /proc/asound/cards
> 0 [ICE1712 ]: ICE1712 - ICEnsemble ICE1712
> ICEnsemble ICE1712 at 0xb800, irq 9
> 1 [ICE1712_1 ]: ICE1712 - ICEnsemble ICE1712
> ICEnsemble ICE1712 at 0xa400, irq 10
> 2 [BCF2000 ]: USB-Audio - BCF2000
> BEHRINGER BCF2000 at usb-0000:02:0d.0-1, full speed
> 3 [M2x4 ]: USB-Audio - MidiSport 2x4
> M-Audio MidiSport 2x4 at usb-0000:02:0d.2-2.1, full speed
> 
> [ks at S01060050da7307e1 ~]$ cat /proc/interrupts
> CPU0
> 0: 6788138 XT-PIC timer
> 1: 9969 XT-PIC i8042
> 2: 0 XT-PIC cascade
> 3: 20852 XT-PIC eth0
> 5: 252 XT-PIC uhci_hcd
> 7: 707 XT-PIC uhci_hcd
> 8: 1 XT-PIC rtc
> 9: 0 XT-PIC ICE1712, uhci_hcd
> 10: 134221 XT-PIC ICE1712, ehci_hcd, uhci_hcd
> 11: 81 XT-PIC ohci1394
> 12: 103360 XT-PIC i8042
> 14: 72473 XT-PIC ide0
> 15: 60520 XT-PIC ide1
> NMI: 0
> LOC: 6788362
> ERR: 0
> MIS: 0
> 
> [ks at S01060050da7307e1 ~]$ /sbin/lsmod
> Module Size Used by
> nls_utf8 2048 1
> realtime 5128 0
> commoncap 8064 1 realtime
> snd_seq_midi 10400 0
> snd_seq_midi_event 10368 1 snd_seq_midi
> snd_seq 76816 2 snd_seq_midi,snd_seq_midi_event
> parport_pc 29380 0
> lp 12780 0
> parport 42440 2 parport_pc,lp
> autofs4 28932 0
> sunrpc 186724 1
> ipt_REJECT 7168 1
> ipt_state 1792 1
> ip_conntrack 45748 1 ipt_state
> iptable_filter 3584 1
> ip_tables 18944 3 ipt_REJECT,ipt_state,iptable_filter
> vfat 14080 4
> fat 45984 1 vfat
> dm_mod 64148 0
> sd_mod 19072 2
> usb_storage 70848 1
> scsi_mod 138368 2 sd_mod,usb_storage
> md5 4096 1
> ipv6 284864 8
> usb_midi 28164 0
> snd_usb_audio 74048 0
> snd_usb_lib 17280 1 snd_usb_audio
> raw1394 44268 0
> dv1394 28748 0
> ohci1394 39812 1 dv1394
> ieee1394 314580 3 raw1394,dv1394,ohci1394
> uhci_hcd 36368 0
> ehci_hcd 42244 0
> i2c_i801 8460 0
> i2c_core 23040 1 i2c_i801
> snd_ice1712 79428 1
> snd_ice17xx_ak4xxx 4992 1 snd_ice1712
> snd_ak4xxx_adda 6912 2 snd_ice1712,snd_ice17xx_ak4xxx
> snd_cs8427 11520 1 snd_ice1712
> snd_ac97_codec 81784 1 snd_ice1712
> snd_pcm_oss 65312 0
> snd_mixer_oss 21760 1 snd_pcm_oss
> snd_pcm 124296 4 snd_usb_audio,snd_ice1712,snd_ac97_codec,snd_pcm _oss
> snd_timer 38276 2 snd_seq,snd_pcm
> snd_page_alloc 10884 1 snd_pcm
> snd_i2c 6272 2 snd_ice1712,snd_cs8427
> snd_mpu401_uart 11136 1 snd_ice1712
> snd_rawmidi 33696 3 snd_seq_midi,snd_usb_lib,snd_mpu401_uart
> snd_seq_device 9740 3 snd_seq_midi,snd_seq,snd_rawmidi
> snd 76164 20 snd_seq_midi,snd_seq_midi_event,snd_seq,snd_usb
>
_audio,snd_usb_lib,snd_ice1712,snd_ice17xx_ak4xxx,snd_ak4xxx_adda,snd_cs8427,snd _ac97_codec,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_timer,snd_i2c,snd_mpu401_uart, snd_rawmidi,snd_seq_device
> soundcore 11360 2 usb_midi,snd
> 3c59x 41512 0
> floppy 66992 0
> ext3 135560 1
> jbd 92184 1 ext3
> [ks at S01060050da7307e1 ~]$
> 
> [ks at S01060050da7307e1 ~]$ jackd -d alsa -r 44100 -d hw
> jackd 0.99.0
> Copyright 2001-2003 Paul Davis 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
> JACK compiled with System V SHM support
> loading driver ..
> apparent rate = 44100
> creating alsa driver ... hw|hw|1024|2|44100|0|0|nomon|swmeter|-|32bit
> configuring for 44100Hz, period = 1024 frames, buffer = 2 periods
> [ctrl-c]
> jack main caught signal 2
> 
> [ks at S01060050da7307e1 ~]$ jackd -d alsa -r 48000 -d hw
> jackd 0.99.0
> Copyright 2001-2003 Paul Davis 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
> loading driver ..
> apparent rate = 48000
> creating alsa driver ... hw|hw|1024|2|48000|0|0|nomon|swmeter|-|32bit
> configuring for 48000Hz, period = 1024 frames, buffer = 2 periods
> [ctrl-c]
> jack main caught signal 2
> 
> [ks at S01060050da7307e1 ~]$ jackd -R -d alsa -r 44100 -d hw
> jackd 0.99.0
> Copyright 2001-2003 Paul Davis 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
> loading driver ..
> apparent rate = 44100
> creating alsa driver ... hw|hw|1024|2|44100|0|0|nomon|swmeter|-|32bit
> configuring for 44100Hz, period = 1024 frames, buffer = 2 periods
> [ctrl-c]
> jack main caught signal 2
> 
> [ks at S01060050da7307e1 ~]$
> 
> Thanks again Mark. I hope this is helpful.
> k
> 
> On Mon, 2005-04-18 at 18:37 -0700, Mark Knecht wrote:
> > Keith,
> >    Sorry your having troubles. It actually looks to me lieka lot of
> > stuff is working and maybe you're sort of confused about the
structure
> > of all of this. I see others have responded so I'll go in a
different
> > direction. I hope it helps. Will you please run a few commands for
me
> > and post the output back in an email? Thanks!
> >
> > uname -r
> >
> > cat /proc/asound/version
> >
> > cat /proc/asound/cards
> >
> > cat /proc/interrupts
> >
> > /sbin/lsmod
> >
> > My hope here is to get a quick view of the real status of the box.
> >
> > If you would please try strting Jack in a terminal using the
following commands:
> >
> > jackd -d alsa -r 44100 -d hw
> >
> > jackd -d alsa -r 48000 -d hw
> >
> > jackd -R -d alsa -r 44100 -d hw
> >
> > Let's stop there and see how you do. I suspect things are better
than you think.
> >
> > Good luck,
> > Mark
> >
> > On 4/18/05, Keith Smith <kah.smith at shaw.ca> wrote:
> > >
> > > Hello to all.
> > <SNIP>
> > >
> > >      1. What the heck am I doing wrong?
> >
> > Not posting soon enough and gettign frustrated! ;-)
> >
> > <MASSIVE SNIP>
> 



On Mon, 2005-04-18 at 18:37 -0700, Mark Knecht wrote:
> Keith,
>    Sorry your having troubles. It actually looks to me lieka lot of
> stuff is working and maybe you're sort of confused about the structure
> of all of this. I see others have responded so I'll go in a different
> direction. I hope it helps. Will you please run a few commands for me
> and post the output back in an email? Thanks!
> 
> uname -r
> 
> cat /proc/asound/version
> 
> cat /proc/asound/cards
> 
> cat /proc/interrupts
> 
> /sbin/lsmod
> 
> My hope here is to get a quick view of the real status of the box.
> 
> If you would please try strting Jack in a terminal using the following commands:
> 
> jackd -d alsa -r 44100 -d hw
> 
> jackd -d alsa -r 48000 -d hw
> 
> jackd -R -d alsa -r 44100 -d hw
> 
> Let's stop there and see how you do. I suspect things are better than you think.
> 
> Good luck,
> Mark
> 
> On 4/18/05, Keith Smith <kah.smith at shaw.ca> wrote:
> > 
> > Hello to all. 
> <SNIP>
> > 
> >      1. What the heck am I doing wrong?
> 
> Not posting soon enough and gettign frustrated! ;-)
> 
> <MASSIVE SNIP>




More information about the Ardour-Users mailing list