Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Shane Warren <shanew@innovsys.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] Live Transcoding: SCTE35 passthrough
Date: Wed, 20 Jul 2022 15:52:47 +0000
Message-ID: <DM6PR13MB3954B8270FA773244C16C843BA8E9@DM6PR13MB3954.namprd13.prod.outlook.com> (raw)
In-Reply-To: <CAHGibzF1jQyixmDtD-ciUjYtdX6PryTftM-6ZX-UDh5V=HANyg@mail.gmail.com>

Thanks, I hand patched that back into a newer ffmpeg and with a few changes it worked great.

-----Original Message-----
From: ffmpeg-devel <ffmpeg-devel-bounces@ffmpeg.org> On Behalf Of Devin Heitmueller
Sent: Tuesday, July 19, 2022 11:40 AM
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] Live Transcoding: SCTE35 passthrough


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://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FLTNGlobal-opensource%2FFFmpeg-ltn%2Fcommits%2Fn4.3.1-scte35&amp;data=05%7C01%7Cshanew%40innovsys.com%7C2fb835f6c03d4bf4ea9e08da69a564d0%7C7a48ce45ee974a95ac183390878a179b%7C0%7C0%7C637938456345483120%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&amp;sdata=SJJDcJrCY3rHXNn9tzpQ3M5bj6Ey%2BUIepSIOYAZU49M%3D&amp;reserved=0

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://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fltnglobal.com%2F&amp;data=05%7C01%7Cshanew%40innovsys.com%7C2fb835f6c03d4bf4ea9e08da69a564d0%7C7a48ce45ee974a95ac183390878a179b%7C0%7C0%7C637938456345483120%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&amp;sdata=1HYGR80ix2UDxPFGDPiuqE3EM%2Ba%2FDlvevbSy1IW2etU%3D&amp;reserved=0  e: devin.heitmueller@ltnglobal.com _______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fffmpeg.org%2Fmailman%2Flistinfo%2Fffmpeg-devel&amp;data=05%7C01%7Cshanew%40innovsys.com%7C2fb835f6c03d4bf4ea9e08da69a564d0%7C7a48ce45ee974a95ac183390878a179b%7C0%7C0%7C637938456345483120%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&amp;sdata=k6cbuARZH%2FtGrweYhtHuypy5TCyW%2BCDIq%2Fhftl3YxTE%3D&amp;reserved=0

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

      reply	other threads:[~2022-07-20 15:53 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
2022-07-20 15:52   ` Shane Warren [this message]

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=DM6PR13MB3954B8270FA773244C16C843BA8E9@DM6PR13MB3954.namprd13.prod.outlook.com \
    --to=shanew@innovsys.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