similar to: Fixing corrupted ogg files

> Is there any way to understand exactly how it is invalid? I can replicate > this corruption simply by adding large album art to any ogg file with the > latest release of MediaMonkey. The second page is corrupt. The basic structure looks correct, first guess would be bad checksum. I'll look more closely in just a bit. This might explain why some players might accept it--- if

2009/6/18 Adam Rosi-Kessel <adam at rosi-kessel.org>: > On Thu, Jun 18, 2009 at 11:12:30PM +0900, Conrad Parker wrote: >> yow, that's pretty badly corrupted, the vorbis codebooks (usually the >> third packet) is completely gone. It looks like you'd need to throw >> away the first 16 packets, start with fresh headers, and copy in the >> rest of the data

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

2009/6/30 Adam Rosi-Kessel <adam at rosi-kessel.org>: > Monty Montgomery wrote, on 6/25/2009 2:16 PM: >>> Is there any way to understand exactly how it is invalid? I can replicate >>> this corruption simply by adding large album art to any ogg file with the >>> latest release of MediaMonkey. >> The second page is corrupt. ?The basic structure looks

I have over 1,000 ogg vorbis files that are no longer playable or editable. I believe the main cause was a MediaMonkey plugin that automatically fetched album art and added it to the header. The plugin itself just uses the generic MediaMonkey metadata facility, but something happened -- perhaps when the album art bitmap image was too large -- that caused the files to no longer work.

On 6/18/09, Conrad Parker <conrad at metadecks.org> wrote: > This sounds like it needs a new tool specifically for fixing broken > Ogg files. I see two solutions: 1) the new vcut which I reckon will fix the problem since it has to split and rebuild the audio in a new Ogg 2) an Hex editor, even if just to check what's wrong in the metadata section -Ivo

Adam Rosi-Kessel wrote, on 6/30/2009 11:14 AM: > Conrad Parker wrote, on 6/30/2009 11:05 AM: >>> http://adam.rosi-kessel.org/bugs/liboggz/484/other_corruption.ogg >>> Yet also won't play or process properly with oggz or hogg tools. Any >>> ideas whether this is the same or different root cause? (In all of these >>> cases, I'm reasonably certain that

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

ogg.k.ogg.k at googlemail.com wrote, on 7/14/2009 7:16 AM: >> easy to replace. The second packet is the metadata, which we can lose. >> It's just the third packet that needs to be reconstructed. After that, >> you could start at any packet division in the rest of the file and it >> would play fine? So this generic restore tool that I'm positing would >> just

2009/6/18 Adam Rosi-Kessel <adam at rosi-kessel.org>: > Ivo Emanuel Gon?alves wrote, on 6/18/2009 6:14 AM: >> >> On 6/18/09, Conrad Parker<conrad at metadecks.org> ?wrote: >>> >>> This sounds like it needs a new tool specifically for fixing broken >>> Ogg files. >> >> I see two solutions: >> >> 1) the new vcut which I

On Tue, Jul 14, 2009 at 9:48 AM, Adam Rosi-Kessel<adam at rosi-kessel.org> wrote: > The only issue I'm noticing is ogginfo reports: > > Warning: sequence number gap in stream 1. Got page 14 when expecting > page 2. Indicates missing data. > Warning: discontinuity in stream (1) I'd guess this is flagging the data that was overwritten by the bad tagging code. Some

Adam Rosi-Kessel <adam at rosi-kessel.org> wrote: > So I've written a script to do the following: ... I have got lost. Did you manage to identify the rogue software that corrupted the files in the first place? In the greater scheme of things, fixing this (prevention) is more important than repairing the files (cure). Regards, Martin -- Martin J Leese E-mail: martin.leese

Conrad Parker wrote, on 6/20/2009 10:24 PM: >> How about another approach -- is there a tool that will verify the page >> checksums? oggz-validate doesn't seem to do this. If the page checksums >> are okay, then doesn't that suggest the streams are also recoverable? > If the page checksums are bad then the page will get rejected by > libogg, and oggz-validate

Hi, The Annodex Foundation is pleased to announce the general availability of the Annodex Media Validation Service, a free service that checks Web-accessible Ogg, CMML and Annodex media resources for conformance to Annodex and Xiph.Org specifications: http://validator.annodex.org/ Details about the operation of this service are available at: http://validator.annodex.org/about.html

Hi, The Annodex Foundation is pleased to announce the general availability of the Annodex Media Validation Service, a free service that checks Web-accessible Ogg, CMML and Annodex media resources for conformance to Annodex and Xiph.Org specifications: http://validator.annodex.org/ Details about the operation of this service are available at: http://validator.annodex.org/about.html

Hi, The Annodex Foundation is pleased to announce the general availability of the Annodex Media Validation Service, a free service that checks Web-accessible Ogg, CMML and Annodex media resources for conformance to Annodex and Xiph.Org specifications: http://validator.annodex.org/ Details about the operation of this service are available at: http://validator.annodex.org/about.html

Hi, The Annodex Foundation is pleased to announce the general availability of the Annodex Media Validation Service, a free service that checks Web-accessible Ogg, CMML and Annodex media resources for conformance to Annodex and Xiph.Org specifications: http://validator.annodex.org/ Details about the operation of this service are available at: http://validator.annodex.org/about.html

Hi, The Annodex Foundation is pleased to announce the general availability of the Annodex Media Validation Service, a free service that checks Web-accessible Ogg, CMML and Annodex media resources for conformance to Annodex and Xiph.Org specifications: http://validator.annodex.org/ Details about the operation of this service are available at: http://validator.annodex.org/about.html

While testing the new vcut, some of the early results had badly framed headers. I actually didn't notice it at first, because I was testing with oggz-validate, but ogginfo does identify the problem: "WARNING: Vorbis stream X does not have headers correctly framed. Terminal header page contains additional packets or has non-zero granulepos" Conrad (or someone else) may want to

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 > >