Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Julien Bramary <julien.bramary@blueyonder.co.uk>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: How to Test my Driver
Date: Fri, 11 Aug 2006 01:42:15 +0100	[thread overview]
Message-ID: <44DBD267.1070800@blueyonder.co.uk> (raw)
In-Reply-To: <s5hzmecwx2e.wl%tiwai@suse.de>

Takashi Iwai wrote:
> At Thu, 10 Aug 2006 04:30:26 +0100,
> Julien Bramary wrote:
>   
>> Hello all,
>>
>> I am writing an alsa driver for a Micronas DAC on an embedded arm 
>> system. (I am still an Alsa beginner).
>> The device is now able to play wav with aplay and mp3 with madplay 
>> without too much trouble (pause-resume works etc).
>>
>> However, I'd like to know if there is a way to test the driver more 
>> extensively (at various sampling rates etc...).
>>     
>
> I usually try aplay with various wav files that are converted to
> different rates, channels and formats by sox or other tools.
> Also, using different buffer size and period size with aplay is
> recommended.
>
> For multiple channels, speaker-test is a good tool, too.
>
>
> Takashi
>
>   
Thank you Takashi,
I will use audacity to generate the adequate wav files and tweak the 
buffer and period sizes in aplay as you suggested.


Julien


-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642

      reply	other threads:[~2006-08-11  0:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-10  3:30 How to Test my Driver Julien Bramary
2006-08-10 13:16 ` Takashi Iwai
2006-08-11  0:42   ` Julien Bramary [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=44DBD267.1070800@blueyonder.co.uk \
    --to=julien.bramary@blueyonder.co.uk \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=tiwai@suse.de \
    /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