Re: [Alsa-user] RME AES-32 questions
(I'll try answering some of my questions.) John Sigler wrote: I have an RME AES-32 PCI board. http://www.rme-audio.de/en_products_hdsp_aes32.php [...] When I boot, every channel has its volume set to 0. Is this done by the board's firmware? http://lxr.linux.no/linux/sound/pci/rme9652/hdspm.c#L3396 http://lxr.linux.no/linux/sound/pci/rme9652/hdspm.c#L965 Apparently, it's not the board's firmware, it's the device driver which mutes every channel at initialization. Does anybody know why this is done? I used amixer to change the volume. Simple mixer control 'Chn',1 Capabilities: volume volume-joined Playback channels: Mono Capture channels: Mono Limits: 0 - 65536 Mono: 32768 [50%] What is the meaning of the level? Does 100% mean the signal is left unmodified? and 50% means the amplitude is multiplied by 0.50? http://lxr.linux.no/linux/sound/pci/rme9652/hdspm.c#L377 #define UNITY_GAIN 32768 #define MINUS_INFINITY_GAIN 0 So, volume = 32768 means leave the signal as is and volume = 0 means mute the channel. Is that correct? What would volume = 16384 and volume = 49152 mean? (What is the scale?) Regards. - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Alsa-user mailing list Alsa-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/alsa-user
Re: [Alsa-user] RME AES-32 questions
On 03/03/2008, John Sigler [EMAIL PROTECTED] wrote: (I'll try answering some of my questions.) John Sigler wrote: I have an RME AES-32 PCI board. http://www.rme-audio.de/en_products_hdsp_aes32.php [...] When I boot, every channel has its volume set to 0. Is this done by the board's firmware? http://lxr.linux.no/linux/sound/pci/rme9652/hdspm.c#L3396 http://lxr.linux.no/linux/sound/pci/rme9652/hdspm.c#L965 Apparently, it's not the board's firmware, it's the device driver which mutes every channel at initialization. Does anybody know why this is done? It was done to protect one's ears. I used amixer to change the volume. Simple mixer control 'Chn',1 Capabilities: volume volume-joined Playback channels: Mono Capture channels: Mono Limits: 0 - 65536 Mono: 32768 [50%] What is the meaning of the level? Does 100% mean the signal is left unmodified? and 50% means the amplitude is multiplied by 0.50? http://lxr.linux.no/linux/sound/pci/rme9652/hdspm.c#L377 #define UNITY_GAIN 32768 #define MINUS_INFINITY_GAIN 0 So, volume = 32768 means leave the signal as is and volume = 0 means mute the channel. Is that correct? What would volume = 16384 and volume = 49152 mean? (What is the scale?) There is no scale there. It can have a range of value between 0 and 65536 32768 being about 50% of 65536. Now, the ALSA mixer has been improved, and we can now report gain levels instead of these mostly meaningless percentage values. Try running alsamixer, it will show dB values for each mixer control if the driver has been updated to report the information. So, 0 dB means leave the signal as is -X dB means attenuate the signal by X db X db means gain the signal by X db Now that we have these dB gain levels, we could potentially set all mixer controls to 0dB, i.e. not gain and not attenuation, with only the master output control being set to a lower value so as to avoid ears breaking. James - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Alsa-user mailing list Alsa-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/alsa-user
Re: [Alsa-user] alsa-lib-1.0.16 compile error
At Sat, 1 Mar 2008 03:58:16 -0600 (CST),
Stephen Stocker wrote:
Hi.
I'm running kernel 2.4.24-ck1, gcc 3.3.4. Trying to compile the
alsa-lib-1.0.16, I get the following error.
Does the patch below fix?
Takashi
diff -r 14ce0fc9a26d src/pcm/pcm_local.h
--- a/src/pcm/pcm_local.h Fri Feb 29 12:42:57 2008 +0100
+++ b/src/pcm/pcm_local.h Mon Mar 03 18:11:21 2008 +0100
@@ -944,13 +944,17 @@ typedef union snd_tmp_double {
/* get the current timestamp */
static inline void gettimestamp(snd_htimestamp_t *tstamp, int monotonic)
{
+#ifdef HAVE_CLOCK_GETTIME
if (monotonic) {
clock_gettime(CLOCK_MONOTONIC, tstamp);
} else {
+#else
struct timeval tv;
gettimeofday(tv, 0);
tstamp-tv_sec = tv.tv_sec;
tstamp-tv_nsec = tv.tv_usec * 1000L;
+#ifdef HAVE_CLOCK_GETTIME
}
+#endif
}
-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
Alsa-user mailing list
Alsa-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/alsa-user
Re: [Alsa-user] Newbie question - cannot get sound to work in Ubuntu
Nigel, Oops - forgot to mention that I'm using Gutsy Gibbon (7.10). There seem to be quite a few people who've had problems with sound in GG. But none of the solutions on the Ubuntu bulletin board has helped me. Best regards, Peter mailto:[EMAIL PROTECTED] www.ptoye.com - Sunday, March 2, 2008, 5:43:32 PM, you wrote: On Sunday 02 March 2008 14:53, Peter Toye wrote: James, Thanks for this. I am a member of the audio group, so problem there. The sound modules seem to be loaded OK. The relevant bit of the output from lsmod is: $ lsmod |grep snd snd_emu10k1_synth 8192 0 snd_emux_synth 35456 1 snd_emu10k1_synth snd_seq_virmidi 8064 1 snd_emux_synth snd_seq_midi_emul 7680 1 snd_emux_synth snd_emu10k1 137248 2 snd_emu10k1_synth snd_ac97_codec100644 1 snd_emu10k1 ac97_bus3200 1 snd_ac97_codec snd_pcm_oss44672 0 snd_mixer_oss 17664 1 snd_pcm_oss snd_pcm80388 3 snd_emu10k1,snd_ac97_codec,snd_pcm_oss snd_page_alloc 11400 2 snd_emu10k1,snd_pcm snd_util_mem5760 2 snd_emux_synth,snd_emu10k1 snd_hwdep 10244 2 snd_emux_synth,snd_emu10k1 snd_seq_dummy 4740 0 snd_seq_oss33152 0 snd_seq_midi9600 0 snd_rawmidi25728 3 snd_seq_virmidi,snd_emu10k1,snd_seq_midi snd_seq_midi_event 8448 3 snd_seq_virmidi,snd_seq_oss,snd_seq_midi snd_seq53232 9 snd_emux_synth,snd_seq_virmidi,snd_seq_midi_emul,snd_seq_dummy,snd_seq_oss, snd_seq_midi,snd_seq_midi_event snd_timer 24324 3 snd_emu10k1,snd_pcm,snd_seq snd_seq_device 9228 8 snd_emu10k1_synth,snd_emux_synth,snd_emu10k1,snd_seq_dummy,snd_seq_oss,snd_ seq_midi,snd_rawmidi,snd_seq snd54660 15 snd_emux_synth,snd_seq_virmidi,snd_emu10k1,snd_ac97_codec,snd_pcm_oss,snd_m ixer_oss,snd_pcm,snd_hwdep,snd_seq_oss,snd_rawmidi,snd_seq,snd_timer,snd_seq _device soundcore 8800 1 snd $ So that looks OK. Peter Hi Peter. Your lsmod looks ok, and from your previous post /proc/asound/cards only shows one soundcard, so it's not like you have problems like I have, with also having a usb midi keyboard plugged in when booting. That said I know the workaround for that, so it's no problem for me. I have a bunch of distros installed, and have just booted up Kubuntu (Dapper, upgraded from Breezy). Which Ubuntu version are you using? I have an Audigy2 soundblaster (emu10k1) , so the card is more or less the same as yours. I can't remember if there were any problems with getting the sounds working though. I'm puzzled why you have no alsamixer, when trying to start it on the CLI. The 3 Alsa packages that should be installed are alsa-base, alsa-utils, and libasound2. Alsa-utils contains the alsamixer, amongst other stuff. I looked back through my history files to see what I installed post installing Kubuntu. The only 2 relevant packages are alsa-oss, and dialog, but I don't think alsamixer uses dialog to display itself. I think it uses ncurses. it may be worth a look to see if you have the dialog, and ncurses packages installed. For ncurses, the packages are ncurses-base, and ncurses-bin. Also have a look in /var/lib/alsa. The mixer settings are saved in a file named asound.state. The file should exist for alsamixer to display the settings. The commands alsactl restore, and alsactl store, are the ones to use to restore, and store mixer settings if the asound.state file exists in /var/lib/alsa Can't think of anything else to look for at the moment. Nigel. btw. From googling, a saw problems with sound on Gutsy Gibbon, but IIRC, they were to do with hda-intel based soundcards. - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Alsa-user mailing list Alsa-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/alsa-user
Re: [Alsa-user] hda_intel no microphone
At Sun, 02 Mar 2008 22:20:06 +0100, Ferry Toth wrote: I'm using debian lenny (testing) just received alsa 1.0.16-1. As you mentioned this didn't fix my problem. Then try HG version. My ALC662 is for some reason not recognized I get: hda_codec: Unknown model for ALC662, trying auto-probe from BIOS... Would it help set the codec manually? If you have a luck, passing a proper model option may work... Takashi Ferry Op maandag 25-02-2008 om 18:34 uur [tijdzone +0100], schreef Takashi Iwai: At Sat, 23 Feb 2008 09:46:21 +, Daniel Sanabria wrote: could you publish the output of amixer -c 0? Lee, are you aware of any problems in 1.015? you seem to be sure that an upgrade to 1.0.16 could fix this issue? 1.0.16 may still have a bug. I applied some fixes for recording problems on ALC codecs after 1.0.16, so better to try HG version as a first step. Takashi - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Alsa-user mailing list Alsa-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/alsa-user - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Alsa-user mailing list Alsa-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/alsa-user
Re: [Alsa-user] alsa-lib-1.0.16 compile error
On Mon, 3 Mar 2008, Takashi Iwai wrote:
At Sat, 1 Mar 2008 03:58:16 -0600 (CST),
Stephen Stocker wrote:
Hi.
I'm running kernel 2.4.24-ck1, gcc 3.3.4. Trying to compile the
alsa-lib-1.0.16, I get the following error.
Does the patch below fix?
Takashi
diff -r 14ce0fc9a26d src/pcm/pcm_local.h
--- a/src/pcm/pcm_local.h Fri Feb 29 12:42:57 2008 +0100
+++ b/src/pcm/pcm_local.h Mon Mar 03 18:11:21 2008 +0100
@@ -944,13 +944,17 @@ typedef union snd_tmp_double {
/* get the current timestamp */
static inline void gettimestamp(snd_htimestamp_t *tstamp, int monotonic)
{
+#ifdef HAVE_CLOCK_GETTIME
if (monotonic) {
clock_gettime(CLOCK_MONOTONIC, tstamp);
} else {
+#else
struct timeval tv;
gettimeofday(tv, 0);
tstamp-tv_sec = tv.tv_sec;
tstamp-tv_nsec = tv.tv_usec * 1000L;
+#ifdef HAVE_CLOCK_GETTIME
}
+#endif
}
Hi,
I'm still getting an error, but slightly different after applying the
patch. I'm not sure how to shorten it here without losing some vital
message, so here's the complete error:
In file included from ../../include/aserver.h:22,
from control_shm.c:36:
../../src/pcm/pcm_local.h: In function `gettimestamp':
../../src/pcm/pcm_local.h:949: error: `CLOCK_MONOTONIC' undeclared (first use
in this function)
../../src/pcm/pcm_local.h:949: error: (Each undeclared identifier is reported
only once
../../src/pcm/pcm_local.h:949: error: for each function it appears in.)
In file included from ../../include/aserver.h:22,
from control_shm.c:36:
../../src/pcm/pcm_local.h:947:1: unterminated #else
control_shm.c: In function `snd_ctl_shm_action':
control_shm.c:52: error: dereferencing pointer to incomplete type
control_shm.c: In function `snd_ctl_shm_action_fd':
control_shm.c:71: error: dereferencing pointer to incomplete type
control_shm.c: In function `snd_ctl_shm_close':
control_shm.c:90: error: dereferencing pointer to incomplete type
control_shm.c: In function `snd_ctl_shm_async':
control_shm.c:108: error: dereferencing pointer to incomplete type
control_shm.c: In function `snd_ctl_shm_poll_descriptor':
control_shm.c:120: error: dereferencing pointer to incomplete type
control_shm.c: In function `snd_ctl_shm_subscribe_events':
control_shm.c:132: error: dereferencing pointer to incomplete type
control_shm.c: In function `snd_ctl_shm_card_info':
control_shm.c:141: error: dereferencing pointer to incomplete type
control_shm.c: In function `snd_ctl_shm_elem_list':
control_shm.c:155: error: dereferencing pointer to incomplete type
control_shm.c: In function `snd_ctl_shm_elem_info':
control_shm.c:177: error: dereferencing pointer to incomplete type
control_shm.c: In function `snd_ctl_shm_elem_read':
control_shm.c:191: error: dereferencing pointer to incomplete type
control_shm.c: In function `snd_ctl_shm_elem_write':
control_shm.c:205: error: dereferencing pointer to incomplete type
control_shm.c: In function `snd_ctl_shm_elem_lock':
control_shm.c:219: error: dereferencing pointer to incomplete type
control_shm.c: In function `snd_ctl_shm_elem_unlock':
control_shm.c:233: error: dereferencing pointer to incomplete type
control_shm.c: In function `snd_ctl_shm_hwdep_next_device':
control_shm.c:247: error: dereferencing pointer to incomplete type
control_shm.c: In function `snd_ctl_shm_hwdep_info':
control_shm.c:261: error: dereferencing pointer to incomplete type
control_shm.c: In function `snd_ctl_shm_pcm_next_device':
control_shm.c:275: error: dereferencing pointer to incomplete type
control_shm.c: In function `snd_ctl_shm_pcm_info':
control_shm.c:289: error: dereferencing pointer to incomplete type
control_shm.c: In function `snd_ctl_shm_pcm_prefer_subdevice':
control_shm.c:303: error: dereferencing pointer to incomplete type
control_shm.c: In function `snd_ctl_shm_rawmidi_next_device':
control_shm.c:316: error: dereferencing pointer to incomplete type
control_shm.c: In function `snd_ctl_shm_rawmidi_info':
control_shm.c:330: error: dereferencing pointer to incomplete type
control_shm.c: In function `snd_ctl_shm_rawmidi_prefer_subdevice':
control_shm.c:344: error: dereferencing pointer to incomplete type
control_shm.c: In function `snd_ctl_shm_set_power_state':
control_shm.c:357: error: dereferencing pointer to incomplete type
control_shm.c: In function `snd_ctl_shm_get_power_state':
control_shm.c:370: error: dereferencing pointer to incomplete type
control_shm.c: In function `snd_ctl_shm_read':
control_shm.c:389: error: dereferencing pointer to incomplete type
control_shm.c: In function `gettimestamp':
control_shm.c:468: warning: static declaration for `snd_ctl_shm_open' follows
non-static
control_shm.c: In function `snd_ctl_shm_open':
control_shm.c:543: error: dereferencing pointer to incomplete type
control_shm.c:544: error: dereferencing pointer to incomplete type
control_shm.c:550: error: dereferencing pointer to incomplete type
control_shm.c:
Re: [Alsa-user] Newbie question - cannot get sound to work in Ubuntu
On Monday 03 March 2008 18:12, Peter Toye wrote: Nigel, Thanks for this. I've looked at the modules and the only one that's missing is dialog. It seems that this is to make it easy to write scripts which put up dialogue boxes, so I wouldn't have thought that aplay would give an error message about not being able to find the default device if the module's missing. Of course, error messages and their causes aren't always correlated too well. /var/lib/alsa contains asound.state and nothing else. I've no idea asound.state is meant to contain, so I'm attaching it (assuming that this email system allows attachments) in case it's of use. It's a bit long to include in the text. Ok. Nice to see you have an asound.state. When you installed Gutsy Gibbon, this asound.state file was created, and contains the default mixer settings for alsa, and usually the sounds are muted for the sake of your ears. I use KDE, so would then open a Konsole (CLI) , and type alsamixer as user, and can unmute controls, set slider levels, and so on. Same goes I presume, if you use Gnome. Now it has been suggested to me in the past if I can't get access to alsamixer, to remove/rename the asound.state file which may be faulty. I'd suggest renaming asound.state to something like asound.state.old, then reboot, and a new asound.state will be created, then, depending on which desktop you are using, open a terminal/konsole, and type alsamixer. Does alsamixer now open? I also have a USB sound card which I originally tried attaching - got a bit further with it in that I was able to play but not record (which is what I want to use it for). But then I removed it so as not to confuse things, and reloaded Alsa to get a clean system. As a matter of interest, does anyone directly connected with the Alsa project ever reply to queries here, or is it just users? The half-sighted leading the blind as it were. Alsa developers do read the alsa-user postings, and regularly reply to users queries. I'm just a user, but try to help if I can. Just trying to help. Nigel. Best regards, Peter mailto:[EMAIL PROTECTED] www.ptoye.com - Sunday, March 2, 2008, 5:43:32 PM, you wrote: On Sunday 02 March 2008 14:53, Peter Toye wrote: James, Thanks for this. I am a member of the audio group, so problem there. The sound modules seem to be loaded OK. The relevant bit of the output from lsmod is: $ lsmod |grep snd snd_emu10k1_synth 8192 0 snd_emux_synth 35456 1 snd_emu10k1_synth snd_seq_virmidi 8064 1 snd_emux_synth snd_seq_midi_emul 7680 1 snd_emux_synth snd_emu10k1 137248 2 snd_emu10k1_synth snd_ac97_codec100644 1 snd_emu10k1 ac97_bus3200 1 snd_ac97_codec snd_pcm_oss44672 0 snd_mixer_oss 17664 1 snd_pcm_oss snd_pcm80388 3 snd_emu10k1,snd_ac97_codec,snd_pcm_oss snd_page_alloc 11400 2 snd_emu10k1,snd_pcm snd_util_mem5760 2 snd_emux_synth,snd_emu10k1 snd_hwdep 10244 2 snd_emux_synth,snd_emu10k1 snd_seq_dummy 4740 0 snd_seq_oss33152 0 snd_seq_midi9600 0 snd_rawmidi25728 3 snd_seq_virmidi,snd_emu10k1,snd_seq_midi snd_seq_midi_event 8448 3 snd_seq_virmidi,snd_seq_oss,snd_seq_midi snd_seq53232 9 snd_emux_synth,snd_seq_virmidi,snd_seq_midi_emul,snd_seq_dummy,snd_seq_o ss, snd_seq_midi,snd_seq_midi_event snd_timer 24324 3 snd_emu10k1,snd_pcm,snd_seq snd_seq_device 9228 8 snd_emu10k1_synth,snd_emux_synth,snd_emu10k1,snd_seq_dummy,snd_seq_oss,s nd_ seq_midi,snd_rawmidi,snd_seq snd54660 15 snd_emux_synth,snd_seq_virmidi,snd_emu10k1,snd_ac97_codec,snd_pcm_oss,sn d_m ixer_oss,snd_pcm,snd_hwdep,snd_seq_oss,snd_rawmidi,snd_seq,snd_timer,snd _seq _device soundcore 8800 1 snd $ So that looks OK. Peter Hi Peter. Your lsmod looks ok, and from your previous post /proc/asound/cards only shows one soundcard, so it's not like you have problems like I have, with also having a usb midi keyboard plugged in when booting. That said I know the workaround for that, so it's no problem for me. I have a bunch of distros installed, and have just booted up Kubuntu (Dapper, upgraded from Breezy). Which Ubuntu version are you using? I have an Audigy2 soundblaster (emu10k1) , so the card is more or less the same as yours. I can't remember if there were any problems with getting the sounds working though. I'm puzzled why you have no alsamixer, when trying to start it on the CLI. The 3 Alsa packages that should be installed are alsa-base, alsa-utils, and libasound2. Alsa-utils contains the alsamixer, amongst other stuff. I looked back through my history files to see what I installed post installing Kubuntu. The only 2 relevant packages are alsa-oss, and
Re: [Alsa-user] hda_intel no microphone
Hi Takashi, I'm sorry, please explain what is the HG version. Is there anyway (log?) where I can find the model detected by Alsa? I'm guessing the model may be added to future versions of Alsa to prevent falling back to the BIOS? I have the sound system integrated on my Asus P5GC-MX/1333 motherboard. Thanks, Ferry Op maandag 03-03-2008 om 18:33 uur [tijdzone +0100], schreef Takashi Iwai: At Sun, 02 Mar 2008 22:20:06 +0100, Ferry Toth wrote: I'm using debian lenny (testing) just received alsa 1.0.16-1. As you mentioned this didn't fix my problem. Then try HG version. My ALC662 is for some reason not recognized I get: hda_codec: Unknown model for ALC662, trying auto-probe from BIOS... Would it help set the codec manually? If you have a luck, passing a proper model option may work... Takashi Ferry Op maandag 25-02-2008 om 18:34 uur [tijdzone +0100], schreef Takashi Iwai: At Sat, 23 Feb 2008 09:46:21 +, Daniel Sanabria wrote: could you publish the output of amixer -c 0? Lee, are you aware of any problems in 1.015? you seem to be sure that an upgrade to 1.0.16 could fix this issue? 1.0.16 may still have a bug. I applied some fixes for recording problems on ALC codecs after 1.0.16, so better to try HG version as a first step. Takashi - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Alsa-user mailing list Alsa-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/alsa-user - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Alsa-user mailing list Alsa-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/alsa-user
Re: [Alsa-user] hda_intel no microphone
I had a similar problem with my HDA-INTEL card. Tweaking my modprobe did the trick : I only had : alias sound-slot-0 snd_hda_intel And I changed my modprobe so it looked like that : alias sound-slot-0 snd_hda_intel options snd_hda_intel index=0 model=auto For some reasons, it looks like auto is not the default model. Tested on mandriva-2008 with alsa 1.0.14 and 1.0.16 and on Ubuntu 7.10, Alsa 1.0.14. Phil On Mon, Mar 3, 2008 at 4:03 PM, Ferry Toth [EMAIL PROTECTED] wrote: Hi Takashi, I'm sorry, please explain what is the HG version. Is there anyway (log?) where I can find the model detected by Alsa? I'm guessing the model may be added to future versions of Alsa to prevent falling back to the BIOS? I have the sound system integrated on my Asus P5GC-MX/1333 motherboard. Thanks, Ferry Op maandag 03-03-2008 om 18:33 uur [tijdzone +0100], schreef Takashi Iwai: At Sun, 02 Mar 2008 22:20:06 +0100, Ferry Toth wrote: I'm using debian lenny (testing) just received alsa 1.0.16-1. As you mentioned this didn't fix my problem. Then try HG version. My ALC662 is for some reason not recognized I get: hda_codec: Unknown model for ALC662, trying auto-probe from BIOS... Would it help set the codec manually? If you have a luck, passing a proper model option may work... Takashi Ferry Op maandag 25-02-2008 om 18:34 uur [tijdzone +0100], schreef Takashi Iwai: At Sat, 23 Feb 2008 09:46:21 +, Daniel Sanabria wrote: could you publish the output of amixer -c 0? Lee, are you aware of any problems in 1.015? you seem to be sure that an upgrade to 1.0.16 could fix this issue? 1.0.16 may still have a bug. I applied some fixes for recording problems on ALC codecs after 1.0.16, so better to try HG version as a first step. Takashi - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Alsa-user mailing list Alsa-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/alsa-user - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Alsa-user mailing list Alsa-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/alsa-user -- Philippe-Alexandre Lemelin - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___ Alsa-user mailing list Alsa-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/alsa-user
[Alsa-user] vu meter?!#$!
i occasionally record thru the mic jack using sox or arecord. I would prefer to avoid using fat GUI apps like audacity (which is great, but) to perform this simple task; at the same time getting the levels right makes me feel that i should tune engines by remote wearing a blindfold (eventually it will work perfectly :) SOMEONE PLEASE TELL ME THAT 2008 IS THE YEAR WHEN I DISCOVER THE SECRET ALSA VU METER! If i have to learn c programming myself it will happen. But if anyone understands what essential problem i refer to and (better yet) knows the solution let me know. Or maybe there is a more specialized app than audacity for this, i could not find one on the web. PLEASE. - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Alsa-user mailing list Alsa-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/alsa-user
Re: [Alsa-user] vu meter?!#$!
On Mon, Mar 3, 2008 at 8:37 PM, MK [EMAIL PROTECTED] wrote: i occasionally record thru the mic jack using sox or arecord. I would prefer to avoid using fat GUI apps like audacity (which is great, but) to perform this simple task; at the same time getting the levels right makes me feel that i should tune engines by remote wearing a blindfold (eventually it will work perfectly :) arecord -vvv has a crude level meter. Really this should be provided by the recording app. It's surprising that the GNOME sound recorder lacks a level meter. Lee - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Alsa-user mailing list Alsa-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/alsa-user
Re: [Alsa-user] vu meter?!#$!
Lee Revell wrote, on 04/03/08 13:43: On Mon, Mar 3, 2008 at 8:37 PM, MK [EMAIL PROTECTED] wrote: i occasionally record thru the mic jack using sox or arecord. I would prefer to avoid using fat GUI apps like audacity (which is great, but) to perform this simple task; at the same time getting the levels right makes me feel that i should tune engines by remote wearing a blindfold (eventually it will work perfectly :) arecord -vvv has a crude level meter. Really this should be provided by the recording app. It's surprising that the GNOME sound recorder lacks a level meter. Lee KDE's krecord is fairly small and shows recording levels. Arthur. - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Alsa-user mailing list Alsa-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/alsa-user
