From: Kris Modrak <u9514439@anu.edu.au>
To: Jaroslav Kysela <perex@suse.cz>
Cc: "alsa-devel@lists.sourceforge.net" <alsa-devel@lists.sourceforge.net>
Subject: Re: Rate Conversion
Date: Fri, 28 Jun 2002 13:30:24 +1000 [thread overview]
Message-ID: <3D1BD850.C59C43C2@anu.edu.au> (raw)
In-Reply-To: Pine.LNX.4.33.0206271610220.545-100000@pnote.perex-int.cz
Jaroslav Kysela wrote:
>
> On Thu, 27 Jun 2002, Kris Modrak wrote:
>
> > I am writing a PCM application and wish to play a .wav file that has a
> > sampling rate of 8kHz on a hardware setup that only supports sampling
> > frequencies of 44.1 or 48kHz.
> >
> > Does anyone know how to implement this?
>
> You don't need to do this. Use the 'plughw' device which should do all
> conversions from you.
I am a little confused about your advice. I am not sure how to access
the 'plughw' device from my application.
I have a full duplex application that can play a file at 44.1kHz and
record at the same rate but I want it to operate at lower sampling
frequencies.
I am not sure of how I should be setting up my PCM devices. How do I
tell them to convert, say, 8kHz audio data to 44.1kHz audio data so my
hardware can play it at the correct speed?
I tried using aplay with plughw to play an 8kHz file and got the
following results
>aplay -Dplughw s1.wav
Playing WAVE 's1.wav' : Signed 16 bit Little Endian, Rate 8000 Hz, Mono
Segmentation fault
However it worked when using a 441.kHz file.
Regards
Kris Modrak
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Bringing you mounds of caffeinated joy.
http://thinkgeek.com/sf
next prev parent reply other threads:[~2002-06-28 3:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-27 8:29 Rate Conversion Kris Modrak
2002-06-27 14:11 ` Jaroslav Kysela
2002-06-28 3:30 ` Kris Modrak [this message]
2002-06-28 11:28 ` Paul Davis
2002-07-01 2:19 ` Kris Modrak
2002-07-01 11:51 ` Paul Davis
[not found] <200206281126.g5SBQLTk004595@anu.edu.au>
2002-07-02 0:43 ` Kris Modrak
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=3D1BD850.C59C43C2@anu.edu.au \
--to=u9514439@anu.edu.au \
--cc=alsa-devel@lists.sourceforge.net \
--cc=perex@suse.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.