I want to add support for OMA DRM Content Format (DCF), an encrypted file
format. Here is my solution:
(1) I've registered *.dcf files in shared-mime-info, MIME type is
"application/vnd.oma.drm.content".
(2) We developed a DRM-aware GStreamer file source plug-in that can decrypt the
protected
I want to add support for OMA DRM Content Format (DCF), an encrypted file
format. Here is my solution:
(1) I've registered *.dcf files in shared-mime-info, MIME type is
"application/vnd.oma.drm.content".
(2) We developed a DRM-aware GStreamer file source plug-in that can decrypt the
protecte
-list@gnome.org
Subject: [Tracker] Add support for OMA DRM Content format
I want to add support for OMA DRM Content Format (DCF), an encrypted file
format. Here is my solution:
(1) I've registered *.dcf files in shared-mime-info, MIME type is
"application/vnd.oma.drm.content".
(2)
Hi Amanda,
First, why do you write your emails twice? :-/
> I want to add support for OMA DRM Content Format (DCF), an encrypted
> file format. Here is my solution:
>
> (1) I've registered *.dcf files in shared-mime-info, MIME type is
> "application/vnd.oma.drm.content".
>
>
>
> (2) We dev
On 18/02/11 09:00, Aleksander Morgado wrote:
Hi Amanda,
First, why do you write your emails twice? :-/
I want to add support for OMA DRM Content Format (DCF), an encrypted
file format. Here is my solution:
(1) I've registered *.dcf files in shared-mime-info, MIME type is
"application/vnd.oma
On Fri, 2011-02-18 at 16:57 +0800, Lin, Mengdong wrote:
> I want to add support for OMA DRM Content Format (DCF), an encrypted file
> format. Here is my solution:
> (1) I've registered *.dcf files in shared-mime-info, MIME type is
> "application/vnd.oma.drm.content".
>
> (2) We developed a DRM
Thank you all for the advice!
It's straight forward to adding "application/vnd.oma.drm.content" to the list
of mimetypes the gstreamer extractor can handle.
To be honest, writing a new DCF extractor cannot make metadata extraction
faster because it still depends on GStreamer and its extension (t
Supporting DRM formats usually involves proprietary multimedia framework
extension (such as the DRM-aware GStreamer plug-in) and low-level proprietary
HW/SW support. It seems better to enhance GStreamer extractor than writing a
new DCF extractor, because:
- If it depends on GStreamer, it cannot
Here is my change on Tracker GStreamer extractor and it works. Is this method
doable? And Can I submit a patch for it?
For OMA DRM content format (DCF), it will try GStreamer at first. If GStreamer
DRM-aware extensions are installed, then decodebin2 can recognize the original
media type and extr
There may be a better way:
How about introducing a "priority" or "rank" property for the extractors? Once
a extractor is loaded, it's order in the specific/general extractor list is
decided by its priority. If more than one extractors match a mime type, the
higher-priority one will be tired befo
On 23/02/11 06:09, Lin, Mengdong wrote:
Here is my change on Tracker GStreamer extractor and it works. Is
this method doable? And Can I submit a patch for it? For OMA DRM
content format (DCF), it will try GStreamer at first. If GStreamer
DRM-aware extensions are installed, then decodebin2 can rec
Thank you, Martyn! I will. But we have to go through the open source approval
before I could summit the patch for review. It may take 1 ~ 2 weeks.
Best Regards
Amanda
> Can you create a bug report and submit a patch for review based on this
> thread? I don't have an objections to what I have see
12 matches
Mail list logo