That’s right, working cross-platform support will soon be coming to Tagger, as I’ve decided to forsake AtomicParsley and build my own MPEG-4 parser. In addition to Mac OS X and Linux support, files should load faster and the program should be less memory-intensive and occupy less space on your hard drive. I’ll also be able to update the code myself, so any new iTunes features or bugs in Tagger will be easy to address. Stay tuned.
I’ll say this, I’m a little nervous about this, Andrew. I think it might have to do with the amount of bugs in the early versions. Until your new parser is stable enough (in my opinion), I’m going to use Tagger with AP (I’m still using the latest stable version of Tagger (Build 3.2b20070429).
Speaking of Stable releases, I would like to recommend you have 2 versions of Tagger, the latest stable version (Build 3.2b20070429) and the latest alpha version (Alpha Build 4.0b20070913). I would be a bad idea to do this with LongDescription (you guessed it, the latest build still doesn’t release iTunes)
I have both stable versions, I would be happy to e-mail it to you.
Um, isn’t it like this already? Anyway, I finished coding my parser in about three hours yesterday and it reads metadata perfectly. I have yet to implement code that will write an updated file, but I should have that working in a few days. Right now I’ve configured my private working build to use my code to load files, and it’s impossible to tell that it’s being used in place of AtomicParsley. Most of what I coded I learned from the AtomicParsley website and from that project’s lead programmer himself, so I’m confident that it will work out for the best. Having the file parser written in the same language as the client program will save me a ton of problems and potential bugs.
That’s good news i think! Looking forward to that!