Re: [Cellar] FFV1: FFmpeg default version is "0"?

"Peter B." <pb@das-werkstatt.com> Tue, 08 November 2022 12:04 UTC

Return-Path: <pb@das-werkstatt.com>
X-Original-To: cellar@ietfa.amsl.com
Delivered-To: cellar@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BC341C14CF09 for <cellar@ietfa.amsl.com>; Tue, 8 Nov 2022 04:04:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.206
X-Spam-Level:
X-Spam-Status: No, score=-4.206 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iVLHH1WY4jiX for <cellar@ietfa.amsl.com>; Tue, 8 Nov 2022 04:04:55 -0800 (PST)
Received: from zucker.schokokeks.org (zucker.schokokeks.org [178.63.68.96]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0F973C14CE34 for <cellar@ietf.org>; Tue, 8 Nov 2022 04:04:54 -0800 (PST)
Message-ID: <4927b23d-937c-b15c-92c6-db3b07b2c9db@das-werkstatt.com>
Date: Tue, 08 Nov 2022 13:04:47 +0100
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.2.2
Content-Language: en-US
To: cellar@ietf.org
References: <8ccfd556-1a7e-2e58-bd5f-15e47b5c00b5@das-werkstatt.com> <4cb08010-b3b0-742d-6d40-02a64a4f35dd@mediaarea.net>
From: "Peter B." <pb@das-werkstatt.com>
In-Reply-To: <4cb08010-b3b0-742d-6d40-02a64a4f35dd@mediaarea.net>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/cellar/EXCNoElNZvYYEw5O_K8hb4Ltjdk>
Subject: Re: [Cellar] FFV1: FFmpeg default version is "0"?
X-BeenThere: cellar@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Codec Encoding for LossLess Archiving and Realtime transmission <cellar.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/cellar>, <mailto:cellar-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/cellar/>
List-Post: <mailto:cellar@ietf.org>
List-Help: <mailto:cellar-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/cellar>, <mailto:cellar-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 08 Nov 2022 12:04:59 -0000

Thanks Jérôme!



On 08.11.22 12:49, Jerome Martinez wrote:
> Actually it depends on the count of pixels (trigger is if > 720x576)

Thanks! Forgot about that.


> It is a "political" choice from FFmpeg, also for the count of slices 
> by default (always 4, either 720x577 or 4096x2160).
>
> I personally don't care much because I have the count of slices in my 
> scripts so version is defaulted to 3, but now that HD is common and 
> FFV1.3 is supported for a long time, it may be interesting to change 
> the default settings, true.

+1
Don't know about your experiences, but 24 slices has turned out to be 
nice overall default for SD-to-HD.
Opinions?


>
> IMO if the default version is changed, the default count of slices 
> should be changed too (change in FFV1 version would already have an 
> impact with 4 slices if more than 352x288; as the current default 
> setting for FFV1.3 is based on check on 352x288, we could do 4 for SD 
> including the ones with extra VBI so 720x608, 12 for HDReady, 16 for 
> HD/2K, 64 for UHD/4K, 256 for 8K, for having a similar pixel size of 
> slices whatever is the image pixel width).

If auto-default of slices per resolution would be possible, that'd be 
great! :)


I was mainly asking, because in trainings and presentations I've noticed 
that it's definitely nice (especially for FFV1-beginners) if FFmpeg's 
default settings would match the 
somewhat-de-facto-and-proven-to-be-useful values already in use in a 
professional context.

So introducing FFV1 with "-c:v ffv1" is sufficient and proper to start 
with, would be awesome IMO.

Right now, I have the feeling that many archivists feel overwhelmed when 
I mention "oh, please use these parameters that you have no idea yet 
what they're for" :P


>
> Note that changing default version has also an impact on compression 
> ratio (less compression with 4 slices than with the current 1 for SD 
> content).

Got any (rough) compression size benchmarks for this?



Thanks again,
Peter