Posts by chewitt

The LE 10.80.0 (Nexus) images in my team share https://chewitt.libreelec.tv/testing/ contain an experimental fix from Martin B for "the noise" that can be experienced with GXBB, GXL and GXM devices using the AIU audio driver. If you have an S905, S905X/D/W/Y or S912 device; please reduce volume on your TV or AVR, update the image, then spend a few minutes navigating around and fiddling with switches and options in the Kodi audio settings page (normally an easy way to provoke that audio problem). Please post back with success or reports of 'the noise' or crackling or other audio oddities you experience?

NB: These images have partially workiing hardware decode again, using the same ffmpeg patch-set as Raspnerry Pi. This is progress, but it means playback is worse in real-terms since ~50% of things now fail, whereas recent images had software-only decode (completely broken hardware decode) where 100% of 1080p media plays within CPU limits. TL/DR; If you're trying to run these images for daily use, you probably want to disable hardware decoding.

It's not a typo, and please stop hijacking threads with advice if you don't actually know the answer.

Kodi has a user interface that's been designed (it didn't just happen that way) to fit onto a TV screen. If you hack the default fonts to be bigger that throws a whole heap of things out of visual alignment and the defaul GUI (skin) will start looking rubbish. Kodi does support other skins, and some of them may allow the font size to be configured, and/or some of them simply use different sized fonts. Experiment .. because that can be done from a remote without needing to override Font files from the SSH console. Plan B .. get a bigger TV. Plan C .. sit closer to the TV screen. NB: If you think our dumbed-down OS is too complicated for you, please feel free to use something else.

It's not impossible to add an NFS server, but it does require some developer skills and buliding a custom image. Have a look at the commits in escalade RetroELEC GitHub repo for more details.

https://github.com/melmorabity/pl…mment-981832577 ?

Quote from dwhacks

I am using the Argon One V2 case. Any ideas?

We're all getting a bit fed up of random problems with Argon One case users. So before we go any further .. remove the board from the case and start with a clean image (or remove all boot configuration you attempted) and see if the issues all magically solve themselves.

i.e. the same place it was in Kodi 18 / 17 / 16 / 15 / etc.

You clearly didn't follow the thread. eSpeak is not an issue. The size discussion was about picotts; If this is 80MB it will not be added to our images (which are often ~125MB total size) and it will need to go into an add-on.

The type of connectors and components used and layout style of the PCB looks older to me, so I'd put my money on it being an Amlogic S812 device. All the Amlogic S912 boards I've seen use PCBs with more layers and much more dense population of smaller components. Another clue / hint on age will be MMYY or YYMM date codes on components, e.g. RAM chips. There's a 1502 printed on the PCB which would be Feb 2015 which would also align with S812 as S912 devices started to show up in 2016. If it genuinely has a Mali T830 chip; it's a HiSilicon Kirin board, but I think documentation typos (or even the wrong documentation in the box) are more likely.

Sure. In a corporate development enviroment a product manager would task the Engineering team to create it and it would get done. In an open-source environment like Kodi where all the developers are working in their spare time as a hobby that style of development doesn't work or happen. Everyone is typically fiddling with a small area of code aligned to a personal interest, and very few people have the time or skilsets to take on large cross-functional refactorings and integrations. There have been some serious attempts at a browser, but it's proving to be a non-trivial task requiring a large effort, and for a varied mix of "real life" reasons, previous attempts have fizzled out.

Quote from shad

YouTube, Netflix & Co started to stream AV1 encoded content and so on

Yes they started to stream in AV1, but until they stop streaming in H264, VP9, etc. and ONLY stream in AV1 the lack of support for AV1 in boxes isn't really an issue. Hardware will catch-up eventually, but there's no rush.

If you think this is a Kodi bug you need to go file it with Kodi devs in the Kodi forums. It's not an LE bug.

How about you go install it on an SD card and have a look?

Quote from kodiuser1

I have a Vorke Z6 with a S912 and 3G ram. Ive tried both of the gxm device trees but cant get it to boot.

Both? .. there are at least 8x device-trees for GXM boxes and they are all mostly identical. If none of those work .. unless you attach a UART cable and share the u-boot serial console output so we can see where it gets stuck. Note the device-tree process is different in mainline images: You need to use the "box" image and edit the dtb name in uEnv.ini. if you start renamng files like legacy images do that's one reason none will boot.

Quote from shad

Now I’m a bit lost and would like to ask, what box / SoC with AV1 HW support should I look at, which is supported by LE? Any new recommendations one year since the last post here?

AV1 requires the latest Intel chips, which are still a little experimental in places, but you know Intel is committed and will push all the driver support upstream within a reasonable amount of time. None of the SBCs have upstream support at this stage. FWIW, I've always regarded Ugoos as one of the cheaper and more awkward vendors - but that's probably because they refuse to share sources and schematics for the boxes (I'm biased).

Pics show a random circuit board with an assortment of standard connectors; it could be anything. The sole useful bit of info is on the chip under the heatsink. Unless you share that I can only make blind guesses, and I guess your box is not supported.

The name means nothing and "rxj1909-MB-v06" returns zero results in Google so we have no clue (we are not omniprescient or mind-readers). You will probably need to power it on and see what Android claims it is. Worst case you will need to open up the box and take some close-up and in-focus pics of the board with the chip exposed. If any of that seems like too much effort, you should probably stick to Android.

I'd recommend Musicbrainz Picard for organising audio files: https://picard.musicbrainz.org/ as it will also embed their IDs in the files which guarantees things scrape well. It's also the app used by the folks who dev on Audio topics in Team Kodi. Reworking a large library with Picard might take time, but it's one of those tasks that you only need to do properly once, and then future re-scrapes (should they ever be needed) become simple.

If you really want to do things manually.. have a read https://kodi.wiki/view/Scraping_Music