Hello, Claudio, Bethany and I have been busy with the FFmpeg bindings. We have seen some nice progress. While busy with the development, a couple of questions arose for which we might need Rob or Benjamin to help answering them.
First question is about the inclusion of the ffmpeg binding code into pyglet. I wanted to make sure that the idea is still to have in pyglet/media/sources a ffmpeg.py file which would implement a FFmpegSource class deriving from StreamingSource. Or do you want this to be a separate project? The second question is about the location of FFmpeg itself. On Linux and I guess on Mac OS, the binaries could be installed on the machine (in the default location) and pyglet would find them easily. But on Windows, this is another story. We need a mechanism where the developer can tell pyglet where to look for the FFmpeg binaries (the dll files). At the moment, I've added a pyglet option which is documented like this: #: ffmpeg_libs_win #: A tuple containing the FFmpeg dll filenames for Windows. As on this #: platform there is no standard way to find the dll files, and the #: FFmpeg dll names have version number appended at the end, it's easier #: for the developer to state what are the filenames, and hence giving #: the version for each dll files. By default, the filenames are #: 'avcodec-57', 'avformat-57', 'avutil-55', 'swresample-2', 'swscale-4' I'm facing a couple of hurdles. First of all each dll have its version appended to the end of the file name. This is probably anyway a good thing as we have to explicitly state which version we want to use. The other problem is the location of those files. Maybe we could create an empty dll folder in the pyglet structure to allow developers to drop any dll they need and this would be a location where pyglet would look for binaries? More info can be found here: dlls placement and licences, integration <https://bitbucket.org/dangillet/pyglet/issues/7/dlls-placement-and-licences-integration> I understand you don't want to create any dependencies. But we also need to provide the users with an "easy" way of using those external libraries. And a final question: Claudio developed a really awesome utility for measuring video player quality including numbers of frames dropped, difference between video and audio times and other things. Do you think it would be valuable to include it in pyglet for future development with the media player? Where should this utility suite live? In the tools folder maybe? Thanks, Daniel -- 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.
