From: Devin Heitmueller <devin.heitmueller@ltnglobal.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH v2 4/5] mpegtsenc: Don't periodically announce PCR on SCTE-35 streams
Date: Wed, 5 Jul 2023 11:29:10 -0400
Message-ID: <CAHGibzH_N6-tbf01xRveNd=mK9F7t4oPFoEWcm-PYPbmUieBow@mail.gmail.com> (raw)
In-Reply-To: <b98370f0-a7ef-d61-5c90-c9bcc2a16b75@passwd.hu>
Hi Marton,
On Mon, Jul 3, 2023 at 3:20 PM Marton Balint <cus@passwd.hu> wrote:
> Hmm, only one PID per service should generate PCR, and if there is a video
> stream in the service, then that is preferred for PCR generation. An SCTE
> stream should only get selected for PCR if there are no video streams in a
> service. Or are you seeing something else?
>
> And it is also strange that not sending PCR for any stream improves the
> PCR interval test, it should make it worse, because less PCRs are
> provided, no?
You make valid points. Admittedly this is a patch I wrote a couple of
years ago that has been ported to master, and it's entirely possible
that the description is incorrect. I definitely made the patch in
response to seeing that I was getting recurring PCR packets on the
SCTE-35 stream (which is contrary to SCTE-35's typical behavior where
you typically only get packets on the PID when there is an actual
trigger). Also, you generally don't have PCRs delivered on streams
that are composed only of sections (i.e. not containing PES packets),
although I haven't looked to see if that's technically illegal.
I will back out the patch and better document the behavior I am seeing
and update the patch description so it's more clear why it is needed.
Regards,
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:[~2023-07-05 15:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-03 18:15 [FFmpeg-devel] [PATCH v2 0/5] Add passthrough support for SCTE-35 Devin Heitmueller
2023-07-03 18:15 ` [FFmpeg-devel] [PATCH v2 1/5] avcodec: Add new side data type to contain original PTS value Devin Heitmueller
2023-07-03 18:15 ` [FFmpeg-devel] [PATCH v2 2/5] mpegts: Stash original PTS for SCTE-35 sections for processing later Devin Heitmueller
2023-07-03 18:15 ` [FFmpeg-devel] [PATCH v2 3/5] mpegtsenc: Add support for output of SCTE-35 streams over TS Devin Heitmueller
2023-07-03 18:15 ` [FFmpeg-devel] [PATCH v2 4/5] mpegtsenc: Don't periodically announce PCR on SCTE-35 streams Devin Heitmueller
2023-07-03 19:17 ` Marton Balint
2023-07-05 15:29 ` Devin Heitmueller [this message]
2023-07-03 18:15 ` [FFmpeg-devel] [PATCH v2 5/5] bsf: Add new bitstream filter to set pts_adjustment when reclocking Devin Heitmueller
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='CAHGibzH_N6-tbf01xRveNd=mK9F7t4oPFoEWcm-PYPbmUieBow@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