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

Frame index mismatch between GOPRO_Large and GOPRO_Large_all? #66

Open
gmy001 opened this issue Feb 20, 2023 · 1 comment
Open

Frame index mismatch between GOPRO_Large and GOPRO_Large_all? #66

gmy001 opened this issue Feb 20, 2023 · 1 comment

Comments

@gmy001
Copy link

gmy001 commented Feb 20, 2023

Hello, thanks for sharing the great dataset. I am trying to generate my own blur frames using frames in GOPRO_Large_all following the process you described in #59 . However, I met an inconsistency issue of mismatched frame index.
For example, in the GOPRO_Large/test/GOPR0384_11_05, the first blur frame is 004001.png, which if I understand correctly, will be an average of frame GOPRO_Large_all/test/GOPR0384_11_05/044001.png~044011.png. However, when I did the average, the result is not the same, there seems to be a few frames missing.
I also find that GOPRO_Large_all/test/GOPR0384_11_05/044001.png happens to be exactly the same as GOPRO_Large/test/GOPR0384_11_05/sharp/004001.png. Shouldn't the sharp/004001.png be the same as GOPRO_Large_all/test/GOPR0384_11_05/044006.png, since it's the middle of the first 11 frames?

This issue happens also in several other clips. Is there any wrong with my blur generation process?

@DachunKai
Copy link

DachunKai commented Oct 6, 2023

Yes, I found the same problem. Have you found which frames are used to simulate GOPRO_Large/test/GOPR0384_11_05/blur/004001.png. in GOPRO_Large_all?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants