I compiled another image which include a series of patches for HDR on LSPCON. I don't have any devices with LSPCON so no idea if this will work. If anyone wanna try it don't forget to enable "Allow hardware acceleration - PRIME" in Settings-->Player.
whoa .. whoa .. whoa ..
is this a LibreELEC generic build with 4k HDR in development?? If so, I will be glad to help, i THINK i might have a LSPCON .. i have an 8th gen i3 NUC.
Display MoreOn the very first run on a new install there will be an example.zip under amiga just to get ES started (look at /usr/bin/es-firstrun.sh which is started by /usr/lib/systemd/system/es-firstrun.service). ES is somewhat user-unfriendly in matters of getting it up and running, but once it's set up it does a good job of actually launching games and presenting them in a clear way.
Ok, I'll explain a bit about how I intended audio to work as it doesn't seem to automagically work for everyone like it should.
Normally, Kodi is run either with sound output to either Pulseaudio or directly to ALSA. LibreELEC patches Kodi in order to use ALSA, but also keep Pulseaudio available as a choice in order to use Bluetooth speakers. When using ALSA, it's easy to pick an output from the list that appears in Kodi. When using Pulseaudio, Kodi doesn't have functionality to show available sinks, cards, ports etc.
You can get it to behave like vanilla LibreELEC if you like, by setting the environment variable KODI_AE_SINK=ALSA+PULSE in /storage/.config/kodi.conf.
Now why don't I just keep that as a default? Well, if you would like to use emulators then most likely you would need to tailor an asound.conf in order to get audio as well. In other words, some manual setup will be needed either way. On the plus side, once Pulseaudio is set up properly you will be able to have sound in Kodi without it locking the sound card. This way you can for example stream A2DP music from your phone and at the same time have GUI sounds in Kodi, or even watch a movie. Same goes when using emulators. I think the best solution is to have Pulseaudio working correctly.
So... this might sound overcomplicated and you just want to have sound. I get it, the process could be a lot simpler. Basically, you need to tell Pulseaudio which output to use. Here's a small cheat sheet:
List available "sinks" (audio outputs):
# pactl list sinks short
If you have several soundcards, you might need to set the default sink like so:
# pactl set-default-sink alsa_output.pci-0000_00_1f.3.hdmi-stereo
If you still don't have sound, it might be because your sound card have several ports (like HDMI1/HDMI2 etc) and Pulseaudio didn't detect the active one. List your cards profiles and ports like this:
# pactl list cards
Set a profile like this:
# pactl set-card-profile alsa_card.pci-0000_00_1f.3 output:hdmi-surround-extra2+input:analog-stereo
"extra2" is equivalent to HDMI3 on my system, you should be able to figure it out by using the above commands and some patience. If you provided me the logs, they would include all this information so I could tell you the exact command.
Pulseaudio works out of the box on my NUC8, and also when booting the image in VMware on my laptops. I'm curious as to why the auto detection fails for you though.
Okay. Decided to play around with that box again tonight. First thing, I updated to latest build by placing your image in /storage/.update .. worked like a charm.
Next, like with previous build and this build GUI audio works fine right off the bat. However I tried to play a video and nothing. So i wanted to test your instructions of making it like vanilla LibreELEC by placing "KODI_AE_SINK=ALSA+PULSE in /storage/.config/kodi.conf". There is no file like that on my system. I tried to make a file and got this error.
bedroom:~ # nano /storage/.config/kodi.conf
nano: error while loading shared libraries: libncurses.so.6: cannot open shared object file: No such file or directory
What am I missing?
Same as regular LibreELEC, drop the image in the update folder and reboot.
Got it. Cool.
quick question escalade .. any rec's on doing upgrades for your builds short of a re-install? or is it just backup the userdata folder, install to system drive, copy userdata folder back?
Logs please. You guys might need to set the default card, sink or maybe port in Pulseaudio.
@pletobia
That's how Emulationstation behaves until you add ROMs
New images uploaded for every target:
- Mesa updated for the latest performance improvements.
- Linux 5.7 from torvalds' tree has the new exFAT driver from Samsung and Zstd compression for F2FS.
- Latest Sway git + more polish (now shows resolution in the top bar)
- Qt apps should now look like the GTK default (Adwaita)
- Added Discord support to RPCS3
- WayVNC is included # systemctl start wayvnc to run it
- Samba 4.12.1
- Latest SDL2 git
Firefox 75 now has VAAPI support (before X11 too!). At this point only works for H264, so you might consider adding the h26ify to enjoy HW accelerated youtube. Firefox 76 should enable it for all formats I think.
Will give this one a whirl. I'll add a rom of some sort. Previous builds I guess you added something under Amiga and I never saw that screen before.
As for audio. Can you explain a bit more how to do that? Also I was reading through old posts regarding audio in this thread. I know at one point you had it configured to actually use ALSA for Kodi but pulse audio outside of it. I normally use ALSA on other builds but i've seen posts here that with some config you can actually do passthru audio via pulseaudio. That would be something I want to do also but I couldn't find a good post on how to accomplish this.
Loaded this image on my NUC: RetroELEC-Generic.x86_64-9.2-devel-20200406011507.img.gz
Still no audio on loading Kodi. Was gonna try the same thing I did with previous build of starting ES and then going back into Kodi as that works to enable audio in Kodi however ES starts and I get an error "Can't find any systems! ..." when it starts. Quits to a desktop and then loads up again with same error message.
EDIT:
I tried this image now: RetroELEC-Generic.x86_64-9.2-devel-20200406103004.img.gz and still same thing. When you start up ES you get an error "Can't find any systems!...".
Unfortunately I deleted my March build image so I can't go back to that 
I would like to mount stuff NOT to /auto but rather place my rom's folder stored on my NAS via NFS onto /storage/roms
Can I do this?
Also, first post about how to use AutoFS doesn't work.
bedroom:~ # ls -l /auto/nfs/192.168.5.112/Jean.Luc.Picard/
ls: /auto/nfs/192.168.5.112/Jean.Luc.Picard/: No such file or directory
Installed the latest generic image on my NUC (its an 8th gen i3). I get no sound in Kodi. Initially when i was messing around with it my audio choices were:
Default,Default output device(pulseaudio)
Built-in audio Digital stereo, hdmi(pulseaudio) <-- or something like that, I can't remember exactly now because currently it doesn't even let me go into the audio choice, its greyed out. When i was able to select an option neither one gave me gui sounds. Seems after attempting to play a video which didn't play audio it doesn't let me select anything anymore.
No idea what else to provide info wise right now but here is my debug log after a fresh restart.
EDIT:
So i decided to try to run a ROM in ES. It played with audio. Went back into Kodi and now the audio setting is no longer greyed out AND audio is working both in GUI and also in a movie. Reboot the NUC and no audio again and setting is greyed out.
Before coming across this project I first stumbled across this one.
I was just curious how they differ.
EDIT:
Played around with both using usb live sticks.
I was able to get sound to work with the LibreELEC-RR properly (ie ALSA inside kodi so I can do passthrough) but no sound to come through with RetroELEC in kodi, but it did have sound coming through in the ROMs.
Other thing I noticed, LibreELEC seems to have stalled in dev as no updates since Oct of '19 and the Kodi build is at 18.4 while RetroELEC has much more recent nightly's and even are running Kodi 18.6 which does bode better for the future.
In case anyone else becomes interested in Vero vs RPi4 benchmarks.
RPi4 Performance - General Discussion - OSMC Forums
Now my waiting game begins for proper 4k HDR with HD audio streams from RPi4 to the TV.
Cool. Will post there too.
I'm curious because I feel limited by the Vero4k+. I know the RPi4 isn't ready yet for proper 4k hdr but its on its way. Plus I wouldn't be limited to 16GB either. Ideally there would be an x64 option as then I would have no problems running my intensive skin and large media collection.
I was wondering how the performance of the Pi4 compares to the Vero 4k+. I ran CPUBench on my Vero and get roughly a score in the 13500-14000 range.
Get yourself a NAS ....
I have no problems using my NUC booted into windows with HDR. The pi might be better but it’s newer (newer will always be better...) - you’ll also have the heat issue to deal with. My silent fanless 8th gen NUC is perfect for me at the moment, running much cooler than my pi 4 does just at idle...
Any chance I can pick your brain PlatypusW? I have an 8th gen NUC and its not working out for me I feel. When I enable HDR in windows it looks horrible, so washed out and gray. Your not having this issue?
Been a few months and a new build of Kodi since I last asked so I figured I'd check in. Any chance HDR is working yet? Was thinking of buying a 4k tv soon and not have to use a Vero 4k but rather a intel nuc.
from my understanding Kodi can play 10bit HDR, but you won't see the HDR effect at your screen
I think at this point I'll just hold off on Linux and 4k. When I do get my 4k TV i'll move my current htpc over to the bedroom and just get a Vero 4k. I know it works properly at this point as its been tested by someone I trust on his amazing LG OLED tv and the guy is a super snob when it comes to video quality 
there is currently no final or really working solution for linux yet that could be tried
So I the Milhouse nightlies won't work? I was under impression they did, might not be stable but were capable of 10bit HDR
Current generations of NUC are still the best 'performance' option but HDR support in the Intel GPU drivers is still under active development.
Your talking about the Milhouse test builds?
