[Alsa-devel] problems with unresolved symbols in 2.4.25 and intel8x0
Hello, I just did a cvs update -dP on my CVS because I was experiencing lockups when using intel8x0 and my drivers were a bit old. When I had finished running ./cvscompile in alsa-driver, alsa-lib, and alsa-tools along with appropriate make install's, this is the output I got when trying to run modprobe snd-intel8x0 /lib/modules/2.4.25/kernel/sound/acore/snd-pcm.o: unresolved symbol snd_info_unregister_R8ae0c1c7 /lib/modules/2.4.25/kernel/sound/acore/snd-pcm.o: unresolved symbol snd_info_register_R41618e6b /lib/modules/2.4.25/kernel/sound/acore/snd-pcm.o: unresolved symbol snd_card_file_add_Rebed1e7f /lib/modules/2.4.25/kernel/sound/acore/snd-pcm.o: unresolved symbol snd_info_create_card_entry_R1c1b2f3e /lib/modules/2.4.25/kernel/sound/acore/snd-pcm.o: unresolved symbol snd_card_file_remove_Rea2826fe /lib/modules/2.4.25/kernel/sound/acore/snd-pcm.o: unresolved symbol snd_device_register_Rdb26d168 /lib/modules/2.4.25/kernel/sound/acore/snd-pcm.o: unresolved symbol snd_major_R8f595b11 /lib/modules/2.4.25/kernel/sound/acore/snd-pcm.o: unresolved symbol snd_info_create_module_entry_R0088747e /lib/modules/2.4.25/kernel/sound/acore/snd-pcm.o: unresolved symbol snd_register_device_R478a1e3e /lib/modules/2.4.25/kernel/sound/acore/snd-pcm.o: unresolved symbol snd_kcalloc_R4da9e78a /lib/modules/2.4.25/kernel/sound/acore/snd-pcm.o: unresolved symbol _snd_magic_kcalloc_R2061fcb1 /lib/modules/2.4.25/kernel/sound/acore/snd-pcm.o: unresolved symbol snd_device_new_R8feb987a /lib/modules/2.4.25/kernel/sound/acore/snd-pcm.o: unresolved symbol snd_unregister_device_Rb9a10896 /lib/modules/2.4.25/kernel/sound/acore/snd-pcm.o: unresolved symbol snd_magic_kfree_R734de7d7 /lib/modules/2.4.25/kernel/sound/acore/snd-pcm.o: unresolved symbol snd_ctl_register_ioctl_R2aa42294 /lib/modules/2.4.25/kernel/sound/acore/snd-pcm.o: unresolved symbol snd_hidden_kfree_R3d62778c /lib/modules/2.4.25/kernel/sound/acore/snd-pcm.o: unresolved symbol snd_ctl_unregister_ioctl_Rb7f8e374 /lib/modules/2.4.25/kernel/sound/acore/snd-pcm.o: unresolved symbol snd_info_get_str_Rb213fe8b /lib/modules/2.4.25/kernel/sound/acore/snd-pcm.o: unresolved symbol snd_device_free_R8ab7612c /lib/modules/2.4.25/kernel/sound/acore/snd-pcm.o: unresolved symbol snd_hidden_kmalloc_R91c87dfa /lib/modules/2.4.25/kernel/sound/acore/snd-pcm.o: unresolved symbol snd_timer_interrupt_R37d5b4d3 /lib/modules/2.4.25/kernel/sound/acore/snd-pcm.o: unresolved symbol snd_verbose_printd_R85cd4e0b /lib/modules/2.4.25/kernel/sound/acore/snd-pcm.o: unresolved symbol snd_compat_strlcpy_Rb4409a1e /lib/modules/2.4.25/kernel/sound/acore/snd-pcm.o: unresolved symbol snd_timer_new_R76b38309 /lib/modules/2.4.25/kernel/sound/acore/snd-pcm.o: unresolved symbol snd_iprintf_R2f0b152f /lib/modules/2.4.25/kernel/sound/acore/snd-pcm.o: unresolved symbol snd_info_free_entry_R90332a07 /lib/modules/2.4.25/kernel/sound/acore/snd-pcm.o: unresolved symbol snd_power_wait_Rd759a60d /lib/modules/2.4.25/kernel/sound/acore/snd-pcm.o: unresolved symbol snd_timer_notify_R21f43916 /lib/modules/2.4.25/kernel/sound/acore/snd-pcm.o: unresolved symbol snd_info_get_line_R0a6fd27b /lib/modules/2.4.25/kernel/sound/acore/snd-pcm.o: unresolved symbol snd_verbose_printk_Rf52a421e /lib/modules/2.4.25/kernel/sound/acore/snd-pcm.o: insmod /lib/modules/2.4.25/kernel/sound/acore/snd-pcm.o failed /lib/modules/2.4.25/kernel/sound/acore/snd-pcm.o: insmod snd-intel8x0 failed Perhaps something isn't getting built, or I've missed something quite large. Assistance appreciated. _J --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
Re: [Alsa-devel] problems with unresolved symbols in 2.4.25 and intel8x0
Hi, yes this helped, modules are working fine. I still get segv/core when I run alsactl store _J In the new year, Chris Rankin wrote: --- Jeremy Hall [EMAIL PROTECTED] wrote: Hello, I just did a cvs update -dP on my CVS because I was experiencing lockups when using intel8x0 and my drivers were a bit old. When I had finished running ./cvscompile in alsa-driver, alsa-lib, and alsa-tools along with appropriate make install's, this is the output I got when trying to run modprobe snd-intel8x0 I strongly suspect that the following modules (at least) have not been compiled: snd.o snd-timer.o snd-virmidi.o snd-mixer-oss.o They don't get compiled on any of my systems either. You could always try editing your toplevel.config file by hand, and then typing make. Cheers, Chris ___ Yahoo! Messenger - Communicate instantly...Ping your friends today! Download Messenger Now http://uk.messenger.yahoo.com/download/index.html --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
[Alsa-devel] intel8x0: sample rate problems in playback
Hello, I tried to run realplayer after taking a massive CVS update, and now alsa seems to try to up-sample the material, causing a tinny effect. and now with today's CVS, I get: error in snd_ac97_set_rate: cidx=0, reg=0x2e, rate=48000 and no discernable difference in audio, it works ok. _J --- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
Re: [Alsa-devel] Intel8x0 problems with rc1
there also appears to be a delay of upwards of 2 seconds before it starts playing but I don't have anything more in my logs. _J In the new year, Takashi Iwai wrote: At Wed, 03 Dec 2003 15:47:23 +0100, Thomas Charbonnel wrote: Takashi Iwai wrote : Takashi, I applied your patch but nothings shows up in my logs. I even replaced all the KERN_DEBUG by KERN_EMERG, and still nothing. The only thing I get is this : ALSA intel8x0.c:568: codec_semaphore: semaphore is not ready [0x1][0x300100] ALSA intel8x0.c:599: codec_read 0: semaphore is not ready for register 0x56 and the driver still works somehow? Is it possible that your code never gets called ? if the driver works, it must not happen. Takashi Ok, my fault, sorry Takashi, I stupidly reloaded only the snd-intel8x0 module and forgot snd-ac97-codec, here's the log : ac97_pcm_open: rate = 48000, cfg = 2, slots = 0x198 setting ac97 reg 0x2c to rate 48000 setting ac97 reg 0x2e to rate 48000 ALSA ../../alsa-kernel/pci/ac97/ac97_pcm.c:561: error in snd_ac97_set_rate: cidx=0, reg=0x2e, rate=48000 , err=-220ac97_pcm_open: rate = 48000, cfg = 2, slots = 0x198 (The file's rate was 44100 kHz) didn't you get any messages before this? it should be something like checking codec 0, slot = 0xxx / 0xxx probing pcm 0 Takashi --- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel --- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
Re: [Alsa-devel] Intel8x0 problems with rc1
ok, applying.
In the new year, Takashi Iwai wrote:
At Wed, 3 Dec 2003 11:41:23 -0500 (EST),
Jeremy Hall wrote:
there also appears to be a delay of upwards of 2 seconds before it starts
playing
but I don't have anything more in my logs.
you're using the cvs version, right?
then apply the patch below.
Takashi
Index: alsa-kernel/pci/ac97/ac97_pcm.c
===
RCS file: /suse/tiwai/cvs/alsa/alsa-kernel/pci/ac97/ac97_pcm.c,v
retrieving revision 1.8
diff -u -r1.8 ac97_pcm.c
--- alsa-kernel/pci/ac97/ac97_pcm.c 3 Dec 2003 13:37:25 - 1.8
+++ alsa-kernel/pci/ac97/ac97_pcm.c 3 Dec 2003 15:58:24 -
@@ -418,16 +418,19 @@
continue;
avail_slots[0][i] = get_pslots(codec, rate_table[0][i]);
avail_slots[1][i] = get_cslots(codec);
+ printk(KERN_DEBUG checking codec %d, slots = 0x%x / 0x%x\n, i,
avail_slots[0][i], avail_slots[1][i]);
if (!(codec-scaps AC97_SCAP_INDEP_SDIN)) {
for (j = 0; j i; j++) {
if (bus-codec[j])
avail_slots[1][i] = ~avail_slots[1][j];
}
+ printk(KERN_DEBUG - capture slots = 0x%x\n,
avail_slots[1][i]);
}
}
/* FIXME: add double rate allocation */
/* first step - exclusive devices */
for (i = 0; i pcms_count; i++) {
+ printk(KERN_DEBUG probing pcm %d\n, i);
pcm = pcms[i];
rpcm = rpcms[i];
/* low-level driver thinks that it's more clever */
@@ -445,19 +448,23 @@
for (j = 0; j 4 slots; j++) {
if (!bus-codec[j])
continue;
+ printk(KERN_DEBUG .. probing codec %d, slots = 0x%x\n, j,
slots);
rates = ~0;
if (pcm-exclusive) {
/* exclusive access */
tmp = avail_slots[pcm-stream][j] slots;
+ printk(KERN_DEBUG .. tmp = 0x%x\n, tmp);
for (k = 0; k i; k++) {
if (rpcm-stream == rpcms[k].stream)
tmp = ~rpcms[k].r[0].rslots[j];
}
+ printk(KERN_DEBUG .. tmp = 0x%x\n, tmp);
if (tmp) {
rpcm-r[0].rslots[j] = tmp;
rpcm-r[0].codec[j] = bus-codec[j];
rpcm-r[0].rate_table[j] =
rate_table[pcm-stream][j];
rates = get_rates(rpcm, j, tmp, 0);
+ printk(KERN_DEBUG .. rslots = 0x%x,
rate_table = %d, rates = 0x%x\n, tmp, rpcm-r[0].rate_table[j], rates);
avail_slots[pcm-stream][j] = ~tmp;
}
} else {
@@ -476,6 +483,7 @@
}
if (rpcm-rates == ~0)
rpcm-rates = 0; /* not used */
+ printk(KERN_DEBUG -- slots = 0x%x, rates = 0x%x\n,
rpcm-r[0].slots, rpcm-rates);
}
bus-pcms_count = pcms_count;
bus-pcms = rpcms;
@@ -500,6 +508,7 @@
unsigned char reg;
int err = 0;
+ printk(KERN_DEBUG ac97_pcm_open: rate = %d, cfg = %d, slots = 0x%x\n, rate,
cfg, slots);
if (rate 48000) /* FIXME: add support for double rate */
return -EINVAL;
bus = pcm-bus;
@@ -548,9 +557,10 @@
}
if (reg_ok (1 (reg - AC97_PCM_FRONT_DAC_RATE)))
continue;
+ printk(KERN_DEBUG setting ac97 reg 0x%x to rate
%d\n, reg, rate);
err = snd_ac97_set_rate(pcm-r[r].codec[cidx], reg,
rate);
if (err 0)
- snd_printk(KERN_ERR error in
snd_ac97_set_rate: cidx=%d, reg=0x%x, rate=%d\n, err=%d, cidx, reg, rate, err);
+ snd_printk(KERN_ERR error in
snd_ac97_set_rate: cidx=%d, reg=0x%x, rate=%d, err=%d\n, cidx, reg, rate, err);
else
reg_ok |= (1 (reg -
AC97_PCM_FRONT_DAC_RATE));
}
---
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive? Does it
help you create better code? SHARE THE LOVE, and help us help
YOU! Click Here: http://sourceforge.net/donate/
___
Alsa-devel mailing list
[EMAIL
Re: [Alsa-devel] Fwd: [was Re: [linux-audio-user] Multiple (three) RME Hammerfalls... any experience]
You're actually going to want 6 RME9652's if you want 72 channels at 96. In jackd/engine.c, change engine-port_max to 512. I think you won't need all of those, I think you'll need 304. You can slave them together using pcm_multi as long as they're all linked with a master clock, alsa won't do it for you. Look for pcm.rme9652_96 in the archives, and if it's not there, I'll send it again. Be sure to use recent alsa, because syncing multiple cards kicked off a code change that prevented lockups. I'd be interested to know how low you could set your latency before jack kicks something out. _J In the new year, Patrick Shirkey wrote: I have forwarded this to alsa-devel as there is probably more luck finding the answer here and it would be a valuable thread to have as a resource. R Parker wrote: Hi, I can't help you much, however, unless JACK has recently been worked on I think there's a 32 track limitation. It's known to be technically trivial. Otherwise I don't believe alsa would be a problem, assuming you've got wordclock i/o on the hammerfall cards. Midi Time Code syncronization in Ardour could also be problematic, it doesn't work with my Tascam DM-24. Even though transport location is accurate, the automation system can't interpret Ardour mtc. Paul has announced his intention to implement SMPTE but I'm not sure if that's been done yet. I wonder what the status of 96kHz adat is with the hammerfall drivers. Anyway, that's not much help. Sorry. ron --- Ronald van Engelen [EMAIL PROTECTED] wrote: Hi, After rereading my message, I saw too many unclarities and typos, so I'll try again. The problem is that we have to transfer a few hours of 72-channel music from three synced Mackie SDR24/96's to a harddisk. I don't really know what format the music is recorded in. As my colleague is unable to use three RME Hammerfall DSP card's in his dual G4 powermac with OSX (don't know exact version), I wondered if I could use Linux to capture the music to harddisk. If anybody has any experience, please let me know. Otherwise we will proceed with one card and thus 24 channels at a time, which does work. Thanks, Ronald van Engelen Op vr 28-11-2003, om 20:06 schreef Ronald van Engelen: Hi there, A colleague of mine is having major problems using multiple (three) RME Hammerfall cards using Mac OS 9 and X and consulted me for help. The problem is that he has to transfer a few hours of 72-channel music (recorded with Mackie HDR's) to his harddisk for further mixing and processing. I only have experience with (single and dual) stereo cards using alsa, jack, ardour and ladspa. I wonder if anybody have experience with multiple RME cards using alsa, and particullary experience doing such a task with mentioned tools? I haven't had the chance to examine his (Mac-related) problem but it sounds like he might suffering from problems related to his power-supply? Regards, Ronald van Engelen -- Patrick Shirkey - Boost Hardware Ltd. Http://www.boosthardware.com Http://www.djcj.org - The Linux Audio Users guide Apparently upon the beginning of the barrage, the donkey broke discipline and panicked, toppling the cart. At that point, the rockets disconnected from the timer, leaving them strewn around the street. Tethered to the now toppled cart, the donkey was unable to escape before the arrival of U.S. troops. United Press International Rockets on donkeys hit major Baghdad sites By P. MITCHELL PROTHERO Published 11/21/2003 11:13 AM --- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel --- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
Re: [Alsa-devel] CVS server problems: old RCS files corrupted
What about the ones on alsa-project, was it _THAT_ long ago? _J In the new year, Takashi Iwai wrote: At Mon, 17 Nov 2003 18:33:35 +0300, Sergey Vlasov wrote: [1 text/plain; us-ascii (7bit)] Hello! I have tried to look at the ALSA CVS log through the anonymous CVS access (using recursive 'cvs log'), but encountered several errors in old files (which no longer exist in the current version): cvs [server aborted]: unrecognized operation '\x9' in /cvsroot/alsa/alsa-driver/kernel/Attic/mixer.c,v cvs server: warning: duplicate key `log' in version `1.33' of RCS file `/cvsroot/alsa/alsa-driver/lowlevel/isa/Attic/es1688.c,v' cvs server: warning: duplicate key `text' in version `1.33' of RCS file `/cvsroot/alsa/alsa-driver/lowlevel/isa/Attic/es1688.c,v' ... cvs [server aborted]: invalid rcs file /cvsroot/alsa/alsa-driver/lowlevel/isa/Attic/es1688.c,v: premature end of value Tried the backup server too - no difference. Probably the files have been corrupted? looks like so. possibly the filesystem on sf server was corrupt. i guess it's not easy to repair this kind of failures. Takashi --- This SF. Net email is sponsored by: GoToMyPC GoToMyPC is the fast, easy and secure way to access your computer from any Web browser or wireless device. Click here to Try it Free! https://www.gotomypc.com/tr/OSDN/AW/Q4_2003/t/g22lp?Target=mm/g22lp.tmpl ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel --- This SF. Net email is sponsored by: GoToMyPC GoToMyPC is the fast, easy and secure way to access your computer from any Web browser or wireless device. Click here to Try it Free! https://www.gotomypc.com/tr/OSDN/AW/Q4_2003/t/g22lp?Target=mm/g22lp.tmpl ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
Re: [Alsa-devel] anybody else OK with current CVS *and* SMP?
Kai, did you make a multi out of your cards together? _J In the new year, Kai Vehmanen wrote: On Tue, 5 Aug 2003, Paul Davis wrote: i am having a repeated problem with system lockups using current CVS with JACK running SCHED_FIFO on an SMP system, with the Planet's 2.4.21 kernel. No lockups so far with the following setup: 2.4.19-ll ALSA CVS of today JACK CVS of today snd-ens1371/snd-ice1712/snd-dummy low-level drivers (tried all three) jackd run SCHED_FIFO with -n 3 -p 256 two or more JACK clients active Do you get lockups if you use snd-dummy as the lowlevel driver? How about without ardour (just jackd and some example clients running)? -- http://www.eca.cx Audio software for Linux! --- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa0013ave/direct;at.aspnet_072303_01/01 ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel --- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa0013ave/direct;at.aspnet_072303_01/01 ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
Re: [Alsa-devel] anybody else OK with current CVS *and* SMP?
WICKED!
How does THAT work? when was that feature added? how does it maintain
sample-synch? Is it better to use a pcm_multi or this option?
I suspect people are finding locking issues in the multi code, but not
sure. I'm doing ok with it in 2.5.75-mm1, although I'm having latency
issues and clients get killed when you use jack_connect in rapid fire.
_J
In the new year, Kai Vehmanen wrote:
On Thu, 7 Aug 2003, Jeremy Hall wrote:
Kai, did you make a multi out of your cards together?
Nope, jackd accessed the individual soundcards directly (... -d alsa -d
hw:{0,1,2}).
In the new year, Kai Vehmanen wrote:
No lockups so far with the following setup:
2.4.19-ll
ALSA CVS of today
JACK CVS of today
snd-ens1371/snd-ice1712/snd-dummy low-level drivers (tried all three)
jackd run SCHED_FIFO with -n 3 -p 256
two or more JACK clients active
Do you get lockups if you use snd-dummy as the lowlevel driver? How about
without ardour (just jackd and some example clients running)?
--
http://www.eca.cx
Audio software for Linux!
---
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa0013ave/direct;at.aspnet_072303_01/01
___
Alsa-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/alsa-devel
---
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa0013ave/direct;at.aspnet_072303_01/01
___
Alsa-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/alsa-devel
Re: [Alsa-devel] I must be really dense
I reran snddevices and it seems happy, hopefully I can still go back and
forth between old and new setups
thanks
_J
In the new year, Clemens Ladisch wrote:
Jeremy Hall wrote:
when I try to run alsactl restore or alsactl store, it whines
about snd_ctl_open no such file or directory
Did you run snddevices?
state.15 { ...
}
state.15_1 { ...
}
What is the ID of your card? (see /proc/asound/cards)
The other state is old and can be deleted.
HTH
Clemens
---
This SF.Net email sponsored by: Parasoft
Error proof Web apps, automate testing more.
Download eval WebKing and get a free book.
www.parasoft.com/bulletproofapps1
___
Alsa-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/alsa-devel
---
This SF.Net email sponsored by: Parasoft
Error proof Web apps, automate testing more.
Download eval WebKing and get a free book.
www.parasoft.com/bulletproofapps1
___
Alsa-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/alsa-devel
Re: [Alsa-devel] [PATCH] alsactl fixes
it's in the lib somewhere I saw it both with es1938 and intel8x0 (I don't have es1938 anymore) and yes I removed both my /etc/asound.state and .asoundrc _J In the new year, Takashi Iwai wrote: At Tue, 24 Jun 2003 19:57:49 -0400 (EDT), Jeremy Hall wrote: anoncvs has not picked up changes. i just compared the file with the repository and it looks ok for me. perhaps it wasn't notified correctly. could you check it again? I am seeing a core dump when I try to run alsactl store and don't know why. gdb isn't helping me on this machine. grrr, works for me. which soundcard are you using? does it happen even if you remove (or rename) the existing /etc/asound.state? btw, you don't have to run alsactl as root. you can specify the file to store via -f option if you run alsactl store as the normal user. well, in the worst case, printf() is your friend ;) Takashi --- This SF.Net email is sponsored by: INetU Attention Web Developers Consultants: Become An INetU Hosting Partner. Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission! INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
Re: [Alsa-devel] [PATCH] alsactl fixes
anoncvs has not picked up changes. I am seeing a core dump when I try to run alsactl store and don't know why. gdb isn't helping me on this machine. _J In the new year, Takashi Iwai wrote: At Fri, 20 Jun 2003 09:09:43 +0200 (METDST), Clemens Ladisch wrote: When a card doesn't have any controls, the state.cardid.control node isn't written to the output file because the node's join flag has been set. This patch modifies alsactl not to set the join flag in this case to prevent the no state is present for card message from alsactl restore. And the check in line 510 used the wrong variable. applied to cvs. thanks, Takashi --- This SF.Net email is sponsored by: INetU Attention Web Developers Consultants: Become An INetU Hosting Partner. Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission! INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel --- This SF.Net email is sponsored by: INetU Attention Web Developers Consultants: Become An INetU Hosting Partner. Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission! INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
[Alsa-devel] lock with pcm_multi for two rme9652 cards
Hello,
For years I have thought my machine was plagued with heating issues, and
many other reasons for my spurious lockups, indeed I had many different
lockups manifesting themselves, but I now have proof for my madness.
It appears a lockup can somehow be caused if RME9652 both try to stop at
once. Attached is output from gdb that should hopefully at least start to
point us down the right track to resolving this long-standing bug. THe
kernel is still in this state should a developer desire more information,
say from another thread.
_J
Script started on Sun Apr 13 10:30:46 2003
Rainbow:/usr/src/linux-2.5.67 # gdb vmlinux
GNU gdb 5.3
Copyright 2002 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type show copying to see the conditions.
There is absolutely no warranty for GDB. Type show warranty for details.
This GDB was configured as i686-pc-linux-gnu...
gdb_interrupt (irq=4, dev_id=0x0, regs=0xc04f5ddc)
at arch/i386/lib/kgdb_serial.c:194
194 continue ;
warning: shared library handler failed to enable breakpoint
(gdb) bt
#0 gdb_interrupt (irq=4, dev_id=0x0, regs=0xc04f5ddc)
at arch/i386/lib/kgdb_serial.c:194
#1 0xc010cd68 in handle_IRQ_event (irq=4, regs=0xc04f5ddc, action=0xdffee640)
at arch/i386/kernel/irq.c:214
#2 0xc010cfd1 in do_IRQ (regs=
{ebx = -1068548096, ecx = -615541760, edx = 0, esi = -615539544, edi =
-615517184, ebp = -1068540392, eax = -1068548096, xds = 123, xes = 123, orig_eax =
-252, eip = -1072561615, xcs = 96, eflags = 646, esp = -1068548096, xss =
-1049704000}) at arch/i386/kernel/irq.c:395
#3 0xc010b60c in common_interrupt () at net/8021q/vlan.c:130
#4 0xc0332ca0 in snd_pcm_stop (substream=0xc16ec900, state=4)
at sound/core/pcm_native.c:723
#5 0xc0338030 in snd_pcm_update_hw_ptr_interrupt (substream=0xc16ec900)
at sound/core/pcm_lib.c:179
#6 0xc033b88e in snd_pcm_period_elapsed (substream=0xc16ec900)
at sound/core/pcm_lib.c:2016
#7 0xc0340fca in snd_rme9652_interrupt (irq=10, dev_id=0xc1679dc8,
regs=0xc04f5ed4) at sound/pci/rme9652/rme9652.c:1965
#8 0xc010cd68 in handle_IRQ_event (irq=10, regs=0xc04f5ed4, action=0xc1700be0)
at arch/i386/kernel/irq.c:214
#9 0xc010cfd1 in do_IRQ (regs=
{ebx = -615539712, ecx = 1, edx = -615546880, esi = -1049704000, edi = 12, ebp =
-1068540124, eax = -1049704000, xds = 123, xes = 123, orig_eax = -246, eip =
-1070367156, xcs = 96, eflags = 646, esp = -615539712, xss = -1049704000})
at arch/i386/kernel/irq.c:395
#10 0xc010b60c in common_interrupt () at net/8021q/vlan.c:130
#11 0xc033b88e in snd_pcm_period_elapsed (substream=0xc16ec9c0)
at sound/core/pcm_lib.c:2016
#12 0xc0340faf in snd_rme9652_interrupt (irq=12, dev_id=0xc17171c8,
regs=0xc04f5f94) at sound/pci/rme9652/rme9652.c:1961
#13 0xc010cd68 in handle_IRQ_event (irq=12, regs=0xc04f5f94, action=0xc1700340)
at arch/i386/kernel/irq.c:214
#14 0xc010cfd1 in do_IRQ (regs=
{ebx = -1068548096, ecx = -1068548096, edx = -1068548096, esi = -1072657920, edi
= -1072672768, ebp = -1068539960, eax = 0, xds = 123, xes = 123, orig_eax = -244, eip
= -1072657871, xcs = 96, eflags = 582, esp = -1068539944, xss = -1072657697}) at
arch/i386/kernel/irq.c:395
#15 0xc010b60c in common_interrupt () at net/8021q/vlan.c:130
#16 0xc0108adf in cpu_idle () at arch/i386/kernel/process.c:146
#17 0xc0105065 in rest_init () at init/main.c:371
#18 0xc04f68a5 in start_kernel () at init/main.c:463
(gdb) up
#1 0xc010cd68 in handle_IRQ_event (irq=4, regs=0xc04f5ddc, action=0xdffee640)
at arch/i386/kernel/irq.c:214
214 continue;
(gdb) print *action
$1 = {handler = 0xc024fd40 gdb_interrupt, flags = 536870912, mask = 0,
name = 0xc03fff98 KGDB-stub, dev_id = 0x0, next = 0x0}
(gdb) up
#2 0xc010cfd1 in do_IRQ (regs=
{ebx = -1068548096, ecx = -615541760, edx = 0, esi = -615539544, edi =
-615517184, ebp = -1068540392, eax = -1068548096, xds = 123, xes = 123, orig_eax =
-252, eip = -1072561615, xcs = 96, eflags = 646, esp = -1068548096, xss =
-1049704000}) at arch/i386/kernel/irq.c:395
395 retval = 2 + local_enabled;
(gdb) print *eip
No symbol eip in current context.
(gdb) print xes
No symbol xes in current context.
(gdb) up
#3 0xc010b60c in common_interrupt () at net/8021q/vlan.c:130
130 vlan_proc_cleanup();
(gdb) up
#4 0xc0332ca0 in snd_pcm_stop (substream=0xc16ec900, state=4)
at sound/core/pcm_native.c:723
723 SND_PCM_ACTION(stop, substream, state);
(gdb) l
718 /**
719 * snd_pcm_stop
720 */
721 int snd_pcm_stop(snd_pcm_substream_t *substream, int state)
722 {
723 SND_PCM_ACTION(stop, substream, state);
724 }
725
726 static inline int snd_pcm_pre_pause(snd_pcm_substream_t *substream, int push)
727 {
(gdb) print substream
$2 = (snd_pcm_substream_t *) 0xc16ec900
[Alsa-devel] rme9652 in kernel
Hi, I built rme9652 in my kernel so that I could debug with kgdb. Unfortunately it runs rme9652 before hammerfall_mem, so it refuses to insert hammerfalls because of no memory, then it makes the memory but doesn't bother to go back and check for the hammerfalls. Where is the code that sets this order? _J --- This SF.net email is sponsored by: Etnus, makers of TotalView, The debugger for complex code. Debugging C/C++ programs can leave you feeling lost and disoriented. TotalView can help you find your way. Available on major UNIX and Linux platforms. Try it free. www.etnus.com ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
Re: [Alsa-devel] rme9652 in kernel
well, it's simple, adjust the makefile so that hammerfall-mem.o comes before rme9652.o _J In the new year, Jeremy Hall wrote: Hi, I built rme9652 in my kernel so that I could debug with kgdb. Unfortunately it runs rme9652 before hammerfall_mem, so it refuses to insert hammerfalls because of no memory, then it makes the memory but doesn't bother to go back and check for the hammerfalls. Where is the code that sets this order? _J --- This SF.net email is sponsored by: Etnus, makers of TotalView, The debugger for complex code. Debugging C/C++ programs can leave you feeling lost and disoriented. TotalView can help you find your way. Available on major UNIX and Linux platforms. Try it free. www.etnus.com ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel --- This SF.net email is sponsored by: Etnus, makers of TotalView, The debugger for complex code. Debugging C/C++ programs can leave you feeling lost and disoriented. TotalView can help you find your way. Available on major UNIX and Linux platforms. Try it free. www.etnus.com ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
[Alsa-devel] e-mail address changed
Hello, Effective immediately, please use [EMAIL PROTECTED] for all communications for me. [EMAIL PROTECTED] no longer works. _J --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
Re: [Alsa-devel] two RME9652 cards used as a pcm_multi
Hi, I put up a serial console and discovered that when the lock occurs, the sysrq doesn't even work. This rules out memory problems, right? So now we have irq storm and pci misconfiguration? _J In the new year, Jeremy Hall wrote: I specified nosmp and the lockup still occurred. That leaves memory debugging, irq storm, and pci misconfiguration...right? Which is most likely? _J In the new year, Jaroslav Kysela wrote: On Fri, 27 Sep 2002, Jeremy Hall wrote: Hello all, I am using two RME9652 cards together as a single pcm_multi device so that I can get 24 channels both at 48 and 96khz without a cable reconfig. I have an SMP machine and have noticed that when using the pcm_multi device, all the channels are mapped correctly and seem to work correctly until I use jack and ardour. If I use a single card with jack and ardour the sessions can start nicely, but if I use the bonded (YICK) pcm_multi setting, the machine will lock up and the card will endlessly replay some material at a rapid rate causing the famous hammerfall hum that is higher in pitch the smaller the frames_per_cycle. After consulting Paul Davis, the conclusion is that jack exercizes the alsa drivers in unique and interesting ways, exposing subtlties. I have never been able to get 96khz to work at any frames_per_cycle setting, although I can get 48khz to work if I use 1024 or greater frames_per_cycle. This is unacceptable to me as I require smaller latency and would expect at least 512 or 256 to work given that I can get a single card to work reliably at 64 frames_per_cycle. The problem seems to occur when XRUNS are detected rapidly such as session initialization or if the CPU can't keep up with some real-time CPU constraints. I haven't tried this with a UP kernel because I don't know what would happen if I tried to boot a SMP box on a UP kernel--I recall texts saying this was impossible, although this was years ago in the beginning of SMP development. Try specify 'nosmp' with SMP kernel at lilo prompt. Anyway, the lock up should be avoided. Perhaps, you may try to enable spinlock debugging in your kernel (CONFIG_DEBUG_SPINLOCK in kernel debugging menu) and memory allocation (CONFIG_DEBUG_SLAB) for sure. If it does not help to identify the problem, other reasons might be possible: - wrong PCI configuration (PCI bus will cause dead-lock) - IRQ storm Jaroslav - Jaroslav Kysela [EMAIL PROTECTED] Linux Kernel Sound Maintainer ALSA Project http://www.alsa-project.org SuSE Linuxhttp://www.suse.com -- I do not get viruses because I do not use MS software. If you use Outlook then please do not put my email address in your address-book so that WHEN you get a virus it won't use my address in the From field. --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel -- I do not get viruses because I do not use MS software. If you use Outlook then please do not put my email address in your address-book so that WHEN you get a virus it won't use my address in the From field. --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
[Alsa-devel] two RME9652 cards used as a pcm_multi
Hello all, I am using two RME9652 cards together as a single pcm_multi device so that I can get 24 channels both at 48 and 96khz without a cable reconfig. I have an SMP machine and have noticed that when using the pcm_multi device, all the channels are mapped correctly and seem to work correctly until I use jack and ardour. If I use a single card with jack and ardour the sessions can start nicely, but if I use the bonded (YICK) pcm_multi setting, the machine will lock up and the card will endlessly replay some material at a rapid rate causing the famous hammerfall hum that is higher in pitch the smaller the frames_per_cycle. After consulting Paul Davis, the conclusion is that jack exercizes the alsa drivers in unique and interesting ways, exposing subtlties. I have never been able to get 96khz to work at any frames_per_cycle setting, although I can get 48khz to work if I use 1024 or greater frames_per_cycle. This is unacceptable to me as I require smaller latency and would expect at least 512 or 256 to work given that I can get a single card to work reliably at 64 frames_per_cycle. The problem seems to occur when XRUNS are detected rapidly such as session initialization or if the CPU can't keep up with some real-time CPU constraints. I haven't tried this with a UP kernel because I don't know what would happen if I tried to boot a SMP box on a UP kernel--I recall texts saying this was impossible, although this was years ago in the beginning of SMP development. I am looking for words of encouragement as to how I may help diagnose this problem and what proactive steps I may try. I am using 2.4.19-PRE2 with CVS of about a week ago. I am using LL and preempt patches. I realize your schedule is busy and that you may not be able to just jump right on this. Do you have an idea when you might be able to look at this? Your help is appreciated. _J -- I do not get viruses because I do not use MS software. If you use Outlook then please do not put my email address in your address-book so that WHEN you get a virus it won't use my address in the From field. --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
Re: [Alsa-devel] two RME9652 cards used as a pcm_multi
I specified nosmp and the lockup still occurred. That leaves memory debugging, irq storm, and pci misconfiguration...right? Which is most likely? _J In the new year, Jaroslav Kysela wrote: On Fri, 27 Sep 2002, Jeremy Hall wrote: Hello all, I am using two RME9652 cards together as a single pcm_multi device so that I can get 24 channels both at 48 and 96khz without a cable reconfig. I have an SMP machine and have noticed that when using the pcm_multi device, all the channels are mapped correctly and seem to work correctly until I use jack and ardour. If I use a single card with jack and ardour the sessions can start nicely, but if I use the bonded (YICK) pcm_multi setting, the machine will lock up and the card will endlessly replay some material at a rapid rate causing the famous hammerfall hum that is higher in pitch the smaller the frames_per_cycle. After consulting Paul Davis, the conclusion is that jack exercizes the alsa drivers in unique and interesting ways, exposing subtlties. I have never been able to get 96khz to work at any frames_per_cycle setting, although I can get 48khz to work if I use 1024 or greater frames_per_cycle. This is unacceptable to me as I require smaller latency and would expect at least 512 or 256 to work given that I can get a single card to work reliably at 64 frames_per_cycle. The problem seems to occur when XRUNS are detected rapidly such as session initialization or if the CPU can't keep up with some real-time CPU constraints. I haven't tried this with a UP kernel because I don't know what would happen if I tried to boot a SMP box on a UP kernel--I recall texts saying this was impossible, although this was years ago in the beginning of SMP development. Try specify 'nosmp' with SMP kernel at lilo prompt. Anyway, the lock up should be avoided. Perhaps, you may try to enable spinlock debugging in your kernel (CONFIG_DEBUG_SPINLOCK in kernel debugging menu) and memory allocation (CONFIG_DEBUG_SLAB) for sure. If it does not help to identify the problem, other reasons might be possible: - wrong PCI configuration (PCI bus will cause dead-lock) - IRQ storm Jaroslav - Jaroslav Kysela [EMAIL PROTECTED] Linux Kernel Sound Maintainer ALSA Project http://www.alsa-project.org SuSE Linuxhttp://www.suse.com -- I do not get viruses because I do not use MS software. If you use Outlook then please do not put my email address in your address-book so that WHEN you get a virus it won't use my address in the From field. --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
[Alsa-devel] pcm_multi can cause a kernel lockup
Hi,
I am running 2.4.19-pre2+ll+preempt and seeing some annoying crashes when
using pcm_multi.
the setup:
running jack with something like this:
ctl.rme9652_48 {
type hw
card 0
}
pcm.rme9652_48 {
type multi
slaves.a.pcm rme9652_0;
slaves.a.channels 26;
slaves.b.pcm rme9652_1
slaves.b.channels 26
bindings.0.slave a;
bindings.0.channel 0;
...
bindings.27.slave b;
bindings.27.channel 25;
}
ctl.rme9652_0 {
type hw;
card 0;
}
ctl.rme9652_1 {
type hw
card 1
}
pcm.rme9652_0 {
type hw
}
pcm.rme9652_1 {
type hw
card 1
}
Whatever jack period size doesn't seem to matter, the problem seems to be
when for some reason the kernel makes jack wait on the order of
miliseconds, like say 9 or more. Jack's response to this is to stop and
restart the audio device. When this happens using a multi device, the
computer locks and pressing reset is necessary--it won't respond to pings
even.
It is a dual 1.6ghz Athlon machine and the only audio hardware in it are
the two hammerfalls. I am running CVS of recent, looks like Apr 12 at
around 00:08 GMT was when I checked it out. Any help would be
appreciated. card0 is the master, providing word clock to card1.
The ADAT ports have valid sync, but the SPDIF ports do not, for they are
not connected to anything.
_J
___
Alsa-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/alsa-devel
[Alsa-devel] when did the rme9652 driver break?
Hi, What is going on? my computer goes on vacation for a week and when it returns and updates its CVS, alsa now locks the kernel when I try to use the rme9652 card. Jack whines about loads of xruns, which get larger as time goes by, resulting in a system crash that must be hard-reset. When were these unstable changes introduced so I may revert back to a more stable build? Other apps besides jack can cause the computer to lock as well. _J ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
Re: [Alsa-devel] when did the rme9652 driver break?
ah yes, now works GREAT! operating with 1.12 of the rme9652.c _J In the new year, Takashi Iwai wrote: At Tue, 19 Feb 2002 10:03:42 -0500 (EST), Jeremy Hall wrote: Hi, What is going on? my computer goes on vacation for a week and when it returns and updates its CVS, alsa now locks the kernel when I try to use the rme9652 card. Jack whines about loads of xruns, which get larger as time goes by, resulting in a system crash that must be hard-reset. When were these unstable changes introduced so I may revert back to a more stable build? Other apps besides jack can cause the computer to lock as well. oops, sorry, perhaps my fault. a typo was introduced in fixes for non-intel architectures. now fixed on cvs. please give a try. Takashi ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
Re: [Alsa-devel] when did the rme9652 driver break?
Hi, Actually there appear to be some wierd cases where the driver can still cause XRUNS, but these may not be alsa-related things. Do you have an idea where this might be coming from if in alsa? (but don't spend flocks of time on it, just a quick think over it) _J In the new year, Jeremy Hall wrote: ah yes, now works GREAT! operating with 1.12 of the rme9652.c _J In the new year, Takashi Iwai wrote: At Tue, 19 Feb 2002 10:03:42 -0500 (EST), Jeremy Hall wrote: Hi, What is going on? my computer goes on vacation for a week and when it returns and updates its CVS, alsa now locks the kernel when I try to use the rme9652 card. Jack whines about loads of xruns, which get larger as time goes by, resulting in a system crash that must be hard-reset. When were these unstable changes introduced so I may revert back to a more stable build? Other apps besides jack can cause the computer to lock as well. oops, sorry, perhaps my fault. a typo was introduced in fixes for non-intel architectures. now fixed on cvs. please give a try. Takashi ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
Re: [Alsa-devel] More woes with the RME 9652 soundcard
just yesterday I had an issue where ardour was running at frames_per_cycle == 64 and capturing. After about 5 minutes or so (wildly random guess) I had some wierd alignment problems that caused me to be quite concerned that coming next would be the famous hammerfall hum at whatever amplitude it locked for looping. After instructing people to remove headphones quickly, I restarted ardour and all was well. To be safe, I used 128 instead of 64 and it was happier. I have gotten strange results from ardour before, but they really started being more frequent after the mmap api changes went into alsa-lib concerning snd_mmap_commit (or whatever the call is) where it returns the number of committed frames. I noticed that rec-enabling some channels had 3 predictible random responses: 1: the correct signal is heard 2: distorted alien-like noises that sortta resemble the content appear 3: LOUD OBNOXIOUS CRACKLING IS HEARD! It is option 3 that has me most annoyed, an unsuspecting person might have hearing loss if sitting in the control room while bringing up channels--the solution is to tell ardour to roll even when there is no program material--this seems to get things moving nicely again. The option 3 is like an off by one byte issue. All this is AFTER the hw-pointer changes went into alsa-CVS. References to ardour here are audioengine ardour, not jack ardour. _J ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
Re: [Alsa-devel] RE: Hammerfall woes
Try jack (jackit.sf.net) it will help you in part with what you want. latest ardour CVS requires this. _J In the new year, Ivica Bukvic wrote: As far as the ardour is concerned, when I start it with -D rme9652 -i 8 -o 8 flags, and press play it only plays a quick click-like snippet of a sound and immediately stops (no xruns reported). Why is this happening (I am using the 4-6 days old CVS version)? no idea. your description sort of implies you can record with ardour ... or did you just insert a pre-existing soundfile? I inserted pre-existing soundfile. What is also interesting that when the sound stops it is also pretending as if I pressed the stop button (it does not freeze or continue to pretend as if it is playing sound). I will try the latest cvs as well as recompile the alsa drivers in hope that will make it work. the hammerfall cannot do this. the hammerfall-DSP can do matrix routing of signals between channels, but it does not mix software streams down to a channel. Crap! :-) So does this mean that RME card cannot be accessed from multiple applications at the same time? This is one of the most annoying limitations Linux audio architecture has had ever! It automatically eliminates any kind of real-time multi-channel performance capability where one wants to utilize multiple processes (i.e. pd, jmax and cmix running at the same time). Even the old SGI's had this solved in a very elegant fashion, needless to mention OS X or Windows (yes, I know, I know, at the expense of latency, but at least I was not limited to using one app at the time)... It seems that if someone wants to do a multi-channel installation using linux and is interested in live/interactive music, the best bet would be to purchase several SBlive cards (with their horrid resampling stuff) and use them for mixing (unfortunately none of them come as laptop models). Do you know whether this software mixing stuff done in SBLive soundcard is done in hardware or in software that the creative has released? If it is in software, then someone could easily reverse-engineer it and find out how they've done it, which would greatly help make other drivers behave in the same fashion. Is there a way for artsd to be aware of the multiple channels RME card has and for artsd to provide software downmixing despite the fact RME has no mixer? i would note in passing that there are people in the SF bay area who are prepared to pay US$600-$1000 to have machines set up to run linux audio software. its not a trivial thing to do, despite what you may hope for and might have read. in fact, its no more or less trivial than getting windows/macos setup for proper operation with audio software. I am somewhat aware of this, but being primarily a musician, I am growing extremely tired of doing continuous maintenance work instead of composing. All work and no play makes...feel free to add the rest :-( Ico ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
Re: [Alsa-devel] re: Hammerfall woes
I do not know what this rtcmix thingie is, but here are a couple options you have: Convert the rtcmix program to use jack, adding jack functionality to it figure out how to get rtcmix to use a fifo or stdin/stdout, then write a small jack app that interfaces with it. It should be no more than a page of code. _J In the new year, Ivica Bukvic wrote: Try jack (jackit.sf.net) it will help you in part with what you want. latest ardour CVS requires this. _J Thanks for your help. But isn't it true that the app has to be jack-aware in order to utilize it as a software downmixing tool? For instance, I am greatly interested in running multiple processes of RTcmix scripting language, where I would be able to share the mic input with multiple RTcmix processes that would run simultaneously, and at the same time share sound outputting resource between all these resources. RTcmix is currently oss-only. Ico ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
Re: [Alsa-devel] more RME 9652 Hammerfall problems
WHat is line 15 of your .asoundrc? _J ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
Re: [Alsa-devel] more RME 9652 Hammerfall problems
When you use the hw:1 syntax, you are expecting alsa to try to talk to the
card directly. Try this in your .asoundrc.
pcm.rme9652 {
type hw
card 1
device 0
}
ctl.rme9652 {
type hw
card 1
}
pcm.dsp1 {
type plug
slave.pcm.rme9652
}
then
aplay -Ddsp1 filew.wav
Alsa will perform the needed conversions for you.
You want the ctl entry so that ardour will work properly. When you use
aplay or any other application, use dsp1 as your alsa device, and when you
use ardour, use rme9652, because ardour wants the raw access.
_J
In the new year, Ivica Bukvic wrote:
First off, thanks all for your assistance. I'm a bit closer to getting
this darn thing working. Upon being instructed by Paul Davis, I did the
following things:
#alsactl -f foo store 1 (because my Hammerfall is currently seen as the
second card)
I edited foo file, and changed the following:
control.17 {
comment.access 'read write'
comment.type ENUMERATED
comment.item.0 ADAT1
comment.item.1 Internal
iface PCM
name 'ADAT1 Input Source'
value ADAT1
}
to
control.17 {
comment.access 'read write'
comment.type ENUMERATED
comment.item.0 ADAT1
comment.item.1 Internal
iface PCM
name 'ADAT1 Input Source'
value Internal
}
saved the file, then did
#alsactl -f foo restore 1
#alsasound restart
And now I have asound.stat stating that syns is set to internal.
But, now when I try to use the card with aplay, I get the following
error:
#alsactl -Dhw:1 sndfile
Playing WAVE sndfile : Signed 16 bit Little Endian, Rate 44100 Hz,
Stereo
aplay: set_params:734: Access type not available
What does this mean? (I tried also -Dhw:1,0 or -Dhw:1,1 and -Dhw:1,2
without success)
I tried using aplay with my primary card PCI 128 with:
#aplay -Dhw:0 sndfile
and it played just fine.
So what am I doing wrong now?
Just for reference sake, these are only devices I have in my /dev/snd
dir:
controlC0 midiC0D0 pcmC0D0p pcmC1D0c seq
controlC1 pcmC0D0c pcmC0D1p pcmC1D0p timer
Maybe this helps...
Also, could someone please be so kind to send me their asoundrc file
that they are using for the hammerfall, so that I can learn from it as
to how to configure it since the one that comes with alsa-driver package
is rather esotheric for my understanding? Thank you very much!
Sincerely,
Ivica Ico Bukvic, composer, multimedia sculptor,
programmer, webmaster computer consultant
http://meowing.ccm.uc.edu/~ico/
[EMAIL PROTECTED]
To be is to do - Socrates
To do is to be - Sartre
Do be do be do - Sinatra
I am - God
___
Alsa-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/alsa-devel
___
Alsa-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/alsa-devel
Re: [Alsa-devel] what are the latest PCM changes?
Did you try capture or just playback?
I loaded ardour and began record enabling channels until I got to channel
16 (Audio 17) then began to examine why there was a problem.
Due to some bizarre lockup problem, I am updating my kernel this morning,
I'll update CVS of alsa too.
_J
In the new year, Jaroslav Kysela wrote:
On Tue, 11 Dec 2001, Jeremy Hall wrote:
Hi,
I just updated my alsa from about a week ago, I updated then to try out
the new default rme9652 changes that went in.
I began to notice intermitant problems with linking two cards together in
a multi pcm and today after updating to current CVS, I cannot get channels
17-24 to work.
What exactly doesn't work? I've just tested your configuration and it
works perfectly here. I'm using modified dummy driver to emulate two
RME9652 cards and configuration to store stream contents to /tmp/alsa?.raw
files.
I used (in addition to your configuration):
pcm.rme9652_1 {
type file
file /tmp/alsa0.raw
slave.pcm {
type hw
card 1
device 1 # replace with 0; 1 is for dummy driver!!!
}
}
pcm.rme9652_0 {
type file
file /tmp/alsa1.raw
slave.pcm {
type hw
card 0
device 1 # replace with 0; 1 is for dummy driver!!!
}
}
pcm.perex1 {
type plug;
slave.pcm rme9652_48;
ttable.0.0 1;
ttable.1.1 1;
ttable.0.16 1;
ttable.1.17 1;
}
Jaroslav
-
Jaroslav Kysela [EMAIL PROTECTED]
SuSE Linuxhttp://www.suse.com
ALSA Project http://www.alsa-project.org
___
Alsa-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/alsa-devel
___
Alsa-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/alsa-devel
Re: [Alsa-devel] corruption in snd_pcm_multi code
After extensively debugging this, I do not think the problem is in alsa. _J In the new year, Jeremy Hall wrote: any words on this? _J In the new year, Jeremy Hall wrote: Hi, I can't find a difference in the way audioengine and jack open / configure the alsa device, but audioengine works, jack does not. Jack DOES work on a single card, just not when both cards are linked. Abramo, do you have time to look at this? _J In the new year, Jeremy Hall wrote: yeah I know and I looked at that and it all looks fine. I need to look at the exact calls to track it down. I was just hoping you might be able to see an easy thing. Let me know if you do get time to look at it. _J In the new year, Jaroslav Kysela wrote: On Sat, 1 Dec 2001, Jeremy Hall wrote: What more info can I provide to help assist you? I'm sorry, I have no time to check this thing. All initialization is being done in _snd_pcm_multi_open and snd_pcm_multi_open. Jaroslav - Jaroslav Kysela [EMAIL PROTECTED] SuSE Linuxhttp://www.suse.com ALSA Project http://www.alsa-project.org ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
Re: [Alsa-devel] corruption in snd_pcm_multi code
Hi, I can't find a difference in the way audioengine and jack open / configure the alsa device, but audioengine works, jack does not. Jack DOES work on a single card, just not when both cards are linked. Abramo, do you have time to look at this? _J In the new year, Jeremy Hall wrote: yeah I know and I looked at that and it all looks fine. I need to look at the exact calls to track it down. I was just hoping you might be able to see an easy thing. Let me know if you do get time to look at it. _J In the new year, Jaroslav Kysela wrote: On Sat, 1 Dec 2001, Jeremy Hall wrote: What more info can I provide to help assist you? I'm sorry, I have no time to check this thing. All initialization is being done in _snd_pcm_multi_open and snd_pcm_multi_open. Jaroslav - Jaroslav Kysela [EMAIL PROTECTED] SuSE Linuxhttp://www.suse.com ALSA Project http://www.alsa-project.org ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
[Alsa-devel] problems with libaoss
Hi,
I have the following definition in my .asoundrc:
pcm.dsp0 {
type plug
pcm.slave rme9652_48
ttable.0.0 0.25
ttable.1.1 0.25
ttable.0.2 1
ttable.1.3 1
}
When I play with freeamp which was linked with libaoss.so, I get what
sounds like old audio being played in the buffer late. When I use
ecasound with the same alsa device, the correct thing happens, and when I
try to use mpg123 with the LD_PRELOAD hack it says it does not know what
symbol dlsym is and refuses to run. I'd have to link against libaoss I
guess to determine if this definitively is a libaoss thing. I dare not
try the kernel oss driver again because last time I used it it locked my
computer.
This is with the rme9652 and CVS of today.
_J
___
Alsa-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/alsa-devel
Re: [Alsa-devel] corruption in snd_pcm_multi code
What more info can I provide to help assist you?
_J
In the new year, Jeremy Hall wrote:
What more info can I provide?
_J
In the new year, Jeremy Hall wrote:
Here is a segment of my .asoundrc.
pcm_slave.rme9652_s {
pcm rme9652_0
}
pcm.rme9652_1 {
type hw
card 1
}
ctl.rme9652_1 {
type hw
card 1
}
pcm.rme9652_0 {
type hw
card 0
}
ctl.rme9652_0 {
type hw
card 0
}
ctl.rme9652_48 {
type hw
card 0
}
pcm.rme9652_48 {
type multi;
slaves.a.pcm rme9652_0;
slaves.a.channels 26;
slaves.b.pcm rme9652_1;
slaves.b.channels 26;
bindings.0.slave a;
bindings.0.channel 0;
bindings.1.slave a;
bindings.1.channel 1;
bindings.2.slave a;
bindings.2.channel 2;
bindings.3.slave a;
bindings.3.channel 3;
bindings.4.slave a;
bindings.4.channel 4;
bindings.5.slave a;
bindings.5.channel 5;
bindings.6.slave a;
bindings.6.channel 6;
bindings.7.slave a;
bindings.7.channel 7;
bindings.8.slave a;
bindings.8.channel 16;
bindings.9.slave a;
bindings.9.channel 17;
bindings.10.slave a;
bindings.10.channel 18;
bindings.11.slave a;
bindings.11.channel 19;
bindings.12.slave a;
bindings.12.channel 20;
bindings.13.slave a;
bindings.13.channel 21;
bindings.14.slave a;
bindings.14.channel 22;
bindings.15.slave a;
bindings.15.channel 23;
bindings.16.slave b;
bindings.16.channel 8;
bindings.17.slave b;
bindings.17.channel 9;
bindings.18.slave b;
bindings.18.channel 10;
bindings.19.slave b;
bindings.19.channel 11;
bindings.20.slave b;
bindings.20.channel 12;
bindings.21.slave b;
bindings.21.channel 13;
bindings.22.slave b;
bindings.22.channel 14;
bindings.23.slave b;
bindings.23.channel 15;
bindings.24.slave a;
bindings.24.channel 24;
bindings.25.slave a;
bindings.25.channel 25;
bindings.26.slave b;
bindings.26.channel 24;
bindings.27.slave b;
bindings.27.channel 25;
}
In the new year, Jaroslav Kysela wrote:
On Wed, 28 Nov 2001, Jeremy Hall wrote:
Hi,
Today I saw what is believed to be data corruption. In the middle of
snd_pcm_multi_avail_update, I discovered:
(gdb) print *multi-slaves
$13 = {pcm = 0x5, channels_count = 5, close_slave = 5, linked = 5}
(gdb)
WHen it tried to call
357 avail =
snd_pcm_avail_update(multi-slaves[i].pcm);
since multi-slaves appears bogus, this causes a crash! and since
multi-slaves[i].linked is always 5 (greater than 0) none of the calls
will do anything (snd_pcm_prepare etc) because this is not the master
slave. so where is multi-slaves assigned and how can it be set to
spurious values?
What is your configuration?
Jaroslav
-
Jaroslav Kysela [EMAIL PROTECTED]
SuSE Linuxhttp://www.suse.com
ALSA Project http://www.alsa-project.org
___
Alsa-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/alsa-devel
___
Alsa-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/alsa-devel
___
Alsa-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/alsa-devel
Re: [Alsa-devel] corruption in snd_pcm_multi code
yeah I know and I looked at that and it all looks fine. I need to look at the exact calls to track it down. I was just hoping you might be able to see an easy thing. Let me know if you do get time to look at it. _J In the new year, Jaroslav Kysela wrote: On Sat, 1 Dec 2001, Jeremy Hall wrote: What more info can I provide to help assist you? I'm sorry, I have no time to check this thing. All initialization is being done in _snd_pcm_multi_open and snd_pcm_multi_open. Jaroslav - Jaroslav Kysela [EMAIL PROTECTED] SuSE Linuxhttp://www.suse.com ALSA Project http://www.alsa-project.org ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
Re: [Alsa-devel] corruption in snd_pcm_multi code
What more info can I provide?
_J
In the new year, Jeremy Hall wrote:
Here is a segment of my .asoundrc.
pcm_slave.rme9652_s {
pcm rme9652_0
}
pcm.rme9652_1 {
type hw
card 1
}
ctl.rme9652_1 {
type hw
card 1
}
pcm.rme9652_0 {
type hw
card 0
}
ctl.rme9652_0 {
type hw
card 0
}
ctl.rme9652_48 {
type hw
card 0
}
pcm.rme9652_48 {
type multi;
slaves.a.pcm rme9652_0;
slaves.a.channels 26;
slaves.b.pcm rme9652_1;
slaves.b.channels 26;
bindings.0.slave a;
bindings.0.channel 0;
bindings.1.slave a;
bindings.1.channel 1;
bindings.2.slave a;
bindings.2.channel 2;
bindings.3.slave a;
bindings.3.channel 3;
bindings.4.slave a;
bindings.4.channel 4;
bindings.5.slave a;
bindings.5.channel 5;
bindings.6.slave a;
bindings.6.channel 6;
bindings.7.slave a;
bindings.7.channel 7;
bindings.8.slave a;
bindings.8.channel 16;
bindings.9.slave a;
bindings.9.channel 17;
bindings.10.slave a;
bindings.10.channel 18;
bindings.11.slave a;
bindings.11.channel 19;
bindings.12.slave a;
bindings.12.channel 20;
bindings.13.slave a;
bindings.13.channel 21;
bindings.14.slave a;
bindings.14.channel 22;
bindings.15.slave a;
bindings.15.channel 23;
bindings.16.slave b;
bindings.16.channel 8;
bindings.17.slave b;
bindings.17.channel 9;
bindings.18.slave b;
bindings.18.channel 10;
bindings.19.slave b;
bindings.19.channel 11;
bindings.20.slave b;
bindings.20.channel 12;
bindings.21.slave b;
bindings.21.channel 13;
bindings.22.slave b;
bindings.22.channel 14;
bindings.23.slave b;
bindings.23.channel 15;
bindings.24.slave a;
bindings.24.channel 24;
bindings.25.slave a;
bindings.25.channel 25;
bindings.26.slave b;
bindings.26.channel 24;
bindings.27.slave b;
bindings.27.channel 25;
}
In the new year, Jaroslav Kysela wrote:
On Wed, 28 Nov 2001, Jeremy Hall wrote:
Hi,
Today I saw what is believed to be data corruption. In the middle of
snd_pcm_multi_avail_update, I discovered:
(gdb) print *multi-slaves
$13 = {pcm = 0x5, channels_count = 5, close_slave = 5, linked = 5}
(gdb)
WHen it tried to call
357 avail =
snd_pcm_avail_update(multi-slaves[i].pcm);
since multi-slaves appears bogus, this causes a crash! and since
multi-slaves[i].linked is always 5 (greater than 0) none of the calls
will do anything (snd_pcm_prepare etc) because this is not the master
slave. so where is multi-slaves assigned and how can it be set to
spurious values?
What is your configuration?
Jaroslav
-
Jaroslav Kysela [EMAIL PROTECTED]
SuSE Linuxhttp://www.suse.com
ALSA Project http://www.alsa-project.org
___
Alsa-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/alsa-devel
___
Alsa-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/alsa-devel
___
Alsa-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/alsa-devel
Re: [Alsa-devel] corruption in snd_pcm_multi code
Here is a segment of my .asoundrc.
pcm_slave.rme9652_s {
pcm rme9652_0
}
pcm.rme9652_1 {
type hw
card 1
}
ctl.rme9652_1 {
type hw
card 1
}
pcm.rme9652_0 {
type hw
card 0
}
ctl.rme9652_0 {
type hw
card 0
}
ctl.rme9652_48 {
type hw
card 0
}
pcm.rme9652_48 {
type multi;
slaves.a.pcm rme9652_0;
slaves.a.channels 26;
slaves.b.pcm rme9652_1;
slaves.b.channels 26;
bindings.0.slave a;
bindings.0.channel 0;
bindings.1.slave a;
bindings.1.channel 1;
bindings.2.slave a;
bindings.2.channel 2;
bindings.3.slave a;
bindings.3.channel 3;
bindings.4.slave a;
bindings.4.channel 4;
bindings.5.slave a;
bindings.5.channel 5;
bindings.6.slave a;
bindings.6.channel 6;
bindings.7.slave a;
bindings.7.channel 7;
bindings.8.slave a;
bindings.8.channel 16;
bindings.9.slave a;
bindings.9.channel 17;
bindings.10.slave a;
bindings.10.channel 18;
bindings.11.slave a;
bindings.11.channel 19;
bindings.12.slave a;
bindings.12.channel 20;
bindings.13.slave a;
bindings.13.channel 21;
bindings.14.slave a;
bindings.14.channel 22;
bindings.15.slave a;
bindings.15.channel 23;
bindings.16.slave b;
bindings.16.channel 8;
bindings.17.slave b;
bindings.17.channel 9;
bindings.18.slave b;
bindings.18.channel 10;
bindings.19.slave b;
bindings.19.channel 11;
bindings.20.slave b;
bindings.20.channel 12;
bindings.21.slave b;
bindings.21.channel 13;
bindings.22.slave b;
bindings.22.channel 14;
bindings.23.slave b;
bindings.23.channel 15;
bindings.24.slave a;
bindings.24.channel 24;
bindings.25.slave a;
bindings.25.channel 25;
bindings.26.slave b;
bindings.26.channel 24;
bindings.27.slave b;
bindings.27.channel 25;
}
In the new year, Jaroslav Kysela wrote:
On Wed, 28 Nov 2001, Jeremy Hall wrote:
Hi,
Today I saw what is believed to be data corruption. In the middle of
snd_pcm_multi_avail_update, I discovered:
(gdb) print *multi-slaves
$13 = {pcm = 0x5, channels_count = 5, close_slave = 5, linked = 5}
(gdb)
WHen it tried to call
357 avail =
snd_pcm_avail_update(multi-slaves[i].pcm);
since multi-slaves appears bogus, this causes a crash! and since
multi-slaves[i].linked is always 5 (greater than 0) none of the calls
will do anything (snd_pcm_prepare etc) because this is not the master
slave. so where is multi-slaves assigned and how can it be set to
spurious values?
What is your configuration?
Jaroslav
-
Jaroslav Kysela [EMAIL PROTECTED]
SuSE Linuxhttp://www.suse.com
ALSA Project http://www.alsa-project.org
___
Alsa-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/alsa-devel
___
Alsa-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/alsa-devel
[Alsa-devel] debugging clocking problems on rme9652
Hi, I have a couple questions. First, have there been any clock modifications to the rme9652, or potential problems cropping up over the last few months that would make word clock sync not possible? What kind of cabling and terminators should be used? Can one connect the BNC connectors directly to the card without going through a t connector? (as in will the hammerfall provide termination) I thought I saw something from rme on the subject but it appears to have disappeared. Can we have a feature that tells us in the logs (if asked to) that we have lost clock sync on some port, or that time code is not valid if using word clock etc? _J ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
Re: [Alsa-devel] wierd BANGS! in ttable mappings
Abramo? Perex? Anybody? Hello?
any words on this?
_J
In the new year, Jeremy Hall wrote:
Hi there,
any words on this?
_J
In the new year, Jeremy Hall wrote:
Hi,
I have a config that looks like this. Because the monitors I am using
treat levels at 100% at like LOUD ENOUGH TO SHAKE THE HOUSE APART levels,
I have been investigating how to quieten down the output. I know we all
love our music loud, well some of us do, but there is a point where this
is simply too loud!
I have the following configured in my .asoundrc.
pcm.quiet {
type plug;
slave.pcm rme9652;
ttable.0.2 0.04;
ttable.0.3 0.04;
}
When I start this, I get a loud BANG! loud enough to throw me out of my
skin, followed by the correct samples that I wanted, followed by another
loud BANG! when the device is closed. It does not matter what application
I use, and if I set the 0.04 to 1 or 1.0 everything is fine. Please tell
me this is an easy fix.
_J
___
Alsa-devel mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/alsa-devel
___
Alsa-devel mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/alsa-devel
___
Alsa-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/alsa-devel
[Alsa-devel] problems compiling ac3dec in alsa-tools
Hi, snd_pcm_resume is being implicitly declared in alsa-tools/ac3dec. _J ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
[Alsa-devel] need SCHED_FIFO for aplay
Hi, We need an option to aplay that lets you set sched_fifo and a priority so that those of us using a ll kernel can get it right and we won't see xruns because of lack of scheduling. Do we have a -Z? how about a -R? _J ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
