Announcements

Help Wizard

Step 1

NEXT STEP

Normalize volume not applying to artist/album previews

Normalize volume not applying to artist/album previews

The Normalize audio feature doesn't work on previews, making them WAAAAAY louder than normal playback. There's been multiple instances where I’ve opened the preview of an album (because I’d forget this issue) and had to throw off my headphones.
I use “Normal” normalization but this is especially bad with "Quiet" users, since you usually compensate by raising device volume, only for the previews to bypass normalization and blast audio at the increased volume level, risking hearing damage.
This is bad UX and a hearing safety hazard. In what scenario would you want this? Am I supposed to adjust volume/normalization before every preview?
Whether intentional or not, this needs fixing.
Reply
3 Replies

Hey there, 

 

Thanks for getting in touch about this and welcome to the Community. 

 

Thanks for bringing this to our attention. We went ahead and passed this onto the right team. We'll let you know here as soon as we get any news to share. 

 

Cheers!

EniModerator
Help others find this answer and click "Accept as Solution".
If you appreciate my answer, maybe give me a Like.
 
“Music acts like a magic key, to which the most tightly closed heart opens.”– Maria von Trapp

Hey there, 

 

We can confirm that this is the expected behavior of the feature. Currently, there is no volume control on the Preview player. 

 

We appreciate you taking the time to share your feedback with us and will make sure to pass it onto the right team, as we always strive to improve your experience.


Hope this clears things up. If you need a hand with anything else, the Community is here for you.

EniModerator
Help others find this answer and click "Accept as Solution".
If you appreciate my answer, maybe give me a Like.
 
“Music acts like a magic key, to which the most tightly closed heart opens.”– Maria von Trapp

Can you clarify what you mean by "expected behavior"?
Expected behavior as in based on how the code is written, that is the expected behavior (side effect)?
Or is it an intentional design decision? which would be problematic for the reasons addressed above.

Suggested posts

Let's introduce ourselves!

Hey there you,   Yeah, you! 😁   Welcome - we're glad you joined the Spotify Community!   While you here, let's have a fun game and get…

ModeratorStaff / Moderator/ 4 years ago  in Social & Random