search for: ventismedia

Adam Rosi-Kessel wrote: > Yes, it was Mediamonkey. They claim that it was due to a bug in vorbis > libraries. All software has bugs, but this explanation doesn't really add up. libvorbis is the codec. If they had blamed libogg, which does the container, then yes, that would have been a believable explanation :-). Erik --

...could be useful. Does it actually check the CRC, or is there some way for me to do so? I see the output from hogg dumpraw, but am not sure how to interpret it. In other news, the MediaMonkey developers believe this is a bug in a (possibly) older version of vorbis_comment_add_tag(): http://www.ventismedia.com/mantis/view.php?id=5809 Does this seem right and/or shed any light on how to undo the damage? Adam

...actually check the CRC, or is there some way for me to do so? I > see the output from hogg dumpraw, but am not sure how to interpret it. > > In other news, the MediaMonkey developers believe this is a bug in a > (possibly) older version of vorbis_comment_add_tag(): > > http://www.ventismedia.com/mantis/view.php?id=5809 > > Does this seem right and/or shed any light on how to undo the damage? One other potentially interesting observation -- Ogg::Vorbis::Header::PurePerl has no trouble reading the headers on these corrupted files (and outputting the contents correctly), while O...

Adam Rosi-Kessel wrote, on 6/19/2009 3:56 PM: > Conrad Parker wrote, on 6/18/2009 3:15 PM: >> Hopefully at some point the vorbis data in the file becomes valid. >> Perhaps we just need to know the original encoding settings to create >> a new file with valid codebooks and splice them together: oggz-dump -r >> should be ok for that, just take the first 3 packets of the