[Vorbis-dev] packed ogss

[Arc Riley]

On Fri, Jul 30, 2004 at 10:31:12AM +0100, Tony wrote:
> The serials in the oggs will be the same as others in certain cases as there
> not made completely unique as there is sometimes a bit of swapping around of
> which oggs are going into which chains without them being re-encoded,
>
> I don't personally add any extra info between the files I just convert the
> wavs to oggs then do a binary copy to concatenate all the files together, I
> do it this way as ive never seen any documentation on there being a special
> way to create chained files.

If you've run your pieces, prior to chaining them, through a tool like
vcut then the reserializer is what you need.  vcut produced legal
bitstreams which would play, even chained, but didn't change the
serialno on either piece, so as it's playing through it finds the header
for a stream it's already playing, then pages are missing, then it
continues playing what it believes to be the same bitstream.

The reserializer, however, will see Page 0 and record "this is a new
bitstream", thereafter every page marked with that serialno will have a
new randomised serialno, until next Page 0 is found, etc.  This will
even work with muxed files, tho you don't need it to for your uses.

Enough guessing, try the tool (refer to my earlier email on where to get
my libogg2 branch and py-ogg2 from svn) and see if it works.  It makes a
copy of your original as it works, so there's no risk.  Run the result
through ogginfo and see if it still complains.  Worse it should complain
of is "hole in data", which is a perfectly OK thing to have :-)