From: Kieran Kunhya <kierank@obe.tv>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] FFmpeg TC input needed
Date: Sat, 17 Feb 2024 15:59:03 +0000
Message-ID: <CAK+ULv4rVLqXd6r23uQyHKt5znzS2cibWL-5EbZSFib0pn2o+w@mail.gmail.com> (raw)
In-Reply-To: <153dfd89-aedd-4704-aef4-15cca7cc541d@gyani.pro>
On Sat, 17 Feb 2024 at 13:16, Gyan Doshi <ffmpeg@gyani.pro> wrote:
> > Whilst s302m multiple substreams I haven't seen, Dolby E streams
> internally
> > contain multiple programs, often 5.1 and a 2.0 downmix.
>
> That is downstream of the Dolby-E decoder and user will have to use a
> filter like channelsplit to bifurcate
> those channels irrespective of where the s302m code resides.
>
The point is there are several layers of streams that also can change
dynamically.
> > There is a 3x3 matrix of flavours between coded Dolby E and the carriage
> > PCM (16-bit, 20-bit, 24-bit).
>
> Have you seen a larger non-PCM word size inside a smaller AES3 word?
>
Actually I think that case won't work in the real world, true as the LSBs
will be truncated, not passed along.
Kieran
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".
next prev parent reply other threads:[~2024-02-17 15:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-17 11:45 Gyan Doshi
2024-02-17 12:01 ` Kieran Kunhya
2024-02-17 13:15 ` Gyan Doshi
2024-02-17 13:42 ` Niklas Haas
2024-02-17 15:09 ` Gyan Doshi
2024-02-17 15:59 ` Kieran Kunhya [this message]
2024-02-17 17:31 ` Michael Niedermayer
2024-04-02 5:25 ` Gyan Doshi
2024-04-08 13:12 ` Gyan Doshi
2024-04-08 14:16 ` Paul B Mahol
2024-04-12 10:29 ` [FFmpeg-devel] [TC] Technical decision on S302M non-PCM decoding Niklas Haas
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=CAK+ULv4rVLqXd6r23uQyHKt5znzS2cibWL-5EbZSFib0pn2o+w@mail.gmail.com \
--to=kierank@obe.tv \
--cc=ffmpeg-devel@ffmpeg.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
Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
This inbox may be cloned and mirrored by anyone:
git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git
# If you have public-inbox 1.1+ installed, you may
# initialize and index your mirror using the following commands:
public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \
ffmpegdev@gitmailbox.com
public-inbox-index ffmpegdev
Example config snippet for mirrors.
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git