From: "William Juul" <william@juul.no>
To: alsa-devel@alsa-project.org
Subject: new driver: channel alignment (was: 30mS interval problem)
Date: Wed, 27 Feb 2008 13:56:16 +0100 [thread overview]
Message-ID: <2563ac9e0802270456q31e47995m4365a64e7574bbbf@mail.gmail.com> (raw)
Hello
I am new to ALSA and trying to write a new driver for a ADC connected
with PCM to an AVR32 on a NGW100 reference card provided by Atmel.
I have the problem that different channels from the PCM stream comes
in different positions in the WAV file. For example when I disable all
but the first PCM channel on the ADC, I can see with an oscilloscope
that there is only data in the first timeslot on the PCM data stream.
But the data from this channel can occur in any of the 4 channels in
the WAV file. This is consistent throughout the one capture/file, but
in the next capture the data will occur in another channel in the
WAV-file.
How can I make sure that the data from one particular channel always
occur in a fixed position in the WAV file?
Best regards
William Juul
reply other threads:[~2008-02-27 12:56 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=2563ac9e0802270456q31e47995m4365a64e7574bbbf@mail.gmail.com \
--to=william@juul.no \
--cc=alsa-devel@alsa-project.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox