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

Feature request: continue analyzing files after non-compliance instances #66

Open
DSohl opened this issue Sep 23, 2024 · 2 comments
Open

Comments

@DSohl
Copy link

DSohl commented Sep 23, 2024

As av-spex works right now, if I'm processing a large batch of files and one of them does not pass a standard, it stops running. Most recently I had an empty folder in my batch, and av-spex did not process any other folders and files after it, so I had to re-run it this morning.

Specifically what I think could be good is if av-spex would analyze and process all files in the batch and give a printout in terminal afterward of how many files were successfully processed (in green) and how many files aren't up to snuff (in red).

@eddycolloton
Copy link
Collaborator

If there is a file naming error or av-spex does not find an mkv in an input directory, it hard exits. I will change this so that it simply notes the issue and does not stop processing.

'Normal' errors like the ffprobe resolution being wrong or something, should not cause the app to stop processing. Are there other situations, other than missing MKV files or incorrectly named MKV files, where the app is exiting without finishing?

I will work on a report or maybe some kind of dashboard for looking at results in aggregate

@eddycolloton
Copy link
Collaborator

As of v0.4.9.3 (this commit forward: 5da1510) av-spex will not hard exit on empty directories or file/directory naming issues.

If av-spex cannot accurately id a JPC mkv video (due to either none, or more than one mkv in the input directory matching the file naming convention) the directory will be skipped.

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