I am using LibreELEC-S912.arm-8.2.5-Chroma.422.10bit.img. I want to thank you very much for this version. It is solid and it finally works with USB DACs connected to my Minix_Neo U9-H. Your previous version didn't work.
With LibreELEC-S912.arm-8.2.4.1.force.444.10bit.img when I connected my FiiO DAC to the USB of NEO U9, LibreELEC didn't output sound through the USB DAC.
Before, when I had an Intel NUC and the official LibreELEC image, I could connect a USB FIIO DAC to USB. LibreELEC could recognize it as an audio output. With this image on Minix NEO U9-H, my FIIO DAC is not recognized when connected to USB. Any ideas?
I see there is a new image
LibreELEC-S912.arm-8.2.4.2-fix-lost-audio-v2.tar
Could you please explain what this image has more?
The file is not big. As I said it's only 720p AVC with a bitrate of 3000 kb/s. It's not only this. All high frame rates 50-59.94fps have problems. Has anybody played high frame rates files with this?
I have LibreELEC-S912.arm-8.2.4.1.force.444.10bit.img.gz on Minix U9-H and LG OLED TV.
When there is high framerate I have some stutter. At 30fps or lower everything is great. When I play 50 or 59.94fps, I get stutters sometimes. They are normal 720p AVC files. The same files play smoothly on Kodi nVidia Shield. The strange thing is that the stutters are not random but always exactly at the same points.
Anyone has problems with 50 - 59.94 fps videos?
The difference is how they support it. S905D/X internally convert 10-bit to 8-bit for processing. S912 processes 10-bit. Future devices like S905D2/X2 and S922 process at 10-bit. Most users who obsess over the whole 8-bit/10-bit thing won't be able to tell the difference. More users will just be happy the HDR mode triggered on the TV and they can point at the brighter screen and tell their wives it was in HDR and looks so much better (and thus the purchase of the new UHD HDR TV was justified)
That begs the question, what's the difference between S905D2/X2 and S922!
I am reading the Amlogic site and it says all S912, S905D and S905X support UHD HDR. So what's the difference?
Question, the file I made
evdev:input:b0003v0C40p7A1Ce0110*
KEYBOARD_KEY_070070=171 # settings
KEYBOARD_KEY_0700bb=23 # tabs #I (Info)
KEYBOARD_KEY_070065=46 # menu #C
KEYBOARD_KEY_0c0224=esc # back
KEYBOARD_KEY_070073=113 # mic #MUTE
KEYBOARD_KEY_07003a=50 # apps #M Player controls (OSD)
KEYBOARD_KEY_0c00b6=168 #<< REWIND
KEYBOARD_KEY_0c00b5=208 #>> FORWARD for the line
KEYBOARD_KEY_0c0224=esc # backI have to put "esc". If I put the number "1" the line doesn't work. Why is that? "1" is the same code as "esc" and it does the same thing. For some reason all the other 7 codes I put work, except code "1"!
I received my new A3 and as soon as I created an hwdb file, it started to work. It seems something is wrong with my other remote and it's not standard or something.
All I can see is that Coffee Lake is coming out in the bigger skull box. Is it also coming out in the normal NUC size?
Thank you for the information.
I also have one bizarre necessity. I have an OLED LG and it has a major flaw. The optical TV output has audio drops when it is playing from Kodi. So, for not having audio drops I have to connect the audio directly from the Kodi box to the optical in of my soundbar. That's how I use my Minix NEO U9-H and why it's a necessity.
Kaby Lake NUC has no audio optical out?
I'm surprised by the link. So, is it correct to say that if a NUC video output is HDMI 2.0a, it does not necessarily mean it supports HDR? Why Gemini Lake can't get it? I always thought HDMI 2.0a means it can support HDR. Minix NEO U9-H outputs HDMI 2.0.
This is all about if the hardware can support it. The OS and software is not important, I can wait. I want to know if I buy an Intel NUC today, I will be able in a near future to play all things that Minix NEO U9-H can.
I want HDR and H265 10bit hardware acceleration, auto resolution switching in Intel NUC hardware.
I have still not gone the new Intel NUC way, I'm on Amlogic. Do any of the new Intel NUCs support HDR?
fxffrank, that is great.
The problem is that as I said I created an hwdb file and it is still not working for my other remote. I will receive a new A3 a little later and will try it and report here.
When I play 23.976 fps movies, I get perfect and smooth videos but with 59.94 fps material I get jumpings and jerky playback from time to time. Anyone else? Do you play 59.94 fps smoothly?
Could other owners please join in. I'm sure many people here own Minix NEO U9-H and many of them own A3 remote.
Could those owners please tell us what is your experience with the remote? Does the SETTINGS button register under Keymap Editor addon?
This test will be a big step forward and I'm hoping that when those 2 files don't exist, it stops registering under Keymap Editor. Then we know exactly what we have to do.
If you did the test and if the SETTING button stopped registering under Keymap Editor, please copy just the hwdb file first and see if that makes it work again. That way we can pinpoint the file.
Question. I don't find the option color range limited (16-235) in the menus. Was it removed? At what range this build is outputting? I feel like it is (16-235) and not FULL. Colors look very washed out and my old Intel Nuc Libreelec didn't look this washed out on the same TV.