Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Kieran Kunhya <kierank@obe.tv>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Cc: Devin Heitmueller <dheitmueller@ltnglobal.com>
Subject: Re: [FFmpeg-devel] [PATCH v4 2/4] mpegts: Stash original PTS for SCTE-35 sections for processing later
Date: Wed, 9 Aug 2023 09:54:55 -0400
Message-ID: <CAK+ULv4DVtDJSpAChqVjWx7vRHEZ5nwfcSsiMkovzU9Xj9O5JQ@mail.gmail.com> (raw)
In-Reply-To: <1690810686-4723-3-git-send-email-dheitmueller@ltnglobal.com>

On Mon, 31 Jul 2023 at 09:38, Devin Heitmueller <
devin.heitmueller@ltnglobal.com> wrote:

> We need the original PTS value in order to do subsequent processing,
> so set it as packet side data.
>
> Signed-off-by: Devin Heitmueller <dheitmueller@ltnglobal.com>
> ---
>  libavformat/mpegts.c | 11 ++++++++++-
>  1 file changed, 10 insertions(+), 1 deletion(-)
>
> diff --git a/libavformat/mpegts.c b/libavformat/mpegts.c
> index 0b3edda..a1b2420 100644
> --- a/libavformat/mpegts.c
> +++ b/libavformat/mpegts.c
> @@ -1783,8 +1783,17 @@ static void scte_data_cb(MpegTSFilter *filter,
> const uint8_t *section,
>      prg = av_find_program_from_stream(ts->stream, NULL, idx);
>      if (prg && prg->pcr_pid != -1 && prg->discard != AVDISCARD_ALL) {
>          MpegTSFilter *f = ts->pids[prg->pcr_pid];
> -        if (f && f->last_pcr != -1)
> +        if (f && f->last_pcr != -1) {
> +            AVTransportTimestamp *transport_ts;
>              ts->pkt->pts = ts->pkt->dts = f->last_pcr/300;
> +            transport_ts = (AVTransportTimestamp *)
> av_packet_new_side_data(ts->pkt,
> +
>   AV_PKT_DATA_TRANSPORT_TIMESTAMP,
> +
>   sizeof(AVTransportTimestamp));
> +            if (transport_ts) {
> +                transport_ts->pts = ts->pkt->pts;
> +                transport_ts->time_base = av_make_q(1, 90000);
> +            }
> +        }
>      }
>      ts->stop_parse = 1;
>

How is this frame accurate? Surely "last_pcr" can be up to 100ms out. You
need to actually be interpolating the true value in order to be frame
accurate (not saying this is easy/doable in FFmpeg). But at the same time
inaccurate splices aren't great either.

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".

  reply	other threads:[~2023-08-09 13:55 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-31 13:38 [FFmpeg-devel] [PATCH v4 0/4] Add passthrough support for SCTE-35 Devin Heitmueller
2023-07-31 13:38 ` [FFmpeg-devel] [PATCH v4 1/4] avcodec: Add new side data type to contain original PTS value Devin Heitmueller
2023-07-31 13:38 ` [FFmpeg-devel] [PATCH v4 2/4] mpegts: Stash original PTS for SCTE-35 sections for processing later Devin Heitmueller
2023-08-09 13:54   ` Kieran Kunhya [this message]
2023-08-09 16:36     ` Devin Heitmueller
2023-08-10 12:12       ` Kieran Kunhya
2023-08-10 12:20         ` Devin Heitmueller
2023-08-10 12:41           ` Kieran Kunhya
2023-08-10 12:48             ` Kieran Kunhya
2023-08-10 12:58               ` Devin Heitmueller
2023-08-10 13:08                 ` Kieran Kunhya
2023-08-10 15:12                   ` Devin Heitmueller
2023-08-10 15:53                     ` Kieran Kunhya
2023-07-31 13:38 ` [FFmpeg-devel] [PATCH v4 3/4] mpegtsenc: Add support for output of SCTE-35 streams over TS Devin Heitmueller
2023-07-31 13:38 ` [FFmpeg-devel] [PATCH v4 4/4] bsf: Add new bitstream filter to set SCTE-35 pts_adjustment when reclocking Devin Heitmueller
2023-08-04 11:16 ` [FFmpeg-devel] [PATCH v4 0/4] Add passthrough support for SCTE-35 Devin Heitmueller
2023-08-08 14:31   ` Devin Heitmueller
2023-08-08 15:30     ` Dennis Mungai
2023-09-01  9:29       ` Dennis Mungai

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+ULv4DVtDJSpAChqVjWx7vRHEZ5nwfcSsiMkovzU9Xj9O5JQ@mail.gmail.com \
    --to=kierank@obe.tv \
    --cc=dheitmueller@ltnglobal.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