On Tue, Nov 15, 2011 at 6:04 AM, Rémy Sanchez <[email protected]> wrote: > On Mon, 14 Nov 2011 22:33:02 -0700, Nathan <[email protected]> wrote: >> >> On Sun, Nov 13, 2011 at 9:35 PM, Rémy Sanchez >> <[email protected]> wrote: >>> >>> On Sunday 13 November 2011 07:05:21 Nathan wrote: >>>> >>>> FIRST, does anyone know how/where I could find out what video formats >>>> AVbin is supposed to support? I'll search around in the ffmpeg >>>> source, but I'm not sure what I'm even looking for, or where I'd look >>>> for it. >>> >>> "ffmpeg -formats" looks like a good place to start. The output will >>> probably >>> depend on the compilation options though. >> >> Interesting idea. Unfortunately, it looks like the build process of >> ffmpeg from within avbin is completely customized, and no ffmpeg >> binary is produced. Perhaps I will be able to find a way to get the >> binary produced if I muck around in the build process for awhile. > > Well, you'll find how to list the formats in the function behind that > (cmdutils.c, function "int opt_formats(const char *opt, const char *arg)"). > The codecs registration looks pretty static though : > http://cekirdek.pardus.org.tr/~ismail/ffmpeg-docs/allformats_8c-source.html
That's a lot of formats! >>>> SECOND, what video formats are people actually using pyglet to decode? >>> >>> If I can make a suggestion, don't support too much formats and >>> concentrate on >>> free stuffs with few IP problems, let's say WebM for instance. Just my >>> opinion... >> >> Well, I agree with the principle, but *I'm* not really supporting >> formats or not. FFmpeg does...or not. AVbin is just a light wrapper >> for some FFmpeg functions. What I'm really interested in here is what >> video formats people are actually using, so that I can prioritize >> efforts to make the more relevant unit tests first. > > The idea behind is that no one will use Pyglet to make video players sensu > stricto, so for specific applications you generally make custom videos, and > then start wondering what bloody codec you'll use among the hundred > supported by ffmpeg. Then IMHO if your graphical library makes the choice in > your place, this is not too bad. Not to manually disable other formats, but > at least say "Optimized for codec XXX", which would be true because there > will be unit tests for that :) > > And I suggested WebM as it is most probably the codec I am going to use for > my application. Don't know for the others though. Ah, I see. Great suggestion! A list of recommended formats would definitely help steer pyglet users in the right direction. I'll put WebM up at the top of the list, seeing as how no one else who reads the mailing list apparently uses video in pyglet (that is willing to talk about it). ~ Nathan -- You received this message because you are subscribed to the Google Groups "pyglet-users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/pyglet-users?hl=en.
