From: bugtrack@alsa-project.org
To: alsa-devel@alsa-project.org
Subject: [ALSA - driver 0000758]: Full duplex is not working in OSS emulation.
Date: Wed, 29 Dec 2004 17:39:23 +0100 [thread overview]
Message-ID: <d305d4fcb399864d9136d699fb667a04@bugtrack.alsa-project.org> (raw)
A NOTE has been added to this issue.
======================================================================
<https://bugtrack.alsa-project.org/alsa-bug/view.php?id=758>
======================================================================
Reported By: croiset
Assigned To:
======================================================================
Project: ALSA - driver
Issue ID: 758
Category: PCI - RME 96
Reproducibility: always
Severity: major
Priority: normal
Status: new
Distribution: Redhat 7.2
Kernel Version: 2.4.7
======================================================================
Date Submitted: 12-29-2004 10:15 CET
Last Modified: 12-29-2004 17:39 CET
======================================================================
Summary: Full duplex is not working in OSS emulation.
Description:
If I play something with one player, I am unable to record something on the
same device.
The same thing ispossible with the other cards I have.
======================================================================
----------------------------------------------------------------------
croiset - 12-29-04 14:54
----------------------------------------------------------------------
I use nas for playing. This application open the device in write mode
only.
cf nas.conf option : readwrite "no" # for open(device, O_WRONLY|O_SYNC,
0666);
This exact configuration is working with all cards I have except the RME
96/8.
The recorder open the device like that : open(_opt->device,
O_RDONLY|O_NONBLOCK )
----------------------------------------------------------------------
tiwai - 12-29-04 17:39
----------------------------------------------------------------------
Hmm, I don't see problems in rme96.c.
Could you check whether the devices are really opened in O_WRONLY and
O_RDONLY? Maybe strace can show better.
Also, you can check /proc/asound/card0/pcm*/sub0/* files as the current
state, too.
Issue History
Date Modified Username Field Change
======================================================================
12-29-04 10:15 croiset New Issue
12-29-04 10:15 croiset Distribution => Redhat 7.2
12-29-04 10:15 croiset Kernel Version => 2.4.7
12-29-04 14:17 tiwai Note Added: 0002998
12-29-04 14:54 croiset Note Added: 0003000
12-29-04 17:39 tiwai Note Added: 0003004
======================================================================
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
next reply other threads:[~2004-12-29 16:39 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-29 16:39 bugtrack [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-05-10 14:25 [ALSA - driver 0000758]: Full duplex is not working in OSS emulation bugtrack
2006-05-10 14:22 bugtrack
2006-05-10 14:00 bugtrack
2006-05-10 13:48 bugtrack
2006-05-10 12:56 bugtrack
2006-05-09 13:49 bugtrack
2006-05-09 12:09 bugtrack
2006-01-02 8:12 bugtrack
2005-12-30 22:08 bugtrack
2005-09-14 14:16 bugtrack
2005-01-03 15:30 bugtrack
2004-12-29 16:59 bugtrack
2004-12-29 16:56 bugtrack
2004-12-29 13:54 bugtrack
2004-12-29 13:17 bugtrack
2004-12-29 9:15 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=d305d4fcb399864d9136d699fb667a04@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