From: Martin Langer <martin-langer@gmx.de>
To: Jaroslav Kysela <perex@perex.cz>
Cc: ALSA development <alsa-devel@alsa-project.org>
Subject: Re: switch to new PCM API for 1.0 release
Date: Sat, 8 Nov 2003 17:39:22 +0100 [thread overview]
Message-ID: <20031108163922.GA6647@tuba.home> (raw)
In-Reply-To: <Pine.LNX.4.53.0311051141250.1187@F137.suse.de>
On Wed, Nov 05, 2003 at 11:47:58AM +0100, Jaroslav Kysela wrote:
>
> I decided to switch to new PCM API (values are returned using an
> indirect pointer rather as return value, so error codes are not mixed with
> values). The binary compatibility is kept. So, you can use old
> applications with new libraries and you can even use applications compiled
> against 1.0 alsa-lib with 0.9 library binaries.
FYI,
aplay/arecord doesn't work at the moment:
Playing WAVE '/tmp/test.wav' : Signed 16 bit Little Endian, Rate 44100 Hz,
Stereo
aplay: set_params:874: Unable to install hw params:
ACCESS: RW_INTERLEAVED
FORMAT: S16_LE
SUBFORMAT: STD
SAMPLE_BITS: 16
FRAME_BITS: 32
CHANNELS: 2
RATE: NONE
^^^^^^^^^^
PERIOD_TIME: (170666 170667)
PERIOD_SIZE: (22963264 22963265)
PERIOD_BYTES: (91853056 91853060)
PERIODS: (2 3)
BUFFER_TIME: (341333 341334)
BUFFER_SIZE: 45926708
BUFFER_BYTES: 183706832
TICK_TIME: 10000
martin
-------------------------------------------------------
This SF.Net email sponsored by: ApacheCon 2003,
16-19 November in Las Vegas. Learn firsthand the latest
developments in Apache, PHP, Perl, XML, Java, MySQL,
WebDAV, and more! http://www.apachecon.com/
next prev parent reply other threads:[~2003-11-08 16:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-05 10:47 switch to new PCM API for 1.0 release Jaroslav Kysela
2003-11-08 16:39 ` Martin Langer [this message]
2003-11-08 19:04 ` Jaroslav Kysela
2003-11-08 19:14 ` Martin Langer
2003-11-08 19:32 ` Jaroslav Kysela
2003-11-08 20:43 ` Martin Langer
2003-11-24 4:19 ` 1.0.0pre2 - ymfpci tom burkart
2003-11-24 10:17 ` Takashi Iwai
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=20031108163922.GA6647@tuba.home \
--to=martin-langer@gmx.de \
--cc=alsa-devel@alsa-project.org \
--cc=perex@perex.cz \
/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.