Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Devin Heitmueller <devin.heitmueller@ltnglobal.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: [FFmpeg-devel] RFC: Preserving original demux timestamps in AVPackets
Date: Fri, 3 Mar 2023 16:53:27 -0500
Message-ID: <CAHGibzGVaJ=t6N7Xup-_H4hQ8wKAwc8t80oNOXcLqdEOBgzhNw@mail.gmail.com> (raw)

Hello all,

I am working on some SCTE-35 stuff, which embeds PTS timestamps deep
within the section payload.  In order to pass through packets to an
MPEG-TS output, I need the original PTS value that was used when the
packet was received to calculate the correct offsets.

The way a typical ffmpeg-based application works is to read in the
packets, and then recalculate the pts/dts fields prior to output using
the existing fields.  This results in loss of the original values.

I need to stash the original PTS value somewhere within the AVPacket
so I can use it for subsequent calculations on the output side.  In my
private tree I have done this through a new AVPacket side data type
called "AV_PKT_DATA_ORIG_PTS", but it wasn't clear to me if such a
patch would be accepted upstream.  Alternatively, I can set a metadata
field on the packet using av_packet_pack_dictionary() and use the
existing AV_PKT_DATA_STRINGS_METADATA type.  However that would
require it to be converted to a string and back, and seems less than
ideal.

Does anyone have any other suggestions on a way the original received
PTS value can be stashed within an AVPacket in a manner that would be
accepted upstream?

Thanks,

Devin

-- 
Devin Heitmueller, Senior Software Engineer
LTN Global Communications
o: +1 (301) 363-1001
w: https://ltnglobal.com  e: devin.heitmueller@ltnglobal.com
_______________________________________________
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-03-03 21:53 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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='CAHGibzGVaJ=t6N7Xup-_H4hQ8wKAwc8t80oNOXcLqdEOBgzhNw@mail.gmail.com' \
    --to=devin.heitmueller@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