Matthias Reichl wrote: > I just noticed that the current kaa-metadata release reports a > wrong length for my VBR MP3s. kaa-metadata 0.7.5 worked fine. > I encoded my MP3s using LAME and they contain a XING header at > the very beginning. > > I did some testing and it seems that r3821 (new find_header > function in audio/eyeD3/mp3.py) is causing this problems. > If I use the old function (__EYED3_ORIG_find_header) instead, > mminfo reports the correct length. > > Then I added some debug statements and noticed that the old find_header > code returned a header_pos value of 0, whereas the new find_header > function returned a value of 553 for my test-file, thus skipping > over the xing header.
Just to keep Jason busy, the log reports: trying video/quicktime invalid header: <unpritable characters> trying video/mpeg Also: The message: No Type found by Extension. Trying all does not say what the filename.extension is. Do you have a different strategy for debug messages in kaa? In freevo-1 cyclic messages go to level 2 debugging and level 1 is left for user actions and what happens for the action. The message: IOChannel read data: etc is cyclic, every 5 seconds. Cheers Duncan ------------------------------------------------------------------------------ Register Now for Creativity and Technology (CaT), June 3rd, NYC. CaT is a gathering of tech-side developers & brand creativity professionals. Meet the minds behind Google Creative Lab, Visual Complexity, Processing, & iPhoneDevCamp as they present alongside digital heavyweights like Barbarian Group, R/GA, & Big Spaceship. http://p.sf.net/sfu/creativitycat-com _______________________________________________ Freevo-devel mailing list Freevo-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freevo-devel
