-
-
Notifications
You must be signed in to change notification settings - Fork 103
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
master branch is creating massive files #469
Comments
Can you include a link for the tracks that you observed this behaviour with? Or include logs? Seems to be a duplicate of #437. |
Here are the logs:
I did notice that while watching the filesystem the original file is an acceptable size and then after adding metadata the file size balloons. |
Also, I tried |
Interesting, gimme a sec to look at this.. |
Here are a couple of tests using processing tools:
|
The exiftool output shows the cover art taking up the appropriate amount of space (~100kb) and that last line indicates that weird tag name taking up the rest of the file. |
Thanks for all this info, are you on Mac maybe? Also, do you observe this behavior with the docker images? Try |
Yes, I'm on a Mac. I'll give the docker container a try. |
The docker image does the thing correctly! |
I installed the version of AtomicParsley that is used in the container locally (20210715.151551.e7ad03a) and that resolved the large file issues on my side. It appears homebrew only provides the HEAD version (20221229.172126.d813aa6). |
Interesting, can you try building from this branch to test? I'm about to make this the base branch we're vendored off of because we could use the patch in there. |
The atomicparsley binary built from that repo fork worked:
|
Beautiful! Thanks for the info. I'll reopen this and close once we've rebased on that patch. Thanks again! |
Every song it is downloading is 400-500MB so 4-5 albums are currently using about 50GB. Is this the expected behavior?
The text was updated successfully, but these errors were encountered: