All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugtrack@alsa-project.org
To: alsa-devel@alsa-project.org
Subject: [ALSA - liboss 0001164]: aoss + skype: volume_adjust: SOUND_MIXER_WRITE_IGAIN failed: Invalid argument
Date: Tue, 28 Jun 2005 23:45:19 +0200	[thread overview]
Message-ID: <e8b6e576e9967787390af3e711dfd2e8@bugtrack.alsa-project.org> (raw)


A NOTE has been added to this issue.
======================================================================
<https://bugtrack.alsa-project.org/alsa-bug/view.php?id=1164> 
======================================================================
Reported By:                sst4
Assigned To:                
======================================================================
Project:                    ALSA - liboss
Issue ID:                   1164
Category:                   
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     new
======================================================================
Date Submitted:             06-07-2005 00:33 CEST
Last Modified:              06-28-2005 23:45 CEST
======================================================================
Summary:                    aoss + skype: volume_adjust: SOUND_MIXER_WRITE_IGAIN
failed: Invalid argument
Description: 
I've tried 'skype' with my M-Audio Revolution 7.1.

Soon (probably in a second) after this command line:

aoss skype &

the terminal window gets filled with

volume_adjust: SOUND_MIXER_WRITE_IGAIN failed: Invalid argument

messages, and I do not hear anything in 'skype' connecting to their
automated 'echo123' service.

The message is not quite clear, and I believe it shouldn't flood the
screen.

I mean, the code should first check capabilities of the card and its
configuration and
issue the message once.


What is IGAIN in the message above ? Input gain ? That is, capture gain ?

======================================================================
Relationships       ID      Summary
----------------------------------------------------------------------
duplicate of        0001096 no capture with M-Audio Revolution 7.1
======================================================================

----------------------------------------------------------------------
 tiwai - 06-28-05 12:45 
----------------------------------------------------------------------
Unfortunately, the ICE1724 doesn't allow the mixing of multiple sources for
the playback.  That is, *either* PCM, analog-in or spdif-in can be used
*exclusively*.  If you choose the analog-loopback, you can't hear PCM.

The only possible way to solve this is to do mixing on software.  But, of
course, you will get a certain latency in comparison with the hardware
mixing.  The best solution would be to use JACK, but again, OSS-emulation
makes the problem...

I don't see how you started skype in your recent reports.  If you start
skype with "aoss", ~/.asoundrc has influence, and /dev/dsp* doesn't matter
at all because the emulation doesn't open /dev/dsp* at all.
OTOH, if you don't use "aoss", it's most likely through the kernel OSS
emulation.  In this case, ~/.asoundrc has no influence.at all.

Anyway, it looks like aoss still has a problem with IGAIN.  I'll check on
it.  (But if Skype works only with a warning message, you can forget it
for a while...)

----------------------------------------------------------------------
 sst4 - 06-28-05 23:45 
----------------------------------------------------------------------
Takashi, all the time I was using Skype as

aoss Skype
.

And I can't just forget the warning message - printing it consumes too
much
CPU time, and the sound becomes distorted.

In order to be able to use Skype for real purposes I suppressed the
message
this way (starting Skype from 'tcsh'):

aoss skype >& /dev/null
.

The problem is that in such a manner I suppress all error messages - it's
too
reckless IMHO.

The best way to resolve the issue would be to implement SW gain control
( https://bugtrack.alsa-project.org/alsa-bug/view.php?id=1187 ); as a
temporary
measure it would be nice to suppress the particular message this issue is
about.

The latter is possible if the message is produced by ALSA. The
suppression
should be selective, of course, i.e. through command line switch, config
file,
environment variable or something like that.

...

Can there be an ALSA application that even is OSS emulation performs SW
mixing ?

I.e. an application that can take the desired capture stream (if they are
separate) and loop it to PCM out. Is it possible ?

I think such an issue has already been raised in
alsa-user@lists.sourceforge.net .

Thanks,
  Sergei.

Issue History
Date Modified  Username       Field                    Change              
======================================================================
06-07-05 00:33 sst4           New Issue                                    
06-08-05 14:50 tiwai          Note Added: 0004923                          
06-08-05 14:51 tiwai          File Added: aoss-igain-fix.diff                   

06-08-05 14:53 tiwai          Note Added: 0004926                          
06-08-05 14:54 tiwai          File Added: aoss-igain-fix2.diff                  
 
06-08-05 14:55 tiwai          File Deleted: aoss-igain-fix.diff                 
  
06-12-05 19:35 sst4           Note Added: 0004999                          
06-13-05 13:03 tiwai          Note Added: 0005006                          
06-13-05 14:12 sst4           Note Added: 0005009                          
06-13-05 14:30 tiwai          Note Added: 0005010                          
06-13-05 15:55 sst4           File Added: asound.state.geberated_by_alsaconf    
               
06-13-05 15:59 sst4           File Added: asound.state.generated_by_alsaconf    
               
06-13-05 16:05 sst4           Note Added: 0005012                          
06-15-05 08:25 sst4           Note Added: 0005021                          
06-15-05 15:44 tiwai          Note Added: 0005035                          
06-22-05 01:48 rlrevell       Relationship added       duplicate of 0001096
06-28-05 00:59 sst4           Note Added: 0005290                          
06-28-05 01:14 sst4           Note Added: 0005291                          
06-28-05 12:45 tiwai          Note Added: 0005297                          
06-28-05 23:45 sst4           Note Added: 0005301                          
======================================================================




-------------------------------------------------------
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

             reply	other threads:[~2005-06-28 21:45 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-28 21:45 bugtrack [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-03-01  0:02 [ALSA - liboss 0001164]: aoss + skype: volume_adjust: SOUND_MIXER_WRITE_IGAIN failed: Invalid argument bugtrack
2005-12-30  4:07 bugtrack
2005-12-30  3:59 bugtrack
2005-12-30  3:10 bugtrack
2005-06-29 19:40 bugtrack
2005-06-29 18:22 bugtrack
2005-06-28 22:08 bugtrack
2005-06-28 10:45 bugtrack
2005-06-27 23:14 bugtrack
2005-06-27 22:59 bugtrack
2005-06-21 23:48 bugtrack
2005-06-15 13:44 bugtrack
2005-06-15  6:25 bugtrack
2005-06-13 14:05 bugtrack
2005-06-13 12:30 bugtrack
2005-06-13 12:12 bugtrack
2005-06-13 11:03 bugtrack
2005-06-12 17:35 bugtrack
2005-06-08 12:53 bugtrack
2005-06-08 12:50 bugtrack
2005-06-06 22:33 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=e8b6e576e9967787390af3e711dfd2e8@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.