Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
Steps to Reproduce
Expected behavior: The setting is persisted from one run to the next (alternatively, the default application volume is 100%)
Actual behaviour: The setting is 75% for each new run
Reproduces how often: 100% of the time
Installation Method Used
I'm currently using the snap package, although I believe I saw the same behavior with the AUR package (and it seems like a core functionality issue, so I'd imagine probably affects all installation methods)
Hi!, thanks for taking the time to report issues and provide feedback. This is always welcome.
I think your analysis is correct for the most part. Adding a config file option to set a default volume would be easy (and useful). I think this could be implemented quite quickly.
If anyone wants to help, I could provide some easy-to-folow instructions. Otherwise, I'll implement it when I have some time
I have to apologize. I was meaning to look at the implementation of this and then provide the details here for you to pick up, but I thought it was more work to detail it than to do it.
Please have a look at this commit:
Basically, this adds support for this configuration option:
The specified volume there will be honoured when the application is started.
It is in the develop, branch. I'm planning to cut a new release in the next few days.
No worries at all @tizonia , just glad it hit the roadmap. Thanks for the reference to the commit for context.
One thing I've noticed is when skipping through a playlist/album using
Thanks again for the enhancement, very much looking forward to it
Excellent, thanks so much! No worries at all. I use
I'll probably leave the Issue open until a release, or you can feel free to close whenever.