Issue 387604 in chromium: DASH: H.264 Main Profile Video Codec and HE-AAC Audio Codec are not Supported Anymore in Canary Build

[chro...@googlecode.com]

Status: Unconfirmed
Owner: ----
Labels: Type-Bug Cr-Internals-Media Pri-2

New issue 387604 by MalekElk...@gmail.com: DASH: H.264 Main Profile Video
Codec and HE-AAC Audio Codec are not Supported Anymore in Canary Build
http://code.google.com/p/chromium/issues/detail?id=387604

Chrome Version : 38.0.2064.0 (Official Build 279010) canary

URLs (if applicable) :
http://dashif.org/reference/players/javascript/1.1.2/index.html?mpd=http://dash.edgesuite.net/dash264/TestCases/2b/qualcomm/1/MultiResMPEG2.mpd

OS version : Windows 7

Video Format : mimeType="video/mp4" codecs="avc1.4d401f"
Audio Format : mimeType="audio/mp4" codecs="mp4a.40.29"

Behavior in Safari (if known): Unknown
Behavior in Firefox (if known): HTML5 MSE is not supported

Video issue, Audio issue, both, neither? Both

Flash or HTML5? HTML5

What steps will reproduce the problem?
1. Load the above URL in the browser (i.e.
http://dashif.org/reference/players/javascript/1.1.2/index.html?mpd=http://dash.edgesuite.net/dash264/TestCases/2b/qualcomm/1/MultiResMPEG2.mpd)

What is the expected result?
Dynamic-and-Adaptive-Streaming-over-HTTP (DASH) segments are loaded into
the player which starts rendering video content. Audio content is not
played due to codec defined in MPD (i.e. mp4a.40.29). If this is manually
modified in MPD to mp4a.40.5, audio content is played. This is a known
issue.

What is the actual result?
Media content is not played. In the javascript console, it is indicated
that "Video Codec (video/mp4;codecs="avc1.4d401f") is not supported"
and "Audio Codec (audio/mp4;codecs="mp4a.40.29") is not supported". I
should note that the content was playing as expected in older canary builds.

Any additional information (anything else which may help us debug the
issue)?
If the URL above is loaded into Chrome version "35.0.1916.153 (Official
Build 274914) m", the content is being played as expected and the above
console messages do not appear.

The content is DASH content and is composed of multiple segments. The Media
Presentation Description (MPD) and the initialization segments could be
found under:

http://dash.edgesuite.net/dash264/TestCases/2b/qualcomm/1/MultiResMPEG2.mpd

http://dash.edgesuite.net/dash264/TestCases/2b/qualcomm/1/ED_MPEG2_32k_init.mp4

http://dash.edgesuite.net/dash264/TestCases/2b/qualcomm/1/ED_1280_4M_MPEG2_video_init.mp4

http://dash.edgesuite.net/dash264/TestCases/2b/qualcomm/1/ED_768_1440K_MPEG2_video_init.mp4

http://dash.edgesuite.net/dash264/TestCases/2b/qualcomm/1/ED_512_640K_MPEG2_video_init.mp4

--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

[chro...@googlecode.com]

Comment #4 on issue 387604 by amogh.bi...@samsung.com: DASH: H.264 Main

Profile Video Codec and HE-AAC Audio Codec are not Supported Anymore in
Canary Build
http://code.google.com/p/chromium/issues/detail?id=387604

I guess r278670 won't need to be reverted as only new tests for codecs with
profile parameter were added in the CL. Those parameters will anyways be
stripped away as mp4 containers would no longer be in strict mime type
list[1](line 435-436). Also the tests treat probably and maybe equally[2].
However, if there are merge conflicts then please revert it.

------
[1]
http://src.chromium.org/viewvc/chrome/trunk/src/content/renderer/renderer_webkitplatformsupport_impl.cc?annotate=277039
[1]
https://code.google.com/p/chromium/codesearch#chromium/src/chrome/browser/media/encrypted_media_istypesupported_browsertest.cc&q=istypesupported&l=286

[chro...@googlecode.com]

Comment #5 on issue 387604 by amin...@chromium.org: DASH: H.264 Main

Profile Video Codec and HE-AAC Audio Codec are not Supported Anymore in
Canary Build
http://code.google.com/p/chromium/issues/detail?id=387604

Is this a safe revert that will take us back to M36 state?

[chro...@googlecode.com]

Comment #6 on issue 387604 by acolw...@chromium.org: DASH: H.264 Main

Profile Video Codec and HE-AAC Audio Codec are not Supported Anymore in
Canary Build
http://code.google.com/p/chromium/issues/detail?id=387604

amineer@: yes it is safe and will restore the old behavior.

[chro...@googlecode.com]

Updates:
Labels: -Merge-Requested Merge-Approved

Comment #7 on issue 387604 by amin...@chromium.org: DASH: H.264 Main

Profile Video Codec and HE-AAC Audio Codec are not Supported Anymore in
Canary Build
http://code.google.com/p/chromium/issues/detail?id=387604

Merge approved for M37 branch 2062.

[chro...@googlecode.com]

Updates:
Labels: -Merge-Approved merge-merged-2062

Comment #9 on issue 387604 by bugdro...@chromium.org: DASH: H.264 Main

Profile Video Codec and HE-AAC Audio Codec are not Supported Anymore in
Canary Build

http://code.google.com/p/chromium/issues/detail?id=387604#c9

The following revision refers to this bug:

https://chromium.googlesource.com/chromium/src.git/+/100a0f976d7d41e7aea9fec6942177a1bdd10f0e

commit 100a0f976d7d41e7aea9fec6942177a1bdd10f0e
Author: acol...@chromium.org
<acol...@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>
Date: Mon Jul 14 16:43:15 2014

Revert 277386 "Fix: Adding list of supported codecs for MP4 cont..."

Restoring M36 behavior for M37

BUG=387604

> Fix: Adding list of supported codecs for MP4 containers

> A table is added for MP4 mime types and their corresponding containers
> H.264 codecs vary according to the profile version. These are
> represented by hexadecimal numbers (RFC6381). These vary across
> platforms, hence a definite "probably" cannot be given for canPlayType
> query. The best we can say is a "maybe" if the codec is RFC compliant.

> New behaviour of the browser will be
> audio/mp4 -> avc1/ avc1./ avc1.4D4001 = ""
> audio/mp4 -> mp4a/ mp4a.40/ mp4a.40.2 = "maybe"
> audio/mp4 -> mp4a./ mp4a.50/ mp4a.40. = ""

> video/mp4 -> avc1/avc1.4D4001/ = "maybe"
> video/mp4 -> avc1./ avc1.NonHexDigits = ""
> (similar for mp4a and avc3)

> BUG=53193
> TEST=out/Release/content_browsertests --gtest_filter=MediaCanPlayType*

> Review URL: https://codereview.chromium.org/254983006

TBR=amogh....@samsung.com

Review URL: https://codereview.chromium.org/389383002

git-svn-id: svn://svn.chromium.org/chrome/branches/2062/src@282963
0039d316-1c4b-4281-b951-d872f2087c98

[chro...@googlecode.com]

Comment #10 on issue 387604 by bugdro...@chromium.org: DASH: H.264 Main

Profile Video Codec and HE-AAC Audio Codec are not Supported Anymore in
Canary Build

http://code.google.com/p/chromium/issues/detail?id=387604#c10

------------------------------------------------------------------
r282963 | acol...@chromium.org | 2014-07-14T16:43:15.118845Z

Changed paths:
M
http://src.chromium.org/viewvc/chrome/branches/2062/src/chrome/browser/media/encrypted_media_istypesupported_browsertest.cc?r1=282963&r2=282962&pathrev=282963
M
http://src.chromium.org/viewvc/chrome/branches/2062/src/net/base/mime_util_unittest.cc?r1=282963&r2=282962&pathrev=282963
M
http://src.chromium.org/viewvc/chrome/branches/2062/src/net/base/mime_util.cc?r1=282963&r2=282962&pathrev=282963
M
http://src.chromium.org/viewvc/chrome/branches/2062/src/net/base/mime_util.h?r1=282963&r2=282962&pathrev=282963
M
http://src.chromium.org/viewvc/chrome/branches/2062/src/content/browser/media/media_canplaytype_browsertest.cc?r1=282963&r2=282962&pathrev=282963
M
http://src.chromium.org/viewvc/chrome/branches/2062/src/content/renderer/renderer_webkitplatformsupport_impl.cc?r1=282963&r2=282962&pathrev=282963
M
http://src.chromium.org/viewvc/chrome/branches/2062/src/content/child/assert_matching_enums.cc?r1=282963&r2=282962&pathrev=282963

Revert 277386 "Fix: Adding list of supported codecs for MP4 cont..."

Restoring M36 behavior for M37

BUG=387604

> Fix: Adding list of supported codecs for MP4 containers

> A table is added for MP4 mime types and their corresponding containers
> H.264 codecs vary according to the profile version. These are
> represented by hexadecimal numbers (RFC6381). These vary across
> platforms, hence a definite "probably" cannot be given for canPlayType
> query. The best we can say is a "maybe" if the codec is RFC compliant.

> New behaviour of the browser will be
> audio/mp4 -> avc1/ avc1./ avc1.4D4001 = ""
> audio/mp4 -> mp4a/ mp4a.40/ mp4a.40.2 = "maybe"
> audio/mp4 -> mp4a./ mp4a.50/ mp4a.40. = ""

> video/mp4 -> avc1/avc1.4D4001/ = "maybe"
> video/mp4 -> avc1./ avc1.NonHexDigits = ""
> (similar for mp4a and avc3)

> BUG=53193
> TEST=out/Release/content_browsertests --gtest_filter=MediaCanPlayType*

> Review URL: https://codereview.chromium.org/254983006

TBR=amogh....@samsung.com

Review URL: https://codereview.chromium.org/389383002

-----------------------------------------------------------------

[chro...@googlecode.com]

Updates:
Labels: -M-37 MovedFrom-37 M-38

Comment #11 on issue 387604 by amin...@google.com: DASH: H.264 Main Profile

Video Codec and HE-AAC Audio Codec are not Supported Anymore in Canary Build

https://code.google.com/p/chromium/issues/detail?id=387604#c11

Moving all non essential bugs to the next Milestone.

[chro...@googlecode.com]

Comment #12 on issue 387604 by mr.scott...@gmail.com: DASH: H.264 Main

Profile Video Codec and HE-AAC Audio Codec are not Supported Anymore in
Canary Build
https://code.google.com/p/chromium/issues/detail?id=387604

While this bug is being fixed it would be beneficial to add support for
high10, high422, and high444 profiles as well.

i.e.

avc1.f4000d
avc1.f4001f
avc1.f40032
avc1.f40033
avc1.f40034

Chrome plays high444 profile .mp4 files directly but doesn't support the
same codec in Dash segments.

[chro...@googlecode.com]

Updates:
Owner: wolen...@chromium.org
Cc: acolw...@chromium.org

Comment #13 on issue 387604 by wolen...@chromium.org: DASH: H.264 Main

Profile Video Codec and HE-AAC Audio Codec are not Supported Anymore in
Canary Build
https://code.google.com/p/chromium/issues/detail?id=387604

@#12, I'm not sure yet if Android decoders support all of those. WIll
investigate as part of this bug.

wrt OP, Adding avc1.40.29 is more straightforward, though will also need to
check Android support. In current M39, I still repro "Audio Codec
(audio/mp4;codecs="mp4a.40.29") is not supported.", but not the video codec
unsupported error.

[chro...@googlecode.com]

Updates:
Status: Fixed

Comment #16 on issue 387604 by wolen...@chromium.org: DASH: H.264 Main

Profile Video Codec and HE-AAC Audio Codec are not Supported Anymore in
Canary Build

https://code.google.com/p/chromium/issues/detail?id=387604

Issue 315566 fixed the mp4a.40.29 support.

This bug originally tracked the short-term regression fixed in ToT in
comment #8 and merged in #9.

I've filed issue 436714 to track follow-up on comment #12.