Hello, Pyglet currently Requires AVBIn for transcoding. I sent Nathan an email about this earlier, and he basically said what is on the web site.
I cannot quite see the requirement for a separate binary in this regard, but perhaps someone can furnish the answers. The points of interest are: (1) Licensing. AVbin is under LGPL or GPL depending on the features used. And pyglet is under what appears to be the 3 clause BSD license.which means it should be compatible.(http://www.gnu.org/licenses/license-list.html#ModifiedBSD) In any case dynamic linking though ctypes should be possible, and there shouldn't be distribution problems as far as I am aware. However, we could have a chat with the Free Software Foundation lawyers about this. (2) Use of libAV rather than FFmpeg. This could be a thorny issue, but ffmpeg would seem to be the better library to use. There was some madness when Libav forked FFmpeg, and some distributions printed a message saying FFmpeg was deprecated, which was wholly inaccurate and rather confusing, but that is war for you (3) To provide a stable API. I don't know what this means, does it mean between ffmpeg and avbin when the transition happed, or between major releases of ffmpeg? Because there are releases with of FFmpeg wth a stable to a point, hence I am not quite sure how AVbin serves in this respect. If FSML doesn't have a problem, then Where this is all going is investigating the possibility of removing the AVBin binary in order to make the installation of pyglet easier. I would be happy to investigate that possibly, but can't commit to doing any said work right at the moment. I await enlightenment! Jason -- 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 http://groups.google.com/group/pyglet-users. For more options, visit https://groups.google.com/d/optout.
