All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Knecht <markknecht@comcast.net>
To: Nick Arnold <nick.arnold@nautronix.com.au>
Cc: Alsa-Devel <alsa-devel@lists.sourceforge.net>
Subject: Re: HDSP 9652: Input channel corruption
Date: Fri, 10 Oct 2003 17:23:02 -0700	[thread overview]
Message-ID: <1065831781.3447.14.camel@Wizard.knechthome.com> (raw)
In-Reply-To: <20031010165526.A10106@nautronix.com.au>

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

Nick,
   Following on from my other response to you, I do not see the problem
you are speaking of. (Again, assuming I understand what you are saying
the problem is.) The attacked .png file (I hope small enough to be
accepted by the reflector - it's about 27K) shows the audio on channels
8, 10, 12 & 14. This assumes your channel numbering of 0-23 and is all
even (left ) channels on the ADAT 2 input to the HDSP 9652.

   I ran a quick test this evening by creating a session in Pro Tools
where I have a single stereo audio track. I then routed the track (via
sends) to the 4 ADAT stereo output pairs:

Pro Tools	HDSP 9652 in

ADAT 1-2	ADAT-2 8,9
ADAT 3-4	ADAT-2 10,11
ADAT 5-6	ADAT-2 12,13
ADAT 7-8	ADAT-2 14,15

   I recorded the four incoming stereo pairs using Audacity and then
deleted the 9,11,13 & 15 inputs from the display for this picture. 

   As you can see from this display, there is not obvious different
between the 4 channels. Channel 8 appears to be identical to channels
10, 12 & 14. I think that if there was the ordering problem you were
seeing it should be evident in this photo, but I'm not seeing it.

   (This was true for 9,11,13 & 15 also...)

   If I've misunderstood the problem you are debugging, let me know and
I'll set up another test. This only too 5 minutes to do, so I'm happy
(and interested!) in helping you debug this, especially if it does turn
out to be a global problem with the card.

   BTW - what firmware does your HDSP 9652 have? I suppose that a
different revision of firmware could certainly account for differences.

Cheers,
Mark

[-- Attachment #2: snap0000.xpm.gz --]
[-- Type: application/x-gzip, Size: 27750 bytes --]

  parent reply	other threads:[~2003-10-11  0:23 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
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 [this message]
  -- 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=1065831781.3447.14.camel@Wizard.knechthome.com \
    --to=markknecht@comcast.net \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=nick.arnold@nautronix.com.au \
    /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.