-
Notifications
You must be signed in to change notification settings - Fork 263
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Drawing issues on first fragment in version 0.4+ #321
Comments
@dtniland same on your side ? |
i am going to dig into the diff |
ok it also works with v0.4.1.1 if JSLoader is enabled.
I am suspecting the optimization I made are not robust to these kind of errors. |
mm the issue was related to the fact that your TS stream contained an unknown PID, and while optimizing the TS demuxer, i slightly changed the way to handle unknown PID. this should now work as before. cheers, |
Thanks, mangui, I'll check it out. |
Thanks, that fixed it. |
It seems like there is some sort of corruption or error that somehow stops the drawing of the first fragment of video from our encoding service. If you play: http://pmd205470tn.download.theplatform.com.edgesuite.net/PDK_Demo/734/401/Toy_Story_3.m3u8
in any of your reference players, you'll see a strange affect where if hardware is turned on, it will show half of the opening frame with the other half black, green, or often even an image from prior video that may have been left in the hardware buffer. If hardware is turned off (via enableStageVideo = false in OSMF) then it just won't play the first fragment.
I've tried adjusting several of the HLSSettings of your plugin, but nothing seems to make a difference.
We've noticed that the same issue does not affect any of the test media on your site. It is affecting many of the media that we've encoded through our encoding service however. These same media played fine up through flashls version 0.3.7 and we may be forced to revert to that version for our clients.
If there is some encoding setting that is causing the error, we can possibly addess that on our end -- if we know what the issue is.
As always, thank you for your efforts.
The text was updated successfully, but these errors were encountered: