Posts by chewitt

  • [RPi4] No HDMI Audio Passthrough in LibreELEC 12.0.2

    antonvier Kodi detects audio capabilities based on the EDID data on the HDMI connection. It's also odd that the kernel detects the audio hardware, but Kodi then fails to open the device(s) to check properties. The very limited list of resolutions shown here would normally suggest a problem in the display chain. That can result in failure to detect normal 1080p/4K modes etc. but doesn't explain the lack of audio hardware.

    Code
    dtoverlay=vc4-kms-v3d
max_framebuffers=2
hdmi_enable_4kp60=1

    Comment the above ^ out in config.txt. Disabling 4K60 (which 99% of users don't need, 4K30 is enough) also reduces the power draw which might help with an inadequate PSU issue. That's the only real red-flag that I can see; insufficient stable power (under-rated for current normally) will sometimes manifest all kinds of weird issues. RPi4 needs 5V/3A to be stable. Recycled phone chargers or using USB ports on a TV/monitor generally won't work. Check the PSU out. Also check cables/ports, and if you inflicted self-punishment with an Argon case, remove the board from the case before retesting.

    Any difference?

  • [Dreambox One] No HD Audio passthrough

    FWIW, I can replicate the original issue report of no DTS-HD-MA audio. I've no idea what the problem is though, other than it's most likely to be an issue in the DRM layer, and right now (and since I only use PCM output in testing) I'm not motivated to look into the issue further. I am highly confident the issue is specific to Amlogic hardware so no need for you to find RPi threads and make "me too" posts there, it's only adding distraction to other people's (different) issues.

  • [Dreambox One] No HD Audio passthrough

    I don't have any Dreambox hardware, and in the several years since I added upstream support for _emanuel_ nobody has ever bothered to explain (or, here's a crazy idea, add some content to the open wiki to document) that Dreambox devices require some wonky boot arrangement to run the AMLGX image. That only became clear about a week ago, and If I'd have known that before I probably wouldn't have bothered creating and sending the device-trees upstream. Ho hum.

    The latest Dreambox device(s) that _emanuel_ is now asking me to support are Android based, so that's been on my mind among other things. Yes of course the older stuff uses Yocto/OE to make something from the Android BSP from Amlogic. Regardless, the point still stands: If you want an OS where everything works, you need to run the vendor firmware image.

    The AMLGX image is generally curated to use the best (or newer hardware, least-worst) default settings. You can use 4K VP9 as that works, but you will not get far with 4K HEVC because hardware decode is intentionally disabled to prevent the SoC crashing instantly when the V4L2 codec is opened, and that caps HEVC to 1080p max in software. Forcing EGL rendering instead of Direct-to-Plane only loses the benefits of DRMPRIME and makes things worse; and hence I stopped reading the 'testing' .. it's obviously a user flailing around with random settings in the hope of finding a magic combination that beats the negative but clear description of current state provided in release notes. Good luck with that.

  • Dune Homatics Box 4K Plus

    Things moved forwards, but overall not much changed. Amlogic engineers recently submitted support for DRM (video output) and audio support on S4 devices (must-haves for an LE image) but all their patches are poor quality and require many iterations to adapt to upstream standards. They are also slow at iterating, so it will be a while before those changes get merged. I've made a note to ask Khadas for a VIM1S sample (S905Y4, so related to S905X4) to explore packaging.. but I have low expectations of doing much with the board for a while yet.