From: Mark Knecht <markknecht@comcast.net>
To: Alsa-Devel <alsa-devel@lists.sourceforge.net>
Subject: Re: HDSP 9652: Input channel corruption
Date: Wed, 08 Oct 2003 21:07:28 -0700 [thread overview]
Message-ID: <1065672448.3693.12.camel@Wizard.knechthome.com> (raw)
In-Reply-To: <20031009111238.B5188@nautronix.com.au>
On Wed, 2003-10-08 at 20:12, Nick Arnold wrote:
> The symptoms:
> ------------
>
> We connect a sine wave to the first 12 channels and record them, and see
> three channels -- 0, 4, and 8 -- are "corrupted". The remaining channels
> appear to be well-formed and look as we expect them to.
When you say the 'first 12 channels', are you speaking of the
alsa:playback channels, or are you attaching a sine wave the the ADAT
input channels from an external source? I'm not clear on that.
>
> It seems most likely to be some code in the driver, or perhaps the mixer is
> responsible for this incorrect ordering.
OK, first, I apologize, but Thomas and I never looked at 96KHz
operation, and to the best of my knowledge it was only our debug that
went into the Aug. 27th patch. I think this means you are on new ground.
Thomas and I saw a similar problem at 44.1KHz with ADAT input signals at
one point. In hdspmixer I was getting green audio and yellow peak
information that did not make sense. I do not remember how I came to the
conclusion that there was an ordering problem, but Thomas pretty quickly
found it once I pointed it out. Possibly we only fixed normal speed
operation and missed the double speed equivalent problem.
>
> The questions are:
>
> - could this be a bug, perhaps in the hdsp driver?
I think possibly yes.
>
> - alternatively, could this be due to some mixer setting that has been
> turned on by default unbeknownst to us? if so, how can we turn this
> off?
I do not think this is likely, or at least I do not know of anything you
can do.
>
> any help much appreciated,
I think I'm not helping much...
>
> nick.
-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
SourceForge.net hosts over 70,000 Open Source Projects.
See the people who have HELPED US provide better services:
Click here: http://sourceforge.net/supporters.php
next prev parent reply other threads:[~2003-10-09 4:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-09 3:12 HDSP 9652: Input channel corruption Nick Arnold
2003-10-09 4:07 ` Mark Knecht [this message]
2003-10-10 8:55 ` Nick Arnold
2003-10-10 19:34 ` Mark Knecht
2003-10-15 22:01 ` alsa-devel
2003-10-16 0:18 ` Paul Davis
[not found] ` <20031020164753.A16168@nautronix.com.au>
2003-10-21 0:39 ` Mark Knecht
2003-10-11 0:23 ` Mark Knecht
-- strict thread matches above, loose matches on Subject: below --
2003-10-09 3:22 Nick Arnold
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=1065672448.3693.12.camel@Wizard.knechthome.com \
--to=markknecht@comcast.net \
--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.