Posts by wrxtasy
-
-
I don't know if the Tanix would be much slower than the Pro L, I think for vanilla LE the 905X is good to go, I only got the 912 so I could mess around with the Android TV firmwares.
In term of speed and connectivity the MINIX U9 rules them all.
Far better passive chipset cooing vs all others and high quality Samsung DDR RAM and eMMC as well.
Plus some U9 (& U1) packages include that excellent wireless MINIX A2 Lite remote - that works properly for OFF / ON.
Next you need Gigabit Ethernet if home network streaming high bitrate 4K HDR Bluray Rips.
S905 devices generally come with Gigabit Ethernet. Some S912 and S905D devices as well. Others will be slower 100Mbit only
In addition anything with a Wireless USB dongle Mini remote will be more responsive vs the rubbish Infra Red only ones cheap AML boxes comes with, a cheap wireless remote suggestion is found >> START HERE - Pick the Right Kodi Box (updated Oct. 2018)
RAM speed is generally better if using DDR4 boxes vs DDR3.
The Branded devices MINIX, WeTek, ODROID, Vero usually include high quality, faster RAM and eMMC internal storage.
Some devices have weak 2.4GHz only WiFi...others 2.4 / 5GHz AC WiFi
In Terms of AMLogic SoC speeds, these are the rankings, fastest on top:
S912 (HDR)
S905 (NO HDR)
S905D (HDR)
S905X (HDR)
S905W (HDR)
Pick which are the most important features and how much you want to pay.
Cheap S905W devices are fine for LibreELEC, especially if you can get one with an included Wireless remote like the Nexbox A95X Pro
-
Thanks for the response. Maybe I misused the term, with the 8.2.5.1-444-1000nits update I no longer get any 4k video to my TV. My setup is HDMI out of the box into a Yamaha YSP-2700 soundbar which supports 4k video passthrough to my TV. With 8.2.5 422 10-bit, 4k HDR played just fine, audio decoded as it should and video passed through to my TV in the correct format. After updating to 8.2.5.1-444-1000nits, when I tried to play a 4k file my TV would just tell me there was no source but the audio would still decode and play fine from the soundbar.
Curious to know if the the 8.2.5.1-444-1000nits update made any difference for you in regards to the brightness of your 4k HDR rips?
I have the same Yamaha Soundbar. It simply does not like 4K with a 4:4:4 Chroma setting.
Use the 4:2:2 image.
If specific HDR Rips are too dark, then you will have to wait till I get an Ubuntu 16.x Virtual compiler up and running again.
I've upgraded to Ubuntu 18.x and it killed a LOT of previous trouble free LibreELEC 8.2.x compiling.
or disable 444,10bit in Kodi AMLogic settings and Force 4:2:2 by putting this in autostart.sh
echo '422,10bit' > /sys/class/amhdmitx/amhdmitx0/attr
1000nits will be the default in both cases for previously too dark looking 4K HDR Rips
-
With Krypton - Everything these days is Hardware decoded by the Video Engine in the GPU, there is no need to buy extra licences.
SD - mpeg2 and mpeg4 can also be CPU software decoded if you want, there are various LE video decode options available.
-
Using LE 8.2.5.1 latest build on my TX9 Pro S912 box, and have two problems that I wonder if others are having too.
Firstly for watching UK TV with my IPTV client I have to enable the option in the AMlogic System Settings to "Disable Deinterlaced Post Processing'' or else I get chroma horizontal tearing very badly on my TV. BTW the TV is a 6 month old LG 55SJ850 Super UHD model so is pretty much latest state of the art (although sadly not OLED as could not afford one of those !) so surprised I am gettign this effect. I do not notice the problem in streaming movies or other material but seems only with my IPTV client service ??? Do not get this problem with earlier LE builds BTW.
Secondly there seems a problem with 3D content. Although my TV sadly does not have a much missed 3D facility, with previous builds like 8.2.2.3 I seem to rememb er I could watch 3D video files in 2D by selecting that option within KODI with no problems. However now I cannot do so and indeed it locks up the display to a black screen with no sound although the video clock shows it is still playing. After this, some but not all of my video content from my NAS Drive and USB Drive will no longer play exhibiting exactly the same black screen no sound problem, BUT a reboot will allow those to playh agfain normally until once again I try to run a 3D movie file ?? Strange that most still play okay but quite a few won't, need to narrow down which format maybe the culprit here.
Two obscure problems which I would liek to be able to fix if anyone can help. Other than that 8.2.5.1. is excellent though I cannot measure whether I actually get 10 bit and 444 mode on my TV with suitable source material, though I do get the full UHD and HDR which I can check for okay.
There is lots of ongoing testing in the AML Linux Kernel with Bit depth & Chroma output and that is exactly why that Kodi settings option is put in there to bypass such issues. I've only seen such Horizontal red video output on S905W boxes with interlaced TV.
Not sure about 3D support, never use it personally and the only 3D .mkv file I last tested output 1080p. It's definitely not on the high priority list at the moment.
-
The S905 v8.2.x.x releases found in this Google drive folder:
[8.2.4.1] LibreELEC Kodi Krypton - S905 & S912 devices
And the
gxl_p281_2g_a95xr2.dtb
found in this folder:
-
1080p Netflix on any AMLogic device running Kodi Leia & the Netflix Addon is not possible, even on S905X or S905D boxes.
I do not even think 720p Netflix is possible on AMLogic S912 devices.
If you need a reliable 1080p Netflix setup, buy a Netflix Approved device. ie. Shield or Apple TV or Amazon Hardware.
Those will work long term without Netflix cracking down on workarounds or something or another and preventing Netflix streaming.
-
I have dug out my Le Potato and put a fresh install of the Alpha version on. It ran ok for a couple of hours before locking up the same as happened when tried the old kszaq version used to, and I packed it away.
The following folder will have a fixed LE 8.2.5-Bootloader test .img.gz for Le Potato:
-
I've ordered a u9-h and plan to install 8.2.5 on it ... it met all my HDR/Atmos requirement, and that heatsink is incredible.
Today though I came across Le Potato which I could have got for half the price, and seems to have official support.
I can hand-me-down the u9-h to one of the bedrooms if I find something better for the living room, so I was curious of people's thoughts on a u9-h vs a Le Potato, specifically for HDR/Atmos (but also with consideration I suppose to frame-packed 3D via ISO).
I got the u9-h with hope for DV in the future - but the only DV TV in the house atm is in the master bedroom, so all the more reason to shuffle it upstairs - though I'm not sure how well ISO streaming over wireless would go compared to HDR/Atmos repacks which are working great over wireless AC.
You will not find better hardware than the U9 for LE Kodi Krypton or Leia.
There is no 1080p 3D .iso or .mkv support on any AMLogic hardware! And no we are not even going to attempt to add it.
There is also no dual layer Bluray DolbyVision support on any external media player platform anywhere. That needs proprietary Dolby decoding.
I've heard specific Oppo UHD Bluray players may have some BD DV Rip support.
There is No open sourced decoder for playback of dual layer Bluray DV Rips.
Those two features are never likely to happen.
Be happy with what you currently have, you will not find better.
The Apple TV 4K does very specific profile DV streaming from Netflix, VUDU and iTunes. It cannot playback dual layer Bluray rips either.
-
Thx to Millhouse who directed me to a Kodi Leia - GETCHUNKSIZE patch and there is also a 32K Bufsize SMB patch from Sam Nazarko's Vero 4K OSMC:
QuoteFrom SN:
wrxtasy The rationale behind my Vero patch for SMB chunking, around January IIRC was that smbc_read was returning some crackheaded numbers on AML.
After some testing we found 32768 to be the sweet spot. Tested on 3.14 on both 100M and 1000M. For Pi, the same value is also good.
If it is also working for RPi and Chromebox's those two patches that sky42 is using would be good for a LE 8.2.5.1 update methinks.
They should increase speed for all SMB Kodi transfers.
-
Summing it up, a cheap S912 will be faster, run hotter (8 CPU cores) and come with Gigabit Ethernet if you get the right one. Heatsink Cooling mods will likely be required if you really want to push these devices.
It's LE Kodi support will end with Kodi v18 Leia due to changes in Kodi regarding GPU video drivers required.
S905X devices will be slower than the S912 and come with 100M aka Fast Ethernet, good enough for 1080p. Not so good for high bitrate 4K Bluray REMUX Rips. That will last thru Kodi v18 Leia into the future
The S905D is a S905X with Gigabit Ethernet and usually a single MUX TV Sat / Tuner.
It will also last thru Kodi v18 Leia into the future.
Pick your price to performance ratio.
Personally I went with Gigabit and S912 speed and snappiness and will see what the future brings 2 years down the track.
I've only got one S9xx Krypton bug remaining and that is regarding SMB External Subtitles and I think I've found the issue and fix just today.
-
Subtitles Fixing - we hope !
I've got a S912 (at the moment) Subtitles Fix test folder up and running, it's likely it will fix the SMB External Subtitles crashing issue:
https://drive.google.com/open?id=1xqmw0vi1nczle-3pqndknp7u4ey4zjlc
Please test and report back any differences between the "test" and "test1" versions.
-
Did you try this box with LE yet? I have this box too now, but cant get it to work neither with LE or CE. When i try to connect it with Bluetooth (device is called "RemoterATV3", then it first connects and then disconnects. I thought that many people have this remote working with LE and there should be no problems. I tried a remote.conf, but when it doesnt connect over Bluetooth, then it wont help me, i guess.
Bluetooth will not work as LE needs detailed BT custom coding.
But you can try copying the following remote.conf into the "Configfiles" directory of your LE device and reboot, and see if the IR part of that remote works:
-
Letting Kodi encode DTS HD MA and True HD to LPCM 5.1/7.1 channel Audio with Amlogic S905/905X will always downgrade to 16 bits instead of the orginal 24 bits.
From what I understand there is a vesion now that will decode to LPCM 24 bits, and that is LibreELEC-S905.arm-8.2.5-Chroma.422.10bit.
IS this the only one that will do this? Or is there more version that can do this?
Just keep following the version number as they increase, all previous additions are included in subsequent versions.
Otherwise look at the file dates:
ie v8.2.5.1 is the version after 8.2.5
v8.2.5.2 will be the next version after 8.2.5.1 and so on...
You need specialist audio equiptment to actually test bit perfect 24bit audio output as detailed in this Vero 4K development thread:
24-bit output - Vero 4K / Vero 4K + - OSMC Forums
And yes the 24bit Kernel HDMI output signalling changes talked about in that thread are in the LE v8.2.5.x versions onwards.
-
Hi Mr. Rome,
You could test this following that has the vim2 fan driver service included:
-
Flash a USB stick or SD card again and then Install to Internal again.
If that does not work find a Firmware .img and use AMLogic USB burning tool to recover Android.
The Freaktab forum is your friend for all that.
-
This is why 'installoninternal' is a very bad idea
And why we are recommending copying the LE data partition to Internal eMMC storage as the safer more reliable option.
You only then use the SD card / USB stick for booting.
-
Hi wrxtasy, I'm using LibreELEC-S912.arm-8.2.5-Chroma.422.10bit right now but according to my Pioneer receiver the video output is 4:2:2-8bit. Using a Minix U9-H. With previous versions (8.2.4.1) output is 4:4:4-10bit. Any ideas?
It is possible it is only outputting 8bit color depth due to my A/V equiptment not showing such info. I'm really relying on you guys.
Can you do a test by disabling 422,10bit in the Kodi Settings > System > AMLogic and then SSH in and issue this command:
echo "422,12bit" > /sys/class/amhdmitx/amhdmitx0/attr
And then play some 4K HDR material (make sure LE Kodi refresh switching is activated). What is the color depth output ?
If it is still 8bit output then there is a new 444,10bit update available that also has a default 1000/0.005nits MaxFALL/MaxCLL
This will improve brightness of problematic dark looking 4K HDR Bluray Rips:
LibreELEC-S912.arm-8.2.5.1-444-1000nits.tar
LibreELEC-S912.arm-8.2.5.1-444-1000nits.tar
You can read the technical thread regading issues with HDR metadata in HEVC SEI messages of concatenated m2ts files, over in the following Vero 4K forum:
HDR too dark on LG OLED - Vero 4K / Vero 4K + - OSMC ForumsImportant WARNING about Chrome Web Browser Extensions !
chrome-extension://bigefpfhnfcobdlfbedofhhaibnlghod/mega/secure.html#blog_47
Thanks God I did not allow the Rogue Extension permissions - Google has a serious Security issue on their hands here !
QuoteDisplay MoreFrom MEGA:
On 4 September 2018 at 14:30 UTC, an unknown attacker uploaded a trojaned version of MEGA's Chrome extension, version 3.39.4, to the Google Chrome webstore. Upon installation or autoupdate, it would ask for elevated permissions (Read and change all your data on the websites you visit) that MEGA's real extension does not require and would (if permissions were granted) exfiltrate credentials for sites including amazon.com, live.com, github.com, google.com (for webstore login), myetherwallet.com, mymonero.com, idex.market and HTTP POST requests to other sites, to a server located in Ukraine. Note that mega.nz credentials were not being exfiltrated.
Four hours after the breach occurred, the trojaned extension was updated by MEGA with a clean version (3.39.5), autoupdating affected installations. Google removed the extension from the Chrome webstore five hours after the breach.
You are only affected if you had the MEGA Chrome extension installed at the time of the incident, autoupdate enabled and you accepted the additional permission, or if you freshly installed version 3.39.4. Please note that if you visited any site or made use of another extension that sends plain-text credentials through POST requests, either by direct form submission or through a background XMLHttpRequest process (MEGA is not one of them) while the trojaned extension was active, consider that your credentials were compromised on these sites and/or applications.
Users accessing MEGA without the Chrome extension have not been affected.
We would like to apologise for this significant incident. MEGA uses strict release procedures with multi-party code review, robust build workflow and cryptographic signatures where possible. Unfortunately, Google decided to disallow publisher signatures on Chrome extensions and is now relying solely on signing them automatically after upload to the Chrome webstore, which removes an important barrier to external compromise. MEGAsync and our Firefox extension are signed and hosted by us and could therefore not have fallen victim to this attack vector. While our mobile apps are hosted by Apple/Google/Microsoft, they are cryptographically signed by us and therefore im-mune as well.
We are currently investigating the exact nature of the compromise of our Chrome webstore account.
