GNOME Bugzilla – Bug 703015
id3mux Should Support GST_TAG_APPLICATION_NAME
Last modified: 2018-05-01 09:09:40 UTC
Created attachment 247691 [details] id3 debug When I try to set a GST_TAG_APPLICATION_NAME using id3mux, I get the following output: 0:00:04.170137987 11591 0x215b990 WARN tagmux gsttagmux.c:459:gst_tag_mux_sink_event:<muxer> dropping newsegment event in time format 0:00:04.170414912 11591 0x215b990 WARN id3mux id3tag.c:1160:foreach_add_tag: Unsupported tag 'application-name' - not written 0:00:04.170485662 11591 0x215b990 WARN id3mux id3tag.c:1160:foreach_add_tag: Unsupported tag 'audio-codec' - not written 0:00:04.170537275 11591 0x215b990 WARN id3mux id3tag.c:1160:foreach_add_tag: Unsupported tag 'nominal-bitrate' - not written 0:00:04.170730180 11591 0x215b990 WARN id3mux id3tag.c:1160:foreach_add_tag: Unsupported tag 'has-crc' - not written 0:00:04.170782492 11591 0x215b990 WARN id3mux id3tag.c:1160:foreach_add_tag: Unsupported tag 'channel-mode' - not written I can set other tags sucessfully (so there isn't an issue with the code). I'm attaching the debug output.
IIRC there's a ID3 tag that can be used for that, need to be confirmed from the docs though
(In reply to comment #1) > IIRC there's a ID3 tag that can be used for that, need to be confirmed from the > docs though Sorry, I should have said something about it possibly being a bug in the initail report. afaik there aren't any docs for this plugin. I read id3tag.c and I don't see GST_TAG_APPLICATION_NAME listed, so if I'm understanding the code correctly it would need to be added.
Maybe the TSSE frame could be used for that. Or indeed GST_TAG_ENCODER which maps to the TENC id3v2 frame.
I don't think TENC is meant for the application. Maybe it should just be put into a TXXX or comment frame.
I would like to use a tag to determine whether or not files in the directory should be displayed in the interface, so the tag needs to be supported by all of the plugins I'm using. What is a TXXX exactly?
> I would like to use a tag to determine whether or not files in the directory > should be displayed in the interface Could you describe the use-case in a bit more detail? (just out of curiosity) > so the tag needs to be supported by all of the plugins I'm using. Well, sometimes tags just can't be mapped properly. > What is a TXXX exactly? It's a freeform KEY=VALUE extension basically. We can make sure this works both ways in GStreamer then with a suitable mapping, but non-GStreamer applications might not be able to make any sense of it.
(In reply to comment #6) > > I would like to use a tag to determine whether or not files in the directory > > should be displayed in the interface > > Could you describe the use-case in a bit more detail? (just out of curiosity) As you probably know, GNOME 3 applications don't generally use Gtk.FileChooser, but instead populate a listview within the application with files from the appropriate directory. I want to use this tag to determine whether a file should be displayed in this listview. > > > > so the tag needs to be supported by all of the plugins I'm using. > > Well, sometimes tags just can't be mapped properly. > > > > What is a TXXX exactly? > > It's a freeform KEY=VALUE extension basically. We can make sure this works both > ways in GStreamer then with a suitable mapping, but non-GStreamer applications > might not be able to make any sense of it. afaik it doesn't matter if non-gstreamer apps can make sense of it, since I really just need it for the purpose I explained above. Do you think I need to take this into account here for any reason?
Why do you only want to show specific media files in your application though? Using in-file tags for that seems wrong. Maybe you could just store "your" files in a small database, or use something like libattr to tag them on the file system? But I think ideally you would just show all files in a specific directory, i.e. "$HOME/Music/Sound Recorder". Any magic with tags or metadata is just going to confuse users :)
OK, that will be fine. Jon McCann and Cosimo Cecchi suggested that I use this approach, but I think the main idea was to avoid using Tracker for indexing only a specific directory.
No action in 5 years. Closing.