mirror of
https://gitlab.freedesktop.org/gstreamer/gstreamer.git
synced 2024-12-23 08:46:40 +00:00
docs/design/draft-tagreading.txt: Added open issues/thoughts to draft.
Original commit message from CVS: * docs/design/draft-tagreading.txt: Added open issues/thoughts to draft.
This commit is contained in:
parent
6626976347
commit
d5669b316a
2 changed files with 21 additions and 0 deletions
|
@ -1,3 +1,8 @@
|
|||
2007-04-20 Stefan Kost <ensonic@users.sf.net>
|
||||
|
||||
* docs/design/draft-tagreading.txt:
|
||||
Added open issues/thoughts to draft.
|
||||
|
||||
2007-04-19 Sebastian Dröge <slomo@circular-chaos.org>
|
||||
|
||||
* gst/parse/grammar.tab.pre.c:
|
||||
|
|
|
@ -36,6 +36,22 @@ The plan is that applications can do the following:
|
|||
* tagread-elements should have RANK_NONE to be not autoplugged by decodebin
|
||||
|
||||
|
||||
Open Issues
|
||||
-----------
|
||||
* would it make sense to have 2-phase tag-reading
|
||||
* 1st phase: get tag-data that are directly embedded in the data
|
||||
* 2nd phase: get tag-data that has to be generated fetched
|
||||
* e.g. album-art via web, video-thumbnails
|
||||
* what about caching backends
|
||||
* it would be good to allow applications to supply tagbin with a tagcache-
|
||||
object instance. whenever tagbin gets a uri to tagread, it consults the
|
||||
cache first. whenever there is a cache-miss it will tag-read and then store
|
||||
in the cache
|
||||
|
||||
GstTagList *gst_tag_cache_load_tag_data (GstTagCache *self, const gchar *uri);
|
||||
gst_tag_cache_store_tag_data (GstTagCache *self, const gchar *uri, GstTagList *tags);
|
||||
|
||||
|
||||
Reuse
|
||||
-----
|
||||
|
||||
|
|
Loading…
Reference in a new issue