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

analyze.py seems to skip many files if it encounters a corrupt file #339

Closed
kami2012 opened this issue May 22, 2024 · 5 comments
Closed

Comments

@kami2012
Copy link

I analyzed about 2.4 million .wav files in junk files of about 250.000 to 300.000 files. In two of these junks there were 4 corrupted files. Because of these 4 corrupted files, about 6550 other uncorrupted files could not be analyzed. It seems that analyze.py gets some sort of "hiccup" when it encounters a corrupt file and skips hundreds of subsequent files that have no problem.

Is this something that could be optimized in a newer version?

@Josef-Haupt
Copy link
Collaborator

If the Analyzer encounters an error or corrupt file, the file just gets skipped. Could you check your error_log.txt and log.txt for error codes if this happens again?

@GrunCrow
Copy link
Contributor

I encountered a similar issue. I had a folder with 25 audio files, but none of the files were being uploaded for analysis. After doing some checks, I discovered that one of the files was corrupt. The corrupt file was not being skipped, and as a result, the other files were not uploaded for analysis either. Once I deleted the corrupt file, the entire folder uploaded successfully with all the remaining files.

@Josef-Haupt
Copy link
Collaborator

As I said, please check your error_log.txt and log.txt in the install directory for error codes if this happens again, and paste the contents into this issue. Or provide us with a corrupt file, for us to run tests.

@GrunCrow
Copy link
Contributor

As I said, please check your error_log.txt and log.txt in the install directory for error codes if this happens again, and paste the contents into this issue. Or provide us with a corrupt file, for us to run tests.

This is for example a corrupt file:
Corrupt_Audio.zip

@Josef-Haupt
Copy link
Collaborator

I just inserted your corrupt file into a batch, but the current repo correctly skips the file, but analyses the rest. Is this still an issure for you in the current main?

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

3 participants