[GH-ISSUE #62] [Feature Request] Audio Volume Increase on Download #51

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

Originally created by @fafamobile on GitHub (Aug 25, 2025).
Original GitHub issue: https://github.com/Googolplexed0/zotify/issues/62

Audio of downloaded tracks are sometimes quieter than others when downloaded - depends on mixing / mastered file submitted to Spotify (I can tell by the wave forms).

A cool feature may be to implement a CLI flag that increases the volume of the track when downloading (e.g --volume 1.5 for 50% increase). That way, if no volume flag is implemented, the default volume output is the spotify volume level. This would also give user control of the volume filter.

I have tried to play around with the track.py and main.py but haven't been able implement a proper working volume flag. Any quick suggestions would be great.

Originally created by @fafamobile on GitHub (Aug 25, 2025). Original GitHub issue: https://github.com/Googolplexed0/zotify/issues/62 Audio of downloaded tracks are sometimes quieter than others when downloaded - depends on mixing / mastered file submitted to Spotify (I can tell by the wave forms). A cool feature may be to implement a CLI flag that increases the volume of the track when downloading (e.g --volume 1.5 for 50% increase). That way, if no volume flag is implemented, the default volume output is the spotify volume level. This would also give user control of the volume filter. I have tried to play around with the track.py and _main_.py but haven't been able implement a proper working volume flag. Any quick suggestions would be great.
kerem 2026-02-27 04:57:16 +03:00
Author
Owner

@satonotdead commented on GitHub (Aug 25, 2025):

That's related to Spotify itself?

<!-- gh-comment-id:3221761992 --> @satonotdead commented on GitHub (Aug 25, 2025): That's related to Spotify itself?
Author
Owner

@fafamobile commented on GitHub (Aug 25, 2025):

That's related to Spotify itself?

No? I don’t think so? When you download the track, the wave forms of some of the tracks are comparatively lower. This would just mean you would be able to re-download and boost the volume of the specific track.

I managed to hardcode boosting the volume for every track on download, but realised it wasn’t the issue, rather the software I was using to play the tracks. Still, some of the tracks are lower in volume because zotify just extracts the mastered tracks from spotify as they are submitted.

I may be wrong, but I just thought it would be helpful, specifically since I am wanting tracks to be around the same volume level.

Edit:

Here is an example of two tracks downloaded using zotify. You can tell one is much quieter from the other looking at the wave forms.

Image
<!-- gh-comment-id:3221783135 --> @fafamobile commented on GitHub (Aug 25, 2025): > That's related to Spotify itself? No? I don’t think so? When you download the track, the wave forms of some of the tracks are comparatively lower. This would just mean you would be able to re-download and boost the volume of the specific track. I managed to hardcode boosting the volume for every track on download, but realised it wasn’t the issue, rather the software I was using to play the tracks. Still, some of the tracks are lower in volume because zotify just extracts the mastered tracks from spotify as they are submitted. I may be wrong, but I just thought it would be helpful, specifically since I am wanting tracks to be around the same volume level. Edit: Here is an example of two tracks downloaded using zotify. You can tell one is much quieter from the other looking at the wave forms. <img width="1920" height="229" alt="Image" src="https://github.com/user-attachments/assets/7f4e43d6-bb32-46da-84a1-fac39a69fbde" />
Author
Owner

@Googolplexed0 commented on GitHub (Aug 27, 2025):

I like this idea. Honestly it might be easier and more useful to allow users to pass custom FMMPEG args rather than add a cmd flag specifically for volume. Definitely would be more versatile.

I'd add a section of examples to the README, so non-technical users could still adjust simple things like volume and speed if desired.

<!-- gh-comment-id:3229050471 --> @Googolplexed0 commented on GitHub (Aug 27, 2025): I like this idea. Honestly it might be easier and more useful to allow users to pass custom FMMPEG args rather than add a cmd flag specifically for volume. Definitely would be more versatile. I'd add a section of examples to the README, so non-technical users could still adjust simple things like volume and speed if desired.
Author
Owner

@Googolplexed0 commented on GitHub (Sep 2, 2025):

Added to the still-experimental efficient-api branch (see 32cdfb52be)

<!-- gh-comment-id:3243462975 --> @Googolplexed0 commented on GitHub (Sep 2, 2025): Added to the still-experimental efficient-api branch (see 32cdfb52be566c955f7dc8430846ca6948d1af01)
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#51
No description provided.