[PlanetCCRMA] Can get jackd to run

Nigel Henry cave.dnb@tiscali.fr
Sat Feb 18 07:50:02 2006


On Saturday 18 February 2006 06:38, rick parker wrote:
> I'm using an M-Audio 1010, which I do get output from
> and in the envy24control I can see input levels on, so
> that seems to be working.  With Frame/Period 1024 it
> still just dies about 5 seconds after starting.
> I don't see any messages that say "xrun" when I do
> this (I'm just looking in the jack mesaage window,
> don't know where else to look).
> When I uncheck Realtime, it seems to stay running
> though, I don't really know what it's for but I'm
> thinking it's probably important. Truthfully, I don't
> even know what I'm supposed to do it jack to use it
> once it's running...
> I did read the FAQ you listed, and I'll take a look at
> the sourceforge list as well in the meantime..
>
> Thanks.

Hi Nick. The first thing I notice from your first post was that the Midi 
patchbay was not available. The Midi patchbay has nothing to do with Jack, 
but is a facility to enable Midi connections in Qjackctl. Run /sbin/lsmod on 
the command line as user. The module you're looking for is snd-seq-midi, 
which you will no doubt see is missing. To force loading of this, again on 
the command line, this time as root, type the following.
/sbin/chkconfig alsasound on .  The snd-seq-midi module should now be loaded 
each time you boot up.

For realtime to work you need the packages "rtirq" and "rtload" and the kernel 
thats designed to use them. To check if you have those 2 packages.
rpm -q rtirq
rpm -q rtload
If they are not there, there are a couple of packages to install as follows.
apt-get update
apt-get install planetccrma-core
apt-get install planetccrma-core-edge
These are low latency kernels, and with one of the packages you get some 
extras. "rtirq" , "rtload" , and a couple of Alsa packages.

You should now have more kernel options on Grubs menu, and realtime should now 
work. Make sure in Qjackctl's setup that the command to start Jack is jackd, 
and not jackstart, which is specific for 2.4 kernels.

See how you get on. Nigel.
>
> --- David Slimp <rock808@gmail.com> wrote:
> > Not sure I can help much with this one...
> >
> > What sound card are you using?
> >
> > If that is a 500MHz machine... is it possible your
> > settings
> > are too demanding to keep up?  (are you seeing xrun
> > messages?)
> > Try a lower sample rate - not 48000.
> > Try a higher Frames/Period - not 512.
> >
> > Have you looked at the jack website/FAQ/HowTo/docs:
> > http://jackit.sourceforge.net/docs/
> >
> > Have you posted/searched the jack mailing list?
>
> http://sourceforge.net/mailarchive/forum.php?forum_id=3040
>
> > ... not trying to avoid your question, but more
> > people on
> > the jack site can probably answer jack questions
> > faster, and
> > might have more experience with how to debug
> > problems.
> > (good to ask/look in both places)
> >
> > david
> >
> >
> > On 2/17/06, rick parker <rickparkerz@yahoo.com>
> >
> > wrote:
> > > First, forgive me if I'm just totally doing
> >
> > something
> >
> > > wrong, I'm pretty new at this...
> > > Ok, so I have an older computer (pIII 500) and
> >
> > wanted
> >
> > > to try Ardour, so to start fresh I wiped it and
> > > installed Fedora Core 3 (from the links on the
> >
> > Planet
> >
> > > CCRMA website).
> > > Went through the Feddora install ok, then
> >
> > installed
> >
> > > the CCRMA kernel and Alsa drivers and booted into
> >
> > it.
> >
> > > Seemed to run fine so I ran the apt-get install
> > > audio-apps and installed of the audio apps.
> > > Now my problem, when I try to run qjackctl
> >
> > (running
> >
> > > with the default settings since I didn't really
> >
> > know
> >
> > > what to set it to), it starts and then soon dies.
> > > Here's what the ouput says, if anyone can tell me
> >
> > what
> >
> > > I'm doing wrong I'd be grateful...
> > > 21:12:25.212 Patchbay deactivated.
> > > 21:12:26.469 Statistics reset.
> > > 21:12:26.585 Could not open ALSA sequencer as a
> > > client. MIDI patchbay will be not available.
> > > ALSA lib seq_hw.c:451:(snd_seq_hw_open) open
> > > /dev/snd/seq failed: No such file or directory
> > > 21:12:40.548 Patchbay deactivated.
> > > 21:13:01.674 Startup script...
> > > 21:13:01.675 artsshell -q terminate
> > > 21:13:02.495 Startup script terminated with exit
> > > status=256.
> > > 21:13:02.500 JACK is starting...
> > > 21:13:02.503 /usr/bin/jackd -R -dalsa -dhw:0
> >
> > -r48000
> >
> > > -p512 -n2
> > > 21:13:02.530 JACK was started with PID=5119
> >
> > (0x13ff).
> >
> > > jackd 0.99.36
> > > 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 = 48000
> > > creating alsa driver ...
> > > hw:0|hw:0|512|2|48000|0|0|nomon|swmeter|-|32bit
> > > control device hw:0
> > > configuring for 48000Hz, period = 512 frames,
> >
> > buffer =
> >
> > > 2 periods
> > > nperiods = 2 for capture
> > > nperiods = 2 for playback
> > > 21:13:04.562 Server configuration saved to
> > > "/home/rickparkerz/.jackdrc".
> > > 21:13:04.566 Statistics reset.
> > > 21:13:04.906 Client activated.
> > > 21:13:04.913 Audio connection change.
> > > 21:13:04.923 Audio connection graph change.
> > > jackd watchdog: timeout - killing jackd
> > > zombified - calling shutdown handler
> > > 21:13:14.834 Shutdown notification.
> > > 21:13:14.838 Client deactivated.
> > > 21:13:14.843 JACK is stopping...
> > > cannot read result for request type 7 from server
> > > (Connection reset by peer)
> > > cannot send request type 7 to server
> > > cannot read result for request type 7 from server
> > > (Broken pipe)
> > > 21:13:15.058 JACK was stopped successfully.
>
> __________________________________________________
> Do You Yahoo!?
> Tired of spam?  Yahoo! Mail has the best spam protection around
> http://mail.yahoo.com
>
> _______________________________________________
> PlanetCCRMA mailing list
> PlanetCCRMA@ccrma.stanford.edu
> http://ccrma-mail.stanford.edu/mailman/listinfo/planetccrma