Posts by chewitt

The long-standing (since stereo was a new fancy thing) convention for mono output on a multi-speaker system is to send it to FL/FR so that's not unexpected. The HD formats are not mono, they are always multi-channel. So what you describe as "DTS 1.0" is more correctly described as 6-channel DTS where FL/FR/RL/RR/LFE channels have inaudible content and FC channel has audible content. If you disable pass-thru and have set Kodi to downmix to 2.0; that's what Kodi does, it downmixes multiple channels (including the one with audible content) to the default speaker map for 2.0 audio which is FL/FR. So everything working normally and not a bug.

It's probably possible to use alsa confs to define a multi-channel arrangement that remaps true mono to a multi-channel FC-only arrangement but I don't have any links to share and it's a complete bitch to Google for anything alsa related - all you ever get is a bazillion "not quite what you're looking for" results returned. I'll duck the opportunity to think any further about that idea.

My $0.02: Claim the sofa sweet-spot equidistant from FL and FR and then it all sounds like it's in the centre anyway

Clean boot an LE11 image and run "dmesg | paste" and share the URL so we can see the full log. From this we can see if there's any evidence of missing firmware or missing driver. The snippets you've shared are not showing much.

Good boot log must have a typo .. it's not a log. Please check when redoing.

Please run "journalctl | paste" after clean boot and waiting ~2 mins after the Kodi home screen comes up. I want to see URLs for two logs; one for a good boot (WiFi working) and one for a bad boot (WiFi not-working) to see if there are any obvious issues. Test with LE11 as that's using newer drivers/kernel/iwd and should be the target for any changes (if needed).

3. Kodi stores all references to sources and file-paths in an sqlite database (or MySQL for shared DB) so you can always move the content to a new drive and then search/update links in the DB to point to new locations. This might require a bit of experimentation (learn to backup the DB files before you start to permit easy stop/copy/restart of files to revert mistakes) but it's probably not that hard and someone somewhere has probably documented it in the Kodi forums already.

dmesg | grep -i bluetooth

^ run that command and share/show the output. If you're lucky we're just missing firmware of some kind.

I'm not 100% certain, but I suspect the file used to create releases.json processes files and appends data sequentially so you can probably infer file age from file order (hashes doesn't work) although that's probably a complete bitch to parse with a shell script. The work slowly taking shape in this PR should make nightly updates easier in the future: https://github.com/LibreELEC/serv…ttings/pull/276

I moved posts into a new thread since they are nothing specific to do with Amlogic support.

1. If we build a nightly every night regardless of what changed in the repo, the githash may not change (as no new changes in the preceeding 24h period). However the current automation should not build new images if there are no changes in the previous 24h period, so the hash for nightlies should always change. It's not something you can 100% count upon though.

2. No because we cannot predict the size of decompressed KERNEL/SYSTEM files in advance. After decompressing the MD5 hashes extracted from the image are compared against the files on-disk, so if tar expansion fails (lack of space or any other reason) or the hashes are absent; validation falis and the update attempt fails, deleting the content of /storage/.update and rebooting.

There are no official HDR capable LE images for Intel GPU hardware at the moment. You are probably seeing HDR content rendered in SDR.

Search for smp HDR builds in this forum.

LE master (LE11) switched to iwd around a month ago. LE10 will remain on wpa_supplicant. The kernel splat you've posted is WARNING not ERROR, so probably not fatal. NB: I'm only reading the last few posts not the full thread, but I saw mention of "no b43" and wl shows in a log snipped. Historically we've used the wl vendor driver because it supported more chips, but this might need patching for the latest kernel changes, or perhaps dropping for in-kernel b43 if it disagrees with iwd.

Most 4K/HDR TVs have an 'info' option to display that kind of thing on screen. The TV is also the best place since it can display what is actually being sent vs what Kodi thinks it's sending.

In some forums that would be handled by signatures. We used to have signatures active, but it's one of the primary targets for spammers to add link-farming spam to. We also have too many users that think text in distracting weird colours and abnormally large font sizes is great visual design, and a small number harbouring a beef with other forum users and long-term project members who like to add messages that are basically offensive. So signatures have been turned off. Anything that provides a Google scrape-able alternative would likely suffer from the same issues, so I appreciate the idea but we aren't likely to do anything like that.

NB: Anything that's of general benefit to our user audience can (and should) be put in the wiki, which is open for anyone to send changes to through a GitHub pull request.

dmesg

There are no "apps" but there are "add-ons" for a range of useful LE related things in the LE repo, including Docker which opens the door to more unusual things. There are no browser add-ons for ARM devices.

See https://github.com/LibreELEC/amlogic-boot-fip/ .. there are some useful links in the README for the repo to other tools that can be used to sign the u-boot binaries, and some of those tools have more detailed explanations (and all have visible code) showing how it's done.

The boot binaries are signed. What box/SoC is inside?