Source for MediaStreamValidator

I have a lot of problems with this tool as well. It's extremely misleading and doesn't really help you align yourself any closer to the latest hls authoring guidelines. What I find even more annoying is that Apple's official examples, although, a bit contrived, all have "Must fix issues" and a handful of "Should fix issues". Apple's hls examples should not return any validation issues with their own tool. I mean what's up with their IDRs? Do they know something we don't know? They should really just pull this tool until their own streams can pass. It's great for pulling the metadata into a formatted table, but if they can't follow their own spec themselves this tool just sends developers down an unnecessary rabbit hole

It would be nice if they also added a bit more verbosity to their issues, even link back to their own guidelines doc.

Apple's official examples

https://developer.apple.com/streaming/examples/

HLS Validation Report

Stream type: VOD

https://devstreaming-cdn.apple.com/videos/streaming/examples/bipbop_adv_example_hevc/master.m3u8

Variant Overview

Average duration processed: 0:10:00

Rendition Overview

Average duration processed: 0:10:00

I-Frame Variant Overview

Average duration processed: 0:10:00

Checked against HLS Authoring Specification for Apple Devices

Must Fix Issues

1. The server MUST deliver playlists using gzip content-encoding

• Master Playlist
• Variant #1
• Variant #5
• Variant #9
• Variant #10
• Variant #14
• Variant #18
• Variant #19
• Variant #23
• Variant #27
• Variant #36
• Variant #45
• Variant #54
• Rendition #55
• Rendition #59

2. Measured peak bitrate compared to master playlist declared value exceeds error tolerance

• Master Playlist Stream Definition for Variant #9
• Master Playlist Stream Definition for Variant #18
• Master Playlist Stream Definition for Variant #27

Should Fix Issues

3. Target durations SHOULD be 6 seconds.

• All Variants
• Rendition #55
• Rendition #56
• Rendition #57

4. Content protection SHOULD follow the FairPlay Streaming (FPS) specification

• All Variants
• All I-Frame Variants
• Rendition #55
• Rendition #56
• Rendition #57

5. You SHOULD support stream failover

• All Variants
• All I-Frame Variants

6. Key frames (IDRs) SHOULD be present every two seconds

• Variant #28
• Variant #29
• Variant #30
• Variant #31
• Variant #32
• Variant #33
• Variant #34
• Variant #35
• Variant #36
• Variant #37
• Variant #38
• Variant #39
• Variant #40
• Variant #41
• Variant #42
• Variant #43
• Variant #44
• Variant #45
• Variant #46
• Variant #47
• Variant #48
• Variant #49
• Variant #50
• Variant #51
• Variant #52
• Variant #53
• Variant #54

Report Information

Thanks for the feedback, but the most effective place to give feeedback is via a radar or a support incident.

Concerning medaistreamvalidtor source. Nope, not available. Not likely to made available either.

As far as the samples having issues, there are several reasons for that:

- Samples may have passed the validator when the were put up, and the validator got more strict or modified rules later. (But yes, we should probably regen them to be more in line with the current version.)

- The issue of GZIP encoding is really only for production strreams which the sample is not.

- "Should fix" errors are things that you can violate. For example, no stream failover, or not using FPS.