August 2007 - Alsa-devel - mailman.alsa-project.org

[alsa-devel] mic doesn't work with hda-intel/AD1983 driver
by Shuduo Sang 29 Aug '07

29 Aug '07

Hi, I am running ubuntu 7.04 on Dell Optiplex 745 with hda-intel card. The mic does not work now. I tried latest stable alsa driver. The chip is Analog Device AD1983. According to the document of alsa driver, there is no more model parameter can be set. Can anyone give me some information about that? Is it a defect of current driver code? Or something I missed? thanks, Regards, Sang Shuduo

2 4

[alsa-devel] Audiophile Delta 24/96 Midi Out continuously sends zeroes
by Romain Bossart 28 Aug '07

28 Aug '07

Hi, My audiophile 24/96 Midi Out sends zeroes continuously, so I can't use any instrument. I checked that with amidi by looking at the stream output of a connected instrument (midi out -> instrument -> midi in -> amidi). Zeroes are sent whether or not I try to send (normal) midi messages. I know it used some years ago (it was on win32 at that time). Midi In and the instrument do work perfectly. M-Audio answered me that they don't yet support linux. I'm using alsa 1.0.14 on debian/sid 2.6.22. Anyone has an idea? Thank you Romain

1 0

[alsa-devel] Audiophile Delta 24/96 Midi Out continuously sends zeroes
by Romain Bossart 28 Aug '07

28 Aug '07

Hi, My audiophile 24/96 Midi Out sends zeroes continuously, so I can't use any instrument. I checked that with amidi by looking at the stream output of a connected instrument (midi out -> instrument -> midi in -> amidi). Zeroes are sent whether or not I try to send (normal) midi messages. I know it used some years ago (it was on win32 at that time). Midi In and the instrument do work perfectly. M-Audio answered me that they don't yet support linux. I'm using alsa 1.0.14 on debian/sid 2.6.22. Anyone has an idea? Thank you Romain

1 0

Re: [alsa-devel] conexant alsa patch
by Tobin Davis 28 Aug '07

28 Aug '07

On Tue, 2007-08-28 at 15:20 +0200, Takashi Iwai wrote: > At Tue, 28 Aug 2007 00:27:39 +0000, > Hirakendu Das wrote: > > > > Hi. > > > > This regarding the conexant alsa patches authored by you. Firstly, thanks for > > the drivers :). Just wanted to say that if you can kindly look at the following > > minor issue. The master volume control in any mixer frontend (alsamixer or kmix > > etc) doesn't work in the latest patches. It used to work in the old patches. > > Strangely and thankfully, just changing the references of "Master Playback > > Volume" and "Master Playback Switch" in the file patch_conexant.c to simply > > "Playback Volume" and "Playback Switch" as in the old patch seems to make it > > work again as earlier. It works for me on my hp dv5000t notebook with conexant > > 5047. Could you just look into if its the case for all others. (Please see the > > attachments for details.) > > (Its of a bit of cosmetic value for me, as without it, I can't control volume > > using my notebook buttons.) > > PS : Is it true for other sound codecs too ? > > Can you try to build from HG tree? Then you can trace exactly which > commit breaks by bisecting the commits. > > > thanks, > > Takashi Preliminary tests against the 2.6.22 (alsa driver 1.0.14) breaks the automute on my test board (for some reason - still looking at this). I will also try against the tip to see if there are other major issues. -- Tobin Davis <tdavis(a)dsl-only.net>

1 1

[alsa-devel] [patch] kernel-sync
by Trent Piepho 28 Aug '07

28 Aug '07

Here's patch for alsa-kernel to sync bt87x.c with the git kernel, from commit cf784d554fdb94f21671830135dba56b507126cf Or maybe process is to wait for 2.6.23 to be released, and then sync to that? I have some more patch to bt87x, but I'm waiting for this to appear in alsa-kernel so I can base them off it.

2 1

[alsa-devel] echo-cancellation plugin advice?
by Robert Brewer 28 Aug '07

28 Aug '07

I'm writing a small speech input app for my laptop. My app is unusable when other sounds are being generated by the laptop, such as from a music playing app. For this reason, I'd like to have an echo cancellation plugin that would cancel out the music played on the laptop speakers when it is received by the mic. I think this should be doable since the music is playing through alsa. I've done some poking in the plugin documentation, and it's not clear to me how to architect this plugin. Ideally, I would route all my music playing apps through the echo cancelling plugin. I would also route the mic capture stream through the plugin. So the plugin must handle both playback and capture streams. Does the asym plugin hold the answers I need? Does anyone have any thoughts on how I might do this? There are several open source echo cancellation algorithms available, so I'm mainly asking for advice on implementing this as an alsa plugin. Thanks, Rob -- Robert W. Brewer

2 1

Re: [alsa-devel] Altec Lansing FX5051 mixer
by Jeremy Nickurak 28 Aug '07

28 Aug '07

On Tue, Aug 28, 2007 at 01:43:51AM -0600, Jeremy Nickurak wrote: > On Tue, Aug 28, 2007 at 08:50:00AM +0200, Clemens Ladisch wrote: > > > bmaControls( 0) 0x15 > > > Mute > > > Bass > > > Treble > > > bmaControls( 1) 0x02 > > > Volume > > > bmaControls( 2) 0x02 > > > Volume > > > bmaControls( 3) 0x00 > > > bmaControls( 4) 0x00 > > > bmaControls( 5) 0x00 > > > bmaControls( 6) 0x00 > > > > These descriptors say that there is a two-channel volume control that > > applies to the front channels, but I guess it really affects all > > channels. > > > > Please show the output of "amixer contents" for this card. > > numid=3,iface=MIXER,name='Tone Control - Bass' > ; type=INTEGER,access=rw------,values=1,min=0,max=10,step=0 > : values=5 > numid=4,iface=MIXER,name='Tone Control - Treble' > ; type=INTEGER,access=rw------,values=1,min=0,max=10,step=0 > : values=5 > numid=1,iface=MIXER,name='PCM Playback Switch' > ; type=BOOLEAN,access=rw------,values=1 > : values=on > numid=2,iface=MIXER,name='PCM Playback Volume' > ; type=INTEGER,access=rw---R--,values=2,min=0,max=49,step=0 > : values=48,48 > | dBscale-min=-49.00dB,step=1.00dB,mute=0 > > > > > > > ... > > > HID Device Descriptor: > > > bLength 9 > > > bDescriptorType 33 > > > bcdHID 1.00 > > > bCountryCode 0 Not supported > > > bNumDescriptors 1 > > > bDescriptorType 34 Report > > > wDescriptorLength 172 > > > Report Descriptor: (length is 172) > > > Item(Global): Usage Page, data= [ 0x0c ] 12 > > > Consumer > > > Item(Local ): Usage, data= [ 0x01 ] 1 > > > Consumer Control > > > Item(Main ): Collection, data= [ 0x01 ] 1 > > > Application > > > Item(Global): Usage Page, data= [ 0x0c ] 12 > > > Consumer > > > Item(Local ): Usage, data= [ 0xe2 ] 226 > > > Mute > > > Item(Local ): Usage, data= [ 0xe9 ] 233 > > > Volume Increment > > > ... > > > > This describes an input device that reports 'key' presses to the > > computer. I guess the control panel and remote control don't have a > > direct effect but expect the computer to explicitly change mixer > > controls when a key is pressed. > > Since it works fine in Windows without any non-ms software, would this > imply that this is somewhat standard behavior? > > > > > However, this shouldn't prevent alsamixer from working. > > > > It might be possible that the mixer controls don't have many steps and > > that the step size used by alsamixer is so small that the device rounds > > the setting back to the old position. Please try PageUp/Down or Home/ > > End instead of Up/Down keys. > > PgUp/PgDown don't do any better on any controls. I seem to be able to > drop the PCM volume to nothing in practice with End, but Home won't > restore it. Up/Down immediately brings it back up to 100%. The LED's on > the control reflect this btw, but alsamixer still reports 98%. > > -- > Jeremy Nickurak -= Email/Jabber: atrus(a)rifetech.com =- -- Jeremy Nickurak -= Email/Jabber: atrus(a)rifetech.com =-

1 1

[alsa-devel] ALSA sound/core/pcm_lib.c:210: Unexpected hw_pointer value [1] (stream = 0, delta: -4096, max jitter = 8192): wrong interrupt acknowledge?
by Pharaoh . 28 Aug '07

28 Aug '07

I am getting this error at the start of song, I get this only once and the song plays quite well except some periodic minute/unnoticable clicks which occur often if period size is less. Is there any chance of this being the culprit i.e. causing clicks? I used to get the same messages after every buffer size previously, but after fixing my pointer callback this happens only once at the beginning. After reading the code I think that, this might not be the reason behind clicks, since this is just xrun debug thing, but this doesn't correspond to xruns directly, does it? I got the above error message even when there were no xruns. How serious is this issue? After referring web I collected that, this might happen because the period is not processed as fast as it should be. -pharaoh.

2 1

[alsa-devel] Noise at end of audio file
by Lopez Cruz, Misael 27 Aug '07

27 Aug '07

Hi, I listen some noise at the end of playback of an audio file, with some debug I noticed that the noise appears in the last two period of the playback. I tried changing the minimum number of period (it was 16 and changed to 32) but the noise appears even before. Any idea what could be wrong? Misael

2 5

[alsa-devel] Very elementary question regarding period size
by Pharaoh . 27 Aug '07

27 Aug '07

I am testing out my alsa driver for various period and buffer sizes, at some configurations it doesn't work so arises this very basic question. Is every sound card/hardware supposed to work at all the period sizes? The way I have written my driver, makes the DMA processing dependent on period size so the answer is obvious in my case, that it might not work for all period sizes. Does it hold true for all the cards? -pharaoh.

2 2