Page 1 of 2 12 LastLast
Results 1 to 10 of 12

Thread: Apple iOS Acceptance Team rejecting Wowza server media streams

  1. #1
    Join Date
    Feb 2011
    Posts
    14

    Default Apple iOS Acceptance Team rejecting Wowza server media streams

    I had Apple run the media validation tool for me yesterday. I have separate issues for my live and on-demand streams. This is causing rejection by Apple's acceptance team. I have been led to believe this is being introduced by Wowza. Thanks in advance for any help.

    These are the errors being reported by Apple's tool:

    On-Demand:
    media_1.ts?wowzasessionid=1276328531:
    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.

    Live:
    Playlist Validation:
    Error: (-12642:-12312) Media segment doesn't match - sequence 16 --> media_16.ts?wowzasessionid=1765170611

  2. #2

    Default

    Hello egmanred,

    Take a look at these articles and the associated threads:
    http://www.wowza.com/forums/content....amvalidator%29
    http://www.wowza.com/forums/content....tore-64Kbps%29
    http://www.wowza.com/forums/content....to-iOS-Streams

    Some more info about your setup may be helpful. e.g. OS, Java, Wowza versions and how you're doing your encoding, codec, keyframe interval, etc..

  3. #3
    Join Date
    Feb 2011
    Posts
    14

    Default

    Hi Randall.

    1. The validation is what generated the results above.
    2. 64 Kbps minimum stream is not an issue. Was implemented previously and is not failing acceptance.
    3. Do not believe this is applicable to the issue above but good info.

    I will add additional information as soon as possible. Thanks for the help. I need it!

  4. #4
    Join Date
    May 2011
    Posts
    491

    Default

    Hello,
    These warnings are occuring when the first segment has a timestamp of 0. We have filed this bug against the media validator tool with Apple.

    -Lisa

  5. #5
    Join Date
    Feb 2011
    Posts
    14

    Default

    Okay, that helps. Is Apple fairly responsive to Wowza bug submittals? Thanks.

  6. #6
    Join Date
    May 2011
    Posts
    491

    Default

    Hello,
    Apple responded quickly to our message to them saying they would investigate. We have followed Apple's process and have filed a RADAR bug. There are not problems with the Wowza streams, but the media validator tool is throwing these warnings. I realize this situation poses a problem for you and we will post again with any new information. As of today, there is no update to our ticket with Apple. If you could share details about how you are using Wowza with your app or any other relevant information that might help with their investigation, we can add it to our ticket with Apple.

    -Lisa

  7. #7
    Join Date
    Feb 2011
    Posts
    14

    Default

    Lisa,
    I assume you are talking about the VOD warnings above. (There is a live error also, but I think I might have solved that one by changing the key frame interval.)

    On-Demand:
    media_1.ts?wowzasessionid=1276328531:
    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.

    This is a transcode using Microsoft Expressions 4. We are using the h264 baseline profile with a video bitrate of 291 and AAC audio of 32. I believe the frame rate is set to be the same as the source (30 fps) and the key frame interval is 4 seconds, which I think is the default.

    Thanks.

  8. #8

    Default

    The specifics of this problem are as follows:

    The mediastreamvalidator is throwing this error when the first frame of a segment has a PTS (presentation time stamp) of zero. When we stream video on demand content we always start the first segment with a PTS value of zero. We confirmed with Apple that this is a valid PTS value and that the mediastreamvalidator tool should be updated to no longer throw this warning message when this occurs. I guess I would explain this to Apple upon resubmission of your application to the AppStore.

    Charlie

  9. #9
    Join Date
    Feb 2011
    Posts
    14

    Default

    Thanks. We've resubmitted. We will see.

  10. #10

    Default

    Quote Originally Posted by eggmanred View Post
    Thanks. We've resubmitted. We will see.
    Hi Eggmanred,

    I wonder if your submission was successful despite the warnings issues by the Media Validation Tool?

Page 1 of 2 12 LastLast

Posting Permissions

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