From: Pavel Polischouk <pavelp@rogers.com>
To: alsa-devel@lists.sourceforge.net
Subject: Re: [PATCH 1/2] M-Audio USB
Date: Thu, 14 Dec 2006 22:36:08 -0500 [thread overview]
Message-ID: <45821828.6070708@rogers.com> (raw)
In-Reply-To: <20061203215521.beksv3idcw444o4g@webmail.supelec.fr>
Thibault Le Meur wrote:
> However, it does not correct the corrupted initialization state that
> occur when the device is turned on before the snd-usb-audio module is
> initialized with a valid device_setup parameter (see below).
>
There are 2 reasons for this:
1. The default setting "0" will immediately make the device stuck in a
weird semi-working mode. Avoid. I'll add a check to the next patch
revision that will REFUSE to load the driver for M-Audio unless a valid
setup parameter is specified. Another approach would be to use a mixer
control to select available configuration (with the default of NONE).
2. If you're using a daemon that loads USB drivers automatically, it
will always load using "default" setting. If a valid device_setup
parameter is added to /etc/modprobe.conf, it will be possible to turn on
the device before initializing the driver.
> As far as the documentation is concerned, shouldn't it be better to keep
> an Audiophile-USB.txt file with only the following sentence: "Updated
> documentation on this device can now be found in the M-Audio.txt
> file" ?
>
Agreed.
Also, I will update the JACK info. Current version can work natively
with 24bit big-endian interfaces, and also works fine with Quattro in
4-channel input mode.
Another problem that I found with Quattro. The driver works fine in
24/96k mode, no underruns. But in 44k/48k modes, it's always giving me
JACK xruns, or just skips in arecord, even with the most forgiving JACK
settings (high realtime priority and big buffers). This looks
counter-intuitive, that the slower mode performs worse than faster one.
Could it be that the driver reserves not enough USB bandwidth from
hardware, or something similar? What settings could be changed to try to
correct this?
-------------------------------------------------------------------------
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
next prev parent reply other threads:[~2006-12-15 3:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-24 20:26 [PATCH 1/2] M-Audio USB Pavel Polischouk
2006-11-27 11:15 ` Takashi Iwai
2006-11-27 11:18 ` Takashi Iwai
2006-12-03 22:42 ` Peter Oehry
2006-12-15 3:10 ` Pavel Polischouk
2006-12-15 8:42 ` RE : " Thibault Le Meur
2006-12-15 9:25 ` Thibault Le Meur
2006-12-03 20:55 ` Thibault Le Meur
2006-12-15 3:36 ` Pavel Polischouk [this message]
2006-12-15 8:55 ` RE : " Thibault Le Meur
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=45821828.6070708@rogers.com \
--to=pavelp@rogers.com \
--cc=alsa-devel@lists.sourceforge.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.