[RDD] Starting Over
zotz at 100jamz.com
Mon Mar 10 22:04:49 EDT 2008
On Monday 10 March 2008 21:14:31 Michael Barnes wrote:
> Running ps ax shows no instance of jack running. Trying jack_lsp says
> no jack server running. From the command line
> $ jackd -R -d alsa -d hw:0 -r 48000
OK, which user is this?
> It gives all the usual startup stuff and runs. I get appropriate
> response from jack_lsp and other tests. I can run it with or without
> the -R for realtime use. Either way it works from command line. But,
> when I start the rivendell daemons, it apparently starts then stops.
> A jackd.pid file is created with a pid number, but that pid does not
> show up in ps ax.
> I'm sure I am missing something simple I have not set someplace. I
> just can't find (or remember) it. I just did all this last week and
> that went fine (except for the distorted audio).
> The part that worries me is the report from qtjackctl
> "cannot use real-time scheduling (FIFO at priority 10) [for thread
> -1210370368, from thread -1210370368] (1: Operation not permitted)
> cannot create engine"
Which user is running qjackctl?
Did you try unselecting realtime in qjackclt setup?
As a stupid test, what happens if you run qjackctl as root and try starting?
Does google help?:
> On Mon, Mar 10, 2008 at 6:37 PM, drew Roberts <zotz at 100jamz.com> wrote:
> > On Monday 10 March 2008 18:55:42 Michael Barnes wrote:
> > > Jack is starting then crashing. It does create a
> > > /var/run/rivendell/jackd.pid file, but that pid does not exist. I
> > > also find when stopping the daemons, it does not remove the jackd.pid
> > > file.
> > >
> > > As far as I can tell, the command to start jack should be "jackd -R -d
> > > alsa -d hw:0 -r 48000". I can run that from command line and it
> > > starts okay.
> > >
> > > Nowhere can I find any kind of log showing anything about jack.
> > > If I try to start jack with qtjackctl, I get the following error
> > > message.
> > >
> > >
> > >
> > > 17:51:53.169 Patchbay deactivated.
> > > 17:51:53.180 Statistics reset.
> > > 17:51:53.212 MIDI connection graph change.
> > > 17:51:53.392 MIDI connection change.
> > > 17:51:54.852 JACK is starting...
> > > 17:51:54.853 jackd -R -dalsa -dhw:0 -r48000 -p1024 -n2
> > > 17:51:54.859 JACK was started with PID=4980 (0x1374).
> > > jackd 0.102.20
> > > Copyright 2001-2005 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 POSIX SHM support.
> > > cannot use real-time scheduling (FIFO at priority 10) [for thread
> > > -1210370368, from thread -1210370368] (1: Operation not permitted)
> > > cannot create engine
> > > 17:51:54.864 JACK was stopped successfully.
> > > 17:51:54.865 Post-shutdown script...
> > > 17:51:54.865 killall jackd
> > > jackd: no process killed
> > > 17:51:55.079 Post-shutdown script terminated with exit status=256.
> > > 17:51:57.048 Could not connect to JACK server as client. Please check
> > > the messages window for more info.
> > >
> > >
> > > Is the real-time settings what's messing me up? However, when
> > > starting from command line with the -R switch, it runs fine.
> > Are you doing both as the same user? Are you double plus triple sure
> > jack is not already running as another user when trying to start with
> > qjackctl?
> > Exactly how are you starting from the command line?
> > > Michael Barnes told me on 03/10/2008 05:29 PM:
> > > > Well, I wiped out the Ubuntu box and rebuilt it with SUSE. I got
> > > > everything loaded up as best as I can tell. However, the new box
> > > > will not start Jack.
> > > >
> > > > rd.conf, sysconfig, asound.conf are all identical. The new box sets
> > > > up straight to the sound card via alsa. The old box starts jack and
> > > > works.
> > > >
> > > > Where else should I be looking to start jack when Rivendell starts?
> > drew
> Rivendell-dev mailing list
> Rivendell-dev at techweb.rfa.org
More information about the Rivendell-dev