[hamburglar]

I used to espouse this "finer control" argument but I've come to realize it was more typical nerd desire for hyperconfiguration than practical need. Yes, things make noises at different volumes and some are too loud and some are too quiet and they force you to jump and adjust the volume when this happens. But it's not generally predictable, so you're not going to set it just right ahead of time, and having N volume controls to go paging through to find the one that needs adjusting is a hell of a lot more difficult than just having a hardware control, always right there, that adjusts everything immediately. The number of times I've wanted to actually listen to multiple audio sources at once and carefully set their relative volumes is almost certainly in the single digits over my entire lifetime. Unless we're talking about doing mixing for an audio project, which of course we're not.

Every media player on every web page could set its volume permanently to 100% and I really would never even notice.

[timthimmaiah]

I think what we are thinking of is making volume control an optional parameter to enable/disable. That way we can give the embedder the ability to control that experience for the listener. Thoughts?

[anigbrowl]

I don't want the embedder to control my listener experience, actually. That person knows nothing about my listening environment, and I don't want to adjust for their content. I realize this isn't such a big deal for someone that has SoundCloud playing in the background on their laptop while they do something else, but it's a total pain in the ass for anyone who works with audio professionally.

[timthimmaiah]

Got it. We will be implementing volume control. Look for it in the next couple of days :)

[anigbrowl]

Awesome! Thanks for being so responsive, and I'll keep an eye on the project. Feel free to hit me up for feedback.