-
Notifications
You must be signed in to change notification settings - Fork 1.7k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Add support for UTF8 PlayReady CDM messages
- Loading branch information
Greg Rutz
committed
Aug 14, 2015
1 parent
8b045c7
commit f8c0ccc
Showing
1 changed file
with
23 additions
and
5 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
f8c0ccc
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Greg,
On my environment (Linux + Chromium),
new Uint8Array(message.buffer);
does not work.new Uint8Array(message);
works.I'm not a JS expert but it seems like Uint8Array constructor wants the ArrayBuffer variable directly.
f8c0ccc
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@goruklu ee277fa should make the use of ArrayBuffer more consistent across all of the DRM system in dash.js. This commit should also fix the problem you just mentioned.
f8c0ccc
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi
i know that this is a very old ticket! :)
we're looking to use DASHJS on our platform, across many different devices (TVs, STBs) - the majority of devices have a PR CDM which uses the UTF16 format, however some use UTF8.
So, one solution is to maintain a list of clients which require the UTF8 format and use the the setPlayReadyMessageFormat call accordingly.
However, creating and maintaining such a list does add complexity to a large platform.
One potential approach that I am looking at is to propose to manufacturers that they ensure that they standardise on UTF16 - however, this may be a big ask, and it's possible that some manufacturers may not meet this requirement.
Or, i'm wondering as to whether DASHJS could support an option to auto-detect (infer) the format, for example:
this could be enabled by calling
setPlayReadyMessageFormat("autodetect")
any opinions gratefully received! :)
f8c0ccc
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Lets continue discussion here: #3896