Hi Takashi, Thanks for your info. I took readouts of both modes and notice they are both in 16LE format but mplayer/smplayer is using oss emulation. Is there a way to try them with native Alsa? I have attached the dumps. Is there anything I can do for this (besides switch to OSS)? -----Original Message----- From: Takashi Iwai [mailto:tiwai@xxxxxxx] Sent: Wednesday, June 25, 2008 3:23 AM To: Ashwin Chandra Cc: alsa-devel@xxxxxxxxxxxxxxxx Subject: Re: Alsa Issue - Sound playback starts on left speaker only At Wed, 25 Jun 2008 01:52:16 +0800, <Ashwin.Chandra@xxxxxxxxx> wrote: > > I have an Intel ALC861VD. Other players (mplayer, smplayer, aplay) don't > seem to exhibit this problem. Is there any workaround I can do in my > application so that upon first time sound playback, I can get it to play > on both channels? Check /proc/asound/card0/pcm0p/sub0/* files and compare between working and non-working states. I guess the working case uses OSS emulation or 16bit format. If so, try to add the following to ~/.asoundrc: defaults.pcm.dmix.format S16_LE Takashi > > -----Original Message----- > From: stan [mailto:ghjeold_i_mwee@xxxxxxx] > Sent: Tuesday, June 24, 2008 1:25 AM > To: Ashwin Chandra > Cc: alsa-devel@xxxxxxxxxxxxxxxx > Subject: Re: Alsa Issue - Sound playback starts on left > speaker only > > Ashwin.Chandra@xxxxxxxxx wrote: > > > > > > Hello, > > > > I am having an issue with my playback application where upon playback > > start, only the left speaker is outputted. But if I mute and unmute > > (either through my application or using alsamixer), the sound playback > > resumes on both left and right speakers. This only happens on a > > particular system too (out of 5 systems). But I know it is my issue > > because mplayer or smplayer works fine. > > > > > > > > I believe I am setting the correct HW params (ie. 2 channels), etc. > > > > > > > > Any ideas? > > > > > > > > Thanks! > > > > > The ICE1724 driver has exactly this behavior. It is a known bug and has > > been there for years. > You don't say what chip is having the problem, but I would guess that > this is it. Most people > just program a script to adjust the volume at startup to cure it. > _______________________________________________ > Alsa-devel mailing list > Alsa-devel@xxxxxxxxxxxxxxxx > http://mailman.alsa-project.org/mailman/listinfo/alsa-devel >
access: MMAP_INTERLEAVED format: S16_LE subformat: STD channels: 2 rate: 48000 (48000/1) period_size: 1024 buffer_size: 16384 tick_time: 10000 card: 0 device: 0 subdevice: 0 stream: PLAYBACK id: ALC861VD Analog name: ALC861VD Analog subname: subdevice #0 class: 0 subclass: 0 subdevices_count: 1 subdevices_avail: 0 64 1024 state: RUNNING trigger_time: 1214417481.037381475 tstamp : 1214417482.560390900 delay : -73144 avail : 89528 avail_max : 89528 ----- hw_ptr : 73144 appl_ptr : 0 tstamp_mode: NONE period_step: 1 sleep_min: 0 avail_min: 1024 xfer_align: 1024 start_threshold: 1 stop_threshold: 1073741824 silence_threshold: 0 silence_size: 1073741824 boundary: 1073741824
access: RW_INTERLEAVED format: S16_LE subformat: STD channels: 2 rate: 44100 (44100/1) period_size: 1024 buffer_size: 16384 tick_time: 10000 OSS format: S16_LE OSS channels: 2 OSS rate: 44100 OSS period bytes: 4096 OSS periods: 16 OSS period frames: 1024 card: 0 device: 0 subdevice: 0 stream: PLAYBACK id: ALC861VD Analog name: ALC861VD Analog subname: subdevice #0 class: 0 subclass: 0 subdevices_count: 1 subdevices_avail: 0 64 1024 state: RUNNING trigger_time: 1214416493.704612942 tstamp : 1214416498.550250502 delay : 15648 avail : 736 avail_max : 17400 ----- hw_ptr : 213728 appl_ptr : 229376 tstamp_mode: NONE period_step: 1 sleep_min: 0 avail_min: 1 xfer_align: 1 start_threshold: 1 stop_threshold: 16384 silence_threshold: 1040 silence_size: 1040 boundary: 1073741824
_______________________________________________ Alsa-devel mailing list Alsa-devel@xxxxxxxxxxxxxxxx http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
