search

w3c / encrypted-media

Encrypted Media Extensions
https://w3c.github.io/encrypted-media/
Other
180 stars 80 forks source link

Cannot add into chrome and firefox #490

Closed zorrvo3 closed 2 years ago

zorrvo3 commented 2 years ago

Hi, is the any correct way to insert into chrome/forerox extension? Tried already but error due to manifest unreadable

joeyparrish commented 2 years ago

I don't understand your question, but here is some general information about Encryption Media Extensions (EME):

EME is the API that applications use to talk to the Content Decryption Module (CDM) inside the browser or operating system. It can generate license requests, which the application forwards to a license server. The CDM does not do any networking directly, and all network exchanges are controlled by the application. When the CDM has a license, it can use that license to decrypt content played through HTML5 video or MediaSource.

Chrome and Firefox do not require extensions for EME. EME is built in.

Does any of this help?

zorrvo3 commented 2 years ago

May i know how to use this? What kind of software needed to run this application? i need to find key id and key value

{ "keys": [{ "kty":"oct", "k":"tQ0bJVWb6b0KPL6KtZIy_A", "kid":"LwVHf8JLtPrv2GUXFW2v_A" }], 'type':"temporary" }

On Fri, 17 Sep 2021, 4:03 am Joey Parrish, @.***> wrote:

I don't understand your question, but here is some general information about Encryption Media Extensions (EME):

EME is the API that applications use to talk to the Content Decryption Module (CDM) inside the browser or operating system. It can generate license requests, which the application forwards to a license server. The CDM does not do any networking directly, and all network exchanges are controlled by the application. When the CDM has a license, it can use that license to decrypt content played through HTML5 video or MediaSource.

Chrome and Firefox do not require extensions for EME. EME is built in.

Does any of this help?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/w3c/encrypted-media/issues/490#issuecomment-921205917, or unsubscribe https://github.com/notifications/unsubscribe-auth/ATS2JGDIL7UJJMA5H727QUTUCJEQJANCNFSM5ED2C4VA . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

joeyparrish commented 2 years ago

EME is an API provided by the browser. To use it, you build a media-streaming application in JavaScript. This is generally only done for premium (paid) media services, and usually involves a combination of EME and MSE (MediaSource Extensions).

The specs detail the various objects and methods, and you can also find API documentation on the Mozilla Developer Network (MDN). This isn't really the forum for teaching you how to build an application from scratch, though. This is an issue tracker for the specification itself.

If you want to get started quickly with a streaming media application without getting into the details of EME and MSE, you can use open-source tools such as Shaka Streamer to prepare media for streaming with the DASH or HLS standards, and you play that content back in a browser (using MSE and EME under the hood) using open-source JavaScript players such as Shaka Player. (Disclosure: I'm the team lead responsible for both the Shaka Player and Shaka Streamer projects, as well as an editor of the EME spec.) There are plenty of other media tools out there, too, both open-source and commercial.

Does this help?

zorrvo3 commented 2 years ago

thanks