Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Lynne via ffmpeg-devel <ffmpeg-devel@ffmpeg.org>
To: ffmpeg-devel@ffmpeg.org
Cc: Lynne <dev@lynne.ee>
Subject: Re: [FFmpeg-devel] [PATCH] lavu/stereo3d: change baseline and horizontal FOV to rationals
Date: Sun, 23 Jun 2024 16:23:53 +0200
Message-ID: <3256fda9-29aa-482e-909d-4613667f0cb8@lynne.ee> (raw)
In-Reply-To: <cc6dfa3e-1a5f-47e7-90ca-afac59f0975c@gmail.com>


[-- Attachment #1.1.1.1: Type: text/plain, Size: 2344 bytes --]

On 23/06/2024 13:05, Derek Buitenhuis wrote:
> On 6/22/2024 9:11 PM, Lynne via ffmpeg-devel wrote:
>> The API was committed 2 days ago, so changing these fields now
>> is within the realms of acceptable.
>> ---
> 
> You also had weeks to comment on 3 revisions of the set, and it would
> have been nice to hear about this then instead of changing it after I've
> already pushed and integrated it in my own downstream work.
> 
> If I sound grumpy, it's because I am... the set sat commentless.

Sorry. I somehow missed this patchset, both when it was sent for review 
and when it was merged.
I did mention that I don't have strong feelings about changing this, it 
is just being pedantic, so I can drop it if you'd prefer. There's no 
need to argue over thousands of a degree here.

>> diff --git a/libavutil/stereo3d.h b/libavutil/stereo3d.h
>> index 00a5c3900e..097f6c9455 100644
>> --- a/libavutil/stereo3d.h
>> +++ b/libavutil/stereo3d.h
>> @@ -213,9 +213,9 @@ typedef struct AVStereo3D {
>>   
>>       /**
>>        * The distance between the centres of the lenses of the camera system,
>> -     * in micrometers. Zero if unset.
>> +     * in meters. Zero if unset.
>>        */
>> -    uint32_t baseline;
>> +    AVRational baseline;
> 
> Can't be AVRational for the reason James mentioned, uint32_t can't be put in an int,
> and can't be negative.
> 
> Also, in terms of units, using meters here is silly, it's the distance between two
> lenses, meters is an crazy unit to measure that in, not idiomatic at all, and I
> would argue violates the principal of least surprise (both in terms of units, and
> being a distance as a rational).

Fair enough, dropped.

> 
>>       /**
>> -     * Horizontal field of view in thousanths of a degree. Zero if unset.
>> +     * Horizontal field of view, in degrees. Zero if unset.
>>        */
>> -    uint32_t horizontal_field_of_view;
>> +    AVRational horizontal_field_of_view;
>>   } AVStereo3D;
> 
> This one is more reasonable. I am not happy about the post-push change, but
> if the community wants this one, I am not going to block it.
> 
>> +horizontal_field_of_view=0/0
> 
> If it is changed, this should be initialized to 0/1, as that is what James
> last set did for the rest of all side data.

Thanks, changed, and set a v2.

[-- Attachment #1.1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 637 bytes --]

[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 236 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".

      parent reply	other threads:[~2024-06-23 14:24 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-22 20:11 Lynne via ffmpeg-devel
2024-06-22 20:19 ` James Almer
2024-06-22 21:26   ` Lynne via ffmpeg-devel
2024-06-22 21:30     ` James Almer
2024-06-22 22:07       ` Lynne via ffmpeg-devel
2024-06-23 11:05 ` Derek Buitenhuis
2024-06-23 12:03   ` Derek Buitenhuis
2024-06-23 14:23   ` Lynne via ffmpeg-devel [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=3256fda9-29aa-482e-909d-4613667f0cb8@lynne.ee \
    --to=ffmpeg-devel@ffmpeg.org \
    --cc=dev@lynne.ee \
    /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