Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Michael Niedermayer <michael@niedermayer.cc>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [RFC] swscale RGB24->YUV420P
Date: Wed, 16 Aug 2023 19:37:02 +0200
Message-ID: <20230816173702.GV7802@pb2> (raw)
In-Reply-To: <grqpdi9cndmj8vjaq6tsft11s3ujmcnjq9@4ax.com>


[-- Attachment #1.1: Type: text/plain, Size: 1985 bytes --]

On Wed, Aug 16, 2023 at 05:15:23PM +0100, John Cox wrote:
> Hi
> 
> The Pi has a use for a fast RGB24->YUV420P path for encoding camera
> video. There is an existing BGR24 converter but if I build a RGB24
> converter using the same logic (rearrange the conversion matrix and use
> the same code) I get a fate fail on filter-fps-cfr (and possibly others)
> which appears to decode a file to RGB24, convert to YUV420P and take the
> CRC of that so almost any change to the conversion breaks this
> (unrelated?) test.
> 
> My initial assumption was that if the code to conversion in
> libswscale/rgb2rgb_template:bgr24toyv12_c was good enough for BGR24->YUV
> then it should be good enough for RGB24->YUV too. However it breaks this
> fate case - what is an acceptable way to resolve this?

update the checksum (if needed), and put the code under appropriate bitexact flags checks
(there may be remaining issues but hard to say without seeing and being
abel to test the code)


> 
> A further question assuming that the above can be resolved - I have also
> written aarch64 asm for this (RGB24/BGR24->YUV420P). It costs nothing in
> the asm to round the output values to nearest rather than just rounding
> down as the C template does and doing so improves the accuracy reported
> by tests/swscale - however at that point the asm and the C don't produce
> identical results. I assume that the x86 asm for BGR24 conversion does
> match the C. What is the best thing to do here?

The more differences there are between implementations the more annoying
it is but there is a bitexact flag that allows differences

thx

[...]

-- 
Michael     GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB

The real ebay dictionary, page 1
"Used only once"    - "Some unspecified defect prevented a second use"
"In good condition" - "Can be repaird by experienced expert"
"As is" - "You wouldnt want it even if you were payed for it, if you knew ..."

[-- 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".

  reply	other threads:[~2023-08-16 17:37 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-16 16:15 John Cox
2023-08-16 17:37 ` Michael Niedermayer [this message]
2023-08-17  9:42   ` John Cox
2023-08-17 17:13     ` 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=20230816173702.GV7802@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