We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
ffmpeg fills filenames with leading zeros, when told to do so; ffmpeg -t 00:00:01 -i INPUT.360 -map 0:0 -r 1 -q:v 1 track0/img%4d.jpg -map 0:5 -r 1 -q:v 1 track5/img%4d.jpg
ffmpeg -t 00:00:01 -i INPUT.360 -map 0:0 -r 1 -q:v 1 track0/img%4d.jpg -map 0:5 -r 1 -q:v 1 track5/img%4d.jpg
max2sphere -n 1 -m 3 -o out/%d_sphere.jpg track%d/img%4d.jpg gives the error: CheckFrames() - Failed to open first frame "track0/img 1.jpg"
max2sphere -n 1 -m 3 -o out/%d_sphere.jpg track%d/img%4d.jpg
CheckFrames() - Failed to open first frame "track0/img 1.jpg"
The text was updated successfully, but these errors were encountered:
the readme should also normalize the examples for the track5/DIRECTORY_%d with underscore and not. same for the %d or %4d, which is incompatible
Sorry, something went wrong.
No branches or pull requests
ffmpeg fills filenames with leading zeros, when told to do so;
ffmpeg -t 00:00:01 -i INPUT.360 -map 0:0 -r 1 -q:v 1 track0/img%4d.jpg -map 0:5 -r 1 -q:v 1 track5/img%4d.jpg
max2sphere -n 1 -m 3 -o out/%d_sphere.jpg track%d/img%4d.jpg
gives the error:
CheckFrames() - Failed to open first frame "track0/img 1.jpg"
The text was updated successfully, but these errors were encountered: