I have several corrupted ogg files; I believe they were created several years ago with grip, and that the corruption is not disk corruption but just something wrong with the encoder at the time. I would rather not have to re-rip these discs. The error I see with ogginfo is Warning: Hole in data (18000 bytes) found at approximate offset 702086827724505088 bytes. Corrupted ogg. Warning: Hole in data (22500 bytes) found at approximate offset 702086827724505088 bytes. Corrupted ogg. [etc., and then:] Warning: sequence number gap in stream 1. Got page 4 when expecting page 1. Indicates missing data. Warning: discontinuity in stream (1) Warning: Could not decode vorbis header packet 1 - invalid vorbis stream (1) [...] Vorbis stream 1: Total data length: 0 bytes Playback length: 0m:00.000s Average bitrate: nan kb/s Logical stream 1 ended I've googled around for an ogg corruption fixer but there doesn't seem to be anything out there. I've tried rewriting them with mencoder and ffmpeg, but it doesn't make any difference (and I see similar errors during the rewrite). Is there really no tool to repair corrupted ogg files? Would just removing the header possibly fix the problem? If so, how would I do that? Any other suggestions? Thanks, Adam
Use oggz-sort from the liboggz package. -Ivo
Ivo Emanuel Gon?alves wrote, on 3/23/2009 12:59 PM:> Use oggz-sort from the liboggz package.(just BTW, in Debian, these commands are in the oggz-tools package) The result is still corrupted -- although the errors are slightly different. Although oddly, oggz-validate gives no errors on either the source or target file. # oggz-sort input.ogg -o fixed.ogg # ogginfo input.ogg |head -5 Processing file "input.ogg"... New logical stream (#1, serial: 3ab6a24e): type vorbis Warning: Hole in data (18000 bytes) found at approximate offset 598803103457738752 bytes. Corrupted ogg. Warning: Hole in data (22500 bytes) found at approximate offset 598803103457738752 bytes. Corrupted ogg. # ogginfo fixed.ogg |head -5 Processing file "fixed.ogg"... New logical stream (#1, serial: 3ab6a24e): type vorbis Warning: sequence number gap in stream 1. Got page 4 when expecting page 1. Indicates missing data. Warning: discontinuity in stream (1) Warning: Could not decode vorbis header packet 1 - invalid vorbis stream (1) Warning: Could not decode vorbis header packet 1 - invalid vorbis stream (1) Anything else I might try?
2009/3/23 Adam Rosi-Kessel <adam at rosi-kessel.org>:> The result is still corrupted -- although the errors are slightly different. > Although oddly, oggz-validate gives no errors on either the source or target > file.If compiling doesn't scare you, use the latest version from SVN (svn.annodex.net). If that still doesn't solve it, open a bug in the tracker (trac.annodex.net) and attach or link an example file. I personally don't know of any other decent tool to fix Ogg files. -Ivo
Seemingly Similar Threads
- Fixing ogg vorbis corruption caused by bad metadata
- Fixing ogg vorbis corruption caused by bad metadata
- Fixing ogg vorbis corruption caused by bad metadata
- Fixing ogg vorbis corruption caused by bad metadata
- Fixing ogg vorbis corruption caused by bad metadata