Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Miguel Borges de Freitas <enen92@kodi.tv>
To: ffmpeg-devel@ffmpeg.org
Subject: [FFmpeg-devel] Late SEI is not implemented (providing a sample)
Date: Thu, 29 Dec 2022 15:47:39 +0000
Message-ID: <CANdwpqzv-5p5tcbnVH4uUd90g=4Ht8ogMbcdFpoB6SncbfvwsQ@mail.gmail.com> (raw)

Dear all,

While updating Kodi to use the ffmpeg provided A53 side data for
closed captions instead of our custom (old) demuxer (c.f.
https://github.com/xbmc/xbmc/pull/22333) and running it against a
battery of test samples I've found the following messages in the log
for one particular sample:

[ffmpeg/video] h264: Late SEI is not implemented. Update your FFmpeg
version to the newest one from Git. If the problem still occurs, it
means that your file has a feature which has not been implemented.
[ffmpeg/video] h264: If you want to help, upload a sample of this file
to https://streams.videolan.org/upload/ and contact the ffmpeg-devel
mailing list. (ffmpeg-devel@ffmpeg.org)

This happens with ffmpeg version 5.1.2 and current master.
To reproduce the problem you can simply open it with ffplay:

ffplay https://livesim.dashif.org/dash/vod/testpic_2s/cea608.mpd

The sample in question has two closed caption streams, although in
ffmpeg none is detected/demuxed (a53 side data is empty). You can
validate the proper behavior using dash.js for example:

https://players.akamai.com/players/dashjs?streamUrl=https%3A%2F%2Flivesim.dashif.org%2Fdash%2Fvod%2Ftestpic_2s%2Fcea608.mpd

Hope you find this helpful,

Best regards,

Miguel
_______________________________________________
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-12-29 15:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-29 15:47 Miguel Borges de Freitas [this message]
2023-01-15 15:42 Miguel Borges de Freitas

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='CANdwpqzv-5p5tcbnVH4uUd90g=4Ht8ogMbcdFpoB6SncbfvwsQ@mail.gmail.com' \
    --to=enen92@kodi.tv \
    --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