From: Michael Niedermayer <michael@niedermayer.cc> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] [PATCH 0/1] Fix tmix on discontinuities Date: Wed, 9 Jul 2025 00:26:33 +0200 Message-ID: <20250708222633.GJ29660@pb2> (raw) In-Reply-To: <b333lxheuvy6iadew3tuxv4xxas4wjrwhjhgmmkt4g43fdlvaz@3tzna4uyb4yo> [-- Attachment #1.1: Type: text/plain, Size: 1282 bytes --] Hi Ignacy On Sun, Jul 06, 2025 at 08:30:09PM +0200, Ignacy Gawędzki wrote: > A simple example of the bug: > > ffplay -f lavfi color=c=gray -vf 'tmix=enable=gt(t\,1)' > > After one second, the color is wrong (green in my case), not the > expected gray. > > It seems it is due to the fact that parse_weights determines that > the weights are all 1 and FAST_TMIX_SLICE should be used instead of > MIX_SLICE. But if the filter is not running from the very start with > these weights, FAST_TMIX_SLICE will not work properly. It should be possible to fix fast mode so it resets its state when teh filter re-enables But as long as thats not done, i think its ok to fix it by disabling fast mode > > Besides, should FAST_TMIX_SLICE not be used with float types either, > as addition on floats is not associative and rounding errors will > accumulate? yes, the filter is wrong to use this with floats though if there was a state "reset" for re-enabling the filter that could also be used for float periodically thx [...] -- Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB Does the universe only have a finite lifespan? No, its going to go on forever, its just that you wont like living in it. -- Hiranya Peiri [-- Attachment #1.2: signature.asc --] [-- Type: application/pgp-signature, Size: 195 bytes --] [-- Attachment #2: Type: text/plain, Size: 251 bytes --] _______________________________________________ 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".
prev parent reply other threads:[~2025-07-08 22:26 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2025-07-06 18:30 Ignacy Gawędzki 2025-07-08 22:26 ` Michael Niedermayer [this message]
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=20250708222633.GJ29660@pb2 \ --to=michael@niedermayer.cc \ --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