has anyone had experience with the intel ICH7 (high definition audio)
chipset (alsa hda-intel driver) and jack with the alsa backend? i seem
to be getting about 30 xruns per second, sound stutters, no matter what
settings i try.
--
-- Leonard Ritter
-- http://www.leonard-ritter.com
-- http://www.paniq.org
Hi all!
In the past years I've allways been happy using Slackware for
(professional)audio stuff,from versions 9.0 to 10.2.(never any timeconsuming
(kernel)upgrades).Since I have bought a Acer 1690 laptop,that I usually don't
use for audiorecording etc.,I decided to try out Kubuntu 6.06,because of the
out of the box functionality concerning peripherals like WiFi,touchpad&wide
screen graphics.I was able to get some of those working with Slackware ,but
with great effort and some limitations though.To my great surprise it turned
out that through the apt-get manager I was able to get Jack&Ardour up and
running in no time,as where it always took me at least a day to get
everything compiled on the good old P3/800.However,I have no idea about the
lowest latencies I can get with it(with the shipped kernel)and if I want to
compile things from scratch it's certainly no Slackware.
Well,so far so good so nice!
Just my eurocent...
Enrico.
Quoting david <gnome(a)hawaii.rr.com>:
> Paul Winkler wrote:
>
> I don't trust Dell hardware. I spent 11 years working on a help desk for
>
> a large local corporation. When they switched from IBM hardware to Dell
> hardware, our hardware trouble call counts TRIPLED.
I've found people to have very differing opinions about dell. My Dell D820
laptop is an engineering masterpiece (altough it doesn't look as cool as
those *books).
> I can't find any such noise on my Toshiba laptop.
No such noise here either..
Sampo
> Debian testing current libpam-modules 0.79-4 supports rtprio (I use it).
> To be sure just run :
>
> jackd -R -P 70 -d dummy
>
> in another shell launch :
>
> top -H -p `pidof jackd`
>
> PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
> 26812 moino 18 0 21652 21m 3892 S 0 2.1 0:00.01 jackd
> 26813 moino 18 0 21652 21m 3892 S 0 2.1 0:00.00 jackd
> 26814 moino 19 0 21652 21m 3892 S 0 2.1 0:00.00 jackd
> 26815 moino -81 0 21652 21m 3892 S 0 2.1 0:00.00 jackd
> 26816 moino *-71* 0 21652 21m 3892 S 0 2.1 0:00.00 jackd
>
> If rlimit is not working you won't see a thread at prio -71
> Don't be afraid if you don't have the thread at -81 you must have an
> old version of jackd.
>
> If you can verify this you can be sure your problem does not come from
> rlimit or realtime stuff.
> You will have to investigate more.
>
> Goood luck.
>
> PS. If you have a dual core setup I'm not sure your jackd version is patched
> against some hw clock drift problems. Do you have the --clocksource
> option when you launch jackd -h ?
>
> David.
Hi,
thank you for your answer.
rlimits seem to work, becasue i got the same results as mentioned above.
In fact i have a Centrino Duo (Dual Core) notebook, so this might be the reason fpr my xruns and stuttering sound?
If i run jackd -h i got no option mention --clocksource.
What can i do next?
Thank you,
Julian
Okay, I know this question comes up way too often, but I've been
struggling with this for years and for some reason have never been
able to accomplish this, let alone grasp it.
I have a Yamaha Clavinova CLP930 that I wish to use as a MIDI
controller for my computer. Basically I want to be able to play MIDI
events to things like Swami or amSynth through Jack from the
Clavinova. I have an old-style MIDI cable, one with a joystick plug
on the end and a MIDI in and a MIDI out on the other end, which to the
best of my knowledge is hooked up properly. My system is Fedora Core
3 with Planet CCRMA packages and the RDT (?) kernel working properly
as far as I know. Now if there is a better distribution to be using
for this let me know because I plan on getting a new hard drive soon.
I've tried quite a variety and have recently settled on Fedora.
Now when I start Jack up I get an error that claims Jack wasn't able
to connect to the sequencer. I can close Jack and if I type
/sbin/modprobe snd_seq, Jack won't give me this error. I can also
load snd_mpu401uart, but this doesn't seem to have any effect. When I
try to load snd_mpu401 it gives me an error as follows:
FATAL: Error inserting snd_mpu401
(/lib/modules/2.6.11-0.3.rdt.rhfc3.ccrma/updates/drivers/mpu401/snd-mpu401.ko):
No such device
I'm not quite sure what to do about that, but as it stands when I
start Jack now I only have the MIDI Through port listed in my
connections and I'm pretty sure that MPU401 is supposed to be listed.
I can play to all of my MIDI based programs (amSynth and Swami) with
the Virtual Keyboard, and I've tried using Kmidimon to see if any
events are coming across from the Clavinova, there's nothing.
As you can probably tell, I've struggled trying to figure this out for
a while, and still have barely anything. I just don't get the right
feel off of Virtual Keyboard to actually perform. If anybody could
explain this process I promise to make an in-depth howto because I
keep seeing these sorts of questions, but nobody seems to cover
everything (probably because there's a lot to cover). For reference
purposes, because I know somebody will ask for it, I've added my
output of /sbin/lsmod at the bottom of this email.
Chip
Module Size Used by
snd_seq_dummy 4100 0
realtime 5128 0
commoncap 8064 1 realtime
snd_seq 76816 5 snd_seq_dummy
snd_seq_device 9740 2 snd_seq_dummy,snd_seq
parport_pc 29380 1
lp 12780 0
parport 42440 2 parport_pc,lp
autofs4 28932 0
sunrpc 186724 1
ipt_REJECT 7168 1
ipt_state 1792 2
ip_conntrack 45748 1 ipt_state
iptable_filter 3584 1
ip_tables 18944 3 ipt_REJECT,ipt_state,iptable_filter
md5 4096 1
ipv6 284864 8
usblp 13184 0
ohci1394 39812 0
ieee1394 314580 1 ohci1394
uhci_hcd 36368 0
i2c_i801 8460 0
i2c_core 23040 1 i2c_i801
snd_intel8x0 36032 3
snd_ac97_codec 81784 1 snd_intel8x0
snd_pcm_oss 65312 0
snd_mixer_oss 21760 1 snd_pcm_oss
snd_pcm 124296 5 snd_intel8x0,snd_ac97_codec,snd_pcm_oss
snd_timer 38276 2 snd_seq,snd_pcm
snd 76164 15
snd_seq_dummy,snd_seq,snd_seq_device,snd_intel8x0,snd_ac97_codec,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_timer
soundcore 11360 1 snd
snd_page_alloc 10884 2 snd_intel8x0,snd_pcm
e100 50816 0
mii 5120 1 e100
floppy 66992 0
dm_snapshot 18628 0
dm_zero 2432 0
dm_mirror 27884 2
ext3 135560 2
jbd 92184 1 ext3
dm_mod 64148 6 dm_snapshot,dm_zero,dm_mirror
Yves Potin:
>>> It's a lot of work but it's been very stable for me.
>> Thanks Mark, I'll check it out. How long does it take to start from
>> scratch? I have an P4 1.8 that I'd try it on.
>> Then, how long does it take from start (from the small set you
>> mentioned) to a full DAW?
>
> Hi, I take permission to respond to share antother experience with
> gentoo :). If you absolutely don't know gentoo, with a barely solid
> knowledge of a linux system, I would say you'd need more or less one day
> to get a working system (with ardour and MuSE, and other smaller audio
> apps). You need to know how to compile a kernel (and patch it for real
> time of course). Gentoo docs are really well written, and you need to read
> them when installing, especially the handbook.
> http://www.gentoo.org/doc/en/?catid=install (there are many translations).
Hmm, it might take more time. I used 4 days to get something useful. There
were various reasons to this, I don't remember all of them, but I had huge
problems. Not that I wasn't able to solve them, but it took time. The most
irritating thing for me, was that after I got everything to work, I had to
compile up almost everything again after running emerge update, because
an update of a package caused almost everything not to work, and I had to
run a script that checked dependencies of all packages. And of course, non
of this was easy to find out about for a gentoo newbie.
I have the impression though, after reading the forums, that older
install systems (I used the latest 2006 verion) had fewer problems.
Hi,
i am using Debian testing with libpam-modules 0.79-4.
I added
@audio - rtprio 99
@audio - nice -10
@audio - memlock 250000
to /etc/security/limits.conf and i am member of the audio-group.
If i start jack with 'jackd -R -d alsa' it says:
jackd 0.101.1
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 System V SHM support.
loading driver ..
creating alsa driver ... hw:0|hw:0|1024|2|48000|0|0|nomon|swmeter|-|32bit
control device hw:0
configuring for 48000Hz, period = 1024 frames, buffer = 2 periods
nperiods = 2 for capture
nperiods = 2 for playback
As you see there no warning about missing realtime-cappabilities, anyhow realtime seems not work, because i got a lot of xruns....
What i am missing?
Do i need other requirements to fullfill to get realtime to work, e.g. special kernel-configuration?
Thank you,
Julian
There are a lot of hums that are very friendly and encouraging, but the
hum that comes out of my speaker when I start up Jack is way more than
that. It's sharp pitched and I believe it penetrates deep into the soul
and causes unrest there.
It comes about when I use jack at low latencies. I experimented with
ground loops and found it is the same hum (or a similar hum) and simply
gets softer when I use my homebrew ground prong removal cable (it's just
a small extension cord with a three prong socket and a two prong plug. I
must be violating every safety standard in the Universe, and I probably
wouldn't be the first desperate musician to die in an unfortunate
accident caused by valuing artistic purity higher than corporal safety.)
It actually also comes about when I use a pure Alsa program realtime and
at low latencies, but I'm still calling the thing 'Jack Hum' because I
like you jack people so much. That's what you get for being so friendly!
I also don't know any good low latency alsa programs any more.
So... I wonder if someone's looking into this. It's preventing me from
recording stuff. And I've got some insanely good music coming up and
people are actually responding well to my newsletter, which is quite
flabbergasting to me. I'm not used to people responding well to what I do.
I should also mention that I have a firewire audio interface with
included microphone pre-amp, and that the hum gets REALLY lound on the
Mic channels when phantom power is turned on.
So please, please, please help me! I'm desparate. I've been working on
linux audio for over four years and my music's starting to get good
enough to be published and I can't record because of some dumb analogue
engineering problem. Are any smart analogue engineers reading this?
Heck, i'll go for the dumb ones too if it will make my problem go away.
Help!
Carlo
I sent this to PlanetCCRMA ML yesterday, no response. Thought someone
here could help.
For some reason I'm getting the following error when using aplay:
ALSA lib confmisc.c:672:(snd_func_card_driver) cannot find card '1'
ALSA lib conf.c:3492:(_snd_config_evaluate) function
snd_func_card_driver returned error: No such device
I believe there is some mixup during boot about my Midisport 8x8 (which
was 0) and the Delta 66 (which was card 1)
The Midisport doesn't seem to appear now.
For another weirdness, my modprobe is now:
# cat modprobe.conf
alias eth0 3c59x
alias snd-card-1 snd-ice1712
options snd-card-1 index=1
options snd-ice1712 index=1
remove snd-ice1712 { /usr/sbin/alsactl store 1 >/dev/null 2>&1 || : ; };
/sbin/modprobe -r --ignore-remove snd-ice1712
Would the (behind-my-back) removal of the midisport slip the Delta 66
into card 0 spot, but not tell others that the Delta 66 is now card 0
and not card 1? I don't care much about the Midisport, so why doesn't my
Delta66 work?
===
some helpful hints:
# ls /dev/snd
controlC0 pcmC0D0c pcmC0D0p seq timer
# cat /proc/asound/version
Advanced Linux Sound Architecture Driver Version 1.0.11.
Compiled on Jul 25 2006 for kernel 2.6.16-1.2080.16.rrt.rhfc5.ccrma.
# cat /proc/asound/cards
0 [M66 ]: ICE1712 - M Audio Delta 66
M Audio Delta 66 at 0xece0, irq 20
# /sbin/lsmod | grep snd
snd_ice1712 55784 0
snd_ice17xx_ak4xxx 4608 1 snd_ice1712
snd_ak4xxx_adda 6400 2 snd_ice1712,snd_ice17xx_ak4xxx
snd_cs8427 9216 1 snd_ice1712
snd_ac97_codec 84128 1 snd_ice1712
snd_seq_dummy 4100 0
snd_seq_oss 30848 0
snd_seq_midi_event 7296 1 snd_seq_oss
snd_seq 50320 5 snd_seq_dummy,snd_seq_oss,snd_seq_midi_event
snd_pcm_oss 43552 0
snd_mixer_oss 16640 1 snd_pcm_oss
snd_pcm 82976 3 snd_ice1712,snd_ac97_codec,snd_pcm_oss
snd_timer 23068 2 snd_seq,snd_pcm
snd_ac97_bus 2688 1 snd_ac97_codec
snd_i2c 6272 2 snd_ice1712,snd_cs8427
snd_mpu401_uart 8064 1 snd_ice1712
snd_rawmidi 24224 1 snd_mpu401_uart
snd_seq_device 8716 4
snd_seq_dummy,snd_seq_oss,snd_seq,snd_rawmidi
snd 55204 17
snd_ice1712,snd_ice17xx_ak4xxx,snd_ak4xxx_adda,snd_cs8427,snd_ac97_codec,snd_seq_dummy,snd_seq_oss,snd_seq_midi_event,snd_seq,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_timer,snd_i2c,snd_mpu401_uart,snd_rawmidi,snd_seq_device
soundcore 9633 1 snd
snd_page_alloc 10376 1 snd_pcm