All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pierre-Antoine Champin <alsa-050822@champin.net>
To: Richard Smith <smithbone@gmail.com>
Cc: alsa-devel <alsa-devel@lists.sourceforge.net>
Subject: Re: Input gain on M-Audio Audiophile USB
Date: Mon, 05 Dec 2005 12:24:54 +0100	[thread overview]
Message-ID: <43942386.10807@champin.net> (raw)
In-Reply-To: <8a0c36780512050019k3ef806c3h2cb8b9b5edb03088@mail.gmail.com>

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

Richard Smith a écrit :
> Anybody have any idea how to change the line in input gain on the
> M-Audio Audiophile USB?  The way its currently set renders it useless.
>  It's just too hot.   If you connect any normal line level source up
> to it it just bangs the input rails.
> 
> Alsamixer tells me there is not a mixer.
> 
> I know its possible because if you try the same setup under win2k then it works.
> 
> I've tried 1.0.9 and 1.0.10rc3 and they have the same behavior.

I've not tried it recenrly, but the last time I did, I first thought I
had a gain problem, while this was actually a wrong byte order: it was
neither low-endian nor big-endian, but a strange mix, causing low-weight
values to be considered high-weight, hence the saturation impresson.

Filtering the input through a program which changes the order of the
bytes (a,b,c -> c,a,b) gives a good sound; but of course, it kills latency!

I attach the script I used to test that. I'm not sure this is the
problem you have, but it is worth a try.

  Pierre-Antoine



[-- Attachment #2: swap2.py --]
[-- Type: text/x-python, Size: 168 bytes --]

#!/usr/bin/python
import sys

while True:
    try:
        a,b,c = sys.stdin.read (3)
        sys.stdout.write ("".join ((c,a,b)))
    except ValueError:
        break

  reply	other threads:[~2005-12-05 11:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-05  8:19 Input gain on M-Audio Audiophile USB Richard Smith
2005-12-05 11:24 ` Pierre-Antoine Champin [this message]
2005-12-05 16:00   ` Richard Smith
2005-12-06  7:19     ` Richard Smith

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=43942386.10807@champin.net \
    --to=alsa-050822@champin.net \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=smithbone@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.