[gst-devel] tags and metadata

[Mathrick]

W liście z pią, 23-01-2004, godz. 13:49, Benjamin Otte pisze: 
> On Thu, 22 Jan 2004, Mathrick wrote:
> 
> > For me it sounds almost identical as Thomas' registry proposal, with the
> > added bonus of registry not being one-off hack, and being easily
> > extendable.
> >
> ... and the negative side effect of requiring every plugin to play by the
> rules set in stone there.

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? Plugin just obtains its tags
somehow, and doesn't care at all if app thinks it's metadata or
streaminfo.

>  If you could provide a proerty only as the other
> thing, you're hosed.

Err, I don't get that part.

> > Gives you possibility to differentiate _format_ properties from _media_
> > properties, which should be presented differently. For example grouping
> > files by metadata by default instead of grouping by streaminfo seems
> > reasonable thing to do (although one can easily put up case when it
> > would be convenient to be done by streaminfo, so that shouldn't be set
> > in stone).
> >
> I still think there are cases where streaminfo might be metadata or the
> other way round. This would give you stuff like bitrates in different
> groups, and I don't think you want that.

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.

> What you really want is to group them yourself so you're sure they don't
> change position...

Hmm? Could you clear up a bit?

> > Also, to bring back editable vs. noneditable issue, app _may_ try
> > setting Artist (metadata), and maybe error out if that's not possible
> > for whatever reason, while it is obvious it shouldn't even bother trying
> > to set bitrate (streaminfo). So Artist would be shown as an entry box,
> > possibly greyed out, and bitrate as a label.
> >
> What about adjusting/setting the id3 length tag?

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.

Maciej

-- 
"Tautologizm to coś tautologicznego"
   Maciej Katafiasz <mnews2 at wp.pl>
       http://mathrick.blog.pl