Hi,
I just passed my full vorbis collection to OggTester which is a GUI for OggInfo & I found several HOLE & TRUNCATED files in it, but by luck I know the guys who created these files so I know that:
1- All files with HOLE were created with EAC+oggenc 1.01 by a friend of mine which suspect she had trouble with bad RAM, I already posted here for this problem a year ago but didn't found a satisfaying answer
2- All files that are TRUNCATED were created with "Easy CD-DA Extractor Ripper for Winamp3 (http://www.poikosoft.com)" but as ALL the files created by this soft are reported "EOS not set on stream 1" by Ogginfo ... so I suspect I just found a bug in this soft, it seems the Ogg files created by this soft are ALL "unclosed" Oggs
so ... I listened carefully to all these HOLE-TRUNCATED files,
NONE of these files sounds damaged or incomplete ...
so with time being familiar with them (it's 1 year I got them on my HD) I had the idea that maybe only the OGG container was damaged & not the vorbis audio stream ...
As I know retagging Oggs rewritte the whole file ... I said to myself that maybe retagging might fix the error by repacking the vorbis stream in cleaner Oggs
so I retagged all with MP3tag, & "oh magic", the files are now reported OK ...
so the questions are?:
- am i right in thinking retagging can fix basic Ogg Container error ?
- how can the container only become damaged & not the audio stream in it ? Is that what you guys call container error resilency ?
... I saw a lot of people complaining here about vorbis comment being slow ...
... it may be slow (personnaly I won't call it slow, just not instantly) but if you can fix container error by retagging, finally it's not that bad afterall ...