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

Lookahead for existing processed frames in the processing chain #46

Open
pozitronik opened this issue Aug 1, 2023 · 1 comment
Open
Assignees
Labels
dev 🧑‍💻Developer issues (todos, experiments, styling, etc) good first issue Good for newcomers priority: low

Comments

@pozitronik
Copy link
Owner

It is about the case, when a task was stopped, and already processed frames deleted by user (as example, extracted frames when they are already swapped, and now enhancing in progress). Sinner will reprocess those frames again on the next task run, although they are not required anymore.
There is required some lookahead procedure to determine, what processor is running now. It is simple: find last state folder with files, look, what frames are still unprocessed, and prepare only them (if they're not exists).

@pozitronik pozitronik added the dev 🧑‍💻Developer issues (todos, experiments, styling, etc) label Aug 1, 2023
@pozitronik pozitronik self-assigned this Aug 1, 2023
@pozitronik
Copy link
Owner Author

This feature also might include the ignore of not existed target file, if every required frame already exists.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dev 🧑‍💻Developer issues (todos, experiments, styling, etc) good first issue Good for newcomers priority: low
Projects
None yet
Development

No branches or pull requests

1 participant