create_dataset.py issues on Google Colab about super-slomo HOT 3 CLOSED

Google colab has a linux OS while all the code in this repo was tested on Windows. I would suggest, if possible, to create the dataset on your local PC running Windows and upload it to colab. This seems tedious. Another approach would be to debug it on a linux machine. Execute the ffmpeg command for a single video (failing case) in a terminal and try to figure out the problem. Unfortunately, I won't be able to test - debug this issue due to other commitments.

If you do find a bug please post the solution here.

from super-slomo.

Hi @avinashpaliwal,

I did a test on the failed files that you have suggested and I found out the issue to be with the -vsync 0 parameter in the ffmpeg run.

Here are the results when I ran the line for ffmpeg extraction.

vsync On
GOPR9637a.mp4 extracted: 2
GOPR9648.mp4 extracted: 396
vsync Off
GOPR9637a.mp4 extracted: 1244
GOPR9648.mp4 extracted: 860

It looks like the ffmpeg extraction stops at some point when I set the vsync parameter leading to incomplete extraction of frames. I have tested the entire Adobe240fps Test dataset without the -vsync 0 parameter and so far I have no failures. I just want to check if it would be possible to run the ffmpeg line without the vsync parameter? I have been reading the ffmpeg documentation page and I can't seem to connect the relationship between the failures and the -vsync 0 setting. Hope you can clear it out for me.

Also, for anyone else, can I ask for confirmation that I have the correct extracted frames for the video files I have tested?

Will appreciate your help. Thank you!

from super-slomo.

I have tried running the script again and it is working now. I am not sure if it makes sense but I found that Colab has some sort of delay in unpacking files, especially large ones. This may be what's causing the issue regarding the processing of the files. Colab might be trying to process files that have not been fully unpacked completely causing the error messages on random videos.

I have tried running the script right now and all the issues appear to be resolved. All the videos on the Adobe240fps dataset were stripped to their frames without any other issues.

from super-slomo.