From: Ed Wildgoose <Ed@Wildgooses.com>
To: alsa-devel@lists.sourceforge.net
Subject: Problem with simultaneous 16bit Rec/play with rme96/8
Date: Sat, 12 Jul 2003 19:35:09 +0100 [thread overview]
Message-ID: <3F1054DD.30301@Wildgooses.com> (raw)
Hi,
I have an RME 96/8 PAD card and I have tried various versions of the
alsa driver from 0.9 up to 0.94 and I'm seeing a consistent problem with
simultaneous play and record at 16 bit sample levels with OSS
For example running:
sox -r 44100 -t ossdsp -w -s -c 2 /dev/dsp test.wav
is fine, but then in another window doing this:
gentoo root # aplay test.wav
Playing WAVE 'test.wav' : Signed 16 bit Little Endian, Rate 44100 Hz, Stereo
ALSA lib pcm_hw.c:324:(snd_pcm_hw_hw_params) SNDRV_PCM_IOCTL_HW_PARAMS
failed: Device or resource busy
aplay: set_params:840: Unable to install hw params:
ACCESS: RW_INTERLEAVED
FORMAT: S16_LE
SUBFORMAT: STD
SAMPLE_BITS: 16
FRAME_BITS: 32
CHANNELS: 2
RATE: 44100
PERIOD_TIME: (46439 46440)
PERIOD_SIZE: 2048
PERIOD_BYTES: 8192
PERIODS: 8
BUFFER_TIME: (371519 371520)
BUFFER_SIZE: 16384
BUFFER_BYTES: 65536
TICK_TIME: 10000
However, everything is OK if I use only ALSA, for example:
arecord -r 44100 -t wav -c 2 -f S16_LE test.wav
...works fine when I then use "aplay test.wav"
Is this a known problem?
Also, I don't know if it is related, but under gentoo + KDE, when artsd
starts I get the following error message:
Sound server informational message:
Error while initializing the sound driver:
SNDCTL_DSP_SPEED failed - Device or resource busy
The sound server will continue, using the null output device.
My /etc/asound.conf:
pcm.rme96 {
type hw
card 0
}
ctl.rme96 {
type hw
card 0
}
Thanks for any help
Ed W
-------------------------------------------------------
This SF.Net email sponsored by: Parasoft
Error proof Web apps, automate testing & more.
Download & eval WebKing and get a free book.
www.parasoft.com/bulletproofapps1
reply other threads:[~2003-07-12 18:35 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3F1054DD.30301@Wildgooses.com \
--to=ed@wildgooses.com \
--cc=alsa-devel@lists.sourceforge.net \
/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.