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

Disabling overwrite doesn't behave as expected if a subsequent export adds more segments #1690

Closed
5 tasks done
SignpostMarv opened this issue Aug 25, 2023 · 2 comments
Closed
5 tasks done

Comments

@SignpostMarv
Copy link

I have a lot of issues to go through, so in order to make it easier for me to help you, I ask that you please try these things first

Operating System

Windows 11

Steps to reproduce

  1. Disable overwriting
  2. Create a session with less than 100 segments (this may also work with less than 10 segments, have not tested)
  3. Export
  4. Add more segments to bump it over the number padding length (i.e. less than 100 pads to two digits, 100 or more pads to 3 digits)
  5. Export

Expected behavior

presence of 01-foo.mp4 should be treated as presence of 001-foo.mp4

Actual behavior

001-foo.mp4 through 099-foo.mp4 will be created alongside 01-foo.mp4 through 99-foo.mp4

Share log

No response

@mifi
Copy link
Owner

mifi commented Aug 27, 2023

I think the only way to solve this is to allow the user to choose how many zeroes to pad the number with, right?

@SignpostMarv
Copy link
Author

I think the only way to solve this is to allow the user to choose how many zeroes to pad the number with, right?

Either that, or run a file existence check for 1 up / 1 down orders of magnitude's worth of padding?

Having a setting that I can set and forget for the minimum padding length would be good though 👍

@mifi mifi closed this as completed in 1f0a1a4 Aug 27, 2023
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