Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Michael Koch <astroelectronic@t-online.de>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH] avutil/eval: Use even better PRNG
Date: Fri, 19 Jan 2024 09:53:46 +0100
Message-ID: <4d214d22-e1af-9374-1a66-886ca1692ad5@t-online.de> (raw)
In-Reply-To: <20240109015521.26231-1-michael@niedermayer.cc>

There is still a small problem with the random generator, but this has 
nothing to do with the recent changes.
If the random() expression is used in the geq filter, then multiple 
pixels get the same sequence of random numbers.
As can be shown with this command, where the frame has only two pixels:

ffmpeg -loglevel repeat -f lavfi -i nullsrc=size=1x2,format=gray -vf 
"geq=lum='print(random(0));print(random(0));print(random(0))'" -frames 1 
-y out.png

I think it's because the filter is executed in multiple threads.
-filter_threads 1 fixes the problem, but it slows down the whole filter 
thread.

Michael


_______________________________________________
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:[~2024-01-19  9:00 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-09  1:55 Michael Niedermayer
2024-01-10 22:48 ` Stefano Sabatini
2024-01-11  2:39   ` Michael Niedermayer
2024-01-19  8:53 ` Michael Koch [this message]
2024-01-20  0:33   ` Michael Niedermayer
2024-01-13  3:51 Michael Niedermayer
2024-01-14 14:14 ` Stefano Sabatini
2024-01-16  0:27   ` 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=4d214d22-e1af-9374-1a66-886ca1692ad5@t-online.de \
    --to=astroelectronic@t-online.de \
    --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