From: Takashi Iwai Subject: Re: ALC880 on medion laptop Date: Mon, 27 Jun 2005 18:28:32 +0200 Message-ID: References: <20050626162629.GA23335@blackmilk.localzone.fr> <20050627160556.GA32608@blackmilk.localzone.fr> <20050627162323.GA560@blackmilk.localzone.fr> Mime-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII Return-path: In-Reply-To: <20050627162323.GA560@blackmilk.localzone.fr> Sender: alsa-devel-admin@lists.sourceforge.net Errors-To: alsa-devel-admin@lists.sourceforge.net List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , List-Archive: To: fab Cc: alsa-devel@lists.sourceforge.net List-Id: alsa-devel@alsa-project.org At Mon, 27 Jun 2005 18:23:23 +0200, fab wrote: > > [1 ] > > > ok, I can describe you the alsamixer values but I don't know how to give > > > you the "asound.state" (I searched /proc & /sys for it). > > > > I meant "how did you record". Which program did you use with what > > parameters? > > oh ok, I used audacity (I use it on various computers without issues). > I can try with other applications if you want. For the primary testing, use arecord to eliminate unknown factors. For example, % arecord -fcd foo.wav for 44.1kHz or % arecord -fdat foo.wav for 48kHz. If you get noises, try -Dplughw:0 option to skip dsnoop plugin. > > /etc/asound.state is generated after you call "alsactl store" as > > root. This is done usually by alsasound init script. You can do > > "alsactl -f test.state store" as a normal user, too. > > Ok, here is the file. > [2 test.state ] > state.Intel { (snip) > control.10 { > comment.access 'read write' > comment.type INTEGER > comment.count 2 > comment.range '0 - 35' > iface MIXER > name 'Capture Volume' > value.0 0 > value.1 0 > } You didn't set this volume. Raise "Capture" volume in alsamixer (press [F4] to move to capture view mode). > control.16 { > comment.access 'read write' > comment.type ENUMERATED > comment.count 1 > comment.item.0 Mic > comment.item.1 'Front Mic' > comment.item.2 Line > comment.item.3 CD > iface MIXER > name 'Input Source' > value Mic > } So, the input comes from the microphone. I'm not sure whether it's connected from front-mic or mic on your device. Takashi ------------------------------------------------------- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click