search

mitxp / HbbTV-Testsuite

Tests for HbbTV implementations
http://itv.mit-xperts.com/hbbtvtest/
131 stars 56 forks source link

How should be the track ID encoded in to the media tracks / media content components available for MPEG - DASH Media Presentation? #19

Closed sssqa123 closed 10 years ago

sssqa123 commented 10 years ago

As per ISO/IEC 14496 Part 12 : ISOBMFF , the track Identifier specified in track header box "trak" and track fragment header "tfhd" box should be same and unique to each track available in an ISO file.

Also as per ISO/IEC 23009 Part 1 , The track Identifier is same for all the representation of same content component type and unique to a media content component type( Audio / Video etc . . .) in an adaptation set.

But , Most of the mpeg dash non multiplexed sample streams available in internet also with MITXP has encoded same track Identifier in all media tracks ( Audio , video etc. . . ) available for a media presentation. Say track ID for all content component(Audio,Video...) encoded with a value equal to 1.

In this case, If a media player is supported with single mp4 demuxer means, it is not possible to demux the fragmented media sample from various track correctly for a media presentation.

My question is, Having same track identifier for all media content component type in a dash media presentation is MPEG DASH Standard ?

mitxp commented 10 years ago

Hi,

as the note on the DOLBY test page says: In case of questions regarding content, please contact hbbtv@dolby.com -- Unfortunately, the DASH content is not created by us, but from DOLBY. It's a lot better if you could sort out this with DOLBY directly.

Thanks (and sorry for not being able to help you out).

mitxp commented 10 years ago

Closing this issue. In case of problems with Dolby content, please contact hbbtv@dolby.com