From: Pierre Le Fevre via ffmpeg-devel <ffmpeg-devel@ffmpeg.org>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Cc: Pierre Le Fevre <pierre.lefevre@netinsight.net>
Subject: Re: [FFmpeg-devel] [PATCH] avformat/mpegts: Passthrough SCTE 35 Current behavior breaks SCTE 35 by wrapping it in a PES packet, this adds the logic for the SCTE 35 messages to be passed through cleanly.
Date: Thu, 12 Jun 2025 08:48:09 +0000
Message-ID: <mailman.2992.1749718115.1384.ffmpeg-devel@ffmpeg.org> (raw)
In-Reply-To: <CAHGibzEDrkfnuvLgM7ANFd=1xnpuZuV1DHK4pgQ5a9TuT1NzyA@mail.gmail.com>
[-- Attachment #1: Type: message/rfc822, Size: 13521 bytes --]
From: Pierre Le Fevre <pierre.lefevre@netinsight.net>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH] avformat/mpegts: Passthrough SCTE 35 Current behavior breaks SCTE 35 by wrapping it in a PES packet, this adds the logic for the SCTE 35 messages to be passed through cleanly.
Date: Thu, 12 Jun 2025 08:48:09 +0000
Message-ID: <LV3PR17MB719007FA1AFE183A897C8C8AEE74A@LV3PR17MB7190.namprd17.prod.outlook.com>
Hi Devin,
I saw your patch but noticed it was still not merged. Since it’s more comprehensive, I’m all for merging your patch instead of mine if it’s not too stale.
Best,
Pierre
From: ffmpeg-devel <ffmpeg-devel-bounces@ffmpeg.org> on behalf of Devin Heitmueller <devin.heitmueller@ltnglobal.com>
Date: Wednesday, 11 June 2025 at 16:32
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Cc: Pierre Le Fevre <pierre.lefevre@netinsight.net>
Subject: Re: [FFmpeg-devel] [PATCH] avformat/mpegts: Passthrough SCTE 35 Current behavior breaks SCTE 35 by wrapping it in a PES packet, this adds the logic for the SCTE 35 messages to be passed through cleanly.
*EXTERNAL EMAIL*- Use caution before opening links or attachments
Hello Pierre,
On Wed, Jun 11, 2025 at 10:22 AM Pierre Le Fevre via ffmpeg-devel
<ffmpeg-devel@ffmpeg.org> wrote:
> ---------- Forwarded message ----------
> From: Pierre Le Fevre <pierre.lefevre@netinsight.net>
> To: "ffmpeg-devel@ffmpeg.org" <ffmpeg-devel@ffmpeg.org>
> Cc:
> Bcc:
> Date: Wed, 11 Jun 2025 14:22:29 +0000
> Subject: [PATCH] avformat/mpegts: Passthrough SCTE 35 Current behavior breaks SCTE 35 by wrapping it in a PES packet, this adds the logic for the SCTE 35 messages to be passed through cleanly.
> Signed-off-by: Pierre Le Fevre <pierre.lefevre@netinsight.net>
For what it's worth, I submitted a similar patch series a couple of
years ago, which also accommodates modifying the pts_adjust field
(which is mandatory if the output stream's clocks are rebased).
https://ffmpeg.org/pipermail/ffmpeg-devel/2023-July/312417.html
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".
[-- Attachment #2: Type: text/plain, Size: 251 bytes --]
_______________________________________________
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:[~2025-06-12 8:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <LV3PR17MB7190A80B93AB754BB240F92EEE75A@LV3PR17MB7190.namprd17.prod.outlook.com>
[not found] ` <LV3PR17MB719082A865D4524B4A6CB9D6EE75A@LV3PR17MB7190.namprd17.prod.outlook.com>
2025-06-11 14:22 ` Pierre Le Fevre via ffmpeg-devel
2025-06-11 14:31 ` Devin Heitmueller
2025-06-12 8:48 ` Pierre Le Fevre via ffmpeg-devel [this message]
2025-07-03 18:57 ` Gregor Fuis
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=mailman.2992.1749718115.1384.ffmpeg-devel@ffmpeg.org \
--to=ffmpeg-devel@ffmpeg.org \
--cc=pierre.lefevre@netinsight.net \
/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