From: Felix Homann <linuxaudio@showlabor.de>
To: Daniel Mack <zonque@gmail.com>
Cc: "Aurélien Leblond" <blablack@gmail.com>, alsa-devel@alsa-project.org
Subject: Re: M-Audio FTU issues
Date: Fri, 24 Jun 2011 10:52:40 +0200 [thread overview]
Message-ID: <4E045058.6000405@showlabor.de> (raw)
In-Reply-To: <BANLkTimOjiKwOqSveGvujMJ5uBL-JKsBeA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1326 bytes --]
Hi again,
Am 24.06.2011 03:14, schrieb Daniel Mack:
>
> Hence my question is: How do you guys test? I renderened a sine tone
> in different samplerates and bit depths to .wav files and play them
> with aplay (no pulseaudio or anything in the chain). Could you try the
> same and report what happens?
>
OK, I've rendered a sine to a .wav (well, in audacity), played it via
aplay on the FTU8R and could hear the clicks. I've been using plughw
though, cause I don't remember right now how to convert bit-depths.
I even played sines directly from puredata and audacity without JACK and
could still hear the clicks.
Please, make sure you have the routing "diagonal", i.e. "DIn i - Out j"
is set to 0% if i !=j and 100% if i == j. I've attached a small bash
script to accomplish this. After plugging the device in all playback
volumes are initially at 100%. I could not notice the clicks then unless
it turned the volume very very loud (I guess aplay plays back on all
channels, which blurs the clicks).
If you still can't hear the clicks please try using a headphone?
Sometimes the clicks are hardly noticable when there's minimal
background noise. You might even have turn the volume higher than
convenient for your ears...
I hope this helps hearing the clicks using the unmodified driver.
Kind regards,
Felix
[-- Attachment #2: ftu-diagonal-routing.sh --]
[-- Type: application/x-shellscript, Size: 371 bytes --]
[-- Attachment #3: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2011-06-24 8:52 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-24 1:14 M-Audio FTU issues Daniel Mack
2011-06-24 3:27 ` Grant Diffey
2011-06-24 7:35 ` Felix Homann
2011-06-24 8:52 ` Felix Homann [this message]
2011-06-24 15:23 ` Daniel Mack
2011-06-24 15:58 ` Clemens Ladisch
2011-06-24 16:10 ` Daniel Mack
2011-06-28 20:37 ` Aurélien Leblond
2011-06-29 8:08 ` Daniel Mack
2011-07-03 11:52 ` Grant Diffey
2011-07-04 17:14 ` Aurélien Leblond
2011-07-04 17:23 ` Daniel Mack
2011-07-13 21:18 ` Juan Pablo Bouza
2011-07-21 5:08 ` Juan Pablo Bouza
2011-07-21 7:55 ` Daniel Mack
2011-07-21 8:25 ` Felix Homann
2011-07-24 14:12 ` Aurélien Leblond
2011-07-24 14:46 ` Daniel Mack
2011-07-21 20:31 ` Juan Pablo Bouza
2011-07-22 8:42 ` Daniel Mack
2011-07-23 4:25 ` Juan Pablo Bouza
2011-07-25 13:07 ` Clemens Ladisch
2011-06-27 8:52 ` Felix Homann
2011-06-24 9:08 ` Felix Homann
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=4E045058.6000405@showlabor.de \
--to=linuxaudio@showlabor.de \
--cc=alsa-devel@alsa-project.org \
--cc=blablack@gmail.com \
--cc=zonque@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 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.