Skip to content

Conversation

@peaBerberian
Copy link
Collaborator

While working on new DRM integration test in #1478, to add tests for the not-yet-released features proposed by #1484, I noticed that some contents anounced HEVC by beginning the codec string with hev and others with hvc.

When comparing family of codecs, we thus had false negative which may mean we would have ended up playing encrypted hevc on devices where it wasn't supported, if it was anounced in the MPD as hev1....

I now treat both the same way.

While working on new DRM integration test in #1478, to add tests for the
not-yet-released features proposed by #1484, I noticed that some
contents anounced HEVC by beginning the codec string with `hev` and
others with `hvc`.

When comparing family of codecs, we thus had false negative which may
mean we would have ended up playing encrypted hevc on devices where it
wasn't supported, if it was anounced in the MPD as `hev1...`.

I now treat both the same way.
@peaBerberian peaBerberian added bug This is an RxPlayer issue (unexpected result when comparing to the API) Priority: 0 (Very high) This issue or PR has a very high priority. Efforts should be concentrated on it first. labels Aug 13, 2024
@peaBerberian peaBerberian added this to the 4.2.0 milestone Aug 13, 2024
@peaBerberian peaBerberian merged commit f8f932f into dev Aug 14, 2024
peaBerberian added a commit that referenced this pull request Sep 6, 2024
This is a backport of #1499 to the v3
@peaBerberian peaBerberian deleted the fix/chrome-hevc-check-hev branch November 9, 2024 21:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug This is an RxPlayer issue (unexpected result when comparing to the API) Priority: 0 (Very high) This issue or PR has a very high priority. Efforts should be concentrated on it first.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants