[PlanetCCRMA] about Fedora updates
Fernando Lopez-Lezcano
nando at ccrma.Stanford.EDU
Sat Mar 13 12:40:02 PST 2010
On Sat, 2010-03-13 at 11:11 -0800, Niels Mayer wrote:
> On Sat, Mar 13, 2010 at 10:06 AM, Fernando Lopez-Lezcano
> <nando at ccrma.stanford.edu> wrote:
> On Sat, 2010-03-13 at 02:35 -0800, Niels Mayer wrote:
> > The stock Fedora version of Jack does not stop pulseaudio or
> prevent
> > it from interfering with sound devices. Therefore, Peter's
> statement
> > only applies to those using CCRMA kernel and Jack.
>
>
> Hmmm, you should be able to use Planet CCRMA's Jack without
> installing
> or using the rt kernel.
>
> Do you still have the error messages you were getting? Or a
> pointer to
> them? (and which soundcard you were using?). I have somehow
> missed this
> and should work on fixing it as soon as I can get a f12
> machine to test.
>
>
> There's two messages I posted on the subject:
> http://comments.gmane.org/gmane.comp.audio.planetccrma.general/9373
>
>
> Executive summary: I think the error has to do w/ CCRMA's Jack not
> indicating "JACK compiled with System V SHM support" whereas the stock
> F12 jack has this SysV SHM support. The lack of shared mem support
> might prevent the default realtime support in Jack from functioning
> -R, --realtime
AFAICT this has nothing to do with your problems. The startup messages
printed during jack initialization are going to be different because the
code base of jack 1.9.x (aka jack2) is completely different from the one
in jack 0.x (aka jack1) - one written in C, the other in C++ by a
completely different team of programmers.
That does not imply any error, they are just different.
> Soundcard in this case is the stock ASUS mobo soundcard a VIA® VT1708S
> 8-channel High Definition Audio CODEC
> using drivers snd_hda_codec_via and snd_hda_intel . At some point I'll
> retest this issue with the M-Audio Delta 66's I'm now using, and also
> omit the erroneous parameters that cause some error messages to be
> output: I should have used "-Chw:NVidia" and not "-Chw:NVidia,1" ...
> however that doesn't seem to be the source of the CCRMA jack
> issue....
>
>
> The differences are apparent at startup:
>
>
> F12's Jack says:
>
>
> 14:56:06.042 JACK is starting...
> 14:56:06.042 /usr/bin/jackd -R -dalsa -r44100 -p128 -n2 -D
> -Chw:NVidia,0 -Phw:NVidia,0 -Xseq -zs -H -M
> 14:56:06.045 JACK was started with PID=23449.
> jackd 0.118.0
> 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
> JACK compiled with System V SHM support.
> loading driver ..
> 14:56:06.244 ALSA connection change.
> apparent rate = 44100
>
>
> CCRMA's Jack says:
>
> 14:33:27.329 JACK is starting...
> 14:33:27.329 /usr/bin/jackd -R -dalsa -r44100 -p128 -n2 -D
> -Chw:NVidia,0 -Phw:NVidia,0 -Xseq -zs -H -M
> 14:33:27.351 JACK was started with PID=22394.
> 14:33:27.684 ALSA connection change.
> 14:33:27.686 ALSA connection graph change.
> no message buffer overruns
> no message buffer overruns
> jackdmp 1.9.4
> Copyright 2001-2005 Paul Davis and others.
> Copyright 2004-2009 Grame.
> jackdmp 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 server starting in realtime mode with priority 60
These are just regular messages, just different because the code is
different. So far there is no error here that I see.
[MUNCH]
> Fixing my son's old F12 Opteron 1220 box before he discovered I broke
> all his music apps, I also rolled back
> from jack-audio-connection-kit-example-clients-1.9.4-1.fc12.ccrma.x86_64 jack-audio-connection-kit-1.9.4-1.fc12.ccrma.x86_64 jack-audio-connection-kit-1.9.4-1.fc12.ccrma.i686. (i just got him all setup with rosegarden, qjackctl, hydrogen and an Akai LPK 25 "laptop keyboard" he got for his 14th birthday, and he's been playing around with all the synths I installed: dssi-calf-plugins-0.0.18.5-3.fc12.x86_64 dssi-vst-wine-0.8-4.fc12.i686 hexter-dssi-0.6.2-3.fc12.x86_64 csound-dssi-5.10.1-14.fc12.x86_64 fluidsynth-dssi-1.0.0-2.fc12.x86_64 dssi-vst-0.8-4.fc12.x86_64 nekobee-dssi-0.1.7-3.fc12.x86_64 whysynth-dssi-20090608-1.fc12.x86_64 dssi-1.0.0-3.fc12.x86_64 dssi-examples-1.0.0-3.fc12.x86_64 xsynth-dssi-0.9.2-3.fc12.x86_64 bristol-0.40.7-6.fc12.x86_64 zynaddsubfx-2.4.0-2.fc12.x86_64 etc...)
>
>
> Using his system
> with jack-audio-connection-kit-1.9.4-1.fc12.ccrma.x86_64 installed,
> note error:
> 14:33:27.329 JACK is starting...
> 14:33:27.329 /usr/bin/jackd -R -dalsa -r44100 -p128 -n2 -D
> -Chw:NVidia,0 -Phw:NVidia,0 -Xseq -zs -H -M
I would not specify separate capture and playback devices if they point
to the same device, there is no point in doing that (could be triggering
a bug in jack2?). Instead of:
-D -Chw:NVidia,0 -Phw:NVidia,0
I would say just:
-d hw:NVidia
(0 is the default)
> 14:33:27.351 JACK was started with PID=22394.
> 14:33:27.684 ALSA connection change.
> 14:33:27.686 ALSA connection graph change.
> no message buffer overruns
> no message buffer overruns
> jackdmp 1.9.4
> Copyright 2001-2005 Paul Davis and others.
> Copyright 2004-2009 Grame.
> jackdmp 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 server starting in realtime mode with priority 60
> ALSA lib conf.c:4484:(parse_args) Unknown parameter 1
> ALSA lib conf.c:4617:(snd_config_expand) Parse arguments
> error: No such file or directory
> ALSA lib control.c:902:(snd_ctl_open_noupdate) Invalid CTL
> hw:NVidia,0
> control open "hw:NVidia,0" (No such file or directory)
jack is trying to get the hw control interface for the card and is not
finding it.
> ALSA lib conf.c:4484:(parse_args) Unknown parameter 1
> ALSA lib conf.c:4617:(snd_config_expand) Parse arguments
> error: No such file or directory
> ALSA lib control.c:902:(snd_ctl_open_noupdate) Invalid CTL
> hw:NVidia,0
> control open "hw:NVidia,0" (No such file or directory)
> audio_reservation_init
> Acquire audio card Audio-1
it aquires card audio-1 from pulseaudio
> creating alsa driver ... hw:NVidia,0|hw:NVidia,0|128|2|44100|
> 0|0|hwmon|hwmeter|-|32bit
> ALSA lib conf.c:4484:(parse_args) Unknown parameter 1
> ALSA lib conf.c:4617:(snd_config_expand) Parse arguments
> error: No such file or directory
> ALSA lib control.c:902:(snd_ctl_open_noupdate) Invalid CTL
> hw:NVidia,0
> control open "hw:NVidia,0" (No such file or directory)
> Cannot initialize driver
> JackServer::Open() failed with -1
again, can't properly open the alsa driver with the parameters
supplied.
> Failed to start server
> 14:33:28.602 JACK was stopped with exit status=255.
> 14:33:28.602 Post-shutdown script...
> 14:33:28.603 killall jackd
> jackd: no process killed
> 14:33:29.039 Post-shutdown script terminated with exit
> status=256.
> 14:33:29.689 Could not connect to JACK server as client. -
> Overall operation failed. - Unable to connect to server.
> Please check the messages window for more info.
> Cannot connect to server socket err = No such file or
> directory
> Cannot connect to server socket
> jack server is not running or cannot be started
>
>
> Downgrading back to stock f12 jack:
>
> Now, jack works again:
>
>
> 14:56:05.566 Logging started --- Tue Feb 2 14:56:05 2010 ---
> 14:56:05.575 Patchbay deactivated.
> 14:56:05.582 Statistics reset.
> 14:56:05.629 Startup script...
> 14:56:05.629 artsshell -q terminate
> 14:56:05.632 ALSA connection graph change.
> 14:56:06.041 Startup script terminated with exit status=256.
> 14:56:06.042 JACK is starting...
> 14:56:06.042 /usr/bin/jackd -R -dalsa -r44100 -p128 -n2 -D
> -Chw:NVidia,0 -Phw:NVidia,0 -Xseq -zs -H -M
> 14:56:06.045 JACK was started with PID=23449.
> jackd 0.118.0
> 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
> JACK compiled with System V SHM support.
> loading driver ..
> 14:56:06.244 ALSA connection change.
> apparent rate = 44100
> creating alsa driver ... hw:NVidia,0|hw:NVidia,0|128|2|44100|0|0|
> hwmon|hwmeter|-|32bit
> ALSA lib conf.c:4484:(parse_args) Unknown parameter 1
> ALSA lib conf.c:4617:(snd_config_expand) Parse arguments error: No
> such file or directory
> ALSA lib control.c:902:(snd_ctl_open_noupdate) Invalid CTL hw:NVidia,0
> control open "hw:NVidia,0" (No such file or directory)
we still see the alsa error. There is something wrong with the setup of
alsa even for this jack.
Maybe jack1 ignores this error and jack2 refuses to start up?
> configuring for 44100Hz, period = 128 frames (2.9 ms), buffer = 2
> periods
> ALSA: final selected sample format for capture: 32bit integer
> little-endian
> ALSA: use 2 periods for capture
> ALSA: final selected sample format for playback: 32bit integer
> little-endian
> ALSA: use 2 periods for playback
> 14:56:06.337 ALSA connection graph change.
> 14:56:08.262 Server configuration saved to "/home/chop/.jackdrc".
> 14:56:08.266 Statistics reset.
> 14:56:11.999 Client activated.
> 14:56:12.003 JACK connection change.
> 14:56:12.016 JACK connection graph change.
>
>
> Where ~/.jackdrc is now
>
> /usr/bin/jackd -R -dalsa -r44100 -p256 -n2 -D -Chw:NVidia,0
> -Phw:NVidia,0 -Xseq -zs -H -M
I would say there is a problem with the alsa drivers in your system, or
access to /dev/snd/* or with the way you are calling jackd (separate
capture and playback devices). Try a very simple command line first,
like:
jackd -R -d alsa -d hw:NVidia
and see what happens. If that works start adding options one by one to
see which one makes a difference.
So far it does not look to me like a generic problem with Fedora 12's
kernel and Planet CCRMA jack.
-- Fernando
More information about the PlanetCCRMA
mailing list