Posts by crawfish

  • MyVideos144 vs MyVideos143

    OK, I see what happened, and it was my misunderstanding. The officially released v22 Alpha3 was an earlier version of the Nightly I was using and also predates my LibreELEC. Here are the relevant logs from four sequential installations into a Windows Sandbox. Update 1, the 3/19 Alpha3 Nightly, updated 141 to 144. Update 2, the Alpha3 official, updated 141 to 143. Note that while it has the same version 21.90.703 as the 3/19 Nightly, the official Alpha3 is the 3/11 Nightly. Aha! This explains why the official Alpha3 I downloaded and installed on 3/30 appeared to revert to an earlier database. Finally, Update 3 was the current 4/7 Nightly, and it's using 144.

    Your suggestion on getting the different platforms in sync was correct. LibreELEC has been a straight Nightly path, without the backtracking to an earlier Nightly that the official Alpha3 release did for Windows/Android. I guess the lesson is, once you go Nightly, you stick to Nightly, or more generally, make sure you're using the same version of Kodi, which I know is in the documentation.


  • MyVideos144 vs MyVideos143

    That's what I thought, too. FTR, I've been using v22 since Alpha2, which I downloaded and installed on January 20 (I keep the downloads indefinitely for point releases and official alpha/beta and can look at the file dates), and I use Kodi daily. I notice the database versions when I perform weekly backups.

    Looking at the creation dates of the folders in MariaDB on my Windows server, 144 was created (not "modified") on March 21, and 143 was created on March 30. Odd.

    After using Alpha2 since January and the nightly Windows/Android Alpha3 labeled version for days to weeks, I downloaded and installed the officially released Alpha 3 on March 30. That's when 143 appeared, created 10 minutes after. ISTR previously dropping the 143 table to clean up the database after noticing 144, and that's why I was so surprised to see it again, and for LibreELEC to still be using 144.

    I'll try installing some of those earlier versions to get to get to the bottom of this as well as the current nightly to see what it's using. I'll have to re-download those earlier nightlies, because I delete them after moving to a new one or official release.

  • MyVideos144 vs MyVideos143

    I run the official Windows and Android releases of Kodi v22 Alpha 3, and they're using MyVideos143 in my MariaDB shared database. LibreELEC v22 Alpha 3 nightlies, however, are using MyVideos144. I'd like to keep them all synced, so is there a reason for this? (I may be mistaken, but it may be that Windows/Android were using 144 and then the official Alpha 3 releases backtracked to 143. For whatever reason, LibreELEC didn't follow suit. That's my impression of what happened, anyway.)

  • Hardware for 4K movies

    Scanning music in Kodi is so slow even on my 9900X PC, that I simply don't do it. When I need to add music, I find the new albums and scan them in individually. Video scanning and library cleaning OTOH proceed apace. I do have large libraries. BTW, scanning video can seem randomly slow if you switch between Windows and Android and vice versa to perform the scanning on a shared database. I'm talking several minutes vs 10 seconds when I consistently use my Windows 9900X PC. That's because they calculate directory hashes differently. I haven't tried switching to/from LibreELEC for scanning on my N100 mini PC, because I've settled on using my main PC to maintain the database.

  • [x86-64] N100 slips in and out of HDR on Sony Bravia 8 XR80

    Quote from chewitt

    The lack of info in kodi.log proves Kodi didn't do/signal anything so the issue is either something in the Linux kernel/DRM layer or perhaps (as suggested) something related to the TV itself.

    Is there anything in the system log (dmesg)?

    I no longer have the mini PC hooked up but will check that if I ever come back to it. I ended up with an Onn 4K Plus for my backup device, and that really is all it is. Kodi runs perfectly as an internal app on the XR80 (Android 12), and it even exposes 48 Hz, 50 Hz, and 60 Hz 4K resolutions in the whitelist, which I didn't think internal apps could do. It uses them when refresh rate matching and double refresh rates are enabled, such that 25 Hz material plays at 50 Hz. This cleared up some rare motion glitches I was seeing in real material. True 24 Hz material gets the 48 Hz treatment, while the far more usual 23.967 Hz gets 60 Hz. Even so, the latter plays without a hitch, including files I have for testing motion. That's an improvement over my A80J, where native Kodi had occasional motion problems with 23.967 material. One of the other nice things about the internal app is that it doesn't incur the annoying HDMI bonk.

  • [x86-64] N100 slips in and out of HDR on Sony Bravia 8 XR80

    Quote from plingplong

    this maybe just a shoot in the dark, sins I have another model of TV. TCL TV, did the same thing when i had the game mode on the HDMI port where kodi whas connected on the TV activated. Turned game mode off and the tv behaved better. Can it be the same issue here?

    https://www.sony.co.uk/electronics/support/articles/00277404

    I don't think that's it, because the TV was not in Game Mode under LibreELEC. I tried to keep my OP brief by skipping over the initial hurdle I had when I was using Windows 11. Unlike the A80J, the XR80 was stuck in Game Mode, which is totally unsuitable for watching regular media. It was because ALLM was activated in the XR80, and there's no way to turn it off in the TV settings. I had to run cru.exe (Custom Resolution Utility) in Windows 11 and disable ALLM in the EDID for the TV. That freed up the normal TV modes. The rest of what I talked about in my OP for Windows 11 was after doing that.

  • [x86-64] N100 slips in and out of HDR on Sony Bravia 8 XR80

    tl;dr

    Running LibreELEC 12.2.1 (Kodi 21.3), a Beelink S12 Pro N100 box starts all HDR10 material in SDR, switches to HDR a couple minutes later, then switches back to SDR after a few seconds. Kodi debug log:

    External Content pastebin.com
    Content embedded from external sources will not be displayed without your consent.
    Through the activation of external content, you agree that personal data may be transferred to third party platforms. We have provided more information on this in our privacy policy.

    Background

    I recently had a Sony A80J OLED replaced with a Sony Bravia 8 under warranty. I had been using a Beelink S12 Pro N100 box running Windows 11 Pro with the A80J, and it was a perfect Kodi device, matching refresh rate and resolution, doing HDR10 and everything else right. I hooked it up to the new XR80, and it just fell apart. The resolution switching took a lot longer, and playback initiation was accompanied by the UI flashbang I've observed with Android devices like CCwGTV and Onn boxes, where the screen goes black for a second or two, the Kodi home screen flashes, and then playback begins. Also, HDR was broken. HDR10 movies would start out in SDR, after a couple of minutes switch to HDR, then switch back to SDR a few seconds later.

    Troubleshooting (done for both Windows and LibreELEC)

    My TV inputs are correctly set to Enhanced mode. I was using Monoprice Ultra High Speed HDMI cables, but I tried one from a different brand and got the same results. I tried a different TV input, but no joy. I tried my CCwGTV on the same inputs where the N100 was failing, and it worked perfectly with HDR. I tried my main PC running Windows 11 Pro with an Nvidia RTX 3060 Ti, and it worked fine. Since Kodi ran perfectly as a native app on the TV, I concluded there was an incompatibility between the N100 and XR80, gave up, and planned to sell the N100.

    LibreELEC

    I've found it useful to have a backup Kodi device so decided to keep the N100 and try LibreELEC. It's definitely snappier than Windows 11 was loading Movies Wall view, so that's nice. It also doesn't suffer the slower resolution/refresh rate switching with the XR80. It's as good or better than the N100 running Windows was with the A80J, except the HDR issue persists on the XR80. I've linked to a debug log where I play an HDR movie. It begins in SDR, and after 2:12 seconds of viewing, it switches to HDR. After another 38 seconds, it switches back to SDR. This is obvious visually, and it's also reflected in the Sony's "Detailed signal info" overlay as I'm viewing. This happened around 10:55, but there's nothing in the logs between 10:53 and 10:56, unfortunately. I first observed this when LibreELEC was using 12 bits, but I found the script linked here that limits it to 10 bits, and it didn't help.

    Kodi Debug Log

    External Content pastebin.com
    Content embedded from external sources will not be displayed without your consent.
    Through the activation of external content, you agree that personal data may be transferred to third party platforms. We have provided more information on this in our privacy policy.

    MediaInfo video section for file I played

    Video
    ID                                       : 1
    Format                                   : HEVC
    Format/Info                              : High Efficiency Video Coding
    Format profile                           : Main 10@L5@High
    HDR format                               : SMPTE ST 2086, HDR10 compatible
    Codec ID                                 : V_MPEGH/ISO/HEVC
    Duration                                 : 2 h 29 min
    Bit rate                                 : 16.2 Mb/s
    Width                                    : 3 840 pixels
    Height                                   : 2 160 pixels
    Display aspect ratio                     : 16:9
    Frame rate mode                          : Constant
    Frame rate                               : 23.976 (24000/1001) FPS
    Color space                              : YUV
    Chroma subsampling                       : 4:2:0
    Bit depth                                : 10 bits
    Bits/(Pixel*Frame)                       : 0.081
    Stream size                              : 16.9 GiB (78%)
    Default                                  : Yes
    Forced                                   : No
    Color range                              : Limited
    Color primaries                          : BT.2020
    Transfer characteristics                 : PQ
    Matrix coefficients                      : BT.2020 non-constant
    Mastering display color primaries        : Display P3
    Mastering display luminance              : min: 0.0050 cd/m2, max: 4000 cd/m2