On Wed, Sep 30, 2009 at 09:41:26AM +0200, David Schueler wrote: > > I will update the podcarve script in the next days with the new fields. >
great! please try to include a hexdump in the iTunesDB parser. that would make it easier to spot the equivalent field in the iTunesSD and it would help to find errors in the parser like this one: > chunkType: mhlt: list of all the songs on the iPod > > Warning: unpack() [function.unpack]: Type V: not enough input, need 4, have > 0 in /home/evil/public_html/ipod/carve_itunesdb.php on line 95 > > Warning: unpack() [function.unpack]: Type V: not enough input, need 4, have > 0 in /home/evil/public_html/ipod/carve_itunesdb.php on line 95 > [header_id] => tlhm > [header_length] => > [number_of_songs]=> cheers -henrik BTW: does anybody have experience in writing formal grammar descriptions? it would be great if we could put down at least part of the knowledge in a machine readable form, something like EBNF or ABNF ? that would make sharing knowledge among different projects much easier as it removes the (programming)language barrier. i also took a brief look at Eyapp but i don't know if it will be any use for parsing binary data. it very well may be. if we could formalize the structure description, we might be able to generate the parsing/writing code from that description. _______________________________________________ Bug-gnupod mailing list [email protected] http://lists.gnu.org/mailman/listinfo/bug-gnupod
