From: Devin Heitmueller <devin.heitmueller@ltnglobal.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] Live Transcoding: SCTE35 passthrough
Date: Tue, 19 Jul 2022 12:40:04 -0400
Message-ID: <CAHGibzF1jQyixmDtD-ciUjYtdX6PryTftM-6ZX-UDh5V=HANyg@mail.gmail.com> (raw)
In-Reply-To: <DM6PR13MB395448B9C1BDF98ABA986433BA8F9@DM6PR13MB3954.namprd13.prod.outlook.com>
On Tue, Jul 19, 2022 at 9:44 AM Shane Warren <shanew@innovsys.com> wrote:
>
> I have been working on getting scte35 pass through working in FFmpeg. I have the SIT pid being passed through fine, but I need to adjust the pts_adjustment field since I'm doing a live transcode and using vsync 1.
>
> I'm struggling with finding how to match up an incoming frame of video to a transcoded frame of video so I can figure out the pts adjustment. Am I missing something, or is there some way to match up an incoming frame to a encoded frame and figure out their pts difference?
I've got this working in a branch that isn't upstream. This includes
a BSF which deals with the pts_adjust field. It should do what you
need (although the branch point is a bit stale):
https://github.com/LTNGlobal-opensource/FFmpeg-ltn/commits/n4.3.1-scte35
If you're comfortable recompiling from source, you can incorporate a
variant of these patches into your local tree.
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".
next prev parent reply other threads:[~2022-07-19 16:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-19 13:43 Shane Warren
2022-07-19 16:40 ` Devin Heitmueller [this message]
2022-07-20 15:52 ` Shane Warren
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='CAHGibzF1jQyixmDtD-ciUjYtdX6PryTftM-6ZX-UDh5V=HANyg@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