From: Paul B Mahol <onemda@gmail.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH v3 1/2] avformat/avcodec: Add DTS-UHD demuxer and parser, movenc support.
Date: Tue, 13 Jun 2023 20:09:34 +0200
Message-ID: <CAPYw7P4RKYY6eaVVyDcqNY958Oo4YJ_FRa=7wfmKGj1fWxO8bA@mail.gmail.com> (raw)
In-Reply-To: <bc1b7b39-dec0-573e-cb32-115a61259902@funderburk.us>
On Tue, Jun 13, 2023 at 7:43 PM Roy Funderburk <royffmpeg@funderburk.us>
wrote:
>
>
> On 6/13/23 7:26 AM, Paul B Mahol wrote:
> > Why we need new av_* calls, can you elaborate logic behind such approach
> to
> > implement parser?
>
>
> There is common code for dtsuhd audio frame parsing (dtsuhd_common.c) used
> by the libavcodec and libavformat DTS-UHD modules. It is complex enough
> that we do not want to duplicate it.
>
Parser just splits bitstream into packets and packets are then passed to
decoders. Demuxer in such case pass fixed packet sizes to parser minus
optional header/trailer bytes.
There should be no reason for such complexity in parser and/or demuxer if
there are in bitstream valid markers for start/end of packet that is given
to decoder.
Unless this format uses packets that may be not byte aligned than and/or
markers are useless and/or there are no size info of each packet feed to
decoder in such case and only in such case current complexity is valid.
>
> If you refer to the naming of av_*, would changing the names to
> ff_dtsuhd_* as in libavcodec/aac_ac3_parser.c be more appropriate?
>
That is purely for visuals, and not relevant in discussing issues.
>
> Thanks,
> -Roy
>
> _______________________________________________
> 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".
>
_______________________________________________
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:[~2023-06-13 18:10 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-14 15:39 [FFmpeg-devel] [PATCH] " Roy Funderburk
2023-04-14 16:40 ` Hendrik Leppkes
2023-04-14 16:48 ` Roy Funderburk
2023-04-15 14:56 ` Michael Niedermayer
2023-04-15 20:04 ` [FFmpeg-devel] [PATCH v2] " Roy Funderburk
2023-04-16 19:55 ` Michael Niedermayer
2023-04-16 21:52 ` Roy Funderburk
2023-04-17 4:12 ` [FFmpeg-devel] [PATCH v3 1/2] " Roy Funderburk
2023-05-08 17:49 ` Roy Funderburk
2023-05-13 7:28 ` Paul B Mahol
2023-05-15 14:50 ` Roy Funderburk
2023-05-15 20:35 ` Michael Niedermayer
2023-05-15 21:14 ` Roy Funderburk
2023-06-13 14:26 ` Paul B Mahol
2023-06-13 17:43 ` Roy Funderburk
2023-06-13 18:09 ` Paul B Mahol [this message]
2023-06-13 18:20 ` Roy Funderburk
2023-06-13 19:04 ` Anton Khirnov
2023-04-17 4:13 ` [FFmpeg-devel] [PATCH v3 2/2] " Roy Funderburk
2023-06-13 18:32 ` Paul B Mahol
2023-04-15 20:20 ` [FFmpeg-devel] [PATCH] " Roy Funderburk
2023-06-13 18:35 ` Paul B Mahol
2023-06-14 0:00 ` Roy Funderburk
2023-06-14 5:37 ` Paul B Mahol
2023-06-14 6:01 ` Paul B Mahol
2023-06-14 6:06 ` Paul B Mahol
2023-06-14 6:11 ` Paul B Mahol
2023-06-14 18:24 ` Roy Funderburk
2023-06-14 20:01 ` Roy Funderburk
2023-06-15 15:46 ` Paul B Mahol
2023-06-15 18:44 ` Roy Funderburk
2023-06-18 12:18 ` Paul B Mahol
2023-06-20 17:05 ` Roy Funderburk
2023-08-17 21:47 ` Roy Funderburk
2023-08-17 22:31 ` Paul B Mahol
2023-08-17 22:51 ` Roy Funderburk
2024-01-16 21:02 ` Roy Funderburk
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='CAPYw7P4RKYY6eaVVyDcqNY958Oo4YJ_FRa=7wfmKGj1fWxO8bA@mail.gmail.com' \
--to=onemda@gmail.com \
--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