Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The
v3.33.3
is a "legacy" release (now that the v4 is the current major version) mostly containing some of the bug fixes and improvements initially made for the next v4 release (probably the v4.1.0).Both the next v3 and v4 (which contains most of the same fixes and improvements, plus more improvements and some features) should be released at roughly the same time.
Note that this PR is only for visibility, bug fixes and improvements are not all merged yet and consequently this branch does not contain everything announced by the changelog.
Changelog
Bug fixes
maxVideoBufferSize
API [[v3] When listing segments needed, stop filtering the current range #1448][ [v3] Fix duplicate segment requests for low-latency contents #1449]
[[v3] on Edge test comprehensively KeySystems before considering them as usable #1450]
0x0
key id found in DASH initialization segments are they are oftenlinked to unencrypted data. [fix(isobmff): exclude zero-filled keyId from the init segment parsing #1466, DRM: Zero filled TENC KID cause a NO_PLAYABLE_REPRESENTATION error #1458]
unusable to prevent fatal errors [[v3] On the playstation 5, reload ASAP if a key become unusable #1451]
autoPlay
is set to
false
or not set and the video element has the attribute "playsinline"[fix(safari): no longer stuck in buffering on safari iOS when video has attribute "playsinline" #1406, fix(safari): check seeking event type in addition to the videoElement state "seeking" #1404, Infinity loading state on Safari Mobile when autoplay is false #1390]
LOADING
state if theduration
is set toNaN
(rare issue in anormally-unsupported multiple RxPlayer-per-media-element scenario) [[v3] fix(directfile): media with autoplay:false is infinitly in loading state #1452]
[ fix: on chrome display correctly the error message in the console when an error is thrown #1474]
Other improvements
[[v3] api: throw an error if an application use a video element in multiple instance of the RxPlayer #1453]
normalized
property equal to"und"
for better ISO 639-3 compatibility [[v3] fix: safari support audio lang "und" in audioTrack #1454]