Re: [Tracker] How does tracker recognize the mime type of a new file?
- From: Ivan Frade <ivan frade gmail com>
- To: "Lin, Mengdong" <mengdong lin intel com>
- Cc: Michele Tameni <michele tameni it>, "tracker-list gnome org" <tracker-list gnome org>
- Subject: Re: [Tracker] How does tracker recognize the mime type of a new file?
- Date: Tue, 7 Dec 2010 11:43:51 -0500
hi,
Tagreadbin doesn't load any decoder in gstreamer; that is what makes it faster. Not sure how this affect the DRM playcount (that is a question for gstreamer). If it doesn't increase it, then you should do some noise to get tagreadbin integrated into upstream and Meego. So far it is not available.
One possible way of action: register the mimetype in shared-mime-info, write your own extractor module to support that mimetype. In the code you will check if tagreadbin is available (there is a flag for it, grep around for tagreadbin ;)). If it does, you can call the standard gstreamer extraction. If not, you should do some manual extraction at least to return if it is Audio/Video and whatever else you can provide.
Regards,
Ivan
On Tue, Dec 7, 2010 at 3:25 AM, Lin, Mengdong
<mengdong lin intel com> wrote:
Thanks a lot!
The MIME type I want to support is a wrapper file format of OMA DRM : application/vnd.oma.drm.content
It's not supported by " shared-mime-info" yet.
The original media file is embedded in this wrapper.
Now I have two choices to make shared-mime-info support it:
1. Only recognize the mime type of the wrapper format. Then I need to write an extractor extract the meta data.
The defect is that tracker will not know the mime type of the original protected media, such as video or audio. So tracker cannot sort them correctly.
If the user want to find all music on the computer, these DRM-protected music will be missed.
I wonder after the DRM extractor extracts the original media type, does it have a chance to change the mime type and inform tracker?
2. Let the shared-mime-info give the original media type, such audio/* or video/*. Then the GStreamer extractor can be used to extract the meta data.
This seems a better way. But there is still a problem. Some DRM-protected has a play count limit. Using "decoderbin2" will reduce the count, because the GStreamer elements cannot know the intention is to play or extract meta data. Can "tagreadbin" help me? Is it well supported by GStreamer and its elements?
Could some evaluate this two methods and share some suggestions?
Best Regards
Amanda
_______________________________________________
tracker-list mailing list
tracker-list gnome org
http://mail.gnome.org/mailman/listinfo/tracker-list
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]