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

BUG: Video datasets only converting to frames when fps = none #4568

Open
2 tasks
rcho5840 opened this issue Jul 12, 2024 · 0 comments
Open
2 tasks

BUG: Video datasets only converting to frames when fps = none #4568

rcho5840 opened this issue Jul 12, 2024 · 0 comments
Labels
bug Bug fixes core Issues related to Core features

Comments

@rcho5840
Copy link

Describe the problem

I have a video recorded at 30 fps, 1080p from a webcam in mp4 format. I am trying to convert this video into frames and then take the 100 most distinct frames from the video. Given that the video was recorded at 30fps, I only want 1 frame per second of video, but the to_frames method will not actually save my frames to file unless I leave the fps parameter empty.

Code to reproduce issue

My code:
image

What happens when fps = none (works as expected):

image

Note that I have no idea why it says "Setting 63984 frame filepaths on the input collection that exist on disk but are not recorded on the dataset" because it is saving 63984 jpgs to a file path which I definitely do not want

What happens when I put fps = 1 as a parameter in to_frames:

image

It isn't able to write to a file even though I was able to write to file when fps parameter isn't adjusted

# commands and/or screenshots here

System information

  • OS Platform and Distribution (e.g., Linux Ubuntu 22.04): Windows 11
  • Python version (python --version): 3.12.4
  • FiftyOne version (fiftyone --version): 0.24.1
  • FiftyOne installed from (pip or source): pip

Other info/logs

Include any logs or source code that would be helpful to diagnose the problem.
If including tracebacks, please include the full traceback. Large logs and
files should be attached. Please do not use screenshots for sharing text. Code
snippets should be used instead when providing tracebacks, logs, etc.

Willingness to contribute

The FiftyOne Community encourages bug fix contributions. Would you or another
member of your organization be willing to contribute a fix for this bug to the
FiftyOne codebase?

  • Yes. I can contribute a fix for this bug independently
  • Yes. I would be willing to contribute a fix for this bug with guidance
    from the FiftyOne community
  • [ X] No. I cannot contribute a bug fix at this time
@rcho5840 rcho5840 added the bug Bug fixes label Jul 12, 2024
@benjaminpkane benjaminpkane added the core Issues related to Core features label Jul 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Bug fixes core Issues related to Core features
Projects
None yet
Development

No branches or pull requests

2 participants