166
My Linux HTPC/Couch Gaming Build (programming.dev)
submitted 2 months ago by to c/linux@programming.dev
43 comments fedilink hide all child comments
 

I set up a Linux pc to replace my smart TV and add some gaming capabilites. It took some time but I learned quite a lot (Thanks to Debian and Arch wikis). And I haven't missed any TV functionality.

The launcher is flex-launcher on a labwc environment/compositor on a Debian stable distro. (For testing and easy setup, I also did it on Ubuntu Gnome but I don't need a full DE in the background that I don't use. But it's adaptable to other distros and DEs.)

It's now fully usable with a gamepad including turning the TV on and off, so I have also fully replaced the TV remote.

I hope some people may find it interesting. It was also quite a lot of fun, actually.

you are viewing a single comment's thread
view the rest of the comments
[–] 16 points 2 months ago (4 children)

Interested in how you got power on/off to work - I thought Linux couldn’t support ARC due to licensing?

  • permalink
  • fedilink
  • source
  • hideshow 8 child comments
    •
  • [–] 16 points 2 months ago (2 children)

    Powering on/off is part of HDMI-CEC, right? And its unsupported in both Windows and Linux due to most consumer GPUs not supporting it. I think you need a USB adapter to inject the CEC code into the HDMI cable to make it work.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 4 child comments
    •
  • [–] 4 points 2 months ago

    CEC works fine with kodi on my raspberry pi (kodi on top of RPiOS, I did not try libreElec) plugged to an old-ish TV, and it's really nice to have. The Pi puts the TV into standby and wakes it up, and I can control Kodi with the TV's remote

  • permalink
  • fedilink
  • source
  • parent
  • [–] 1 point 2 months ago (1 child)

    I'm pretty sure bitstreaming Dolby Atmos/TrueHD or DTS X/HDMA doesn't work from Linux. So if you're using an AV receiver with a surround sound system, you may still want to stick with Microslop. I'd be ecstatic if I was wrong about this, so if I am, someone, please correct me.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 4 points 2 months ago (1 child)

    Bitstreaming/passthrough for lossless formats like Dolby TrueHD (including Atmos) and DTS-HD Master Audio (including DTS:X) works perfectly on Linux.Linux does not natively decode Dolby Atmos or DTS:X because it lacks the commercial licenses to process the spatial metadata. However, Linux excels at HDMI Audio Passthrough. Instead of processing the audio, your Linux machine treats the uncompressed bitstream like a raw data package and forwards it directly to your AV receiver via HDMI. The receiver recognizes the signal and handles the heavy decoding lifting.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 1 point 2 months ago* (last edited 2 months ago) (1 child)

    When I look at the settings and the wiki, it says passthrough still won't work with DTS-HD or Atmos:

    Note: PulseAudio does not currently allow TrueHD or DTS-MA passthrough, this is a PulseAudio limitation and not a limitation of the Kodi implementation, in order to get 7.1 audio Multichannel Mode must be used

    https://kodi.wiki/view/PulseAudio

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] -1 points 2 months ago (1 child)

    Sorry for the AI answer but it does look possible.

    The confusion in image.png stems from the difference between what the Linux kernel can do versus what specific audio servers like PulseAudio support. The "real answer" is that Tabooki2 is technically correct, but crimson_iris is correct regarding a specific (and common) software limitation. Here is the breakdown: The Short Answer Yes, Linux can bitstream/passthrough Dolby Atmos and DTS:X, but you have to use the right audio architecture. If you use PulseAudio, it will fail (as shown in the wiki snippet in image.png). If you use PipeWire or bypass the sound server entirely (using ALSA directly), it works perfectly. Why the conflict exists in image.png The debate in the screenshot is a classic "it depends on your stack" scenario: The PulseAudio Limitation: As noted in the wiki link in image.png, PulseAudio was never designed to handle the high-bandwidth "packets" required for lossless passthrough like TrueHD or DTS-MA. It tries to "help" by processing audio, which breaks the raw bitstream needed for your receiver to see "Atmos." The PipeWire Solution: Most modern Linux distributions (like Fedora, Ubuntu, or Arch) have moved to PipeWire. PipeWire does support passthrough for these formats much more effectively. The ALSA "Direct" Method: For home theater PC (HTPC) apps like Kodi or Plex HTPC, you can often set the audio output device to "ALSA (Direct)" or "HDA Intel HDMI." This bypasses the desktop sound server entirely and sends the raw data straight to the HDMI port, which is exactly what Tabooki2 describes. How to get it working If you are setting up a Linux-based media center and want that "Atmos" light to turn on your receiver: Check your Sound Server: Ensure you are running PipeWire instead of PulseAudio. Application Settings: In software like Kodi, go to Settings > System > Audio. Enable "Allow Passthrough." Select the specific formats your receiver supports (TrueHD, DTS-HD, etc.). Kernel Support: Since you are managing complex home server stacks with Docker and Portainer, ensure your containerized media apps have direct access to the /dev/snd hardware devices to avoid software-layer interference. Summary: The information from Tabooki2 is the ultimate truth of the hardware capability, while the note from crimson_iris is a valid warning for users stuck on older PulseAudio configurations.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •