From: Marton Balint <cus@passwd.hu>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH v2] avformat/mpegts: set data broadcast streams as such
Date: Tue, 19 Apr 2022 02:00:39 +0200 (CEST)
Message-ID: <a819ae7-c93a-8d9a-37b6-c52a4c8234@passwd.hu> (raw)
In-Reply-To: <CAEu79Sb+eW2WhQhm4kEu7aBYyr-hH2zEh1h2HFtDGv=uzYZ=ew@mail.gmail.com>
On Thu, 14 Apr 2022, Jan Ekström wrote:
> On Mon, Apr 11, 2022 at 1:50 PM Jan Ekström <jeebjp@gmail.com> wrote:
>>
>> From: Jan Ekström <jan.ekstrom@24i.com>
>>
>> Additionally, they should not be probed, as this is essentially
>> various types of binary data.
>>
>> Signed-off-by: Jan Ekström <jan.ekstrom@24i.com>
>> ---
>
> Ping.
>
> Basically this checks if we have an unknown stream with a private
> stream type still at the end of the per-stream loop in PMT parsing,
> and then cancels the stop of parsing that usually occurs as a PMT is
> hit. Instead the logic will continue parsing further. When an SDT is
> then found and a PMT for that program has already been received, it
> will then stop header reading at that point.
But why does it matter when the initial parsing is stopped? I mean it
stops at the first PMT right now, nobody expects it to find all the
programs and all the streams or all the stream codecs/parameters.
I am saying, that ideally, the ts->stop_parse magic should not be needed
to be changed to fix your issue and when an SDT is detected with the
broadcast descriptor that should stop any existing data stream parsing. Do
you know why it does not work like that?
Thanks,
Marton
_______________________________________________
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-04-19 0:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-11 10:50 Jan Ekström
2022-04-11 13:31 ` Jan Ekström
2022-04-14 6:59 ` Jan Ekström
2022-04-19 0:00 ` Marton Balint [this message]
2022-04-19 10:13 ` Jan Ekström
2022-04-19 14:08 ` Jan Ekström
2022-04-19 20:06 ` Marton Balint
2022-04-25 10:36 ` Jan Ekström
2022-04-25 11:33 ` Jan Ekström
2022-04-25 12:19 ` Jan Ekström
2022-04-25 14:45 ` Jan Ekström
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=a819ae7-c93a-8d9a-37b6-c52a4c8234@passwd.hu \
--to=cus@passwd.hu \
--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