s7ephen at gmail.com
Mon May 22 20:35:44 PDT 2006
I have been trying to use pyogg (without pyvorbis) to get API access
to purely the ogg container. I don't often expect API documentation,
but even big parts of the python code lack docstrings, which made it a
bit difficult. I have my heart set on ogg for this particular project,
so (after I propose the question, and if the answer is no) I am
willing to make modifications to the ogg bindings to make it work,
and would like to submit any changes for consideration in future
releases of pyogg. That said, here is the question. For the purposes
of encoding, is it up to pyogg user to handpack the packets? (it seems
like this would kinda defy the purpose of an API if so). essentially I
would like to instantiate a OggStreamState object, and use one of its
methods to push pages into the stream (encoding) to be ultimately
written to file. However, all the methods that look like they would be
responsible for creating packets/pages from raw data report that they
expect an object of type OggPacket, which is a class that doesnt
seemed to be definite
anywhere in pyogg. From looking at some of the sample "encoders" out
on the web, it looks like OggPacket creation is done actually done in
ogg.vorbis? is this correct?
Thank you very much for you help.
On 5/22/06, Ralph Giles <giles at xiph.org> wrote:
> On Mon, May 22, 2006 at 04:34:42PM -0400, Stephen Whiters-Ridley wrote:
> > I have been trying to get in contact with some of the pyogg folks via
> > IRC and individual email, but have been having little success. I
> > wanted to get some information about the svn commital/maintainers
> > process....
> The python stuff isn't very actively maintained; this (or the ogg-dev
> list) is a good place to ask questions. What can we do for you?
More information about the Vorbis-dev