[PlanetCCRMA] Re: JACK configuration

Sat Apr 9 14:46:01 2005

On Apr 9, 2005 2:04 PM, Bob Bailey <bob@digisonus.com> wrote:
>  Ron,
>  
>  Thanks.  Actually I am using the 2.6 kernels.  I had the same problem in
> both the latest stable release and a couple of the edge kernels.  The issue
> seems to be related to the realtime patch.  I can start jackd, but not
> jackd-realtime (JACK Connection Kit gives 3 options in 'Server Path').

I believe that on Planet machines you are always supposed to use jackd
-R to get realtime operation. My FC2 machine here doesn't even have
jackd-realtime as an executable.

I checked my box and jackd -R is giving better performance (i.e. - no
xruns) while jackd by itself is producing many xruns. Do a similar
test for yourself. If you run jackd -R with a low latency setting and
do well, but then remove the -R and get xruns, then obviously it's
loaded.

rtirq status will give you some info, assuming rtirq is loaded. (lsmod
| grep for that)

[mark@Godzilla mark]$ /etc/rc.d/init.d/rtirq status

  PID CLS RTPRIO  NI PRI %CPU STAT COMMAND
  241 FF      80  -5 120  0.0 SW<  IRQ 8
   20 FF      60  -5 100  0.0 SW<  IRQ 9
  868 FF      60  -5 100  0.0 SW<  IRQ 5
  940 FF      59  -5  99  0.0 SW<  IRQ 11
  343 FF      50  -5  90  0.0 SW<  IRQ 1
  262 FF      49  -5  89  0.0 SW<  IRQ 12
  302 FF      46  -5  86  0.0 SW<  IRQ 14
  304 FF      45  -5  85  0.0 SW<  IRQ 15
  406 FF      43  -5  83  0.0 SW<  IRQ 10
 2126 FF      40  -5  80  0.0 SW<  IRQ 7
 2148 FF      39  -5  79  0.0 SW<  IRQ 4
 2149 FF      38  -5  78  0.0 SW<  IRQ 3
 3164 FF      37  -5  77  0.0 SW<  IRQ 6

[mark@Godzilla mark]$

>  
>  How can I check to see that I have the realtime module loaded at boot and
> running?  I did find the following information when I checked 'serviceconf':
>  
>  Realtime kernel module is loaded, current parameters are:
>  any=1; gid=-1; mlock=1
>  
>  -bb
> 
>  
>  On Sat, 2005-04-09 at 08:24, R Parker wrote: 
>  --- Bob Bailey <bob@digisonus.com> wrote:
> > Mark,
> > 
> > I had enabled the alsa sound start up script with
> > '/sbin/chkconfig
> > alsasound on' 
> > 
> > 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.11.rhfc2.ccrma.
> > 
> > cat /proc/asound/cards:
> > 
> > 0 [M410 ]: ICE1712 - M Audio Delta 410
> > M Audio Delta 410 at 0xd000,
> > irq 10
> > 
> > Starting JACK from the terminal worked using 'jackd
> > -d alsa -d hw'. 
> > When I look into the settings for qjackctl it is
> > using 'jackd-realtime'
> > as the Server Path. Could that be why it couldn't
> > find the JACK server
> > even though I have the the Realtime kernel module
> > loaded?
> 
> All apps must be started by the same user. I assume
> this is a 2.4 kernel. If correct, use jackstart and
> start qjackctl with your normal user account and
> follow suit for all other applications.
> 
> ron
> 
> > RESULT:
> > 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 ..
> > creating alsa driver ...
> > hw|hw|1024|2|48000|0|0|nomon|swmeter|-|32bit
> > configuring for 48000Hz, period - 1024 frames,
> > buffer - 2 periods
> > nperiods - 2 for capture
> > nperiods - 2 for playback
> > 
> > MusE started fine. Now I'll reboot and try this
> > with an Edge kernel. 
> > I'm trying to get a system to the point that a non
> > technical user can
> > use it, preferably with no need to use command lines
> > (ie. system used
> > only as DAW, boots into realtime kernel, alsa
> > started and running
> > indefinitely, JACK control Kit configured with
> > pre-patch for sound card,
> > apps pre-configed, etc..) 
> > 
> > If you see anything else... it is much appreciated. 
> > 
> > 
> > Bob
> > -- 
> > 
> > digi|SONUS
> > p:: 877.769.3173
> > e:: info@digisonus.com
> > 
> > 
> > On Fri, 2005-04-08 at 21:51, Mark Knecht wrote:
> > 
> > > Bob,
> > > Is Alsa running? cat /proc/asound/version and
> > cat /proc/asound/cards
> > > 
> > > Try a couple of simple things first:
> > > 
> > > (as a user)
> > > jackd -d alsa -d hw
> > > 
> > > Does it work?
> > > 
> > > If it does then man jackd and look at the options.
> > If it doesn't we'll
> > > look at why.
> > > 
> > > Interesting options (from memory...)
> > > 
> > > jackd -R -d alsa -r 44100 -n 2 -p 256 -d hw
> > > 
> > > [mark@Godzilla mark]$ jackd -R -d alsa -r 44100 -n
> > 2 -p 256 -d hw
> > > 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 = 44100
> > > creating alsa driver ...
> > hw|hw|256|2|44100|0|0|nomon|swmeter|-|32bit
> > > configuring for 44100Hz, period = 256 frames,
> > buffer = 2 periods
> > > nperiods = 2 for capture
> > > nperiods = 2 for playback
> > > 
> > > 
> > > Interesting. I'm not seeing realtime getting
> > enabled. PlanetEdge kernel.
> > > 
> > > Anyway, give it a try.
> > > 
> > > Cheers,
> > > Mark
> > 
> > 
> > 
> 
> 
>  
> __________________________________ 
> Do you Yahoo!? 
> Make Yahoo! your home page 
> http://www.yahoo.com/r/hs
>  
> 
> 
> -- 
> digi|SONUS
> 1018 4th ave., ste. 306
> oakland, ca 94606
> p:: 877.769.3173
> e:: info@digisonus.com
> 
> 
> 
> 
> 
>