On Tue, Dec 13, 2011 at 11:15 PM, Nathan <[email protected]> wrote:
> On Tue, Dec 13, 2011 at 3:52 AM, anatoly techtonik <[email protected]> > wrote: > > On Monday, December 12, 2011 8:11:12 PM UTC+3, Nathan wrote: > >> > >> AVbin doesn't "play" a video file, per se. Some application or > >> framework (like Pyglet, for example) uses AVbin to decode a video > >> frame by frame and then presents the visual/audio information to some > >> device to play it. > >> > >> You can tell that AVbin has nothing left to decode from a video file > >> when a call to avbin_decode_video() returns 0 (successful finish) or > >> -1 (hit an error). > > > > I couldn't find any documentation on AVbin. pyglet docs are also very > > limited in this regard. Are there any plans to provide some tutorial and > > Python bindings for AVbin out of the box? So that people can > `easy_install > > avbin` and `import avbin` to play with its API/features? > > AVbin documentation is currently in the form of comments in > include/avbin.h in the AVbin source. You WILL need to read that if > you want to use AVbin's interface directly. It's on the Version 9 > roadmap to get online documentation generated (in fact, it looks like > it's all set up to be generated by Doxygen, as soon as I figure out > how to use Doxygen). > Well, to tell the truth, I am not really interested in Doxygen API reference for C part of the library. Though I am curious about the process of stripping FFmpeg to a minimal set of bare functionality needed, but what really interests me is playing with AVbin from Python console. > Pyglet includes a full set of python bindings already in > pyglet.media.avbin (AVbin was originally created just for that > purpose, after all). I don't have any plans to create or maintain a > separate set of Python bindings, though I don't mind if someone else > wants to. The main motivation here is not to create YetAnothePythonBinding-for-FFmpeg, but to make it possible for pyglet to just `import AVbin` - that would be useful for other applications as well. AVbin is already an external dependency, so it will be convenient to have it wrapped in Python package. Another useful outcome of clearly separated API is that FFmpeg is not the only A/V library out there, and it becomes evident for other that it is possible to create non-GPLed AVbin replacement that only operates with WebM, for example. > If you wanted to, you could take Pyglet's version and adapt > it to your own use. (see pyglet/media/avbin.py) I don't know why > that file isn't included in Pyglet's API reference. > API reference is still a reference - not a replacement for documentation explaining concepts and use cases. Good documentation is inspiring. Good API reference is full, but concise. It is quite hard to pursue all these goals. I don't currently have any plans to make a tutorial. There IS an > example C program in AVbin under example/avbin_dump.c that may be > useful towards that end, though. > Example should be available from the web. First you read an example, and then (if it is interesting enough) download code. > Those were good questions. Thanks! > No problem. I will probably have more if these are "fixed". =) -- You received this message because you are subscribed to the Google Groups "pyglet-users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/pyglet-users?hl=en.
