No new kernel for Amlogic hardware yet unfortunately, we're definitely all waiting for that as the current kernel is a mess.
Posts by powerarmour
-
-
If you've got an Amlogic box just use CoreELEC instead, at least until LibreELEC switches to the mainline kernel.
-
Thats sadly not easily fixable without heavy Kodi patching and starting fixing the known very broken kernel codebase for AMLogic 3.14.
We have decided to not do that for K18 because the new kernel codebase is already at the corner and properly fixing the old one takes too much efforts that are basically wasted after K18 (the old way AML Kernel 3.14 is doing things is getting completely removed for K19). There is also a news article about it Development Update – LibreELEC .
Understood and appreciate the honest info. I'll just have to skip LE9 then on my WP2 as this is a deal breaker for my setup (Optical out to my receiver only), I can get by on 8.2.5 until the mainline kernel versions are hopefully stable.
-
Same for me on Wetek Play 2 (and LePotato) with any DTS passthrough playback, it's been a bug since the early Alpha's unfortunately.
Le Potato HDMI passthrough mode, i have no sound for video with 2.0 channels.LE 8.90.009
-
-
AFAIK, you won't get HDR yet on x64 under LE due to the fact it's not patched into the kernel yet. HDR only works for some select ARM boards (Amlogic, Rockchip etc) under LE due to there being existing patches for their respective chipsets.
4K HDR10 - State of Play thread - important media player limitations.
-
.008 is not stable on my WeTek Play 2 either (.007 is stable, but has DTS passthrough issues), all good on my other RPi 3B+ box however.
-
Normally just the setting 'Sync playback to display: Start/Stop' is all I need, it'll then auto switch the refresh rate of the display to match the content.
(But yes, obviously your TV needs to have 23.96/24/25hz refresh rates)
-
I run a 2400G at home as a general work/light gaming machine with DDR4-3200 memory, works fine.
-
Same for me with a WeTek Play 2, and the same behaviour on 8.90.007.
The audio defaults to the AML-M8AUDIO Analogue output via HDMI, but once you switch to the AML-M8AUDIO HDMI output there is no sound on video playback. Because there is no way to change passthrough from the HDMI driver, it breaks when the Analogue output is enabled (garbled/reverb noise).
-
How long can you wait?, generally Raspberry Pi's have the most stable performance and the longest software lives out of all the ARM SBC's, if an RPi 4 is due soon, I'd wait for that.
-
I own both, and about from the GUI being a bit slower on a RPi3 B+ there really isn't much difference in regards to 1080p playback, though I find the RPi more pleasant to use in the fact that 'it just works' and every setting does what it's supposed to.
Obviously for anything 4K you're SOL with an RPi, but a WeTek Play 2 doesn't output HDR (it'll decode it however) so it's not perfect with that either.
-
So would my best bet here be to just get a new CPU once LE9 comes out?
I'd either just use your existing Celeron, or you could even go for an RPi3 if you don't have 4K display or content. For 1080p you really don't need the extra overkill most of the time, it depends on what you're happy with.
-
You could certainly fit an Radeon RX 550 or a similar GCN based card which will be a bit more futureproof in regards to VAAPI, but I'd recommend just running it with your Intel IGP (if that old Celery has one), or slightly more drastic, swap the whole motherboard out for an integrated Apollo/Gemini Lake mITX, which will be silent and just as futureproof in regards to >LE9.
-
-
-
The RPi3 is the most stable for sure, it just all works as it should, every setting, every output.
-
DTS passthrough seems to cause an audio glitch for me on the Wetek Play 2, whereby once a play a file with DTS (which will work fine) and then return to the menu the audio is reverby and delayed, and sounds like it's in slow motion until the unit is restarted.
Other than that all good, apart from having to get used to how the resolution Whitelists are supposed to work, not having much fun at seeing 3840 × 2160 50Hz selected by some of my test files, and then ended up with a blank screen... but hey, I know that's a Kodi thing now.