You probably need to enable HDR modes for specific HDMI sockets. Something like "Enhanced Mode" or "Deep Colour Mode" or such (there is no standard term).
Posts by chewitt
-
-
The original developer of the add-on hasn't been around for a while now, so all add-on maintenance is crowd sourced and we're lucky that it doesn't appear to need much effort. The only documentation is "prior art" in the code and if you'd like to see a new feature; it's your resposibilty to either code it or find someone to code it. The project staff can usually find someone to review any changes that are submitted but we don't really have the resources to handle requests.
-
It appears the original add-on (in the Kodi repo) is now unmaintained and changes to some of the upstream sites that radio feeds are sourced from mean it's no longer working. In some cases a little manual tweaking to add-on files can get things working. In others more invasive changes are needed. There are also forks or replacement/alternative add-ons appearing, though none are in the Kodi repo at the moment (and that may not happen based on the whims of individual developers. It's best to read the add-on support threads: https://forum.kodi.tv/forumdisplay.php?fid=148 .. for the radio add-on, skip-to/start around page 50.
-
I'd guess the USB-C dock advertises 'monitor' capabilities not AVR/TV capabilities. If you connect direct to the receiver over HDMI do you get the normal resolutions?
-
-
Isn't ASIO specifically a Windows thing - not sure I get how it's related to Linux? Or am I missing something?
ASIO is Windows only. There's no direct equivalent to ASIO on Linux (only good-old ALSA) but I do see folks in the RPi audio distro ecosystem using RT (real-time) kernels because that's supposed to be better juju for your listening experience. Magic
-
"Newly created posts will remain inaccessible for others until approved by a moderator."
It's true (for new registrants with no posting history) but there's about 10x moderators and they're spread over a few timezones so the time between posting and someone approving is never that long.
-
If the fonts are rendered as a "square" glyph you need to add /storage/.kodi/userdata/Fonts/Arial.ttf using an 'Arial' font that includes Asian character support.
-
I think the dream setup is to use Kodi and just have DSD work. LE kernels support the higher bitrates needed (hence MPD can be a solution for some) but Kodi has no handling for media above 192k that I can see (perhaps that's where HDMI maxes out?) so the ALSA audio sink code probably needs to evolve a little. And since Kodi is ultimately a big fancy wrapper around ffmpeg some work will be needed there too - and ffmpeg being the fun place to submit patches, that might take a while. As always in the Kodi world, it requires someone with the tryptych of patience, coding skills, and the initiative to do the work.
-
The original post was approved withing a few hours of you posting. Nothing is stuck or needs approving. Just nobody cared to reply to your post. I'd guess because nobody can replicate the claimed problem. For example: I'm running LE13 nightlies on an RPi5 and the InfoWall view is available everywhere for me. Right now LE13 is still using the same Kodi Omega version as LE12 as we didn't bump up to Kodi 'P' just yet.
I would stop and rename the /storage/.kodi folder to /storage/.kodi-old and restart. If the (now empty, all new) Kodi library DB has Infowall back, something is messed up or corrupt in the kodi-old settings or DB files and you can now stop, move files, restart Kodi to move old config and bits to the 'new' Kodi folder until you find out what caused the issue.
You can also share a debug log, but I rather doubt the issue will be visible that way.
-
The content of /storage/.kodi is what you want to rsync. In reality it's the userdata folders, but you might as well sync add-ons and such too assuming it's the same hardware in both places.
-
Do you think it will be compatible with LibreELEC and Tvheadend ?
It's never guaranteed but I think it should be. Hauppauge are one of the few DVB device vendors who actively maintain their drivers in the upstream kernel and most mentions of that device I see (including on the Hauppauge website) are referencing support in old kernels (meaning support has been around for a long time).
-
It looks like two issues:
a) Some builds are taking so long they reach a timeout value and are killed.
b) Because they took so long the next build is trying to schedule itself and can't find a free worker, so fails
Some DevOps'ing needed I suspect. Not sure why things are running slow.
-
The same fix is in the same kernel used in both LE12 and LE13 nightlies. No need to use my images. NB: The 16K page fix has nothing to do with the normal run-of-the-mill stupdity with NTFS filesystems being marked dirty and failing to mount. That still requires you to go fix the drive on Windows before reconnecting to Linux.
-
/etc/fstab exists solely to stop some error messages from being shown. It's not actually used so you will never see content about drive mounts there. And I'm guessing the command sequence based on the "emmctool" script that's embedded in the Amlogic image. The general principle is that you shouldn't peform change operations on mounted partitions and filesystems and some commands result in auto-remount being triggered so you need to unmount things again before you run the next command. So unmount, grow the parition to 100%, then resize the filesystem to 100%. There's no need for crash helmets as the worst that happens is you mess up something that isn't being used and doesn't already work. You can always start over and have another go.
NB: I'm wondering if an "nvmetool" script might be useful for RPi5 boards.
-
It might need an eeprom and USB firmware update at some point, but there should be no reason why it cannot run LE12.
-
Is there anyway to edit a conf to disable the SSL requirement in the interim?
No, it needs to be compiled with the right options. The fix is in LE12/13 nightlies for a while so just update to the current one?
-
You probably found 3 add-ons, which are still using Python 2.
Probably not if the addon was working under LE11 as per post #1.
Seeing a full debug log would be useful.
