From: Eran Kornblau <eran.kornblau@kaltura.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: [FFmpeg-devel] Playback issue on Sony TVs caused by btrt box
Date: Mon, 21 Feb 2022 15:06:52 +0000
Message-ID: <AS8PR04MB8913462A8D369133493B45C6F53A9@AS8PR04MB8913.eurprd04.prod.outlook.com> (raw)
Hi all,
We've recently upgraded our ffmpeg version, and we got a playback issue on some Sony TV models that are playing HBBTV/DASH+DRM - video plays fine, audio doesn't play at all.
Listing here some of the affected models (not pasting all, the list is long...) - KDL-32W600D, KDL-40W650D, KDL-48W650D, KDL-43W750D, KDL-49W750D, KDL-55W650D.
After some investigation, we found the cause was the addition of the 'btrt' atom to the mp4 –
https://github.com/FFmpeg/FFmpeg/commit/3838e8fc210aa09a9f9058506c0ce80b6ad9b9c3
The TV decoder expects to get the sinf atom right after esds, and doesn't properly handle the btrt atom in between
(our packager adds the sinf atom at the end of the original stsd entry that was read from the mp4 file).
Since, in my understanding, the btrt atom was added mostly for reporting reasons, IMHO, it should be a config option - off by default.
I would happily submit a patch for it, but sending this first, in case there are any concerns/objections.
Thank you!
Eran
_______________________________________________
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 reply other threads:[~2022-02-21 15:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-21 15:06 Eran Kornblau [this message]
2022-02-21 18:16 ` Jan Ekström
2022-02-21 20:40 ` Eran Kornblau
2022-02-22 7:54 ` Marton Balint
2022-02-22 11:16 ` Jan Ekström
2022-02-22 12:06 ` Eran Kornblau
2022-03-06 9:40 ` Eran Kornblau
2022-03-21 9:10 ` Eran Kornblau
2022-03-28 5:39 ` Eran Kornblau
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=AS8PR04MB8913462A8D369133493B45C6F53A9@AS8PR04MB8913.eurprd04.prod.outlook.com \
--to=eran.kornblau@kaltura.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