[GH-ISSUE #18] Files end up named with "_1.mp3" #14

Closed
opened 2026-02-27 04:57:07 +03:00 by kerem · 5 comments
Owner

Originally created by @U2EZNeko on GitHub (Jun 7, 2025).
Original GitHub issue: https://github.com/Googolplexed0/zotify/issues/18

Originally assigned to: @Googolplexed0 on GitHub.

Using your branch since it has the authentication fix.

However im running into an issue.

Here's my config for the output.

"OUTPUT": "/mp3s/{artist}/{album}/{song_name} - {artist}",

Why do songs end up named for example "Uncle Arthur - David Bowie_1.mp3"?

It's not a duplicate track, i tried clearing all song_ids but not much luck.

Any clues?

PS: Also while it's in the readme, i do not think {ext} currently works as a placeholder, it will auto add the extension at the end.

Originally created by @U2EZNeko on GitHub (Jun 7, 2025). Original GitHub issue: https://github.com/Googolplexed0/zotify/issues/18 Originally assigned to: @Googolplexed0 on GitHub. Using your branch since it has the authentication fix. However im running into an issue. Here's my config for the output. "OUTPUT": "/mp3s/{artist}/{album}/{song_name} - {artist}", Why do songs end up named for example "Uncle Arthur - David Bowie_1.mp3"? It's not a duplicate track, i tried clearing all song_ids but not much luck. Any clues? PS: Also while it's in the readme, i do not think {ext} currently works as a placeholder, it will auto add the extension at the end.
kerem closed this issue 2026-02-27 04:57:07 +03:00
Author
Owner

@Googolplexed0 commented on GitHub (Jun 7, 2025):

The {ext} placeholder is not currently included in the README, as it was removed for being redundant. I am not seeing the described behavior with my personal configs, could you please include your config.json file so that I can replicate your issue?

<!-- gh-comment-id:2953160236 --> @Googolplexed0 commented on GitHub (Jun 7, 2025): The `{ext}` placeholder is not currently included in the README, as it was removed for being redundant. I am not seeing the described behavior with my personal configs, could you please include your `config.json` file so that I can replicate your issue?
Author
Owner

@U2EZNeko commented on GitHub (Jun 10, 2025):

config.json

I couldn't trace the issue back to anything reproduceable but a close 5% of my downloads are affected.

I'm guessing the couldn't get audio key error is something else entirely?

<!-- gh-comment-id:2960128810 --> @U2EZNeko commented on GitHub (Jun 10, 2025): [config.json](https://github.com/user-attachments/files/20675731/config.json) I couldn't trace the issue back to anything reproduceable but a close 5% of my downloads are affected. I'm guessing the couldn't get audio key error is something else entirely?
Author
Owner

@Googolplexed0 commented on GitHub (Jun 10, 2025):

I'm guessing the couldn't get audio key error is something else entirely?

The "Failed to get audio key" error is a rate limit on the API, it's out of my hands. Even with your config I'm still not seeing anything. Are you sure your installation is up to date? I have been pushing lots of improvements lately.

a close 5% of my downloads are affected

Is it a consistent 5% of songs (the same songs will always be suffixed, every time they are downloaded) or a random draw of 5% for every song?

It's not a duplicate track, i tried clearing all song_ids but not much luck.

The duplicate checker does three checks in total, for the filename, local archive, and global archive. Throw the --debug flag into the command line next time and see what it shows for Duplicate Check.

EDIT:
Looks like your config is old, it's using "SONG_ARCHIVE" rather than "SONG_ARCHIVE_LOCATION", which was a config update I made a while ago. This means the file you're looking at likely doesn't correspond with what the config.py is checking. Just added a depreciated config checker, so that may help identify other issues.

<!-- gh-comment-id:2960317145 --> @Googolplexed0 commented on GitHub (Jun 10, 2025): > I'm guessing the couldn't get audio key error is something else entirely? The "Failed to get audio key" error is a rate limit on the API, it's out of my hands. Even with your config I'm still not seeing anything. Are you sure your installation is up to date? I have been pushing lots of improvements lately. > a close 5% of my downloads are affected Is it a consistent 5% of songs (the same songs will always be suffixed, every time they are downloaded) or a random draw of 5% for every song? > It's not a duplicate track, i tried clearing all song_ids but not much luck. The duplicate checker does three checks in total, for the filename, local archive, and global archive. Throw the `--debug` flag into the command line next time and see what it shows for Duplicate Check. EDIT: Looks like your config is old, it's using "SONG_ARCHIVE" rather than "SONG_ARCHIVE_LOCATION", which was a config update I made a while ago. This means the file you're looking at likely doesn't correspond with what the `config.py` is checking. Just added a depreciated config checker, so that may help identify other issues.
Author
Owner

@U2EZNeko commented on GitHub (Jun 11, 2025):

Thanks a bunch for the help.

I've played around a bit but still couldn't reproduce it consistently.
Downloading the same album ~5 times left me with 3 different songs having the _1. in the name.
I updated my config, I'll throw in the debug flag and test a bit more when im home.

For now I have a script replace every instance of _1.mp3 with .mp3, janky but works. lel

<!-- gh-comment-id:2961910215 --> @U2EZNeko commented on GitHub (Jun 11, 2025): Thanks a bunch for the help. I've played around a bit but still couldn't reproduce it consistently. Downloading the same album ~5 times left me with 3 different songs having the _1. in the name. I updated my config, I'll throw in the debug flag and test a bit more when im home. For now I have a script replace every instance of _1.mp3 with .mp3, janky but works. lel
Author
Owner

@U2EZNeko commented on GitHub (Jun 13, 2025):

I did some more testing, cant figure it out.

Sometimes it happens, sometimes it doesn't.

Not too important of an issue either way

<!-- gh-comment-id:2971793366 --> @U2EZNeko commented on GitHub (Jun 13, 2025): I did some more testing, cant figure it out. Sometimes it happens, sometimes it doesn't. Not too important of an issue either way
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/zotify#14
No description provided.