Hello Matthew, This is an interesting topic. I've been reading about it and here is what I figured out.
Current situation: - Pyglet binds into AVbin which is a thin C wrapper around Libav. This guarantees a stable ABI (Application Binary Interface). - Pyglet uses AVbin in order to implement class AVbinSource(StreamingSource) found in pyglet/media/sources/avbin.py - Libav is a fork from FFmpeg (see here <https://en.wikipedia.org/wiki/Libav> ). - It seems that today FFmpeg is better maintained than Libav. So in order to use FFmpeg over Libav, the path of least resistance would be to update AVbin in order to link to FFmpeg instead of Libav. The function names seem pretty identical. Maybe some changes might be required due to the new features of FFmpeg, but in general the code could be left pretty untouched. This has also the advantage that you would not have to change the pyglet code for AVbin. I'm no expert in this area. But this what I came up with so far. Let me know what you think. Dan Le vendredi 20 janvier 2017 12:24:19 UTC+1, Matthew Macdonald-Wallace a écrit : > > > I'm happy to explore what's involved in creating bindings for FFMpeg > instead, as this seems to be included in pretty much all modern linux > distros, however I've never written bindings before for anything, so if > anyone is willing to help me do this that would be great. > > -- You received this message because you are subscribed to the Google Groups "pyglet-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/pyglet-users. For more options, visit https://groups.google.com/d/optout.
