[FFmpeg-devel] [PATCH] cmdutils: include threading caps in codecs listing.

[Michael Bradshaw]

On Wed, May 30, 2012 at 2:03 PM, Reimar Döffinger
<Reimar.Doeffinger at gmx.de> wrote:
> On Wed, May 30, 2012 at 01:51:32PM -0600, Michael Bradshaw wrote:
>> On Wed, May 30, 2012 at 1:47 PM, Reimar Döffinger
>> <Reimar.Doeffinger at gmx.de> wrote:
>> > On Wed, May 30, 2012 at 09:40:49PM +0200, Nicolas George wrote:
>> >> -           " D..... = Decoding supported\n"
>> >> -           " .E.... = Encoding supported\n"
>> >> -           " ..V... = Video codec\n"
>> >> -           " ..A... = Audio codec\n"
>> >> -           " ..S... = Subtitle codec\n"
>> >> -           " ...S.. = Supports draw_horiz_band\n"
>> >> -           " ....D. = Supports direct rendering method 1\n"
>> >> -           " .....T = Supports weird frame truncation\n"
>> >> -           " ------\n");
>> >> +           " D....... = Decoding supported\n"
>> >> +           " .E...... = Encoding supported\n"
>> >> +           " ..V..... = Video codec\n"
>> >> +           " ..A..... = Audio codec\n"
>> >> +           " ..S..... = Subtitle codec\n"
>> >> +           " ...S.... = Supports draw_horiz_band\n"
>> >> +           " ....D... = Supports direct rendering method 1\n"
>> >> +           " .....T.. = Supports weird frame truncation\n"
>> >> +           " ......F. = Supports frame-based multi-threading\n"
>> >> +           " .......S = Supports slice-based multi-threading\n"
>> >> +           " --------\n");
>> >
>> > I don't have much of an opinion, but I was wondering if maybe
>> > F Supports frame-based multi-threading
>> > S Supports slice-based multi-threading
>> > B Supports both frame-based and slice-based multi-threading
>> > would be better
>>
>> Personally, I like them separate. None of the other fields have a
>> combined field (i.e. there's no C = supports decoding and encoding),
>> and plus I don't have to remember what "B" is for.
>
> Well, there is one argument for it (and using "E" for "either" instead):
> it - currently at least - is not possible to use both, you have to
> decide for one. However it would be possible to support both at the
> same time, in which case "B" would become useful.
> With two separate fields it gets a bit hard to signal the difference
> between supporting both or either...
> But bikeshed, as said I only wondered...

I'll be fine either way, and don't want to hold up this patch. I just
personally don't think "B" clarifies that (valid) point very well.

But yes, it's a bikeshed. I'm fine either way.