Fixed
Status Update
No update yet.
Comments
va...@google.com
Labels: Needs-Triage-M126
cl...@electronjs.org
From testing, I've found this problem may be caused by the mp4 muxer (via the MediaRecorderEnableMp4Muxer feature flag, recently enabled in
The mp4 files produced are not usable by many other common media software, e.g. the built-in media players in Android (ExoPlayer), iOS (AVPlayer), and macOS (QuickTime), when this feature is enabled.
I've attached a 5-second video recorded on Chromium 126.0.6478.57 of my cat using the demo mentioned in #1, with the format set as video/mp4;codecs=avc1,mp4a.40.2. Chromium can play the video back, but QuickTime reports the video as unplayable.
Using ffprobe on the created video produces the following error that may give more context:
$ ffprobe test.mp4
[h264 @ 0xSNIP] sps_id 32 out of range
[h264 @ 0xSNIP] Invalid NAL unit size (1107304329 > 36197).
[h264 @ 0xSNIP] missing picture in access unit with size 36206
go...@google.com
Tried to reproduce this issue on reported chrome browser version #126.0.6478.127 using Mac 14.5 by following steps as per
Steps to reproduce
================
1. Launched Chrome
2. Navigated to the demo URL - "https://webrtc.github.io/samples/src/content/getusermedia/record/ "
3. Recorded a stream from a camera with the codec "video/mp4;codecs=avc1,mp4a.40.2" or "video/mp4"
4. Saved recording as .mp4 file
5. Opened saved file in QuickTime Player
6. Observed - Cannot be opened.
Attached screencast for reference
Reporter@: Could you please review the attached reference and let us know if anything being missed here.
Could we consider point 6 as a bad behaviour and issue you are pointing to?, otherwise please provide us with expected and actual results for better understanding of the issue.
**Note: Requesting you to copy-paste the entire content of chrome://version details to a .txt file format and attach it.
Thanks..!!
Steps to reproduce
================
1. Launched Chrome
2. Navigated to the demo URL - "
3. Recorded a stream from a camera with the codec "video/mp4;codecs=avc1,mp4a.40.2" or "video/mp4"
4. Saved recording as .mp4 file
5. Opened saved file in QuickTime Player
6. Observed - Cannot be opened.
Attached screencast for reference
Reporter@: Could you please review the attached reference and let us know if anything being missed here.
Could we consider point 6 as a bad behaviour and issue you are pointing to?, otherwise please provide us with expected and actual results for better understanding of the issue.
**Note: Requesting you to copy-paste the entire content of chrome://version details to a .txt file format and attach it.
Thanks..!!
be...@gmail.com
Yes, point 6 can be considered a problem.
It is expected that the recorded mp4 can be viewed in any browser that supports mp4, for example Safari, and can also be opened in any system player
It is expected that the recorded mp4 can be viewed in any browser that supports mp4, for example Safari, and can also be opened in any system player
pe...@google.com
Thank you for providing more feedback. Adding the requester to the CC list.
da...@chromium.org
su...@microsoft.com
dalecurtis@, I'm looking at this issue as high priority. so far, VeaEncoder causes many ffprobe failures like such as invalid nalsize; it is caused by AUD (9) NALU. When using software encoder, only single failure as it doesn't have AUID NALU. It's not clear though whether these ffprobe failure is root cause of the QuickPlayer issue. Planning to clean ffprobe first if possible.
da...@chromium.org
+Dan who can help out if you have corrupt samples.
su...@microsoft.com
It looks like the NALU start code needs to be replaced with size before stored, which is different from webm format, at least the change clean ffprobe validation, still not working on quick player yet.
ap...@google.com
Project: chromium/src
Branch: main
commit 0cf881aea158b882f1b0768ef25e61421b3187e5
Author: Sunggook Chue <sunggch@microsoft.com>
Date: Wed Jul 10 18:32:37 2024
Convert NALU start code with NAL size for MP4 container.
h264 encoders produced NALU data that started with started
code and WebM container expected it.
Meanwhile, many MP4 player expected that MP4 file has NAL
size instead of NALU start code.
The change converts incoming encoded data to the NAL size
replaced data before adding to the MP4 mdat box data.
Bug: 348923066
Change-Id: I3f5f27f2863efd241300776f140aa19145a6eaf3
Reviewed-on:https://chromium-review.googlesource.com/c/chromium/src/+/5677470
Reviewed-by: Rahul Singh <rahsin@microsoft.com>
Reviewed-by: Dan Sanders <sandersd@chromium.org>
Commit-Queue: Sunggook Chue <sunggch@microsoft.com>
Cr-Commit-Position: refs/heads/main@{#1325638}
M media/muxers/mp4_muxer_delegate.cc
M media/muxers/mp4_muxer_delegate.h
M media/muxers/mp4_muxer_delegate_fragment.cc
M media/muxers/mp4_muxer_delegate_fragment.h
M media/muxers/mp4_muxer_delegate_unittest.cc
https://chromium-review.googlesource.com/5677470
Branch: main
commit 0cf881aea158b882f1b0768ef25e61421b3187e5
Author: Sunggook Chue <sunggch@microsoft.com>
Date: Wed Jul 10 18:32:37 2024
Convert NALU start code with NAL size for MP4 container.
h264 encoders produced NALU data that started with started
code and WebM container expected it.
Meanwhile, many MP4 player expected that MP4 file has NAL
size instead of NALU start code.
The change converts incoming encoded data to the NAL size
replaced data before adding to the MP4 mdat box data.
Bug: 348923066
Change-Id: I3f5f27f2863efd241300776f140aa19145a6eaf3
Reviewed-on:
Reviewed-by: Rahul Singh <rahsin@microsoft.com>
Reviewed-by: Dan Sanders <sandersd@chromium.org>
Commit-Queue: Sunggook Chue <sunggch@microsoft.com>
Cr-Commit-Position: refs/heads/main@{#1325638}
M media/muxers/mp4_muxer_delegate.cc
M media/muxers/mp4_muxer_delegate.h
M media/muxers/mp4_muxer_delegate_fragment.cc
M media/muxers/mp4_muxer_delegate_fragment.h
M media/muxers/mp4_muxer_delegate_unittest.cc
su...@microsoft.com
ap...@google.com
Project: chromium/src
Branch: main
commit 8fd19c05188e3edea14b73fe622af46186f56b0e
Author: Sunggook Chue <sunggch@microsoft.com>
Date: Tue Jul 16 22:18:10 2024
Make quickPlayer/Safari runs MP4 file from Chromium MediaRecorder.
There are multiple changes here in order to compatible with
quick player.
1. Make default version as 0 with 1 (64bits) support only for the required boxes.
2. Add btrt box to the visual sample entry.
3. Fix small wrong formats in the tfra and tkhd boxes.
Bug: 348923066
Change-Id: Iac6fcb2cf3f2b4e870b9011573a4cf1b45ccd577
Reviewed-on:https://chromium-review.googlesource.com/c/chromium/src/+/5704282
Commit-Queue: Sunggook Chue <sunggch@microsoft.com>
Reviewed-by: Dale Curtis <dalecurtis@chromium.org>
Reviewed-by: Dan Sanders <sandersd@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1328476}
M media/formats/mp4/fourccs.h
M media/formats/mp4/writable_box_definitions.h
M media/muxers/box_byte_stream.h
M media/muxers/mp4_fragment_box_writer.cc
M media/muxers/mp4_movie_box_writer.cc
M media/muxers/mp4_muxer_delegate.cc
M media/muxers/mp4_muxer_delegate_fragment.cc
M media/muxers/mp4_muxer_delegate_fragment.h
M third_party/blink/renderer/modules/mediarecorder/media_recorder_handler_unittest.cc
https://chromium-review.googlesource.com/5704282
Branch: main
commit 8fd19c05188e3edea14b73fe622af46186f56b0e
Author: Sunggook Chue <sunggch@microsoft.com>
Date: Tue Jul 16 22:18:10 2024
Make quickPlayer/Safari runs MP4 file from Chromium MediaRecorder.
There are multiple changes here in order to compatible with
quick player.
1. Make default version as 0 with 1 (64bits) support only for the required boxes.
2. Add btrt box to the visual sample entry.
3. Fix small wrong formats in the tfra and tkhd boxes.
Bug: 348923066
Change-Id: Iac6fcb2cf3f2b4e870b9011573a4cf1b45ccd577
Reviewed-on:
Commit-Queue: Sunggook Chue <sunggch@microsoft.com>
Reviewed-by: Dale Curtis <dalecurtis@chromium.org>
Reviewed-by: Dan Sanders <sandersd@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1328476}
M media/formats/mp4/fourccs.h
M media/formats/mp4/writable_box_definitions.h
M media/muxers/box_byte_stream.h
M media/muxers/mp4_fragment_box_writer.cc
M media/muxers/mp4_movie_box_writer.cc
M media/muxers/mp4_muxer_delegate.cc
M media/muxers/mp4_muxer_delegate_fragment.cc
M media/muxers/mp4_muxer_delegate_fragment.h
M third_party/blink/renderer/modules/mediarecorder/media_recorder_handler_unittest.cc
su...@microsoft.com
ni...@gmail.com
Hi, thanks for the updates. Would this fix come with the next chrome release? I'm on version 126.0.6478.183 and the issue is still reproducible.
be...@gmail.com
There is no problem in Chrome Canary 128.0.6602.2, in stable chrome 126.0.6478.183 or chrome beta 127.0.6533.57 the problem is still there. Apparently, we need to wait for the next stable versions
ni...@gmail.com
Yep not reproducible in the canary build. I guess I'll wait for the next stable versions. Thanks!
he...@aneesiqbal.ai
Hey Team!
This was marked as fixed so sorry for reviving a dead issue, but I'm running into this with the current latest Chrome stable v131 with
users on both Windows & macOS. The MediaRecorder output is only playable in chrome and fails in QuickTime or ffmpeg, with the following logs
[h264 @ 0x129e05810] Unknown SAR index: 192.
[h264 @ 0x129e05810] Truncated VUI (-8)
[h264 @ 0x129e05810] Overread VUI by 8 bits
[h264 @ 0x129e05810] Invalid NAL unit size (1119887500 > 68351).
[h264 @ 0x129e05810] missing picture in access unit with size 68360
(repeated countless times)
The only reliable workaround for our usecase right now is to record in webm. Is what we're running into the same/similar bug that's resurfaced or
are we running into a unique bug?
Best Regards
This was marked as fixed so sorry for reviving a dead issue, but I'm running into this with the current latest Chrome stable v131 with
users on both Windows & macOS. The MediaRecorder output is only playable in chrome and fails in QuickTime or ffmpeg, with the following logs
[h264 @ 0x129e05810] Unknown SAR index: 192.
[h264 @ 0x129e05810] Truncated VUI (-8)
[h264 @ 0x129e05810] Overread VUI by 8 bits
[h264 @ 0x129e05810] Invalid NAL unit size (1119887500 > 68351).
[h264 @ 0x129e05810] missing picture in access unit with size 68360
(repeated countless times)
The only reliable workaround for our usecase right now is to record in webm. Is what we're running into the same/similar bug that's resurfaced or
are we running into a unique bug?
Best Regards
da...@chromium.org
Re:
I couldn't repro using 132.0.6834.83. We'll likely need at least a sample app that uses the same codec string you're using as well as chrome://gpu information to debug.
zh...@bytedance.com
I can’t reproduce this on M131 or M132 using macOS 12/14/15, the encoded H.264 video has no issue from my side.
Is there a screen recording or mp4 recorded sample that could reproduce the issue? Thanks
Is there a screen recording or mp4 recorded sample that could reproduce the issue? Thanks
Description
Steps to reproduce the problem
Problem Description
mp4 video recorded in Chrome 126 cannot be played by the system player or other browser. Only Chrome. It’s not clear what’s wrong and how it can be fixed. Do you need some specific configuration of the MediaRecorder or creation of a MediaStram with certain parameters?
Summary
mp4 video recorded in Chrome 126 cannot be played by the system player or other browser
Custom Questions
Which component does this fall under?
Not sure - I don't know
Does this work in other browsers?
Yes - This is just a Chrome problem
Additional Data
Category: API
Chrome Channel: Stable
Regression: N/A