Using Jack audio connection kit with Fedora Core 2
I'm trying to install and use Rosegarden audio application on my Fedora Core 2 x86_64 box running a 2.6.9 kernel.
My system is the following:
AMD Athlon 64 3000+
Asus K8V SE mobo
1GB of DDR400 memory
SATA-150 RAID0 with 2xSeagate Barracuda 7200.2 120MB disks on promise controller
I have succeeded to recompile my kernel so that I have selected a proper CPU (AMD Athlon 64), pre-emptive kernel option and Default security set to module so that I'm able to load realtime-lsm-0.1.1 kernel module.
The module loads up fine and I''m using following command:
It seems that most of the how-to and project documentations handle only 2.4 series kernels. Also it seems that 64bit version help is hard to find.
Should I consider to install another distro (ie SuSe 9.2 or Debian with agnus?) or is there any hope for me to get this system working?
If you need any more details (config files, commands that I've used etc.) please ask for them since I have not necessarily provided all the needed info.
Just some more bits of information for my case.
Audacity was able to play 20 cd quality mono tracks on Fedora Core 2 stock kernel 2.6.9-1.6FC2 with no problems after I had it compiled (does not use Jack)
Ardour plays the track but I've only tried it with latency of about 50ms so the sound breaks up badly even with one mono track
Rosegarden seems like it's playing, but there's no sound. This is only tested with 50ms latency too...
Oh, I forgot.
I have tried LD_ASSUME_KERNEL=2.4.19 but then the Jack will not even do ./configure saying that my selected processor does not support x86 command set
i can't really help but can at least fill in a little bit
i'm using jack on LFS with kernel 2.6.3
kernel is compiled with ICC not GCC (Pentium 4) 32 bit
never used the realtime module like you said
just use sudo on jackd and jack apps so they run as root
with jackd and ladccad running CPU usage is from 0.2 to 0.4 percent
the jackcontroll configuration page says down in the corner latency is 42.7 msec
never tweeked those settings at all..
never had any latency troubles at all and never had sound breaking up.
both midi keyboard and mic input is perfectly in sync with playback.
something is definitly wack about the high cpu usage and that's what is causing sound troubles i think
I also tried executing the Jack as a root when still running the FC2 stock kernel. The latency reported by qjackctll was then about that 48 - 50ms and then there was no overwhelming CPU usage. However with Ardour the sound broke up badly.
possibly some alsa software mixing thing -- just guessing
i have this in .asoundrc (i give the whole thing cause i don't know what might effect)
in the mixer window thingy down at the bottom you have those buttons labled "output"
click on them and choose edit to see what's what
you can either output each individual track to alsa_pcm:playback_1 alsa_pcm:playback_2
or output each track to Ardour/master/in and run master to alsa_pcm:playback
(i think that's how it works anyway)
just play with it
it is possible to make some horrible feedback loops here i found out
my suspicion is just alsa not set up to do software mixing ?
edit to turn off those smily faces
make sure you are not overdriving your soundcard with things turned up too loud
ardour mixer sliders as well as alsamixer settings
seems to be real easy to do with alsa drivers for some reason
and some effects plugins don't work and break up sound real bad in ardour
but i bet you haven't goten to them yet
Thank you for your suggestions foo_bar_foo.
Did you mean with that .asoundrc a file that shoud be located at ~/.asoundrc ? I checked out my /usr/share/alsa//alsa.conf and it tries to load some configuration from
yea ~/.asoundrc sorry for not being clear
(if things are running as root /root/.asoundrc)
i put it both places
if that reads out without complaint then alsa understands .asoundrc ok i think
the other issue i have never seen
it looks lke the kernel module is not loaded
/sbin/lsmod | grep real
should give you realcap and commoncap
have never tried to patch kernel for realtime so not alot of help
jack_create_thread: error -1
that's a jack error not arbour
try this for starting realcap before you start jack
/sbin/service realcap start
/sbin/service realcap stop
i tried reading about the planetccrma build for fedora core2 and they are having the same xrun troubles you were having with jack -R option so even very experienced people can't seem to get this to work yet
you can follow changelog here and try to install planetccrma packages using apt after they get it working
or i guess like you said try another distribution
appearently everything works great with fedora core 1
i personally would go with the debian or audioslack version
might also want to first try building the fastest smallest kernel you can (change the makefile otpimizations)
and trim out all the fat but leave out all the patches that don't seem to work then use sudo to safely get mlock and realtime access. But it is possible that only works for me because i have kernel compiled with intel compiler which is a huge performance gain ? i wonder ?
Hi and thanks again foo_bar_foo!
It seems that I have to work a bit more to get that .asoundrc working. At the end of this message is the output from arecord -L. It does not contain the changes you proposed so the configuration is not propably loading.
realcap is apparently an another way to patch the kernel realtime capable. I propably have to check that out too. I'm using the realtime-lsm-0.1.1 and grepping with lsmod tells:
I'll check out your proposals in more detail at the evening.
Just solved my problem. 2 minutes ago!-) (I'll propably go out and throw
a party ;-)
My solution was to disable the onboard sound chipset and install SB
Audigy Platinum Ex to PCI slot 4 (only slot that does not share the IRQ
channel). I had the card standing unused on my another computer. Then I
just recompiled Jack and everything was working fine!
I suspect that the problem I had might been related to the fact that the
VIA82xxx sound card (onboard) did not have any latency setting when I
looked at it with lspci. Also I had Dlink WLan (ACX111) on my PCI4 slot
and now it is moved to the slot 2 sharing with Marvel Gigabit
Also I had to tweak modules.conf manually to load Audigy driver
(snd-emu10k1) at startup. Currently I'm loading snd-emu10k1-synth
manually. Should I add it to the modules.conf also? What should be the
alias for the driver? How do I get Alsa/Jack/another software to know
about the synth?
So. Only thing to resolve is how to get sound out of Rosegarden. Ardour
seems to work fine now.
Thank you all for your help!
Forgot to mention that I now run jackd with following command line.
You can also get great help for linux audio on irc at irc.freenode.net, channel #lad.
Hope it helps
|All times are GMT -5. The time now is 08:04 AM.|