Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: GitHub issues - edited <github@alsa-project.org>
To: alsa-devel@alsa-project.org
Subject: "aplay -D oss -l" still reads sound cards through ALSA, not OSS
Date: Thu, 17 Sep 2020 05:49:27 +0200 (CEST)	[thread overview]
Message-ID: <20200917034927.7DFEEF80212@alsa1.perex.cz> (raw)
In-Reply-To: <1600314563401345015-webhooks-bot@alsa-project.org>

alsa-project/alsa-utils issue #56 was edited from yurivict:

I don't have any ALSA devices, only OSS devices.

When the OSS PCM is selected ```aplay``` still tries to read ALSA devices:
```
$ /usr/bin/aplay -D oss -l
aplay: device_list:272: no soundcards found...
```

```
$ /usr/bin/aplay -L
null
    Discard all samples (playback) or generate zero samples (capture)
oss
    Open Sound System
```

But ```/usr/bin/aplay x.wav``` plays it through the OSS card.

aplay should list OSS cards when -D is selected.
The ALSA interface should also list OSS cards when no ALSA cards are present but it doesn't.

alsa-lib-1.1.8
alsa-plugins-oss-1.1.6
alsa-utils-1.1.8

Issue URL     : https://github.com/alsa-project/alsa-utils/issues/56
Repository URL: https://github.com/alsa-project/alsa-utils

       reply	other threads:[~2020-09-17  3:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1600314563401345015-webhooks-bot@alsa-project.org>
2020-09-17  3:49 ` GitHub issues - edited [this message]
     [not found] <1600313482498797894-webhooks-bot@alsa-project.org>
2020-09-17  3:31 ` "aplay -D oss -l" still reads sound cards through ALSA, not OSS GitHub issues - opened

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=20200917034927.7DFEEF80212@alsa1.perex.cz \
    --to=github@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