I just did an in-place fc6-to-f8 upgrade and it went pretty smoothly.
One gotcha was I had to adjust the qjackd settings thusly:
1. Change "Server Path" on qjackctl's Setup page to "pasuspender jackd
--". This suspends PulseAudio so it isn't hogging the ALSA ports while
I'm running jackd.
2. Change the "Interface" setting to "hw:0" from "default". jackd
wouldn't start up otherwise. Any idea why?
Fedora 8, 7 and 6 still contain Audacity 1.3.2-beta. There have been
two new beta releases since then. Sooner or later somebody surely will
open a ticket and use reproachful words when requesting an upgrade to
1.3.4-beta, just because it's newer. So, here's some sort of status
update and the opportunity for the community to help with evaluating
that latest beta release. We, the packagers, appreciate all forms of
success and failure reports as well as feedback sent to the Audacity
Fedora 8 binaries of Audacity 1.3.4-beta for i386 and x86_64 can be found here:
They are not signed, but the directory contains a SHA1SUMs file signed
with my key.
The source of these packages can be found in Fedora Package CVS, of
course, albeit in a separate devel branch. A README file in the
rpms/audacity directory contains a few notes about that branch:
The packages were built with wxGTK 2.8.4 as included with Fedora 8 and
no longer with wxGTK 2.6.x. This may result in changes in the GUI.
The packages are NOT built with JACK support, because the PortAudio
v19 audio I/O driver system in Audacity 1.3.4-beta starts the JACK
daemon during initialisation and blocks the ALSA and OSS drivers from
working correctly. There are many errors printed to a terminal. When
built without JACK support, at least one can evaluate the ALSA support
(with or without running Pulse Audio).
Further, as of Audacity 1.3.3-beta, the heavily changed PA v19 driver
system determines inappropriate sample rates, which are rejected by
ALSA, leading to an error dialog until the user chooses a compatible
project rate out of many incompatible ones. This is reason enough to
assume that it breaks in similar ways for other users with different
Anyway, I'm interested in success and problem reports, and I'm even
more interested in anybody's attempts at reporting problems to the
Im trying to use jackd on fc8 on a lenovo x61 laptop.
Sound is ridiculously choppy. Even if I fail to set realtime settings
properly or something it shouldnt be this choppy. Normal sound
through alsa works well.
It makes no difference if I run jackd as root or not.
I run it through qjackctl, and set alsa port hw:0.
I also tried no duplex.
I dont think I have any other sound daemons such as pulseaudio,
esd or arts running.
Any hints how to debug this are apreciated.