17 May
2010
17 May
'10
3:59 a.m.
On Mon, 2010-05-17 at 11:32 +1000, Patrick Shirkey wrote:
On 05/17/2010 11:27 AM, Rick Green wrote:
If Rick is starting jackd 1.9.4 that is not necessary. Pulse will
relinquish the card when jackd starts.
On Sun, 16 May 2010, Niels Mayer wrote:
Sorry if this has been done but there is a lot of info to go over here.
You may need to run pulseaudio -k before you start jackd. You can add
that line to the start commands in qjackctl. I
also disabled the pulseaudio of video -- kernel mode setting -- and
behold
the glory of masses of scrolling text at bootup, stable updates, and no
weird ATI radeon bugs.
Speaking of pulseaudio,
http://old.nabble.com/Re:-Fwd:-jack2-p28288652.html is
a potential bad interaction between pulseaudio and jack (through
/etc/security/limits.conf, potential priority escalation issue).
Thanks for all the suggestions. I'll read the articles at those
links, but for now, I'm trying to figure out how to make this system
work with a vanilla configuration as supplied by fedora + CCRMA. My
belief is if those tweaks are necessary, they'll be implemented in
either the fedora or CCRMA install scripts.
a few more observations since my last post:
'desktop' audio isn't working either. I just realized that I'm
getting no beeps or startup sounds from fedora. The motherboard sound
system was detected and automagically configured by Ubuntu, but F12
seems to have detected it, but not generated a functional
configuration. I wonder if that is causing the lock-ups of jackd and
Ardour?
The fedora12 installation didn't detect the other OS installs on the
system, and it over-wrote the MBR, so right now I haven't figured out
how to boot into either my kubuntu 7.10 or Ubuntustudio 10.04
systems. I've looked at the grub.conf on the various partitions, and
they have radically different syntax, so it looks like f12 and US10.04
are running different versions of grub, with different config syntax,
so I can't simply cut'n'paste a few menuentry sections into the f12
grub.conf.
Also have you verified that the card can play any
audio directly through
alsa or pulse audio?
It looks likely there is a problem with the soundcard driver. Too many
things are not working as they should.
-- Fernando
Have you unmuted and adjusted the output with
alsamixer or gnome-mixer
You can run alsamixer on the terminal.
Cheers.
Patrick Shirkey
Boost Hardware Ltd