From: Anssi Hannula <anssi.hannula@iki.fi>
To: Mark Hills <mark@xwax.org>
Cc: alsa-devel@alsa-project.org
Subject: Re: S/PDIF and track markers (echo3g)
Date: Fri, 17 Jun 2016 20:43:22 +0300 [thread overview]
Message-ID: <576436BA.4090104@iki.fi> (raw)
In-Reply-To: <1606171339510.3384@stax.localdomain>
17.06.2016, 16:29, Mark Hills kirjoitti:
> Hi,
Hi,
> Is there any provision in ALSA (either within the kernel or libasound) for
> extracting track marker information from S/PDIF?
I don't know what track marker data looks like, but see below.
> I have a large number of MiniDisc recordings to preserve as FLAC format.
>
> Losing track markers would be a huge inconvenience, though I don't care
> for the rest of the metadata (track names etc..)
>
> There's enough recordings to be worth developing specific software for the
> archival if it can access this information.
>
> I don't really know which path is likely to be successful:
>
> * An ALSA API to access the information; though I can't see anything
> specific to track markers
>
> * Whether a timecode could be used to detect track change; but I can't see
> any in /proc/asound/Layla3G/status
>
> * Does ALSA provide access to raw AES streams, so I could decode it in
> userland? I'm un-sure if this relates to hardware AC3 decoding.
ALSA does provide access to the raw stream with drivers that support
that. You'll need to record with IEC958_SUBFRAME_LE or
IEC958_SUBFRAME_BE sample formats.
> * Maybe this sort of status is only available to the firmware of the
> interface and never makes it to userland (in my case, echo3g); though I
> can see some constants relating to 'non audio' S/PDIF.
Unfortunately the echo3g driver doesn't seem to support
IEC958_SUBFRAME_* sample formats.
The HDA driver, used for most mainboard/laptop integrated audio, does
support that format if the hardware is capable. I'm not sure if the
hardware commonly supports that format or not, though.
> The hardware I have here is Echo Layla 3G (snd-echo3g) and a Pioneer
> MJ-D707 MiniDisc recorder.
>
> Any advice appreciated -- many thanks.
>
--
Anssi Hannula
next prev parent reply other threads:[~2016-06-17 17:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-17 13:29 S/PDIF and track markers (echo3g) Mark Hills
2016-06-17 17:43 ` Anssi Hannula [this message]
2016-06-24 8:55 ` Mark Hills
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=576436BA.4090104@iki.fi \
--to=anssi.hannula@iki.fi \
--cc=alsa-devel@alsa-project.org \
--cc=mark@xwax.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.