Posts by chewitt

  • Hauppauge WinTV-NOVA-S2 tuner not recognised

    Quote from jcjefferies

    Is there something else I should be doing?

    Sharing a log file?

    NB: These days we are not too enthusiastic about adding patches that we can't drop in the future with a kernel bump, so if there are things in Issues/Forum threads that work (meaning, they need to be tested and confirmed first) someone needs to submit them to the linux-media mailing list. As long as there are signs that patch(es) will be merged upstream we will be happy to pick/backport the changes until some future kernel bump drops them. Firmware is more easily handled as we mostly have our own collection(s) and can add things to our own repo.

    Also note that I'm unable to test any form of DVB hardware (as no DVB-T/DVB-S feeds) so I depend on being told what's needed.

  • Libreelec 11, 12 and 12.2 doesnt work on S905 "Minix Neo U1" Box. Why?

    Kodi uses a 'compromise' but safe default for software deinterlacing. It's possible (with patching) to make it use other deinterlace algorithms that ffmpeg supports, but older ARM SoC boards like S905 don't have CPU grunt for the fancier ones that give better results. The S905 hardware has a dedicated deinterlace function, but software support for that only exists in the Amlogic vendor codebase that Kodi and LE moved away from. Older LE/CE images are more feature complete.

    DRMPRIME is a zero-copy rendering path (nothing to do with Amazon); meaning we read the video stream and then all processing stages through Kodi, FFMpeg, and kernel drivers; exchange a pointer to the original data in memory instead of reading it from RAM, changing it in some way, then writing back to RAM again. It's more efficient, but it's use requires the kernel hardware decode drivers which are not perfect. The only alternative is to disable hardware decode and use ffmpeg software decode. Playback start and seek on HEVC media then works great, but unless the video bitrate is extremely low you won't have enough CPU grunt to handle 1080p media. If you only need to play SD or 720p media (or have faster hardware like S922X/A311D) it's an option though.

    Nobody is working on the hardware decoders for several years now, so I have no expectations of improvements coming. For some users AMLGX works good-enough. For others not-good-enough. I am not a driver developer so I'm merely keeping the status-quo until either someone appears to do work, or the hardware dies out. S905 is now a decade old so the later is more likely.

  • Power fail corrupts mounted drives

    Quote from jsprenkle

    Hello, any suggestions how to prevent corruption when the power fails?

    Disabling the write cache helps. Mounting read-only helps. Using EXT4 or perhaps BTRFS (with more advanced journaling) instead of NTFS also probably helps. Using hardware RAID helps. We do not support software RAID; there are too many variants and tools and we prefer to avoid the bloat incurred. No filesystem is corruption proof so if you truly want to prevent corruption, prevent the loss of power (Yes, get a UPS).

  • [Odroid-C2] TV Power-On by CEC

    The ability to turn on from CEC probably requires support in (mainline) u-boot and for the device to be in a suspended state so there's some level of power to detect things on the HDMI connection. I've no idea if that's implemented or not. I'll ask the main Amlogic u-boot custodian, but an answer might take a while as I know he's currently on vacation.

  • [x86-64] Wrong speed with "Sync Playback to Display"

    Quote from thomaz

    PLS, HEAD DEVS OF LIBREELEC/KODI. THINK ABOUT MY IDEA!!!

    Your idea requires all media to be adapted to a different refresh rate. This requires excessive CPU resources. The idea also breaks the concept of a zero-copy video pipeline which something that Kodi has long-worked to implement because it's the most efficient way to process high-bitrate and large filesize media. In short; the idea is a load of hooey and dead in the water :)

  • [x86-64] Crash

    The cause is not clear, but it crashes shortly after starting, and in one log very-shortly after add-ons are loaded; so I'll guess the cause is an incompatible add-on (perhaps not updated for K22 alpha).

    Skins (and the many add-ons they depend upon sometimes) are a common cause for major crashes, so perhaps delete the skin add-on to force Kodi to default back to Estuary and see if that helps.

    If not, you need to hunt down the problem add-on. Stop Kodi, rename /storage/.kodi to /storage/.kodi-old and copy essential config over, e.g. sources and add-on settings. Then restart kodi and start reinstalling add-ons from repos. Either it all works (problem solved) or at some point you install something and problems start; then you know which add-on is the cause.

  • Help with drivers for MyGica PT682C

    Hauppague are a reputable manufacturer with good upstream kernel support, and Sundtek have well supported userspace drivers that don't depend on the kernel, which makes life easier. I can't speak for whether they are cheap or not, but they should work with LE well. If you go cheap, you're more likely to need a separate device for the server that can run a specific distro/kernel someone hacked up the drivers for, instead of using LE.