All of lore.kernel.org
 help / color / mirror / Atom feed
From: Clemens Ladisch <clemens@ladisch.de>
To: Dan MacDonald <allcoms@gmail.com>
Cc: alsa-devel@alsa-project.org
Subject: Re: CM6206, S/PDIF + JACK
Date: Tue, 13 Nov 2012 22:25:34 +0100	[thread overview]
Message-ID: <50A2BACE.80107@ladisch.de> (raw)
In-Reply-To: <CANOoOjtGq5OYYkhVHrxivCSrPmvzid1_-vbvuzDtgDqChUHTSQ@mail.gmail.com>

Dan MacDonald wrote:
> However, I had a quick go at capturing audio from SPDIF and the default
> stereo inputs (after making sure SPDIF in was enabled under alsamixer)
>  this morning but I got nothing. I have zero experience with SPDIF devices
> and Linux (or any other OS) so I dunno what to watch out for

This depends entirely on how the hardware implements the routing.

> In my quick test I was trying to capture audio from a audio CDR so there
> won't have been any copy protection on the disc. CDs are 44.1Khz of course
> but I was running JACK at 48Khz - that shouldn't be an issue should it or
> would I need to run JACK at 44.1 to capture an audio CD via SPDIF? Maybe rt
> resampling isn't supported?

I didn't find a box labeled "high-quality resampler for those lazy Jack
users" in the datasheet ...

> Another thing thats just come to mind is I think that the mic and line
> inputs were also set to capture so maybe I'd need to only enable capture
> for the SPDIF input but nothing else?

In theory, only one input can be enabled at the same time.
What does "amixer contents" show for this device?


Regards,
Clemens

  reply	other threads:[~2012-11-13 21:25 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-13 11:41 CM6206, S/PDIF + JACK Dan MacDonald
2012-11-13 12:55 ` Clemens Ladisch
2012-11-13 13:25   ` Dan MacDonald
2012-11-13 21:25     ` Clemens Ladisch [this message]
2012-11-13 21:46       ` Dan MacDonald
2012-11-14  7:40         ` Clemens Ladisch
2012-11-14 10:29           ` Dan MacDonald

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=50A2BACE.80107@ladisch.de \
    --to=clemens@ladisch.de \
    --cc=allcoms@gmail.com \
    --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 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.