m4a tagging support?
brian.nickel at gmail.com
Fri Sep 29 19:58:41 CEST 2006
Running out of space isn't an issue, as TagLib has some beautiful
methods to change block sizes. The issue is the devalidation of a box
that contains data offsets. This issue can be overcome by finding the
new size difference and then overwriting the content offset box.
On Fri, 2006-09-29 at 13:06 +0100, Michael wrote:
> If I understand the issue correctly, the problem with writing MOOV only
> arises when a user edits the metadata and it ends up bigger in size than
> it was before so you run out space in between FTYP and MDAT.
> Now, wouldn't it be convenient to write a temp file where you can nicely
> store the atoms in the right order (and maybe add some padding after the
> metadata for future editing)? Some developers have chosen this route
> anyway because you don't risk wrecking a file when the app or computer
> crashes while writing.
> About checking or reviewing, I'd be happy to help as much as I can. I
> must say I'm a bit handicapped right now because I'm separated from all
> my own computers by a sea for the next few months. :) I'm using the
> Powerbook of a friend to browse and e-mail and miss some of my own
> stuff. Still worth a try though. Good luck and keep me posted!
> Jochen Issing wrote:
> > Michael,
> > thanks for the detailed information. I actually thought about the "solution"
> > for implementation as well, although I didn't have such detailed information
> > about nero and foobar2000; I just wanted to figure out, how it was done by
> > Brian. Maybe, if I can finish it, you can review/check the implementation?
> > Best Regards,
> > jochen
> taglib-devel mailing list
> taglib-devel at kde.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the taglib-devel