Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Martijn van Beurden <mvanb1@gmail.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] Trivial codec based on QOI and zstd compresses better than all lossless ffmpeg codecs on my data from screen
Date: Sat, 11 Jun 2022 11:03:02 +0200
Message-ID: <CADQbU6_SsKaxx_bHQGA=BkvqP72E-25FnnaBuv2of-Ea7_PWAw@mail.gmail.com> (raw)
In-Reply-To: <CAPnZJGA_WgDjdKJkmRqsJMTn6EBNp5tEb0mN2NjRB2sh8EE9fQ@mail.gmail.com>

Op za 11 jun. 2022 01:37 schreef Аскар Сафин <safinaskar@gmail.com>:

> ffv1 spec reads: "FFV1 is designed to support a wide range of lossless
> video applications such as... screen recording..." Unfortunately, ffv1
> turned out to be bad compared to my codec
> on screen recording data, so it is possible ffv1 could benefit from my
> ideas.
>

While the spec indeed mentions screen recording, it seems the kind of
screen recording you do is probably not a use where ffv1 shines.

The spec abstract starts with "This document defines FFV1, a lossless,
intra-frame video encoding format." Notice "intra-frame". ffv1 does not do
inter-frame decorrelation like most other codecs do. So, when compressing
data with high inter-frame correlation, ffv1 doesn't do well.

ffv1 does very well on for example film scans, when the presence of film
grain makes inter-frame decorrelation of relatively little use. In screen
captures where > 95% of the frame stays exactly the same, this approach
doesn't work well indeed.
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel

To unsubscribe, visit link above, or email
ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".

  parent reply	other threads:[~2022-06-11  9:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-10 23:37 Аскар Сафин
2022-06-11  8:39 ` Paul B Mahol
2022-06-11 10:16   ` Аскар Сафин
2022-06-11  9:03 ` Martijn van Beurden [this message]
2022-06-11 15:24 ` Michael Niedermayer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CADQbU6_SsKaxx_bHQGA=BkvqP72E-25FnnaBuv2of-Ea7_PWAw@mail.gmail.com' \
    --to=mvanb1@gmail.com \
    --cc=ffmpeg-devel@ffmpeg.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel

This inbox may be cloned and mirrored by anyone:

	git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \
		ffmpegdev@gitmailbox.com
	public-inbox-index ffmpegdev

Example config snippet for mirrors.


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git