From: bugtrack@alsa-project.org
To: alsa-devel@alsa-project.org
Subject: [ALSA - driver 0001224]: artsd-like style
Date: Sun, 18 Sep 2005 09:36:27 +0200 [thread overview]
Message-ID: <967f63567f018d4d4819b371a9928baa@bugtrack.alsa-project.org> (raw)
A NOTE has been added to this issue.
======================================================================
<https://bugtrack.alsa-project.org/alsa-bug/view.php?id=1224>
======================================================================
Reported By: Hetfield
Assigned To:
======================================================================
Project: ALSA - driver
Issue ID: 1224
Category: PCI - ens1370
Reproducibility: always
Severity: major
Priority: normal
Status: new
Distribution:
Kernel Version: 2.6.x
======================================================================
Date Submitted: 07-01-2005 14:49 CEST
Last Modified: 09-18-2005 09:36 CEST
======================================================================
Summary: artsd-like style
Description:
i'd like to know if that's a roadmap to let alsa drivers have a artsd (or
windows) style, i mean, multiple streams at once.
that could be very important for example using skype voip and listening
music at the same time.
======================================================================
Relazioni ID Riassunto
----------------------------------------------------------------------
é duplicata da 0001228 Skype Does not work with aoss
======================================================================
----------------------------------------------------------------------
rlrevell - 09-18-05 03:33
----------------------------------------------------------------------
OK, now we are getting somewhere. Create a new .asoundrc containing only:
cards.ENS1370.pcm.dmix.period_time 0
cards.ENS1370.pcm.dmix.period_size 256
cards.ENS1370.pcm.dmix.buffer_size 16384
and post the Skype debug output again.
The log shows that Skype uses SNDCTL_DSP_SETFRAGMENT ioctl to ask for one
256 byte fragment per buffer then sets the format to 16 bit mono @48000Hz.
Next it calls SNDCTL_DSP_GETOSPACE which tells us the buffer is 33436
bytes, we can write 4096 fragments without blocking, the fragments are 16
bytes, and the buffer is divided into 8 fragments. These values obviously
make no sense, but then Skype proceeds to loop write()ing 960 bytes at a
time to the audio device.
As Skype only uses one fragment per buffer, and does not bother to check
the available space after each write, or notice that GETOSPACE returned
bizarre values, it must be counting on write() eventually returning
-EWOULDBLOCK when the buffer fills up.
IOW it looks like AOSS is still buggy, but Skype is really abusing the OSS
API.
----------------------------------------------------------------------
Hetfield - 09-18-05 09:36
----------------------------------------------------------------------
now skype works with aoss! but those settings are buggy.
the problem is dmix is pretty disabled:
skype using dsp? no other apps can use it.
but even using 2 alsa native apps, i can't use both.
playing mp3 and starting mplayer, make mplayer stops, waiting for mp3
player to exit.
kiax continues not to work, completly.
ALSA_OSS_DEBUG=1 aoss ./skype.bin
open("/dev/mixer", 2, 0) -> 35
open("/dev/mixer", 2, -1227608792) -> 37
open("/dev/mixer", 2, 142850184) -> 39
Opened PCM dsp0 for stream 0 (result = -2)
Opened PCM default for stream 0 (result = 0)
Opened PCM default for stream 1 (result = 0)
open("/dev/dsp", 2, 145797372) -> 41
ioctl(41, SNDCTL_DSP_GETCAPS, 0xb6d42ccc) -> [13056]
ioctl(41, SNDCTL_DSP_SETFRAGMENT, 0x8760d08[100008])
ioctl(41, SNDCTL_DSP_STEREO, 0x8760d0c[0]) -> [0]
ioctl(41, SNDCTL_DSP_SETFMT, 0x8760d10[16]) -> [16]
ioctl(41, SNDCTL_DSP_SPEED, 0x8760d24[48000]) -> [48000]
ioctl(41, SNDCTL_DSP_GETOSPACE, 0xb6d42cd0) -> {16 16 256 4096}
write(41, 0xb41fdcc0, 960) -> 960
write(41, 0xb41fdcc0, 960) -> 960
write(41, 0xb41fdcc0, 960) -> 960
write(41, 0xb41fdcc0, 960) -> 960
write(41, 0xb41fdcc0, 960) -> 960
write(41, 0xb41fdcc0, 960) -> 960
write(41, 0xb41fdcc0, 960) -> 960
write(41, 0xb41fdcc0, 960) -> 960
write(41, 0xb41fdcc0, 960) -> 960
write(41, 0xb41fdcc0, 960) -> 960
write(41, 0xb41fdcc0, 960) -> 960
[CUT]...i hangup
Opened PCM dsp0 for stream 0 (result = -2)
Opened PCM default for stream 0 (result = -16)
open("/dev/dsp", 2, 0) -> -1
/dev/dsp-1: Dispositivo o risorsa occupata
close(39) -> 0
Issue History
Date Modified Username Field Change
======================================================================
07-01-05 14:49 Hetfield New Issue
07-01-05 14:49 Hetfield Kernel Version => 2.6.x
07-01-05 20:16 Hetfield Note Added: 0005337
07-01-05 20:33 rlrevell Note Added: 0005338
07-01-05 22:56 Hetfield Note Added: 0005343
07-02-05 18:53 pzad Note Added: 0005356
07-02-05 20:11 Hetfield Note Added: 0005357
07-02-05 21:46 pzad File Added: aoss-fcntl.patch
07-02-05 21:47 pzad Note Added: 0005361
07-03-05 09:25 Hetfield Note Added: 0005370
07-03-05 14:09 pzad Note Added: 0005376
07-03-05 15:57 Hetfield Note Added: 0005378
07-04-05 11:49 pzad File Added: aoss.patch
07-04-05 11:53 pzad Note Added: 0005384
07-04-05 14:02 Hetfield Note Added: 0005385
07-08-05 12:16 tiwai Note Added: 0005417
07-08-05 12:27 Hetfield Note Added: 0005418
07-17-05 10:25 Hetfield Note Added: 0005503
07-17-05 10:29 rlrevell Note Added: 0005504
07-17-05 10:46 rlrevell Note Added: 0005505
07-17-05 11:10 Hetfield Note Added: 0005506
07-17-05 11:11 Hetfield File Added: log.tar.gz
07-17-05 19:41 rlrevell Note Added: 0005508
07-17-05 19:50 Hetfield Note Added: 0005509
07-17-05 19:51 rlrevell Note Added: 0005510
07-17-05 20:21 Hetfield Note Added: 0005511
07-17-05 21:14 rlrevell Note Added: 0005512
07-17-05 21:22 Hetfield File Added: log2.tar.gz
07-17-05 21:22 Hetfield File Added: log2
07-17-05 21:23 Hetfield Note Added: 0005513
07-17-05 22:21 rlrevell Note Added: 0005514
07-17-05 23:28 Hetfield Note Added: 0005515
07-17-05 23:43 rlrevell Note Added: 0005516
07-18-05 03:33 rlrevell Note Added: 0005517
07-18-05 06:04 rlrevell Note Added: 0005518
07-18-05 07:33 rlrevell Note Added: 0005519
07-18-05 09:23 Hetfield Note Added: 0005520
07-18-05 09:24 Hetfield File Added: asoundrc
07-18-05 22:08 rlrevell Note Added: 0005524
07-21-05 19:55 Hetfield Note Added: 0005540
07-21-05 19:56 Hetfield Note Added: 0005541
07-24-05 09:55 Hetfield Note Added: 0005556
07-24-05 19:10 rlrevell Note Added: 0005558
07-28-05 22:40 rlrevell Note Added: 0005578
07-29-05 17:43 tiwai Note Added: 0005579
08-01-05 10:20 Hetfield Note Added: 0005595
08-10-05 00:49 rlrevell Relationship added has duplicate 0001228
08-28-05 15:56 Hetfield Note Added: 0005963
09-02-05 19:57 tiwai Note Added: 0006020
09-02-05 20:22 Hetfield Note Added: 0006021
09-02-05 20:24 tiwai Note Added: 0006022
09-02-05 20:26 Hetfield Note Added: 0006023
09-02-05 20:31 Hetfield Note Added: 0006024
09-17-05 14:05 Hetfield Note Added: 0006249
09-17-05 14:51 Hetfield Note Added: 0006250
09-17-05 19:43 rlrevell Note Added: 0006253
09-17-05 19:46 Hetfield Note Added: 0006254
09-17-05 19:50 rlrevell Note Added: 0006255
09-17-05 19:55 pzad Note Added: 0006256
09-17-05 20:10 rlrevell Note Added: 0006257
09-17-05 20:11 rlrevell Note Added: 0006258
09-17-05 21:21 Hetfield Note Added: 0006261
09-17-05 22:05 rlrevell Note Added: 0006262
09-17-05 22:38 Hetfield Note Added: 0006263
09-17-05 22:52 Hetfield Note Added: 0006264
09-18-05 03:26 rlrevell Note Added: 0006265
09-18-05 03:33 rlrevell Note Edited: 0006265
09-18-05 09:36 Hetfield Note Added: 0006266
======================================================================
-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server.
Download it for free - -and be entered to win a 42" plasma tv or your very
own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php
next reply other threads:[~2005-09-18 7:36 UTC|newest]
Thread overview: 75+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-18 7:36 bugtrack [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-01-02 17:53 [ALSA - driver 0001224]: artsd-like style bugtrack
2006-01-02 17:47 bugtrack
2005-12-30 23:18 bugtrack
2005-11-01 10:12 bugtrack
2005-09-23 8:18 bugtrack
2005-09-20 19:35 bugtrack
2005-09-20 18:20 bugtrack
2005-09-20 14:02 bugtrack
2005-09-20 13:46 bugtrack
2005-09-20 12:56 bugtrack
2005-09-20 7:19 bugtrack
2005-09-19 19:44 bugtrack
2005-09-18 8:55 bugtrack
2005-09-18 8:28 bugtrack
2005-09-18 8:14 bugtrack
2005-09-18 1:26 bugtrack
2005-09-17 20:52 bugtrack
2005-09-17 20:38 bugtrack
2005-09-17 20:05 bugtrack
2005-09-17 19:21 bugtrack
2005-09-17 18:11 bugtrack
2005-09-17 18:10 bugtrack
2005-09-17 17:55 bugtrack
2005-09-17 17:50 bugtrack
2005-09-17 17:46 bugtrack
2005-09-17 17:43 bugtrack
2005-09-17 12:51 bugtrack
2005-09-17 12:05 bugtrack
2005-09-02 18:31 bugtrack
2005-09-02 18:26 bugtrack
2005-09-02 18:24 bugtrack
2005-09-02 18:22 bugtrack
2005-09-02 17:57 bugtrack
2005-08-28 13:56 bugtrack
2005-08-09 22:49 bugtrack
2005-08-01 8:20 bugtrack
2005-07-29 15:43 bugtrack
2005-07-28 20:40 bugtrack
2005-07-24 17:10 bugtrack
2005-07-24 7:55 bugtrack
2005-07-21 17:56 bugtrack
2005-07-21 17:55 bugtrack
2005-07-18 20:08 bugtrack
2005-07-18 7:23 bugtrack
2005-07-18 5:33 bugtrack
2005-07-18 4:04 bugtrack
2005-07-18 1:33 bugtrack
2005-07-17 21:43 bugtrack
2005-07-17 21:28 bugtrack
2005-07-17 20:21 bugtrack
2005-07-17 19:23 bugtrack
2005-07-17 19:14 bugtrack
2005-07-17 18:21 bugtrack
2005-07-17 17:51 bugtrack
2005-07-17 17:50 bugtrack
2005-07-17 17:41 bugtrack
2005-07-17 9:10 bugtrack
2005-07-17 8:46 bugtrack
2005-07-17 8:29 bugtrack
2005-07-17 8:25 bugtrack
2005-07-08 10:27 bugtrack
2005-07-08 10:16 bugtrack
2005-07-04 12:02 bugtrack
2005-07-04 9:53 bugtrack
2005-07-03 13:57 bugtrack
2005-07-03 12:09 bugtrack
2005-07-03 7:25 bugtrack
2005-07-02 19:47 bugtrack
2005-07-02 18:11 bugtrack
2005-07-02 16:53 bugtrack
2005-07-01 20:57 bugtrack
2005-07-01 18:33 bugtrack
2005-07-01 18:16 bugtrack
2005-07-01 12:49 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=967f63567f018d4d4819b371a9928baa@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