search for: unfixed_corrupted

...t realized that the hogg tools will fix the CRC issues (by design accident: hogg ignores the CRC on reading but sets it correctly on writing). "hogg rip" rewrites the pages (fixing the CRC), and "hogg reconstruct" also rewrites the I've uploaded the outputs of these, run on unfixed_corrupted.ogg, to: http://seq.kfish.org/~conrad/tmp/484 These pass oggz-validate without warnings about the headers, and have the Vorbis headers intact (including large COVERART). However in the ripped version the codebooks are not visible to libogg, so something else is corrupt there. For the reconstru...

Can I fix the checksum with a hex editor? Sent from my iPhone On Jun 25, 2009, at 3:23 PM, Monty Montgomery <monty at xiph.org> wrote: > Confirmed--- the checksum on the second page (the comment page where > the album art was added) is incorrect. Vorbis players are not allowed > to decode any stream in which one of the setup headers is corrupt, and > a bad checksum counts as

...; In other words, everything in between ^Evorbis and OggS is the setup > header? no, you can't just rip the bytes out because the setup header may be split across two pages. eg. looking at the start of the stream with "hogg pagedump": conrad at chichai:~/share/484$ hogg pagedump unfixed_corrupted.ogg |head -n 12 0x00000000: Vorbis serialno 1225743615, granulepos 0|0 *** bos: 58 bytes [30] 00:00:00.000 0x0000003a: Vorbis serialno 1225743615, granulepos 0|0 (incplt): 53525 bytes [49719,3570] 00:00:00.000 0x0000d1c0: Vorbis serialno 1225743615, granulepos 0|0 (cont): 1421 byt...

On Fri, Jul 17, 2009 at 12:48:27PM -0700, Ralph Giles wrote: > > In my ongoing quest to restore corrupted ogg files, I'm trying to find > > an easy way to identify the setup header without having to actually > > decode it. I understand that it starts with [packet_type] = 5 and then > > the string 'vorbis', but is there some way to figure out where it > >