[Vorbis-dev] ogg only encoding

[Stephen Whiters-Ridley]

So, I abandoned the hope of using the ogg python bindings to do pure ogg
container encoding.
I started looking at the libogg in the hopes of retooling the bindings to
follow a better object model
and it actually looks like the problem is down in libogg, not the bindings.
Am I crazy or does libogg
rely on libvorbis to return ogg_packets, and that there are no functions
that will build an ogg_packet for you from
your own data like an array of bytes? It looks like API users are required
to fill in all the meta
fields of the ogg_packet themselves? Is this correct?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.xiph.org/pipermail/vorbis-dev/attachments/20060605/f5093ff6/attachment.html