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: Fri, 30 Dec 2005 04:59:13 +0100 [thread overview]
Message-ID: <bac9011e75bbb4903d3327e258c63b0f@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: 12-30-2005 04:59 CET
======================================================================
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
======================================================================
----------------------------------------------------------------------
rlrevell - 12-30-05 04:10
----------------------------------------------------------------------
Were you ever able to get this working?
----------------------------------------------------------------------
sst4 - 12-30-05 04:59
----------------------------------------------------------------------
Am I still supposed to compile the patch and the whole ALSA or the patch
is already in the main code ?
Anyway, now even with non-redirected STODUT/STDERR and lot of
volume_adjust: SOUND_MIXER_WRITE_IGAIN failed: Invalid argument
messages the sound with Skype is smooth; I do not know whether it's due
to
changes in Skype, quality of connection or slightly different kernel
- now it's 2.6.11-6mdk-i686-up-4GB instead of 2.6.11-6mdk-i586-up-1GB.
I hope to make and upgrade to Mandriva 2006 next week, I think it has
ALSA
vesrion 1.0.9b.
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
06-29-05 00:08 sst4 Note Added: 0005302
06-29-05 20:22 tiwai Note Added: 0005311
06-29-05 21:40 sst4 Note Added: 0005316
12-30-05 04:10 rlrevell Note Added: 0007202
12-30-05 04:59 sst4 Note Added: 0007229
======================================================================
-------------------------------------------------------
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
next reply other threads:[~2005-12-30 3:59 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-30 3:59 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:10 bugtrack
2005-06-29 19:40 bugtrack
2005-06-29 18:22 bugtrack
2005-06-28 22:08 bugtrack
2005-06-28 21:45 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=bac9011e75bbb4903d3327e258c63b0f@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.