Posts by 5schatten

Quote from HaLeXz

Well, it seems your use of retroarch is somewhat limited if you're not considering all the retroarch hotkeys you can use during gameplay (volume up/down, for example, or save/restore state, or change save slot). Gamepads are for playing, keyboard is for managing retroarch

As already said, in kodi and chrome the keyboard is working fine, so it's obvious I've already applied the right configuration in kodi for my keyboard layout

I wrote to you because, as already said, only in retroarch the keyboard layout is totally wrong. And, if YOU read the libretro docs link you sent to me, there's nothing about configuring/fixing keyboard layout (I've already read it before writing to you the first time, and this is the third for the same problem)

So, please, don't think every question people ask to you are "waste of time"... I thought maybe you hardcoded something in retroarch binaries that messes up the layout... In retroarch installed on the official LE9 build my keyboard layout was right... it must be something in your retroarch implementation

In retroarch configuration there's nothing about keyboard layout... you can only configure mappings... but, if you want to map "-" key for volume down and when you press it in the mapping it maps "f3", you see... the layout is wrong...

Thank you

Display More

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.

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.

You can right click on the "LibreELEC Add-ons" repo and let manually search for updates if you don't want to wait.

Quote from BlaBla1973

Sorry for the delay.

The milhouse version(LibreELEC-Generic.x86_64-9.1-Milhouse-20190311210303-#0311-g28f2bb3) works without any problems.

Ca you try build RR-20190314-bdc55bc? I reverted the driver update and maybe this solves your problem.

Quote from andersos

5schatten

Can you please update MakeMKV to latest version? I have a Blu-ray that doesn't play now. Probably needs the new AACS of the latest MakeMKV.

I can update the addon but it won't work on for Milhouse & my builds because it will depend on glibc 2.29 & openssl 1.1.1 so is 9.1 only.

https://drive.google.com/open?id=1wwixtfci-ar9vzebgdy5yv18q28ut6af

If you still use vanilla LE then ping duck7000 and kindly ask for the addon package -> he builds my addon for the 9.0 branch.

Quote from kodi_for_president

Okay.

If I understand it correct, Chrome and Spotify-Client are not in the raspberry pi images.

Is there a way I can add them manually or do they simply not work for arm-based cpus?

You can use librespot on ARM if you have a premium account but Chrome is for generic only.

Quote from kodi_for_president

I currently have the latest milhouse build of official libreelec on my pi3 b+.

Can I now just set my Update Channel to Index of /builds/ and update?

Or do I need to flash the 9.1 Version from your Starting post and then set the Update-Channel?

Does the Netflix addon (widevine encrypted) work with your fork?

Thanks

This is LE 9.x with additions so what works with master LE most likely works with my build too. But you have to make a clean install first. Afterwards you can switch between any version as you like but since vanilla LE uses 512MB partition size my builds don't fit.

Quote from scottns

Are there any 32-bit graphics libraries for Nvidia cards in your build? From what I've been reading that my be why PCSX2 is not working for me.

PCSX2 is included in a Docker image because generic LE builds are 64bit only The Docker image of course features only one Nvidia driver which is recent. So it installs this Arch Linux - nvidia 418.43-7 (x86_64) which ist right now version 418.43 and all other drivers can't be installed at the same time Reverse Conflicts: nvidia-340xx, nvidia-340xx-dkms, nvidia-390xx, nvidia-390xx-dkms, nvidia-dkms so if you own an older card which is not supported by the lates driver set it will fail.

In the end blame either PCSX2 because they are too lazy to rewrite a proper 64bit recompiler or blame Nvidia for not including opensource drivers that cover all of their products.

rooty

you can run sm-checker in a terminal to see what kind of vulnerabilities exist & what kernel commands you've to add to disable them.

Quote from HaLeXz

Ok for opengl-vulkan stuff. For the keyboard layout, I don't know what logs could be helpful to you... if I run chrome, the keyboard layout is right, if I try to write in emulationstation, it's right... if I run retroarch and go to the input configuration to remap some keys (volume up/down for example), when I press the keyboard keys, no key has the right association.

I have a Logitech wireless keyboard+mousepad (fn key present) with Italian layout.

Thank you

Well if you have an italian keyboard layout & a multimedia keyboard you can't expect it to work out of the box. You have to change your keyboard layout in LibreELEC settings to get your keys interpreted as italian layout and you have to probably have to change the language in Retroarch to italian too.

Also I'm not entirely sure what you're going to remap and what purpose this serves. In the end it makes not much sense to use any emulator without a proper gamepad

Anyway there is a complete documentation available for such topics Input and Controls - Libretro Docs

Quote from rooty

5schatten, a though concerning Spectre & Meltdown vulnerabilities... It's a known fact that related patches for the vulnerabilities are slowing down an OS.

I know those patches are crucial for hosting companies for obvious reasons. As for LibreELEC we basically have just root user so I feel like it's useless to have them enabled.

Well I'm not an expert if it comes to spectre & meltdown but afaik it's partly about isolating memory content from access of other software so i.e. one website shouldn't be able to read your protected account data from another one. Anyway those patches are included in bios updates, kernel firmware and finally in in the kernel itself. If you think it's worth it then feel free to disable them, I'll stick to the LE upstream kernel as far as possible.

Btw. a lot of lr cores like mame2010, scummvm, yabause etc. already use -O3 as GCC optimization so I hardly doubt you'll see any crucial performance improvements.

As escalade said if you have to tweak GCC optimize options to make things run properly you better think about upgrading your hardware

Quote from crookers13

Well you run your games in 4K on a "Haswell" system. :D:D:D my bad.

That hadnt even crossed my mind, I only had a new 4K TV delivered yesterday so it has always just been set at 1080/60 not 2160/30

Kodi had autodetected and switched over to 4K, I've just switched it back to 1080 at 60 and everything is fine and working.

apologies for all the hassle. feeling at bit silly now.

Cheers for all the help.

Correct me if I'm wrong but you need at least HDMI 2.0 or Displayport 1.2 to drive your Display at the resolution & desired refresh rate. So maybe change the output device to DP if available.

Quote from crookers13

it was the "use module-udev-detect to autodetect PulseAudio device" option

hastebin

thats the kodi log from log uploader and below are the other logs from the var folder

thanks for looking into this.

This is only necessary if autodetect doesn't work or if you use a GPU as video output for example. The tsched option is independent of this.

Well you run your games in 4K on a "Haswell" system.

My build isn't optimized/tested for this resolution and maybe doesn't set appropriate refresh rates. You've probably have set Kodi to 50Hz or something and so NTSC games won't run at full speed also the log says "Rate 60.00 Hz not available for this size" so I'm not sure if your system or display can use 4K@60Hz

Open a terminal and enter this: xrandr | paste and post the generated link. Also post a full log zip because I have no clue what system you use.

Quote from crookers13

Hi

I hadn't tried that but I have just tried it now and also disabling the udev option above it as well and the problem still persists.

Which logs do you require? the standard kodi logs or emulationstation?

cheers

What kind of udev option? Read the start post there is explained how to obtain logs.

Quote from crookers13

Hello mate

Scharen

Just wanted to say thanks for a great build.

I have just updated to the above version, kodi is working all good with sound options but when I start emulationstation intially I had no sound playing on the videos and all the sound in the games are playing really slow and weird sounding, so had a read through here and used the rr config addon to change to HDMI dev 1 and changed backend audio to pulse from ALSA.

Did a reboot and now the sound is great playing the videos etc.

The problem I'm having is that when I start any game in any system the audio in the game itself is playing really slow and muffled low tones instead of normal.

All the games sounds were working on the previous version I was using which was RR-201907-011018c i believe.

I have tried everything from changing the hdmi to changing the audio back end from pulse to ALSA but still nothing in the games it still just plays really slowly.

Im on the generic build with built in intel graphics.

Cheers for any help with this.

Crookers

Display More

You've tried to disable tsched if you use PA? In the past I had hard coded tsched=0 which disabled it for all systems but now you can enable or disable it if you need to.

Anyway I need logs.

BlaBla1973
You could try this build Index of /testing/ it comes with the older Nvidia 410.104 driver. But beware this is a true LE 9.1 build that depends on 9.1 addons so after the update you have to wait until all LibreELEC addons pulled updates from the repo too.

escalade
-Os saves me about 10MB compared to -O2 so my image size increased from 639MB to 649MB and I literrally couldn't care less
If some programs run at least 1,5% faster it's worth it and if not it won't hurt.

HaLeXz
If you had problems with PPSSPP & Vulkan too this is fixed in 1.8.0+ [Vulkan] anv_bind_buffer_memory: Assertion (...) failed. · Issue #11882 · hrydgard/ppsspp · GitHub

Quote from BlaBla1973

I did provide a log file, but the wrong one (?)

Here are my log files, tested the version RR-20190307 (and RR-20190308)

Kodi lists hdmi:CARD=NVidia,DEV=0 as device

2019-03-13 20:20:59.509 T:140256358246144  NOTICE: Found 2 Lists of Devices
2019-03-13 20:20:59.509 T:140256358246144  NOTICE: Enumerated ALSA devices:
2019-03-13 20:20:59.509 T:140256358246144  NOTICE:     Device 1
2019-03-13 20:20:59.509 T:140256358246144  NOTICE:         m_deviceName      : default
2019-03-13 20:20:59.509 T:140256358246144  NOTICE:         m_displayName     : Default (HDA NVidia HDMI 2)
2019-03-13 20:20:59.509 T:140256358246144  NOTICE:         m_displayNameExtra:
2019-03-13 20:20:59.509 T:140256358246144  NOTICE:         m_deviceType      : AE_DEVTYPE_PCM
2019-03-13 20:20:59.509 T:140256358246144  NOTICE:         m_channels        : FL, FR
2019-03-13 20:20:59.509 T:140256358246144  NOTICE:         m_sampleRates     : 32000,44100,48000,88200,96000,176400,192000
2019-03-13 20:20:59.509 T:140256358246144  NOTICE:         m_dataFormats     : AE_FMT_S32NE,AE_FMT_S16NE,AE_FMT_S16LE
2019-03-13 20:20:59.509 T:140256358246144  NOTICE:         m_streamTypes     : No passthrough capabilities
2019-03-13 20:20:59.509 T:140256358246144  NOTICE:     Device 2
2019-03-13 20:20:59.509 T:140256358246144  NOTICE:         m_deviceName      : hdmi:CARD=NVidia,DEV=0
2019-03-13 20:20:59.509 T:140256358246144  NOTICE:         m_displayName     : HDA NVidia
2019-03-13 20:20:59.509 T:140256358246144  NOTICE:         m_displayNameExtra: HDMI #0
2019-03-13 20:20:59.509 T:140256358246144  NOTICE:         m_deviceType      : AE_DEVTYPE_HDMI
2019-03-13 20:20:59.509 T:140256358246144  NOTICE:         m_channels        : FL, FR
2019-03-13 20:20:59.509 T:140256358246144  NOTICE:         m_sampleRates     : 32000,44100,48000,88200,96000,176400,192000
2019-03-13 20:20:59.509 T:140256358246144  NOTICE:         m_dataFormats     : AE_FMT_S32NE,AE_FMT_S16NE,AE_FMT_S16LE,AE_FMT_RAW
2019-03-13 20:20:59.509 T:140256358246144  NOTICE:         m_streamTypes     : STREAM_TYPE_AC3,STREAM_TYPE_DTSHD,STREAM_TYPE_DTSHD_MA,STREAM_TYPE_DTSHD_CORE,STREAM_TYPE_DTS_1024,STREAM_TYPE_DTS_2048,STREAM_TYPE_DTS_512,STREAM_TYPE_EAC3,STREAM_TYPE_TRUEHD
2019-03-13 20:20:59.509 T:140256358246144  NOTICE:     Device 3
2019-03-13 20:20:59.509 T:140256358246144  NOTICE:         m_deviceName      : hdmi:CARD=NVidia,DEV=1
2019-03-13 20:20:59.509 T:140256358246144  NOTICE:         m_displayName     : HDA NVidia
2019-03-13 20:20:59.509 T:140256358246144  NOTICE:         m_displayNameExtra: HDMI #1
2019-03-13 20:20:59.509 T:140256358246144  NOTICE:         m_deviceType      : AE_DEVTYPE_HDMI
2019-03-13 20:20:59.509 T:140256358246144  NOTICE:         m_channels        : FL, FR
2019-03-13 20:20:59.509 T:140256358246144  NOTICE:         m_sampleRates     : 32000,44100,48000,88200,96000,176400,192000
2019-03-13 20:20:59.509 T:140256358246144  NOTICE:         m_dataFormats     : AE_FMT_S32NE,AE_FMT_S16NE,AE_FMT_S16LE,AE_FMT_RAW
2019-03-13 20:20:59.509 T:140256358246144  NOTICE:         m_streamTypes     : STREAM_TYPE_AC3,STREAM_TYPE_DTSHD,STREAM_TYPE_DTSHD_MA,STREAM_TYPE_DTSHD_CORE,STREAM_TYPE_DTS_1024,STREAM_TYPE_DTS_2048,STREAM_TYPE_DTS_512,STREAM_TYPE_EAC3,STREAM_TYPE_TRUEHD
2019-03-13 20:20:59.509 T:140256358246144  NOTICE:     Device 4
2019-03-13 20:20:59.509 T:140256358246144  NOTICE:         m_deviceName      : hdmi:CARD=NVidia,DEV=2
2019-03-13 20:20:59.509 T:140256358246144  NOTICE:         m_displayName     : HDA NVidia
2019-03-13 20:20:59.509 T:140256358246144  NOTICE:         m_displayNameExtra: HDMI #2
2019-03-13 20:20:59.509 T:140256358246144  NOTICE:         m_deviceType      : AE_DEVTYPE_HDMI
2019-03-13 20:20:59.509 T:140256358246144  NOTICE:         m_channels        : FL, FR
2019-03-13 20:20:59.509 T:140256358246144  NOTICE:         m_sampleRates     : 32000,44100,48000,88200,96000,176400,192000
2019-03-13 20:20:59.509 T:140256358246144  NOTICE:         m_dataFormats     : AE_FMT_S32NE,AE_FMT_S16NE,AE_FMT_S16LE,AE_FMT_RAW
2019-03-13 20:20:59.509 T:140256358246144  NOTICE:         m_streamTypes     : STREAM_TYPE_AC3,STREAM_TYPE_DTSHD,STREAM_TYPE_DTSHD_MA,STREAM_TYPE_DTSHD_CORE,STREAM_TYPE_DTS_1024,STREAM_TYPE_DTS_2048,STREAM_TYPE_DTS_512,STREAM_TYPE_EAC3,STREAM_TYPE_TRUEHD
2019-03-13 20:20:59.509 T:140256358246144  NOTICE: Enumerated PULSE devices:
2019-03-13 20:20:59.509 T:140256358246144  NOTICE:     Device 1
2019-03-13 20:20:59.509 T:140256358246144  NOTICE:         m_deviceName      : Default
2019-03-13 20:20:59.509 T:140256358246144  NOTICE:         m_displayName     : Default
2019-03-13 20:20:59.509 T:140256358246144  NOTICE:         m_displayNameExtra: Bluetooth Audio (PULSEAUDIO)
2019-03-13 20:20:59.509 T:140256358246144  NOTICE:         m_deviceType      : AE_DEVTYPE_PCM
2019-03-13 20:20:59.509 T:140256358246144  NOTICE:         m_channels        : FL, FR
2019-03-13 20:20:59.509 T:140256358246144  NOTICE:         m_sampleRates     : 5512,8000,11025,16000,22050,32000,44100,48000,64000,88200,96000,176400,192000,384000
2019-03-13 20:20:59.509 T:140256358246144  NOTICE:         m_dataFormats     : AE_FMT_U8,AE_FMT_S16NE,AE_FMT_S24NE3,AE_FMT_S24NE4,AE_FMT_S32NE,AE_FMT_FLOAT
2019-03-13 20:20:59.509 T:140256358246144  NOTICE:         m_streamTypes     : No passthrough capabilities

You're using DP-1 as connector

2019-03-13 20:22:04.424 T:140252626810624 NOTICE: Display resolution ADJUST : DP-1: 1920x1080 @ 23.98Hz (22) (wei ght: 0.000)

So I don't see what's the problem Which output did you use at my older build?

Also post a full log zip.

You could try LibreELEC Testbuilds for x86_64 (Kodi 18.0) / libreelec-generic.x86_64-9.1-milhouse-20190311210303-#0311-g28f2bb3.tar so one of Milhouse test builds which is based on master too and check if Kodi audio is working. It's possible that something is broken in 418.43 so I would revert to 410.104.

Quote from escalade

Never heard of issues with -O2 in general.

The Performance Between GCC Optimization Levels - Phoronix

-O2 is faster, there is IMO no valid reason to use -Os over it unless you are running out of space on /flash.

Maybe it made sense in the past but diskspace is pretty cheap nowadays

Quote from escalade

You need to look at TARGET_CFLAGS which includes GCC_OPTIM: LibreELEC.tv/optimize at a98586ba336e1d396e8f6c95bae42106ec9113ac · LibreELEC/LibreELEC.tv · GitHub

So the default is still -Os.

Of course, even RPi can run arcade games at full speed, this will only matter in cores like Citra, reicast, ppsspp and the likes.

Ah I see you've set it to -O2 LibreELEC.tv/optimize at le82 · escalade/LibreELEC.tv · GitHub did you run into any problems?

Anyway Os is basically O2 without some space saving features but I guess the last note could be important,

Quote from https://gcc.gnu.org/onlinedocs/gcc/Optimize-Options.html

-Os

Optimize for size. -Os enables all -O2 optimizations except those that often increase code size:

-falign-functions -falign-jumps

-falign-labels -falign-loops

-fprefetch-loop-arrays -freorder-blocks-algorithm=stc

It also enables -finline-functions, causes the compiler to tune for code size rather than execution speed, and performs further optimizations designed to reduce code size.

Display More

I guess I should give "-O2" a try then.

Quote from escalade

Here's a recent compiler optimization benchmark: GCC 9 Compiler Tuning Benchmarks On Intel Skylake AVX-512 - Phoronix

They conclude with -O2 being the most effective option, although as you can see applications like C-Ray greatly benefit from more specific tuning. As far as I understand it, the AVX optimization of the compiler does not depend on the application itself utilizing AVX.

Would be interesting with some actual benchmarks of emulators, haven't bothered with it myself (is there a good way to do benchmarks with RetroArch?). I think there's definitely a benefit, but most likely nothing you'd be able to spot with your eyes. I really should just buy a new computer instead of obsessing over optimizations

To be honest I'm not an expert if it comes to compiler optimizations. If it comes to ARM there is a huge benefit if NEON is used by the emulator and makes the difference between running at increased resolution or starts with stuttering sound as you can see at PCSX_reARMed.

I've tested Dolphin a while ago with [Unofficial] New Dolphin 5.0 CPU benchmark - results automatically updated! and there was some fluctuation but the AVX optimized build had no real impact on my performance. As I said the IGP was the bottleneck.

Stuff like beetle-psx suffers from missing x86 dynarecs so there are other problems as well. From my perspective you have either a low-end cpu like an Atom or Celeron which lacks AVX and runs not that fast or you use a more or less recent i3/i5/i7 which is fast enough to properly emulate games anyway and you won't gain any benefit since most games are capped at PAL or NTSC refresh rate or anything related to an integer divisor or them. Also there are plenty of alternatives if it comes to x86 emulation so if Mesen or BSNES won't run you could always use Nestopia or snes9x, same goes for MAME if 2016 is no option try 2003-plus or Final Burn Alpha. I still use a somewhat dated i3-6100 and I'm able to run everything at full speed. Even my cheap @$$ ~70€ J3455-ITX board is able to run most emulators & games and even simple Dolphin stuff at basic resolution. Even my oldschool x220 Thinkpad was able to run most games beside PCSX2 and Citra.

Correct me if I'm wrong but looks like -O2 & native is already the default for LE?

https://github.com/LibreELEC/LibreELEC.tv/blob/master/config/optimize#L25

Quote from duck7000

i have a , probably noob, question

In the package.mk in depend folder there is a sha256 code.

Did you make this hash code yourself, because it is not available on the makemkv download site?

This hash is generated by the download script used by LE

Quote from butanon2

I have pressed the FN key before pressinng the F1 key but nothing happens.

The problem was the hotkey. The 'alt' button was defined as a hotkey.

The "alt" key isn't used in Retroarch but in Emulationstation.

Quote from HaLeXz

Hi 5schatten! I have finally installed your great build. Thank you for your work and time!

I have an issue with the wireless keyboard+mousepad connected to my Intel nuc (Logitech). It's working fine in kodi, but in retroarch the key mapping is totally wrong (ex. - button maps to f3). I think it could be a misconfiguration at shell level. How can I configure the keyboard mapping/configuration?

Glide works fine, vulkan don't. Intel integrated graphics. Is it normal?

Thank you

Logs.

I don't know what you mean by Glide? OpenGL? Vulkan should work for specific games with Intel IGP. Dolphin should work, PPSSPP used to work but crashs right now probably due to Mesa 19.0.0-rc7 bugs or else. Most libretro cores won't work flawless with Vulkan so it makes no sense to enable it in Retroarch. Basically Vulkan makes sense for Dolphin everything else won't suffer from OpenGL or doesn't support video acceleration at all.