-
-
Notifications
You must be signed in to change notification settings - Fork 910
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
ffmpeg extraction fails to start if missing extracted frames folder with custom paths #39
Comments
Oh yeah I should add the function to create folders automatically if they're missing. |
I saw your code review, and I've already finished adding the features. |
I have just released version |
One minor addition to this to request: Adding either a command line or config option to skip the "Create folder/directory?" request. Currently this breaks batching the script when intending to use custom paths. |
By design, if you have the destination folder created, it shouldn't prompt you. Is it not working properly? |
Part of the original concern is there in which regardless of whether the temp folders are used or custom paths, they are deleted at the tail end of the script. Specifically this section of code: So I can create the custom folders I wish to use for extracted and upscaled frames, but when the script finishes it will delete these outright and the next cycle it will ask to create those because they no longer exist. |
Maybe you can set "preserve_frames" to I'll look into adding an option for it, or make changes that will make this problem go away. |
Found out with the custom extracted and upscaled frames folders if those are missing, at the very least the ffmpeg extraction step fails. Not sure if waifu2x-caffe will do the same as I did not get that far. Where this comes in is the end of the script when it wipes those folders, it'll do so whether using the temp directory or custom paths. In a batch this is a no-go.
I've done a potentially crude fix for this which I'll try and do a PR for. You may wish to do a cleaner version of course. :)
The text was updated successfully, but these errors were encountered: