All of lore.kernel.org
 help / color / mirror / Atom feed
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: @Daniel Mack: Send you a FTU
Date: Tue, 14 Jun 2011 13:37:53 +0200	[thread overview]
Message-ID: <4DF74811.2080409@showlabor.de> (raw)
In-Reply-To: <BANLkTimNHyp3_RqCjGQ8p-UOS8_LG+SKeQ@mail.gmail.com>

Hi Daniel,

(just to have it public on the list)

Am 14.06.2011 10:56, schrieb Daniel Mack:
>
> Quite frankly, I'm not fully aware about known issues with these
> devices that need attention. Could you summarize which problems are
> left to look at?
>


Here's a list of the issues I'm aware of:

1. Playback clicks:

There are periodic clicks in the playback at all sample rates. They are 
not very noticable in normal use but when you playback a plain sine the 
clicks are very obvious. When we discussed it last year we suspected 
that the device uses "implicit feedback". For the record: When we used 
the device with QUIRK_AUDIO_STANDARD_INTERFACE quirks we had clickless 
playback at 48 kHz and 96 kHz, but playback at 44.1 kHz and 88.2 kHz was 
totally distorted and the kernel would eventually crash after a minute 
or so.


2. External clock sync

The FTU devices are capable of syncing to an external clock via SPDIF. I 
don't know how to switch between internal and external clock. I don't 
even have a second audio interface to test with.


3. Mixer control steps:

The mixer controls are working fine now but are very fine grained. Being 
that fine grained it is hard to control the mixer in some mixer programs 
like alsamixer (alsamixer-qt4 and gamix work fine). A little bit of fine 
tuning would be nice. But I don't know which step size the hardware 
actually supports.

4. Reverb unit:

The FTU devices have a reverb unit which isn't supported, yet. It's 
straight forward based on the basic mixer support . I've almost got it 
wroking except for the "Reverb Program" switch. I know how to do it, so 
probably there will be a patch soon.


5. "Lost" URBs:

Some users reported occasional playback distortion combined with dmesg 
output like this: "ALSA urb.c:480: frame 5 active: -18". I don't know if 
this is really related to the driver. Actually I don't think so but who 
knows ...


Are there any other issues?

Kind regards,

Felix

  parent reply	other threads:[~2011-06-14 11:37 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-13 10:25 @Daniel Mack: Send you a FTU Aurélien Leblond
2011-06-13 17:27 ` Paul Menzel
2011-06-14  7:46 ` Felix Homann
2011-06-14  8:56 ` Daniel Mack
2011-06-14  9:21   ` Aurélien Leblond
2011-06-14 10:18   ` Aurélien Leblond
2011-06-14 11:37   ` Felix Homann [this message]
2011-06-14 13:05     ` Aurélien Leblond
2011-06-14 13:15       ` Daniel Mack
2011-06-15 12:32         ` Aurélien Leblond
2011-06-21  9:36         ` Aurélien Leblond
2011-06-21  9:40           ` Daniel Mack

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=4DF74811.2080409@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.