<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
On 11/29/11 13:47, Krenar Qehaja wrote:
<blockquote
cite="mid:CALtvnxLT3H2zaQO=F7rCKV3Kpy1pYoJ=3W_4eZPkDAyiy13sTg@mail.gmail.com"
type="cite">Hi everyone,
<div><br>
</div>
<div>I noticed that when I'm trying to process a DRM-protected
content with VLC, it uses a lot more CPU than it normally does.</div>
<div><br>
</div>
<div>I searched for insights in this topic but didn't encounter
anything. Is it a bug or is it the way it is, DRM-protected
content uses a lot more CPU?</div>
<div><br>
</div>
<div>Regards,</div>
<div>Krenar</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">______________________________________________________
vlc mailing list
To unsubscribe or modify your subscription options:
<a class="moz-txt-link-freetext" href="http://mailman.videolan.org/listinfo/vlc">http://mailman.videolan.org/listinfo/vlc</a>
</pre>
</blockquote>
It's most likely because DRM is an encryption layer. In case you
don't know when a media player plays a video it has to decode the
encapsulation, the video, and the audio. Adding DRM means adding
yet another thing to process, a very heavy thing at that. Also note
that these processes are all active (to my understanding most media
players decrypt/decode actively and put everything into a buffer.
The video actually starts to play before it's completely decoded.
One more thing now that I think about it is that DRM probably hides
certain data from the media player that's readily available under
normal circumstances.<br>
</body>
</html>