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: M-Audio FTU issues
Date: Fri, 24 Jun 2011 09:35:03 +0200	[thread overview]
Message-ID: <4E043E27.3060902@showlabor.de> (raw)
In-Reply-To: <BANLkTimOjiKwOqSveGvujMJ5uBL-JKsBeA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2190 bytes --]

Hi Daniel,


Am 24.06.2011 03:14, schrieb Daniel Mack:
> So, I've looked into this today and as expected, the device normally
> operates in implicit feedback mode. After installing a proprietary
> driver on Mac OS X (that regularily crashed my kernel), the analyzer
> shows that for every inbound packet, an out packet is sent back with
> the same amount of data in it. And there are no feedback endpoints.

Thank you very much!


>
> What surprises me though, is that I can't hear the clicks and pops you
> guys describe. Instead, I hear a quite annoying distortion for both
> 44100 and 48000 Hz which I can't explain either.

As Grant wrote, I only experienced something like this when I accidently 
had turned on some reverb effects in the Windows control center. But if 
it sounds as if the output was completely "chopped" then it would rather 
remind me of the days when it only worked at 48/96 kHz and I tried 
playing back at 44.1/88.2 kHz.

> I patched the driver so that it supports implicit feedback, but that
> didn't change anything in that regard.

Great, that you could already do the implicit feedback part! (BTW, don't 
hesitate to send me early experimental patches.)


> Hence my question is: How do you guys test?

I'm usually using puredata for this. I've attached the very simple pd 
file. I've always tested with JACK, never with ALSA directly. But as I 
said earlier: If I boot an old kernel with "initial support" (i.e. the 
one using just QUIRK_AUDIO_STANDARD_INTERFACE; only working at 48/96 
kHz) the clicks go away. Hence it doesn't seem related to using JACK. 
(Using my internal soundcard I don't hear clicks using pd/JACK either).

I even "ported" back the initial support to a current kernel a month or 
so ago and could reliably switch between "Clicks at all sampliing rates" 
and "No clicks at 48/96 kHz; kernel crash at 44.1/88.2 kHz".

Initially though I generated a sine in audacity, too.

>   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?

I will try this morning and report.

Kind regards,

Felix

[-- Attachment #2: pd-sine.pd --]
[-- Type: text/plain, Size: 96 bytes --]

#N canvas 736 426 450 300 10;
#X obj 150 143 dac~;
#X obj 87 60 osc~ 10000;
#X connect 1 0 0 0;

[-- Attachment #3: Type: text/plain, Size: 0 bytes --]



  parent reply	other threads:[~2011-06-24  7:35 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 [this message]
2011-06-24  8:52 ` Felix Homann
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=4E043E27.3060902@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.