From: Pavel Hofman <pavel.hofman@insite.cz>
To: Lex Wassenberg <lex.wassenberg@gmail.com>
Cc: alsa-devel@alsa-project.org
Subject: Re: Sound streaming application: which device to use?
Date: Wed, 10 Jun 2009 12:02:10 +0200 [thread overview]
Message-ID: <4A2F84A2.9050503@insite.cz> (raw)
In-Reply-To: <45c981ab0906100242g234bfa08u8137c58bd08b9960@mail.gmail.com>
Lex Wassenberg wrote:
> On Wed, Jun 10, 2009 at 4:42 AM, Lee Revell<rlrevell@joe-job.com> wrote:
>> On Tue, Jun 9, 2009 at 10:01 AM, Lex Wassenberg<lex.wassenberg@gmail.com> wrote:
>>> Is there nobody that can help me out on the questions above? I figured
>>> the answer to question 4 (passing a pointer to an uninitialized
>>> integer; I thought the integer was only used for reporting back, which
>>> is not true), but all other questions still stand. Nobody??
>> You don't provide enough info. What soundcard? What distro? What is
>> the output of "aplay -v file.wav" when file.wav is the same audio
>> format your app uses?
>>
>> Lee
>>
>
> The distro is OpenSuse 10.3 , the soundcard doesn't (or shouldn't)
> matter: the application program knows nothing about the soundcard and
> it doesn't want to either. It should just use that sound card that is
> present on the machine where it runs. I thought that it would be ALSA
> that takes care of the particularites of the underlying hardware.
> That's why I programmed the device to be "default" or "plughw".
>
> For the requested output of the aplay program I would first have to
> find a wave file with the specific format.
>
Just use sox, it will convert to any format you need. Details man sox, e.g.
sox your.mp3 -r 44100 -b 16 new-44k-16.wav
Pavel.
prev parent reply other threads:[~2009-06-10 10:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-04 11:28 Sound streaming application: which device to use? Lex Wassenberg
2009-06-04 14:30 ` Colin Guthrie
2009-06-09 14:01 ` Lex Wassenberg
2009-06-10 2:42 ` Lee Revell
2009-06-10 9:42 ` Lex Wassenberg
2009-06-10 10:02 ` Pavel Hofman [this message]
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=4A2F84A2.9050503@insite.cz \
--to=pavel.hofman@insite.cz \
--cc=alsa-devel@alsa-project.org \
--cc=lex.wassenberg@gmail.com \
/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