[gst-devel] tags and metadata

[Benjamin Otte]

On Fri, 23 Jan 2004, Mathrick wrote:

> Hmm, I don't really understand your concern. How is it better than
> having it hardcodes into nautilus media, as you proposed? What is the
> problem with changing that info if you think it's wrong? And no, it's
> not true that every plugin should comply to the "rules set in stone
> there", it's the "rules" that have to correspond to reality, otherwise
> these rules have no value, do they? But even if plugins does not
> "conform" to the rules, what harm is done other than app thinking that
> streaminfo is metadata or other way around?
>
What useful is the distinction of streaminfo and metadata if noone
complies with it anyway?

> Sure, that's why I think it still should be possible for example to sort
> by "bitrate" column, if that's what you mean by bitrate being metadata.
> But it doesn't change the fact we want to present bitrate through label,
> not entry box.
>
So what you're after is still a distinction between writable and not
writable?

> That's what I asked about in other post. As long as "length" tag flagged
> GST_TAG_FLAGS_{INFO,DERIVED} is separate from "length" not flagged as
> such, everything is fine. Actually, *not* having that distinction is
> what'd make adjusting id3 length tag difficult.
>
So you want to have 2 different length tags?

Benjamin