AVbin vs PyFFmpeg

[anatoly techtonik]

How does AVbin compare to PyFFmpeg? I've asked this on PyFFmpeg list, but haven't receive any reply yet. Would be nice if people here could add something to the thread.

[Nathan]

I have no experience with PyFFmpeg, but from what I read on their site it appears that they are shooting for a general-purpose encoding/decoding/transcoding library + utiltities.  In other words, it appears they are aiming at exposing as much FFmpeg functionality as they can.

AVbin, in contrast, is (currently) designed specifically to meet only the audio/video decoding needs of the Pyglet project.  I don't believe anyone has any plans to add any other functionality to AVbin other than decoding.

Does that help?

~ Nathan

On Wed, Nov 16, 2011 at 8:45 AM, anatoly techtonik <tech...@gmail.com> wrote:

How does AVbin compare to PyFFmpeg? I've asked this on PyFFmpeg list, but haven't receive any reply yet. Would be nice if people here could add something to the thread.

--
You received this message because you are subscribed to the Google Groups "pyglet-users" group.
To view this discussion on the web visit https://groups.google.com/d/msg/pyglet-users/-/E3rQ8efe4RIJ.
To post to this group, send email to pyglet...@googlegroups.com.
To unsubscribe from this group, send email to pyglet-users...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/pyglet-users?hl=en.

[anatoly techtonik]

Probably the main question is if there is any difference in the development/maintenance process of the wrapper? If both projects do the same, why not to join efforts instead of reinventing the wheel? It is always possible to strip unneeded API from the result. 

[Nathan]

Seeing as how the development/maintenance, much of the basic functionality, the target goal, and the supported platforms are _not_ the same, the question isn't particularly relevant.  At least not at this point in time.

~ Nathan

On Wed, Nov 16, 2011 at 11:17 AM, anatoly techtonik <tech...@gmail.com> wrote:

Probably the main question is if there is any difference in the development/maintenance process of the wrapper? If both projects do the same, why not to join efforts instead of reinventing the wheel? It is always possible to strip unneeded API from the result. 

--

You received this message because you are subscribed to the Google Groups "pyglet-users" group.

To view this discussion on the web visit https://groups.google.com/d/msg/pyglet-users/-/swenBeHbkLgJ.