-
Notifications
You must be signed in to change notification settings - Fork 426
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
master/TBA remaining issues #531
Comments
are these two handled by the same PR?
|
yes |
I thought someone said #425 would be included in this release, but I don't see it in the list above. Any plans to address that issue? |
We haven't had a change to look at #425, it would've potentially been fixed by this but definitely possible it hasn't. Is that still a problem happening in master? |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
It seems like #425 is fixed in master. I added a manifest to test the file with http://d2zihajmogu5jn.cloudfront.net/bad-pmt/index.m3u8 although it's possible I did not create an accurate reproduction. |
#624 (comment) is fixed by videojs/mux.js#317 |
I tested this with wowza but not sure if its requesting the sub fragments properly. how can I test it to confirm it's requesting properly ?. The LHLS urls are working at least with these updates. |
Unfortunately, we do not have full support for Apple's or the open LHLS specs. |
So it's not fully working yet apart from requesting fragments ? It's playing but don't know if its requesting properly. What requests are we expecting to see ? |
The reason this is called LHLS is because it was done in service to getting support for low latency streaming, such as being able to download and use parts of segments. Yes, it's confusing, but it kind of stuck. However, actual support for the specs isn't included yet. That means we don't handle anything related to the parts stuff in Apple's LHLS or the prefetch tags from the open source spec. |
OK. Well it's requesting LHLS wowza streams fine, but we should expect partial requests then when it's working. |
|
Closing as complete. There's just the two PRs in the 2.0 milestone left, and we can use the milestone to track any other work. |
issues
handlePartialData
via VHS optionshandlePartialData
set totrue
mux.js
improvements
type
specifier for urlPushed Back
handlePartialData
. The issue here is that during handlePartialData with muxed content browsers expect theinitSegment
that we generate to contain the same tracks as they did previously. For non partial we can set the Coalesce stream toremux
, which makes it so that theinitSegment
has both tracks. For the partial transmuxer it is much harder because we don't have a Coalesce stream.testing
handlePartialData
The text was updated successfully, but these errors were encountered: