Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Dynamic zooming zooms in too much for lens correction strengths other than 0 and 100% #384

Open
2 tasks done
avsaase opened this issue Jun 22, 2022 · 6 comments
Open
2 tasks done
Labels
💎 Bounty bug Something isn't working
Milestone

Comments

@avsaase
Copy link

avsaase commented Jun 22, 2022

Is there an existing issue for this?

  • I have searched the existing issues

Have you tried the latest build?

  • I have tried the latest build

Gyroflow version

72b8eb6

What operating system are you using?

Windows 10

What GPU are you using?

No response

What happened?

When selecting lens correction strengths other than 0 and 100% dynamic and fixed zooming zooms in too much. Take for example this clip without motion from the Firefly X Lite II on 2.7K 4:3.

0% lens correction:
image

100% lens correction:
image

50% lens correction:
image

As you can see in the 50% lens correction example there is FOV "left on the table". This happens with all settings between 0 and 100% but seems to be maximized at or around 50%.

I increased the FOV to 1.5 to make it more obvious but it's not a bug in the Safe area guide because it also happens with FOV=1. It's also not related to the output size setting because I tried setting that to the input resolution but that didn't make a difference. I tried a couple of different lens profiles for this camera and setting, all with the same result. I recall seeing this with the Mobius Maxi 4K as well.

Here's the clip and .gyroflow file: https://mega.nz/folder/00NwGYwL#TAKzsDrmqTZ-FLzTkrvhIg

Relevant log output

No response

@avsaase avsaase added the bug Something isn't working label Jun 22, 2022
@AdrianEddy
Copy link
Collaborator

AdrianEddy commented Jun 22, 2022

I know, this is because I don't know how to calculate camera params when adding lens distortion back, so currently it's something approximated, see:

float2 factor = (float2)max(1.0f - params->lens_correction_amount, 0.001f); // FIXME: this is close but wrong

This will likely stay this way until someone smarter than me figures it out

@AdrianEddy AdrianEddy added this to the 1.2.2 milestone Sep 3, 2022
@AdrianEddy AdrianEddy modified the milestones: 1.2.2, 1.4.0 Oct 2, 2022
@AdrianEddy
Copy link
Collaborator

/bounty $150

@algora-pbc
Copy link

algora-pbc bot commented Sep 22, 2023

💎 $150 bounty • Gyroflow

Steps to solve:

  1. Start working: Comment /attempt #384 with your implementation plan
  2. Submit work: Create a pull request including /claim #384 in the PR body to claim the bounty
  3. Receive payment: 100% of the bounty is received 2-5 days post-reward. Make sure you are eligible for payouts

Thank you for contributing to gyroflow/gyroflow!

Add a bountyShare on socials

Attempt Started (GMT+0) Solution
🟢 @aazam-gh Oct 1, 2023, 8:50:00 AM WIP
🔴 @Rutik7066 Dec 25, 2023, 8:21:50 AM WIP

@aazam-gh
Copy link

aazam-gh commented Oct 1, 2023

/attempt #384

Options

@Rutik7066
Copy link
Contributor

Rutik7066 commented Dec 25, 2023

/attempt #384
got it.

Options

Copy link

algora-pbc bot commented Dec 25, 2023

Note

The user @aazam-gh is already attempting to complete issue #384 and claim the bounty. We recommend checking in on @aazam-gh's progress, and potentially collaborating, before starting a new solution.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
💎 Bounty bug Something isn't working
Projects
None yet
Development

No branches or pull requests

4 participants