public inbox for alsa-devel@alsa-project.org
 help / color / mirror / Atom feed
From: bugtrack@alsa-project.org
To: alsa-devel@alsa-project.org
Subject: [ALSA - liboss 0001278]: fails to read volume for software volume control
Date: Fri, 30 Dec 2005 23:38:07 +0100	[thread overview]
Message-ID: <0b3ea4b5a62f0d27d59aed9eb8dcd3ed@bugtrack.alsa-project.org> (raw)


A NOTE has been added to this issue.
======================================================================
<https://bugtrack.alsa-project.org/alsa-bug/view.php?id=1278> 
======================================================================
Reported By:                jdthood
Assigned To:                
======================================================================
Project:                    ALSA - liboss
Issue ID:                   1278
Category:                   
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     new
======================================================================
Date Submitted:             07-23-2005 18:23 CEST
Last Modified:              12-30-2005 23:38 CET
======================================================================
Summary:                    fails to read volume for software volume control
Description: 
From: http://bugs.debian.org/319628:

Package: alsa-oss
Version: 1.0.8-1

Hi,

My MacMini's audio chip seems to have no hardware volume control (or it 
is unsupported in the kernel I use), so I use software volume control, 
with the attached .asoundrc. (I'm still a newbie about alsa, there may 
be some mistakes in my .soundrc file.)

While trying to use hotkeys (that only understands oss) with aoss, I 
discovered that aoss did not allow to read the volume control, while it 
can write it flawlessly.

After a few tests, I discovered that it was related to the failing 
snd_mixer_selem_get_playback_switch function call, and I could 
workaround the issue with the attached trivial quick&dirty patch.


Cheers,

Nicolas Boullis


-- System Information:
Debian Release: 3.1
Architecture: powerpc (ppc)
Kernel: Linux 2.6.12-irma
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)

Versions of packages alsa-oss depends on:
ii  libasound2                  1.0.8-3      ALSA library
ii  libc6                       2.3.2.ds1-22 GNU C Library: Shared
libraries an

-- no debconf information



pcm.!default {
  type plug
  slave {
    pcm {
      type softvol
      slave {
        pcm {
	  type dmix
	  ipc_key 7666
	  slave {
	    pcm "hw:0,0"
	    period_time 0
	    period_size 1024
	    buffer_size 8192
	    rate 44100
	  }
	}
      }
      control {
        name Master
        card 0
      }
    }
  }
}

pcm.dsp0 {
  type plug
  slave.pcm "!default"
}




only in patch2:
unchanged:
--- alsa-oss-1.0.8.orig/alsa/mixer.c
+++ alsa-oss-1.0.8/alsa/mixer.c
@@ -487,9 +487,7 @@
 				break;
 			}
 			err = snd_mixer_selem_get_playback_switch(elem,
SND_MIXER_SCHN_FRONT_LEFT, &sw);
-			if (err < 0) 
-				break;
-			if (sw) {
+			if ((err < 0) || (sw)) {
 				err = snd_mixer_selem_get_playback_volume(elem,
SND_MIXER_SCHN_FRONT_LEFT, &lvol);
 				if (err < 0) 
 					break;
@@ -499,9 +497,7 @@
 				rvol = lvol;
 			} else {
 				err = snd_mixer_selem_get_playback_switch(elem,
SND_MIXER_SCHN_FRONT_RIGHT, &sw);
-				if (err < 0) 
-					break;
-				if (sw) {
+				if ((err < 0) || (sw)) { 
 					err = snd_mixer_selem_get_playback_volume(elem,
SND_MIXER_SCHN_FRONT_RIGHT, &rvol);
 					if (err < 0) 
 						break;



======================================================================

----------------------------------------------------------------------
 jdthood - 08-01-05 08:09 
----------------------------------------------------------------------
No, the submitter reports that the bug is still present in 1.0.9.

----------------------------------------------------------------------
 rlrevell - 12-30-05 23:38 
----------------------------------------------------------------------
Was this ever resolved?

(BTW The ALSA bug tracker should have a PATCH status)

Issue History
Date Modified  Username       Field                    Change              
======================================================================
07-23-05 18:23 jdthood        New Issue                                    
07-29-05 18:02 tiwai          Note Added: 0005584                          
08-01-05 08:09 jdthood        Note Added: 0005594                          
12-30-05 23:38 rlrevell       Note Added: 0007295                          
======================================================================




-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click

             reply	other threads:[~2005-12-30 22:38 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-30 22:38 bugtrack [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-01-05 18:47 [ALSA - liboss 0001278]: fails to read volume for software volume control bugtrack
2006-01-04 22:46 bugtrack
2005-08-01  6:09 bugtrack
2005-07-29 16:02 bugtrack
2005-07-23 16:23 bugtrack

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=0b3ea4b5a62f0d27d59aed9eb8dcd3ed@bugtrack.alsa-project.org \
    --to=bugtrack@alsa-project.org \
    --cc=alsa-devel@alsa-project.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox