2020-03-24, 08:08
Hi guys, I ran out of posts the day I started this thread, then, sorry, was on hiatus there for a minute trying to deal with this virus and my aging parents, who want to act like they're on Spring Break...
Anyway, so I did some troubleshooting, and used MediaInfo to see what the audio codec was for several of the .mkv and .mp4 container videos in my collection. Next I picked about 10 to be sure I had a good mix of audio/video formats in the containers, and then tested them to see if the issue happened with each video. It did in all videos. So that eliminates audio codec types within video file containers as an issue.
I also noticed this during my testing: the first video I play after starting Kodi, I get the low volume/vol amp setting not applied issue. I open the audio settings, and the slider is at 24. I adjust the vol amp slider from 24 to 23.9. The video volume jumps to normal levels. I stop the video. Next, I play another video file. Again, volume is too low, but when I open the audio settings page, I see that the vol amp slider is still at the 23.9 I just set, not back at 24 again (per the "default for all media" setting). I move it to, say 24.4, the volume jumps back to normal again. Stop the video. Play another, it's still at 24.4... etc. If I restart Kodi, the first video I play the slider is back at 24 regardless of where it was for the last video before I closed it.
I expected that each time I play a new video, the slider and setting should go back to 24, since that's the default I set it at "for all media." I tested that setting out on another install of Kodi elsewhere, and the setting does act as I expected: each time I play a video on the other install, the vol amp slider is reset to 24. Every time. So something is hosed in my Kodi install.
I'm going to uninstall Kodi and manually remove any remnants from the registry and file system, and reinstall a fresh copy (I already reinstalled when this happened, but it didn't fix it). I'll report back if that fixes it, although even if it does, I'd really like to actually know why it happened so it doesn't happen again in the future.
In fact, this might be a true bug maybe? Considering that, do I want to do anything before I reinstall that might help identify this as a bug, like post some log files or something for the devs to look at?
Thanks again for everyone's help!
Anyway, so I did some troubleshooting, and used MediaInfo to see what the audio codec was for several of the .mkv and .mp4 container videos in my collection. Next I picked about 10 to be sure I had a good mix of audio/video formats in the containers, and then tested them to see if the issue happened with each video. It did in all videos. So that eliminates audio codec types within video file containers as an issue.
I also noticed this during my testing: the first video I play after starting Kodi, I get the low volume/vol amp setting not applied issue. I open the audio settings, and the slider is at 24. I adjust the vol amp slider from 24 to 23.9. The video volume jumps to normal levels. I stop the video. Next, I play another video file. Again, volume is too low, but when I open the audio settings page, I see that the vol amp slider is still at the 23.9 I just set, not back at 24 again (per the "default for all media" setting). I move it to, say 24.4, the volume jumps back to normal again. Stop the video. Play another, it's still at 24.4... etc. If I restart Kodi, the first video I play the slider is back at 24 regardless of where it was for the last video before I closed it.
I expected that each time I play a new video, the slider and setting should go back to 24, since that's the default I set it at "for all media." I tested that setting out on another install of Kodi elsewhere, and the setting does act as I expected: each time I play a video on the other install, the vol amp slider is reset to 24. Every time. So something is hosed in my Kodi install.
I'm going to uninstall Kodi and manually remove any remnants from the registry and file system, and reinstall a fresh copy (I already reinstalled when this happened, but it didn't fix it). I'll report back if that fixes it, although even if it does, I'd really like to actually know why it happened so it doesn't happen again in the future.
In fact, this might be a true bug maybe? Considering that, do I want to do anything before I reinstall that might help identify this as a bug, like post some log files or something for the devs to look at?
Thanks again for everyone's help!