[haiku-commits] Re: r39175 - haiku/trunk/src/add-ons/index_server
- From: "Stephan Assmus" <superstippi@xxxxxx>
- To: haiku-commits@xxxxxxxxxxxxx
- Date: Fri, 29 Oct 2010 14:54:35 +0200
Hi,
Von: "Clemens Zeidler" <clemens.zeidler@xxxxxxxxxxxxxx>
> Am 29.10.2010, 07:25 Uhr, schrieb François Revol <revol@xxxxxxx>:
> > Le 28 oct. 2010 à 20:12, clemens.zeidler@xxxxxxxxxxxxxx a écrit :
> >
> >> Author: czeidler
> >> Date: 2010-10-28 20:12:14 +0200 (Thu, 28 Oct 2010)
> >> New Revision: 39175
> >> Changeset: http://dev.haiku-os.org/changeset/39175
> >>
> >> Modified:
> >> haiku/trunk/src/add-ons/index_server/Jamfile
> >> Log:
> >> Cleanup there is no Audio plugin yet.
> >>
> >
> > You'll also want to have a look at
> > http://revolf.free.fr/beos/patches/indexing-translator-samplecode.diff
> >
> > François.
>
> Thanks any suggestions for a good id3 tag library?
I've already extended the BMediaFile and BMediaTrack API to support meta data.
The meta data is converted from what FFmpeg supports into a (possibly nested)
BMessage. From what I can tell, the FFmpeg project aims at a consistent naming
scheme for the meta data keys. It should work to look at a couple MP3 or Vorbis
files which have tags and see what's in the BMessages you get back from
BMediaFile or BMediaTrack. To make it more robust, you could have a look at the
FFmpeg AVFormatReader class and introduce a mapping for the key names, like
I've already done for certain meta data keys. That would insulate us against
changes in FFmpeg.
Best regards,
-Stephan
Other related posts:
