wiseplay key systems should be com.wiseplay.drm

[TonyChenSEU]

Have you read the FAQ and checked for duplicate open issues?
yes

If the problem is related to FairPlay, have you read the tutorial?
no

What version of Shaka Player are you using?
4.13.6

Can you reproduce the issue with our latest release version?
yes

Can you reproduce the issue with the latest code from main?
yes

Are you using the demo app or your own custom app?
yes

If custom app, can you reproduce the issue using our demo app?
N/A

What browser and OS are you using?
HarmonyOS

For embedded devices (smart TVs, etc.), what model and firmware version are you using?

What are the manifest and license server URIs?
test resource

What configuration are you using? What is the output of player.getNonDefaultConfiguration()?
servers: {
'com.huawei.wiseplay': licenseServer
}

What did you do?

1. create demo page with [email protected]
2. load HLS manifest and configure license server
3. player.load

What did you expect to happen?

1. shake-player RequestMediaKeySystemAccess of com.wiseplay.drm

What actually happened?

1. shake-player RequestMediaKeySystemAccess of com.huawei.wiseplay

Are you planning to send a PR to fix it?
yes if it's possible ,simply replace all com.huawei.wiseplay with com.wiseplay.drm should be fine . refer this
https://developer.huawei.com/consumer/en/doc/harmonyos-guides/native-drm-mediakeysystem-management-V14

[avelad]

@vlazh You added this in Shaka, can you confirm if this is correct or not? (see: #7854)

[vlazh]

@vlazh You added this in Shaka, can you confirm if this is correct or not? (see: #7854)

I can't confirm that is correct. I got reply from huawei support that key sytem name should be com.huawei.wiseplay:

Also take a look at others:
https://docs.nagra.com/public/apidocs/player/android/opy-sdk-android-5.27.2.1680254288-javadoc/html/classnagra_1_1otv_1_1sdk_1_1drm_1_1_o_t_v_d_r_m.html
https://github-wiki-see.page/m/xbmc/inputstream.adaptive/wiki/Integration-DRM

And if anybody have huawei device you can try https://9wv3nd.csb.app/ (open sources and edit as you need).
On device that I have I get "SUPPORTED" only for "com.huawei.wiseplay".

[TonyChenSEU]

from your document it's Android OpenTV Player SDK, i'm not sure if huawei andriod wiseplay keysystem use a different name.

I'm devloping demo for huawei devices with HarmonyOS, which need wiseplay js player for drm, and our test stream also use the same UUID(3d5e6d35-9b9a-41e8-b843-dd3c6e72c42c). and i have to change the key system name to com.wiseplay.drm, then the player can work. (there are also
few changes for HLS EXT-X-KEY:METHOD handling ).

since current wiseplay support of huawei device is untested, maybe later we can find out whichi is corrent.

[vlazh]

The main reason that I used "com.huawei.wiseplay" is an answer from official huawer developers support.
Have you tried https://9wv3nd.csb.app/ ? What result you get with both names? If you get "SUPPORTED" only with "com.wiseplay.drm" then there is a reason to add that name with the same uuid. But on my device (EMUI 14.2) I get "SUPPORTED" only with "com.huawei.wiseplay".

[TonyChenSEU]

The main reason that I used "com.huawei.wiseplay" is an answer from official huawer developers support. Have you tried https://9wv3nd.csb.app/ ? What result you get with both names? If you get "SUPPORTED" only with "com.wiseplay.drm" then there is a reason to add that name with the same uuid. But on my device (EMUI 14.2) I get "SUPPORTED" only with "com.huawei.wiseplay".

I got support only with "com.wiseplay.drm", and i discuss with hardware drm developer, they said the uuid is for ChinaDRM, and wiseplay is only an implementation. but i can now find any matrial from the internet to prove that.

Now I think the way to improve is to support both keySystem name. just like other drm have multiple keySystem names.