Aw, okay. I misunderstood... I thought you were using pulseaudio even in kodi for digital output.
So, if you're using alsa in kodi like me, the only difference is analog or digital output? With digital audio your scripts work fine but with analog don't?
I'll wait for your fix now that it's identified. Thanks a lot for your work.
ALSA is basically useless & only needed for some special snowflake software like PCSX2. My TV uses HDMI and changing the ALSA Master volume does not even effect the audio output so it does not make sense to add any functions for this backend while PA normally works fine & is mandatory for video previews for example.
Sure. I agree to select pulseaudio as backend. So, maybe the code is not working for all the folks using analog outputs.
I would select pulse audio in kodi too, but it's not selectable for me 
I only have bluetooth audio output for pulseaudio section in kodi audio devices.
Okay so does your volume only change if you use Pulse? Or also when you use ALSA? If the code works it's only a question where I have to place it.
Nope. With alsa backend selected in rr config there's not volume selector available, so it's obvious it stays untouched at 100%.
Display MoreWell let's continue to find what's the root cause. When you run kodifreeze.sh freeze in a terminal it should stop Kodi also. Can you check if the ALSA volume changes too? (kodifreeze.sh unfreeze starts Kodi)
1 time with PA backend & 1 time with ALSA backend?
Depending on the backend setting it should give a different result.
LibreELEC.tv/kodifreeze.sh at libreelec-9.x-rr · 5schatten/LibreELEC.tv · GitHub
If for whatever reason the PulseAudio changes ALSA volume I could probably hardcode it too 100% back too though I have no clue how it touches the device.Which audio output do you use? HDMI or some analog?
with kodifreeze the volume drop to 44% and stays there after unfreeze (pulseaudio as backend). With alsa backend it stays always at 100% (that's the reason why we use pulse as backend: the emulators volume is too high)
Another way could be to provide a volume selector for alsa backend in rr config, as you developed for pulse backend. In this way with both backends everyone can set a backend volume.
Thank you again
does amixer set Master 100% unmute restore the volume for you? If yes I'll add it to the script
EDIT:
Do you know how to create and run a Linux script?
so log into a terminal then run nano test.sh copy & paste the content, then run chmod +x test.sh and finally ./test.sh
Bash#!/bin/sh # SPDX-License-Identifier: GPL-2.0 # Copyright (C) 2018-present 5schatten (https://github.com/5schatten) if [ ! $(amixer get Master | awk '$0~/%/{print $4}' | tr -d '[]%') = "100" ]; then amixer -q set Master,0 100% unmute echo "Restoring ALSA Master volume to 100%" fiIf this works I can add this straight to the script and this should fix this problem.
Yes, both worked fine.
Thank you
Analog. Thank you.
I'll try the tests.
Answering your "pulse audio changes alsa volume" I suggest to read the link I posted, it writes about it.
Just tried it.
1. Rebooted.
2. amixer returns 100%
3. systemctl stop kodi
4. amixer returns 100%
5. systemctl start kodi
6. amixer returns 100%
Continued some other tests.
7. run ra
8. amixer returns 44% (that is not 25% as defined in rr addon config, but it's okay because is pulse audio to be set, not alsa)
9. pactl list sinks | paste - http://ix.io/1g4b
10. exited ra
11. pactl list sinks | paste - http://ix.io/1g4c
12. Looked deep into amixer and alsamixer:
amixer returns all values to 100% but master to 44%, in alsamixer I find master to 18 value.
13. systemctl stop kodi
14. amixer returns 44%
15. systemctl start kodi
16. amixer returns 44%
Does these infos tell you something more?
Thank you
Again I don't change the ALSA volume so my scripts don't touch this. Does you volume only change if you run ES or change also if you run RA or Pegasus because all three are completely different.
What you can do is to reboot your system, enter systemctl stop kodi and check again with amixer or alsamixer if the volume has changed. Also grab this image LibreELEC Testbuilds for x86_64 (Kodi 18.0) and check if a recent LE master build shows a somewhat similar behavior -> if you made a clean install of my build you can switch between them on the fly.
The main question is under which circumstances the ALSA volume changes because my scripts don't touch it. You use this device? AOpen Digital Engine DE67-HA ab â¬Â 0 (2019) | heise online Preisvergleich / Deutschland
Yes, it happens with all three frontends (es, ra, pegasus).
I use a Fujitsu Esprimo Q900.
After rebooting the system the alsa volume goes back to 100% as already said in previous post. I'll try stop kodi just after a fresh reboot as you said to verify what volume value it loads. If this is the case, where can I find this volume definitions in the code? Thank you.
-----------------------------------------
I've already explained with details and logs in which circumstances the alsa volume changes: all the volume changes work correctly (booting the system, launching frontends) except exiting the frontends where alsa volume doesn't go back to 100% but is set to 44% (and this value doesn't match the value of pulse audio level set in rrconfig add-on which I set to 25%). This value (44%) could be useful to understand where an how it is obtained (very strange). I don't know what informations could be useful to you to understand something more about this issue, but please tell me what you need... I'm available to debug tasks and tests as told.
Can you provide some lines of code to add to your original code to debug? I'm not familiar with python, but I think if I can add some lines to print out some results to a text file for every if statement of the code you linked in the previous post, maybe we can point out where the code is not working as we expect.
As a workaround maybe I can add a line of code that doesn't use RR variables to set the volume back to 100% when exiting from emu frontend.
Thank you
Non of my config files or scripts ever touched the ALSA volume so I suspect some malconfigured addon or leftover causes this. The only thing that is configured is the PulseAudio volume & only temporary. Since nobody else ever reported a similar issue I tend to expect it's not related to my build.
But to make sure it's not some weird quirk grab an usb-drive install the latest build and check if still the volume drops when you launch RA since this should start out-of-the box.
Hi 5schatten,
I made the test right now and unfortunately the issue is still there: the volume drop to 44% after even only launching ES and exiting.
I installed your 0305 build on an USB drive and booted with that, upgraded the clean installation with the last 0404 (in the first release there's not the volume level configuration in the rr addon, just backend selection), configured pulse as backend audio and pulseaudio volume to 25% in RRconfig addon. Launched ES, exited, the volume in kody drop to 44% (amixer command through ssh in every step, like in your previous post).
What can I do to report to you something considerable to discover the issue?
Thank you
The keyboard issue is related to Retroarch -> needs to fixed by them
[Linux] [Regression] Keyboard keycodes no longer take into account keyboard layout · Issue #8303 · libretro/RetroArch · GitHubAbout the sound problem well it looks like it always sets back the volume to 44% no matter what you do. My scripts don't touch ALSA volume in any way so have you tried a clean install i.e. to an usb-drive to make sure it's not related to some quirks?
Well, I made a clean install with your release a few days after my first post on this thread (maybe less than 2 months) and on it I just copied the addon_data dirs related to the most important addons I had installed on official libreelec (amazon, netflix and tvheadend server) just to save my configurations and data.
All the emulation stuff is clean install of your release and the only things I modified are es config file and retroarch config file (after the last tests I tried to modify dolphin to set the volume).
So... I think the best way for me is to compare these three config files with the originals of your github. Isn't it so?
Really I would like to avoid reinstall it all again. Sure, I can test from a USB stick as you said too, but I think in the end I should compare those files to find out what's wrong.
I'll give feedback of what I'll find.
Thank you again
Display MoreAgain not a single log file is provided.
Enter this in a terminal setxkbmap -query |paste & post the link. I added libxkbcommon which Lakka also uses and updated all keyboard config & mapping files. Personally I don't see what else could be changed.
I hardly doubt that my script can change the ALSA volume because it reduce the volume of a temporary Pulse Audio sink
And once you return to Kodi it sets the volume of the sink back to 100% before it's unloaded.
So all in all the sink is created for the time the emulators or frontends are used and once you shut them down it sets the default volume and unloads it. So run this command in a terminal beforeamixer | paste you start a frontend and run it again while the emulation is running and once you return to Kodi. And post all links in the correct order.
The FAQ clearly states that audio for video previews is only available with PA and it also states that changing the audio configs in the emulators will probably screw the config at all so I don't see what might be "unexpected"
Thank you 5schatten
Here are the info.
setxkbmap -query | paste - http://ix.io/1fge
amixer | paste
in kodi: http://ix.io/1fgc
es launched: http://ix.io/1fgd
game dolphin launched: http://ix.io/1fgd
dolphin and es closed, back to kodi: http://ix.io/1fgd
rolled back volume to 100% with alsamixer (in alsamixer I find master volume to 18%, not 25% like RRconfig setting, not 44% like amixer pastebin says)
in kodi: http://ix.io/1fgc
es launched: http://ix.io/1fgd
es closed, back to kodi: http://ix.io/1fgd
rolled back volume to 100% with alsamixer
in kodi: http://ix.io/1fgc
pegasus launched: http://ix.io/1fgd
pegasus closed, back to kodi: http://ix.io/1fgd
I saw the it,us keyboard layout, but in libreelec configuration i cannot remove the second layout... so I changed the second to it too, but even after reboot it and verifying "setxkbmap -query | paste" - http://ix.io/1fgx the keyboard mapping is the same in retroarch (if I press the + button it recognize "rightbracket", if I press - button it recognize "slash" - in the + button I have the rightbracket corresponding to the AltGr combination, but in the - button I only have the _ )
Libreelec log file: log-2019-04-08-19.49.48.zip
Another test: if I leave the master volume to 18% in alsamixer and reboot the system, the alsa master volume rolls back to 100%.
Is there a way to manage audio volume for emulationstation/dolphin/mupen64plus? I tried different setups, but with no success.
1. Kodi uses alsa
2. Backend in RRconfig set to alsa - the emulationstation/dolphin/mupen64plus volume is very very high.
3. Backend in RRconfig set to pulse and adjust the volume to 25% - this works, but when you go back to kodi the volume is very very low - so checking it in alsamixer through ssh it shows the master volume changed to 25%. Have to ssh every time I use a game to roll the volume level back to 100%.
4. I tried to change the audio levels in dolphin configuration but it has no effect on the audio volume.
5. If I use alsa the audio of video preview of emulationstation doesn't work. With pulse it works.
6. In kodi I cannot select pulse because the only audio device I see on pulse driver is "bluetooth".
7. I cannot find a way to change the volume during execution of emulationstation, nor dolphin, nor mupen64plus.
Is it a bug that setting the volume in pulse sets it even in alsa or is it correct?
Thank you
Setup: intel nuc core i5 - ssd 128GB - 6GB RAM - intel integrated graphics - logitech k400r wireless keyboard ita layout + touchpad - 2 gamesir g3s - 1 dolphin bar + 1 nintendo wiimote plus + nunchuck - generic USB IR remote control - stereo speakers connected to analog out - LibreElec 9.x RR 0404 release.
P.S.: The keyboard stuff introduced in 0326 release didn't fix the keyboard layout/mapping issue.
Updated to the latest build, but not a single addon auto updated. There's no new TVHeadend version, so that doesn't work now
Have you been able to solve it? Thank you.
It takes some time until your Kodi refreshes the available addons.
I tried to manually update the addon, even remove and reinstall without removing addon config files, but it always display "installation failed" message I'm installing the previous 0803 build over the 1403.
Build RR-20190314-bdc55bc is online
- changed GCC optimize options from -Os to -O2 as escalade suggested & rooty brought up
- updated to latest LE 9.x
- switched addon repo from 9.0 to 9.1
- upgraded Generic kernel to 4.19.29 / RPi kernel to 4.19.28
- updated to mesa-19.0.0
- reverted nvidia driver to 410.104
- updated pegasus-frontend to Alpha 11
- updated Skyscraper to v3.1.3
- reorganized the Retroarch shaders -> check out the subdirs common | glsl | slang (Vulkan only)
- ppsspp: updated to v1.8.0+ / keep v1.7.5 for Amlogic_Legacy -> I pinged hrydgard and nagged a bit about the Vulkan issue and he fixed it after some debugging and testing. [Vulkan] anv_bind_buffer_memory: Assertion (...) failed. · Issue #11882 · hrydgard/ppsspp · GitHub
- lr-ppsspp: updated to v1.8.0+ / fix video stuttering -> intro videos should play fine now
- updated several libretro-cores
- updated citra & dolphin
Beware this is the first "true" LE 9.1 build so the addon repo is now based based on LE 9.1 too. Make sure you've enabled addon auto-updates and install all of them before you "nag" about non working stuff. Many outdated 9.0 based addons won't start because they were linked against openssl 1.0.2 for example. Once all of your binary addons provided by the LibreELEC repo pulled updates they should work fine again.
I think I updated to the last version without paying attention about tvheadend availability for LE9.1. Is there a way to reinstall tvheadend server on the new build?
Thank you
From my perspective it's pretty simple. If you run into problems you have to follow the rules. If you don't know which log might be helpful just follow the outlined steps.
Personally I don't care how you or others use RA. My gamepad has menu shortkey and manually loading and saving savestates just takes a blink of an eye. If you use a keyboard to suit your needs that's totally fine but first you have to make sure it's not your special snowflake hardware that's problematic.
A common misconception is that if something works in Kodi it has to run in ES or RA too. None of them are linked in any way. ES uses SDL for input handling while RA uses udev but could also use several other input APIs. Just because Kodi supports your multimedia keyboard this means basically nothing.Also I'm not aware of a "Retroarch installed on the official LE9" there is afaik only GitHub - bite-your-idols/Gamestarter: Retrogaming kodi add-on repository for LibreELEC which comes with Retroarch but at least in the past it partly relied on escalades or my binaries and pulled the cores from the build-bot. I guess you think Retroplayer is the same as Retroarch. Retroplayer is just team Kodis implementation of the Libretro API nothing more or less. If you still think they are the same just try to run any game that needs OpenGL or any other 3d acceleration in Kodis Retroplayer.
So in summary if you run into problems post logs. if you don't know which in particular post all of them (=logfile zip) If your keybaord behaves strange get a standard keyboard first connect it to your system and double check if it also maps wrong keys. I also own a Logitech multimedia keyboard and the function keys only work if pressed with the fn key first. Also I pointed to the libretro docs because this thread is mainly to iron out problems with this builds not how to configure Retroarch, Dolphin or else because there are dedicated forums for this.
Thank you. I have the same Logitech keyboard of yours, but with italian layout instead of german layout.
I mean exactly bite your idols retroarch implementation. With that my keyboard worked fine.
I know all the stuff you explained about differences between kodi, es, retroarch, etc. Maybe i have to change from udev to another one in retroarch. I will try... if you can check what you're using in your configuration, maybe you changed udev to other.
