Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Volume low despite settings in audio gui for Volume Amplification #17564

Closed
1 of 7 tasks
biner73 opened this issue Mar 26, 2020 · 7 comments · Fixed by #20136
Closed
1 of 7 tasks

Volume low despite settings in audio gui for Volume Amplification #17564

biner73 opened this issue Mar 26, 2020 · 7 comments · Fixed by #20136
Labels
Resolution: Fixed issue was resolved by a code change Triage: Needed (managed by bot!) issue that was just created and needs someone looking at it

Comments

@biner73
Copy link
Contributor

biner73 commented Mar 26, 2020

Bug report

Describe the bug

Here is a clear and concise description of what the problem is:
Sometimes when launching Kodi, the volume is low, despite having Volume amplification set as default for all, (.set at 14db currently) and Audio settings in gui showing 14db.

Expected Behavior

Here is a clear and concise description of what was expected to happen:

Once the Volume Amplification is set correctly, it should always work.

Actual Behavior

Possible Fix

To Reproduce

Steps to reproduce the behavior:

Steps to recreate:

  1. Launch Kodi
  2. Play media (movie or tvshow)
  3. Volume will be low (despite setting in gui)
  4. Bring up the Audio Settings in gui, and select the Volume Amplification slider.
  5. Move the slider down or up from current position, and volume will jump back up to current setting (14db) and will now be correct.
  6. Select "set as default for all media" again
  7. Close media and exit Kodi
  8. Start Kodi and volume will be low again, despite Volume Amplification will still be showing 14db.

Debuglog

The debuglog can be found here:
kodi.log

Screenshots

Here are some links or screenshots to help explain the problem:

Additional context or screenshots (if appropriate)

Here is some additional context or explanation that might help:

Your Environment

Used Operating system:

  • Android

  • iOS

  • Linux

  • OSX

  • Raspberry-Pi

  • Windows

  • Windows UWP

  • Operating system version/name:

  • Kodi version: 18.6 release
    WIndows 10 with all latest updates

note: Once the issue is made we require you to update it with new information or Kodi versions should that be required.
Team Kodi will consider your problem report however, we will not make any promises the problem will be solved.

@xbmc-gh-bot xbmc-gh-bot bot added the Triage: Needed (managed by bot!) issue that was just created and needs someone looking at it label Mar 26, 2020
@DaVukovic
Copy link
Member

Thanks for ignoring our template by not providing a debuglog.

Please provide one. We have to ask way to many questions to solve that what a simple logfile will answer.

@DaVukovic DaVukovic added the Ignored rules issue that does not follow the rules (no template, missing debug log, ...) label Mar 27, 2020
@xbmc-gh-bot
Copy link

xbmc-gh-bot bot commented Mar 27, 2020

Thank you for using Kodi and our issue tracker. This is your friendly Kodi GitHub bot 😉

The issue that you have opened was marked as ignoring the rules of our bug tracker by a team member. Please review the following requirements for issue reports and make sure that you follow all of them:

  • Reports must follow our template and have all relevant fields filled in.
  • A full debug log is always mandatory.
    • Make sure that you restart Kodi after setting the log level to debug.
    • Log files may not be modified except for the removal of personally identifying information, usernames/passwords and similar.
    • For build errors, include a full build log instead.
  • You may not have any banned add-ons installed.
  • Bugs should be reproduced on a clean Kodi installation whenever possible.

Please understand that adherence to these rules is required for the team to be able to handle the volume of open issues efficiently. The issue will be closed after one week has passed without satisfactory follow-up from your side.

@biner73
Copy link
Contributor Author

biner73 commented Mar 27, 2020

kodi.log
Attaching debug log

@pcurtis456
Copy link

Hi there.
Ive got exactly the same problem.
kodi.log

@DaVukovic
Copy link
Member

@biner73 You are using directsound if I'm not mistake. Does it make any difference if you are using WASAPI?
Also, just for the note. It's pretty normal that movies do have a different loudness. Beside using the volume amplification, I would rather suggest to regulate the volume on the TV/AVR in use. Not saying that there might not be a bug somewhere. Just making a suggestion. Using the volume amplification on such a high level wouldn't be something I would recommend at all. As (as far as I understand), by using the Kodi amplification, at some point it will sound pretty bad and I guess your TV or your AVR can do a better job on this.

Maybe @fritsch is able to confirm.

@pcurtis456 You are not playing anything in that log.

@DaVukovic DaVukovic removed the Ignored rules issue that does not follow the rules (no template, missing debug log, ...) label Apr 5, 2020
@biner73
Copy link
Contributor Author

biner73 commented Apr 7, 2020 via email

@biner73
Copy link
Contributor Author

biner73 commented Mar 31, 2021

I've been doing more testing, and I think this issue started with Kodi 18.0 when the menus for audio settings and subtitle settings were split apart. In Kodi 17.6, where the audio/subtitle onscreen menu is together in one, this issue does not occur.

I also noticed that in Kodi 18 in addition to the volume amplification "not remembering" the setting after Kodi is shutdown/started, subtitles flash at the beginning of playback. I believe that during the transition from Kodi 17->18 where the audio/subtitles dialogs were seperated, there is a bug somewhere around how they read/process the settings from guisettings.xml on startup.

Hope this might be a direction to look in.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Resolution: Fixed issue was resolved by a code change Triage: Needed (managed by bot!) issue that was just created and needs someone looking at it
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants