Results 1 to 6 of 6

Thread: [Q] Media Validator1.1 warning message

  1. #1
    Join Date
    Jan 2012
    Posts
    2

    Default [Q] Media Validator1.1 warning message

    I got below warning message from Mediastreamvalidator1.1

    How Can I Clear this warning? Please Help me....

    +-------------------------------------------------+

    Playlist Validation:

    OK

    Segments:

    media_1.ts?wowzasessionid=1552218001&token=5jusXon%2BnkquWDenUd%2BYtFCuCqQDuomSIV9gyEK9hVLjlhTCyLpZV Sb4c0vV9fjZi%2F8C1OoLDL2uWDenUd%2BYtFCuCqQDuomSIV9gyEK9hVLjlhTCyLpZVfrA0YfY4oA0bMPAjuZaycEfjVsN%2FqD KvetL5hX43GaJMxyjFzG80AavmX5%2BiFbzFqPlUZpWM6xWEgZG%2Fq17qD0%3D:

    WARNING: Unable to read video timestamps in track 0; this may be due to not having a key frame in this segment.
    WARNING: Unable to read decode timestamps in track 0; this may be due to not having a key frame in this segment.
    WARNING: Unable to read video timestamps in track 1; this may be due to not having a key frame in this segment.
    WARNING: Unable to read decode timestamps in track 1; this may be due to not having a key frame in this segment.

    Average segment duration: 9.57 seconds
    Average segment bitrate: 188114.06 bps
    Average segment structural overhead: 37082.65 bps (19.71 %)

  2. #2
    Join Date
    Dec 2007
    Posts
    21,962

    Default

    I'm not sure about the WARNING lines, but they might not be critical to streaming or to App store. Do you have audio only streams involved? Do you see any problem other than these lines?

    What is critical to App store is "Average segment bitrate" being +-10% of target. That would be lower down in the report, but your structural overhead is an indicator that you failed. If so, it is easy to fix: adjust the system-bitrate settings in your .smil file until MediaValidator agrees

    Richard

  3. #3
    Join Date
    Dec 2007
    Posts
    21,962

    Default

    What encoder are you using, and what are the encoding details?

    Have you tried a different encoder?
    Last edited by rrlanham; 01-05-2012 at 12:30 PM.

  4. #4
    Join Date
    Jan 2012
    Posts
    2

    Default

    Quote Originally Posted by rrlanham View Post
    I'm not sure about the WARNING lines, but they might not be critical to streaming or to App store. Do you have audio only streams involved? Do you see any problem other than these lines?

    What is critical to App store is "Average segment bitrate" being +-10% of target. That would be lower down in the report, but your structural overhead is an indicator that you failed. If so, it is easy to fix: adjust the system-bitrate settings in your .smil file until MediaValidator agrees

    Richard
    I've attached Validator 1.1 results fullly.
    We have 300k Video service and 40kbps(64k under) Audio only stream.

    I have 2 questions to your commet.
    1) How can I decide "Average segment bitrate" is OK?
    2) I can't understand "System-bitrate setting in .smil" is meaning. Could you explain more detail...and some example?


    +-----------------------------------------------------------------------------------------------------------------------------+

    mediastreamvalidator validate --timeout=60 http://vds.digicaps.com:9090/vod/iph...ZG%2Fq17qD0%3D

    Validating http://vds.digicaps.com:9090/vod/iph...ZG%2Fq17qD0%3D

    Validating child playlist http://vds.digicaps.com:9090/vod/iph...wowzaaudioonly

    Validating child playlist http://vds.digicaps.com:9090/vod/iph...ZG%2Fq17qD0%3D



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

    http://vds.digicaps.com:9090/vod/iph...ZG%2Fq17qD0%3D

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



    Playlist Validation:



    OK



    Alternate playlist(s):



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

    http://vds.digicaps.com:9090/vod/iph...wowzaaudioonly

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



    Playlist Validation:



    OK



    Segments:



    OK



    Average segment duration: 9.61 seconds

    Average segment bitrate: 40210.40 bps



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

    http://vds.digicaps.com:9090/vod/iph...ZG%2Fq17qD0%3D

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



    Playlist Validation:



    OK



    Segments:



    media_1.ts?wowzasessionid=1552218001&token=5jusXon%2BnkquWDenUd%2BYtFCuCqQDuomSIV9gyEK9hVLjlhTCyLpZV Sb4c0vV9fjZi%2F8C1OoLDL2uWDenUd%2BYtFCuCqQDuomSIV9gyEK9hVLjlhTCyLpZVfrA0YfY4oA0bMPAjuZaycEfjVsN%2FqD KvetL5hX43GaJMxyjFzG80AavmX5%2BiFbzFqPlUZpWM6xWEgZG%2Fq17qD0%3D:



    WARNING: Unable to read video timestamps in track 0; this may be due to not having a key frame in this segment.

    WARNING: Unable to read decode timestamps in track 0; this may be due to not having a key frame in this segment.

    WARNING: Unable to read video timestamps in track 1; this may be due to not having a key frame in this segment.

    WARNING: Unable to read decode timestamps in track 1; this may be due to not having a key frame in this segment.



    Average segment duration: 9.57 seconds

    Average segment bitrate: 188114.06 bps

    Average segment structural overhead: 37082.65 bps (19.71 %)

  5. #5
    Join Date
    Dec 2007
    Posts
    21,962

    Default

    Are you using a .smil file? If so, can you show it that?

    The best way to provide audio is using the following method, extracting the audio from the other file, the 300kbs video in your case.

    http://www.wowza.com/forums/content....pStore-64Kbps)

    Richard

  6. #6
    Join Date
    Jan 2012
    Posts
    1

    Default

    I have the same problem here:

    Validating http://80.73.144.82:1935/vod/9398_BA.../playlist.m3u8
    Validating child playlist playlist.m3u8?wowzasessionid=1482173066
    Validating child playlist playlist.m3u8?wowzaaudioonly&wowzasessionid=1482173066

    --------------------------------------------------------------------------------
    http://80.73.144.82:1935/vod/9398_BA.../playlist.m3u8
    --------------------------------------------------------------------------------

    Playlist Validation:

    OK

    Alternate playlist(s):

    --------------------------------------------------------------------------------
    playlist.m3u8?wowzasessionid=1482173066
    --------------------------------------------------------------------------------

    Playlist Validation:

    OK

    Segments:

    media_1.ts?wowzasessionid=1482173066:

    WARNING: Unable to read video timestamps in track 0; this may be due to not having a key frame in this segment.
    WARNING: Unable to read decode timestamps in track 0; this may be due to not having a key frame in this segment.
    WARNING: Unable to read video timestamps in track 1; this may be due to not having a key frame in this segment.
    WARNING: Unable to read decode timestamps in track 1; this may be due to not having a key frame in this segment.

    Average segment duration: 12.11 seconds
    Average segment bitrate: 348463.76 bps
    Average segment structural overhead: 38100.02 bps (10.93 %)

    --------------------------------------------------------------------------------
    playlist.m3u8?wowzaaudioonly&wowzasessionid=1482173066
    --------------------------------------------------------------------------------

    Playlist Validation:

    OK

    Segments:

    OK

    Average segment duration: 12.13 seconds
    Average segment bitrate: 65346.80 bps
    How could I use a smil file?

Similar Threads

  1. Help change this message Wowza Media Server 3 Monthly Edition 3.0.2 build866
    By inforsepulveda in forum Server Administration Discussion
    Replies: 8
    Last Post: 12-17-2013, 03:51 PM
  2. Replies: 14
    Last Post: 03-19-2013, 07:24 AM
  3. What does this warning mean?
    By terbooter in forum General Forum
    Replies: 3
    Last Post: 03-09-2013, 11:35 AM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •