SFML uses these libraries, but there is no video rendition available there:
- *libogg <http://www.vorbis.com/>* is distributed under the BSD 3 license <http://opensource.org/licenses/BSD-3-Clause> - *libvorbis <http://www.vorbis.com/>* is distributed under the BSD 3 license <http://opensource.org/licenses/BSD-3-Clause> - *libflac <https://xiph.org/flac/>* is distributed under the BSD 3 license <http://opensource.org/licenses/BSD-3-Clause> There are different potential possibilities, whereby one could choose which libraries to depend on, but that's jumping the gun I think. Having pyglet be self contained in some respect without the need for AVbin which needs maintenance would seem to be preferable, even if some maintenance might then fall into a pyglet layer. And, as I say ffmpeg API's don't presumably change overnight, nor do new breaking API's have to be adopted straight away. On the other hand, I don't know the reality of that. I just assume that it cannot be as bad as made out, otherwise no applications would be able to make use of it. On Thursday, 12 November 2015 23:47:27 UTC, Benjamin Moran wrote: > > Just to add to the conversation, one of the main things that attracted me > to pyglet in the first place was that it's a "pure" Python module. I love > PySDL2, but there always seems to be that one person who has trouble with > the SDL2 modules. > > Currently pyglet supports png and wav decoding natively, which suits my > purposes for the moment. If I were to dream, I'd wish for native python > decoding support for at least one lossless audio format. Perhapps Ogg > Vorbis would make the most sense. > > -Ben > > > > On Friday, November 13, 2015 at 5:36:52 AM UTC+9, Jason Spashett wrote: >> >> 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.
