Menu

#327 MP4Box DASH generation with H.265 Content Conformance Issues

v1.0 (example)
open
nobody
5
2015-02-17
2014-08-20
No

Dear all,

I have generated DASH content with MP4Box based on H.265 video (x265 in FFmpeg).
MP4Box - GPAC version 0.5.1-DEV-rev5322 is being used, running on Windows 7 32 bits.

The conformance test of the video representations obtained gave the following issues:

Section 6.3.4.3. of ISO/IEC 23009-1:2012(E): If 'sidx' is present in a Media Segment, the first 'sidx' box shall document the entire Segment. Violated for Media Segment 1. Segment duration 596.333333, Sidx documents 597.208333 for track 1, diff 0.875000.

Referenced moof earliest_presentation_time 10.291667 does not match to reference EPT 10.416667 for sidx number 1 at reference count 1.

SAP found with presentation time 12.000000 lesser than the declared SAP time 12.125000 (SAP_delta_time 0.000000), for sidx number 1 at reference count 2; first SAP shall be signalled as per Section 8.16.3.3 of ISO/IEC 14496-12 4th edition.

starts_with_SAP declared but the first sample's composition time does not match, for sidx number 1 at reference count 2 (checking sample 1 of trun 1, traf 1, moof 3).

Referenced track duration 10.291667 of track 1 does not match to subsegment_duration 10.416667 for leaf with EPT 0.000000, difference 1.250000e-001, threshold 8.138021e-005 (Leaf count 1).

The command used was:

MP4Box -dash 5000 -profile onDemand -rap -frag-rap -url-template -out
C:\xampp\htdocs\Dashcontent\BBB_H265\BBB_OnDemand_H265.mpd -segment-name %s_ -segment-ext mp4
~\ContentSources\bbb_720p_2000k_H265.mp4 ~\ContentSources\bbb_720p_1000k_H265.mp4
~\ContentSources\bbb_audio_32k.mp4

I would appreciate your comments related to this issue.

Thanks in advance!

Kind regards,

Diego Suarez

Related

Bugs: #327

Discussion

  • Romain Bouqueau

    Romain Bouqueau - 2014-08-20

    Hi Diego,

    We are aware of this and plan to investigate when we find time. However you'll notice these are just warnings about imprecise timings and should not prevent your content to play.

    Just for my knowledge, have you run the conformance checker on an equivalent stream with x264?

    Romain

     
  • Diego Andres Suarez

    Hi Roman,

    Yes. Using the same content but encoding it with H.264 gives no conformance issues.

    Kind regards,

    Diego

     
  • Diego Andres Suarez

    Dear Roman,

    I hope everything is fine by your side.

    We would like to report you some conformance issues that we have DASHing
    HEVC in Live profile.

    Software Versions (updated on 17/02/2015):
    GPAC version 0.5.2-DEV-rev75-g7c128ee-master
    ffmpeg version N-69861-g2bae7b3

    Platform:
    Windows 7 32 bits.

    Commands for Representation Generation:

    //BBB HEVC 720 @ 1000K
    ffmpeg -t 16 -i ~\ContentSources\bbb_720p_H265_TS.ts -f mp4 -vcodec
    libx265 -s 1280x720 -aspect 16:9 -b:v 1000k -an -maxrate 1008k -bufsize
    2008k -threads 0 -x265-params
    no-open-gop=1:min-keyint=96:scenecut=0:keyint=96 -y
    ~\ContentSources\bbb_720p_1000k_H265_16Secs_265params.mp4

    //BBB HEVC 720 @ 2000K
    ffmpeg -t 16 -i ~\ContentSources\bbb_720p_H265_TS.ts -f mp4 -vcodec libx265
    -s 1280x720 -aspect 16:9 -b:v 2000k -an -maxrate 2016k -bufsize 4008k
    -threads 0 -x265-params no-open-gop=1:min-keyint=96:scenecut=0:keyint=96 -y
    ~\ContentSources\bbb_720p_2000k_H265_16Secs_265params.mp4

    //BBB HEVC 720 @ 4000K
    ffmpeg -t 16 -i ~\ContentSources\bbb_720p_H265_TS.ts -f mp4 -vcodec
    libx265 -s 1280x720 -aspect 16:9 -b:v 4000k -an -maxrate 4032k -bufsize
    8032k -threads 0 -x265-params
    no-open-gop=1:min-keyint=96:scenecut=0:keyint=96 -y
    ~\ContentSources\bbb_720p_4000k_H265_16Secs_265params.mp4

    //AUDIO Rep:
    ffmpeg -i ~\ContentSources\bbb_720p_H265_TS.ts -t 16 -vn -b:a 32k -ar 48000
    -ac 2 -acodec libvo_aacenc -profile:a aac_he_v2 -threads 0 -y
    ~\ContentSources\bbb_32k_16Secs_audio.mp4

    Commands for DASHing:

    //DASH Live:
    MP4Box -dash 4000 -profile live -rap -frag-rap -url-template -out
    ~\Dashcontent\BBB_H265_16Secs_FFMPEG_265params_Live\BBB_Live_H265_265params.mpd
    -segment-name %s_ -segment-ext mp4
    ~\ContentSources\bbb_720p_1000k_H265_16Secs_265params.mp4
    ~\ContentSources\bbb_720p_2000k_H265_16Secs_265params.mp4
    ~\ContentSources\bbb_720p_4000k_H265_16Secs_265params.mp4
    ~\ContentSources\bbb_32k_16Secs_audio.mp4

    Conformance Issues:
    Please find it in the attached file.

    Content used:
    https://app.box.com/s/7fy5cnyntsjhdxzqh95ceoybu7xm1z94

    DASHed files (MPD and segments):
    https://app.box.com/s/rlvm3wo4e4ceqx918924rcq20duuiyok

    I appreciate your help checking this issue.

    Kind regards,

    Diego

    On Wed, Aug 20, 2014 at 6:41 PM, Diego Andres Suarez diegosuarez@users.sf.net wrote:

    Hi Roman,

    Yes. Using the same content but encoding it with H.264 gives no
    conformance issues.

    Kind regards,

    Diego

    Status: open
    Group: v1.0 (example)
    Labels: DASH H.265 Conformance Issues
    Created: Wed Aug 20, 2014 09:20 AM UTC by Diego Andres Suarez
    Last Updated: Wed Aug 20, 2014 03:30 PM UTC
    Owner: nobody

    Dear all,

    I have generated DASH content with MP4Box based on H.265 video (x265 in
    FFmpeg).
    MP4Box - GPAC version 0.5.1-DEV-rev5322 is being used, running on Windows
    7 32 bits.

    The conformance test of the video representations obtained gave the
    following issues:

    Section 6.3.4.3. of ISO/IEC 23009-1:2012(E): If 'sidx' is present in a
    Media Segment, the first 'sidx' box shall document the entire Segment.
    Violated for Media Segment 1. Segment duration 596.333333, Sidx documents
    597.208333 for track 1, diff 0.875000.

    Referenced moof earliest_presentation_time 10.291667 does not match to
    reference EPT 10.416667 for sidx number 1 at reference count 1.

    SAP found with presentation time 12.000000 lesser than the declared SAP
    time 12.125000 (SAP_delta_time 0.000000), for sidx number 1 at reference
    count 2; first SAP shall be signalled as per Section 8.16.3.3 of ISO/IEC
    14496-12 4th edition.

    starts_with_SAP declared but the first sample's composition time does not
    match, for sidx number 1 at reference count 2 (checking sample 1 of trun 1,
    traf 1, moof 3).

    Referenced track duration 10.291667 of track 1 does not match to
    subsegment_duration 10.416667 for leaf with EPT 0.000000, difference
    1.250000e-001, threshold 8.138021e-005 (Leaf count 1).

    The command used was:

    MP4Box -dash 5000 -profile onDemand -rap -frag-rap -url-template -out
    C:\xampp\htdocs\Dashcontent\BBB_H265\BBB_OnDemand_H265.mpd -segment-name
    %s_ -segment-ext mp4
    ~\ContentSources\bbb_720p_2000k_H265.mp4
    ~\ContentSources\bbb_720p_1000k_H265.mp4
    ~\ContentSources\bbb_audio_32k.mp4

    I would appreciate your comments related to this issue.

    Thanks in advance!

    Kind regards,

    Diego Suarez

    Sent from sourceforge.net because you indicated interest in
    https://sourceforge.net/p/gpac/bugs/327/

    To unsubscribe from further messages, please visit
    https://sourceforge.net/auth/subscriptions/

     

    Related

    Bugs: #327

  • Romain Bouqueau

    Romain Bouqueau - 2015-02-17

    The input file seem to contain open-GOPs:

    MP4Box -add bbb.hevc -new bbb.mp4
    HEVC import - frame size 1280 x 720 at 25.000 FPS
    HEVC Import results: 14309 samples - Slices: 448 I 3130 P 10731 B - 0 SEI - 1 IDR
    Stream uses forward prediction - stream CTS offset: 2 frames
    OpenGOP detected - adjusting file brand
    Saving bbb.mp4: 0.500 secs Interleaving

    I sent you a PM. I can't see any attachment to the previous message.

     

Log in to post a comment.

MongoDB Logo MongoDB