All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richi Plana <richip@richip.dhs.org>
To: Clemens Ladisch <cladisch@fastmail.net>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: Frequency Problems with 0d8c:0201 and	snd-usb-audio
Date: Thu, 16 Nov 2006 11:23:28 -0700	[thread overview]
Message-ID: <1163701408.3406.41.camel@richip.dhs.org> (raw)
In-Reply-To: <1163697994.10962.276090935@webmail.messagingengine.com>

On Thu, 2006-11-16 at 18:26 +0100, Clemens Ladisch wrote:

> Your device claims to support both 44.1 and 48 kHz.
> 
> What kind of distortion?

As objectively as I can describe it: the audio played at 48 kHz seems to
be coming out at the right speed, but the sound itself is played at a
higher pitch. It's as if each sample block is sent and received at the
correct interval, but actual data from the block is being played back at
a higher rate. It feels like either the DAC is playing at a higher rate
but each block comes at the correct intervals ... or the data isn't
getting to the processor fast enough so it tries to play the bursts as
quickly as it can.

Sorry, I'm not a sound engineer.

> What are the contents of /proc/asound/card0/stream0 while some
> 48 kHz stream is playing?

Here's the content when playing at 44100 Hz:

=========================================================================
PnP Audio Device         at usb-0000:00:13.2-2, full speed : USB Audio

Playback:
  Status: Running
    Interface = 1
    Altset = 2
    URBs = 3 [ 8 8 8 ]
    Packet Size = 196
    Momentary freq = 44100 Hz (0x2c.199a)
  Interface 1
    Altset 1
    Format: 0x2
    Channels: 8
    Endpoint: 6 OUT (ADAPTIVE)
    Rates: 44100, 48000
  Interface 1
    Altset 2
    Format: 0x2
    Channels: 2
    Endpoint: 6 OUT (ADAPTIVE)
    Rates: 44100, 48000
  Interface 1
    Altset 3
    Format: 0x2
    Channels: 4
    Endpoint: 6 OUT (ADAPTIVE)
    Rates: 44100, 48000
  Interface 1
    Altset 4
    Format: 0x2
    Channels: 6
    Endpoint: 6 OUT (ADAPTIVE)
    Rates: 44100, 48000
  Interface 1
    Altset 5
    Format: 0x2
    Channels: 2
    Endpoint: 6 OUT (ADAPTIVE)
    Rates: 48000

Capture:
  Status: Stop
  Interface 2
    Altset 1
    Format: 0x2
    Channels: 2
    Endpoint: 5 IN (ASYNC)
    Rates: 44100, 48000
=========================================================================

... and at 48000 Hz:

=========================================================================
PnP Audio Device         at usb-0000:00:13.2-2, full speed : USB Audio

Playback:
  Status: Running
    Interface = 1
    Altset = 5
    URBs = 3 [ 8 8 6 ]
    Packet Size = 392
    Momentary freq = 48000 Hz (0x30.0000)
  Interface 1
    Altset 1
    Format: 0x2
    Channels: 8
    Endpoint: 6 OUT (ADAPTIVE)
    Rates: 44100, 48000
  Interface 1
    Altset 2
    Format: 0x2
    Channels: 2
    Endpoint: 6 OUT (ADAPTIVE)
    Rates: 44100, 48000
  Interface 1
    Altset 3
    Format: 0x2
    Channels: 4
    Endpoint: 6 OUT (ADAPTIVE)
    Rates: 44100, 48000
  Interface 1
    Altset 4
    Format: 0x2
    Channels: 6
    Endpoint: 6 OUT (ADAPTIVE)
    Rates: 44100, 48000
  Interface 1
    Altset 5
    Format: 0x2
    Channels: 2
    Endpoint: 6 OUT (ADAPTIVE)
    Rates: 48000

Capture:
  Status: Stop
  Interface 2
    Altset 1
    Format: 0x2
    Channels: 2
    Endpoint: 5 IN (ASYNC)
    Rates: 44100, 48000
=========================================================================

The diff:

=========================================================================
<     Altset = 2
<     URBs = 3 [ 8 8 8 ]
<     Packet Size = 196
<     Momentary freq = 44100 Hz (0x2c.199a)
---
>     Altset = 5
>     URBs = 3 [ 8 8 6 ]
>     Packet Size = 392
>     Momentary freq = 48000 Hz (0x30.0000)
=========================================================================

I hope it tells you something because it's pretty meaningless to me.

> I guess the problem is that ALSA's default channel order isn't the same
> as that defined in the USB audio specification, and ALSA doesn't yet
> remap the channels for USB devices.

So it's likely that the physical ports are wired correctly and it's just
the mixer that's getting things mixed up? Ah well, a minor annoyance.
I'm sure that feature will get into ALSA one of these days. Maybe I'll
even pick up on it one of these days if I ever find the time.

Thanks!
--

Richi


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV

  reply	other threads:[~2006-11-16 18:23 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-15 18:00 Frequency Problems with 0d8c:0201 and snd-usb-audio Richi Plana
2006-11-16  9:10 ` Clemens Ladisch
2006-11-16 17:08   ` Richi Plana
2006-11-16 17:26     ` Clemens Ladisch
2006-11-16 18:23       ` Richi Plana [this message]
2006-11-16 18:29         ` Richi Plana
2006-11-17 17:26         ` Clemens Ladisch
2006-11-17 18:57           ` Richi Plana
2006-11-20 13:54             ` Clemens Ladisch
2006-11-20 13:55             ` Clemens Ladisch
2006-11-17 19:39 ` Lee Revell
2006-11-20 13:54   ` Clemens Ladisch

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=1163701408.3406.41.camel@richip.dhs.org \
    --to=richip@richip.dhs.org \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=cladisch@fastmail.net \
    /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.