I’m a robotics researcher. My interests include cybersecurity, repeatable & reproducible research, as well as open source robotics and rust programing.

  • 9 Posts
  • 5 Comments
Joined 3 years ago
cake
Cake day: June 9th, 2023

help-circle

  • I just tried Plasma Bigscreen via KDE Neon in a VM. Everything related to PC->TV automation worked as expected, aside from two fixed bugs related to missing greeter service setup and an old systemd bug still biting folks from ubuntu 24.04 based distros.

    I’ll note that the TisVlay UI isn’t yet friendly for gamepad input navigation that Plasma Bigscreen encourages, so that’s room for improvement in the Slint interface. Thanks for the leads.

    But having things like power and volume control on my phone would be really nice QoL improvements.

    I know on KDE Connect, there is a “Run Command” button in the android app UI. You could use that to run the TisVlay CLI to automate TV related macros (chaining power/input/volume commands), or just use the system/user profiles to drive the TV based on standard events like moving mouse/keyboard or other HID that would wake wayland’s idle timeout.

    I currently need to use my TV remote for power and input selection and my speaker remote for volume (though at least Jellyfin has its own volume control too).

    TisVlay can switch inputs on power for backends with input capability bits (like LG WebOS), and for as for HDMI-CEC backend - the TV firmware normally switch to the port that sent the CEC power to the TV already. But for speaker bars/stereos, that’s another idea to add to the HDMI-CEC backend. Perhaps I should extend TisVlay to control/monitor other device classes on the TV’s same CEC bus… That’d be cool for a next release.


  • Thanks! I’ve not used Plasma Bigscreen yet, but as long as it make use of the same wayland interfaces that normal KDE Plasma does, I’d imagine that session and greeter event watchers (tisvlay-session, tisvlay-greeter) implemented for idle and resume detection would work the same. Another way Plasma Bigscreen could differ is how they use screensavers or DPMS control, given the developers behind Bigscreen would be aware that OLED panel burn-in or projector bulb burn-out would bigger concern for target users, and DPMS would be moot for HDMI hardware.

    A separate question I may have would be how Plasma Bigscreen handles session login (or auto-login). TisVlay’s greeter integration monitor the host while no user is logged in runs as the same user as the DE’s own login manager. KDE recently forked SDDM for Plasma Login Manager, and that’s what I’ve been daily driving, and suspect Plasma Bigscreen uses for same HDR support.

    One thing I think would be cool to collaborate on with the Plasma team, or other distro developers such as Cachy or SteamOS is better user-land HDMI CEC integration in Linux. TisVlay already makes use of Valve’s linux-cec rust crate, and many gaming distros already ship kernels with CONFIG_CEC_CORE enabled. Rather than working on orthogonal control planes for driving CEC based peripherals, it could be wise to split that out into a shared abstraction. TisVlay does publish a public SDK, but that is more so for programmatically interfacing with TisVlay’s daemon at runtime, rather than say hardware abstraction library.

    That all aside, I’ll add Plasma Bigscreen in my que for QA, and check if nixpkgs has merged any changes for it that I could quickly test from.

    Have you used Plasma Bigscreen yet or know what the development status is nowadays?