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

Command-line option to process batch of images #320

Open
kikoreis opened this issue Jan 17, 2025 · 3 comments
Open

Command-line option to process batch of images #320

kikoreis opened this issue Jan 17, 2025 · 3 comments

Comments

@kikoreis
Copy link

kikoreis commented Jan 17, 2025

Hello there; love spek and use it regularly to understand encoding quality of my music library.

So regularly, in fact, that I'd like to generate output in batch (to compare files in a set, for instance). Would it be possible to have a command-line option that generates one or more PNGs and exits with a zero return value if the run was successful? Something like

-b, --batch generate PNG image file(s) and exit; filenames are suffixed with ".png"

would be fine for my use case, as it would allow something like spek -b ~/00MUZAK/*mp3, outputting Spek files following the format ~/00MUZAK/*.mp3.png.

I considered adding a comment to issue 169, but the request there is not about generating the PNGs, but rather outputing a text value; I'm not looking for that, as I think the PNG is more useful when comparing. Note that a -o option to allow customizing the path/filename might be useful but I personally wouldn' need it.

@kikoreis
Copy link
Author

kikoreis commented Jan 17, 2025

Oh, is this actually fixed in the spek-alternative fork? Am looking at withmorten#1 and withmorten@cf02f3c and seeing the commit provides a filename output option.

I'm running the Ubuntu snap version, --version says Spek version 0.8.2.

@kikoreis
Copy link
Author

kikoreis commented Jan 17, 2025

Note that change also appears to have been integrated into release 0.9.0 of the https://github.com/MikeWang000000/spek-X fork

@kikoreis
Copy link
Author

I think this bug is technically a dupe of #131

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

1 participant