m4a tagging support?

Jochen Issing jochen at mcf-music.de
Fri Sep 15 14:26:25 CEST 2006

Hi All,

sorry for latency, I just came out of vacations - 9 hours ago and needed some 
sleep ;-) Comments inline:

On Wednesday 06 September 2006 22:31, Michael wrote:
> Brian Nickel wrote:
> > Michael,
> >
> > There is a read-only patch at
> > http://www.isign-softart.de/download/taglib-1.4_with_itunes.tar.bz2
> >
> > I've made a readable/writable Mpeg4.File class based on it in my C#
> > library TagLib#, which shouldn't be too hard to backport to TagLib
> > (except for the fact there are 25 classes). You can get it here:
> > http://svn.myrealbox.com/viewcvs/trunk/taglib-sharp/src/TagLib/Mpeg4/
Wow, I haven't heard of it before. Can you tell something about how you did 
the write support? Do you use the skip/free boxes as buffers and reallocate 
the boxes in case of new data exceeding the free-boxes?

Well for my part, I did read support and still need to do some restructuring 
for a full write support. Because writing a tag into an mp4file can require 
to rebuild the whole offset table - something that has actually nothing to do 
with metadata, but who cares...

I hope to get to taking hands on the code again, although the last weeks have 
been quite busy - need to work for my job ;-)



> >
> > - Brian
> Thanks Brian! I had seen Jochen Issings patch but not your
> implementation. Looks interesting at first glance, I'll have a further
> look...
> I must say my question wasn't really for my own benefit, I'm not
> building an app right now. It was more of a general question for the
> benefit of OSS developers in general.
> Wouldn't it be great for both Taglib and OSS developers when m4a tagging
> came out-of-the-box? Furthermore, I reckon the more centralized bug
> tracking system of Taglib would be an improvement over having multiple
> different third-party patches and their maintainers. I'm sure the
> developers of Amarok, Cog, Songbird or any other app using Taglib would
> welcome native support. Just getting the regular version, let's say
> Taglib 1.6, and the three most common formats in the world are supported.
> In an earlier posting on this subject I read that Scott is very strict
> in what he allows in the lib and I think that's very good, that's what
> made Taglib such a clean, dependable and easy to use lib. Are any of
> these issues still unresolved?
> Regards,
> Michael
> _______________________________________________
> taglib-devel mailing list
> taglib-devel at kde.org
> https://mail.kde.org/mailman/listinfo/taglib-devel

 jochen issing
 gpg-sig: 0A121BC8
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 191 bytes
Desc: not available
Url : http://mail.kde.org/pipermail/taglib-devel/attachments/20060915/770774d6/attachment.pgp 

More information about the taglib-devel mailing list