Closed nocin closed 6 months ago
Hi Are you sure you start HyperHDR as an application from the menu and you have the icon in the systray? Not as a service/Daemon?
Hi,
ahh, that was easy... Since I saw the message "Start the service: sudo systemctl start" after the installation, I somehow expected that it had to be executed as a systemd service. I completely overlooked the "Troubleshooting? Run HyperHDR manually" part.
I now have one option, which is Display nr: 0, and also this helpful explanation box above, that tells me exactly what I did wrong when I had it running as a service. This was exactly the message I needed before, but it wasn't shown to me, as you can see in the screenshot above. Display nr: 0 seems to be a combination of all three displays.
Is there any way to select only display 3?
Thanks, Nico
I'm afraid that's not possible, at least for now. Under Ubuntu/Gnome, the x11 session capturing also works with the Pipewire grabber (the same one used by default for Wayland sessions), and you can probably select a specific monitor there because the Portal dialog for Pipewire offers advanced options. But it looks like Pipewire x11 capturing is not implemented here. A workaround is to use the crop function, thanks to which you can cut out the area you are interested in. But of course this is not an optimal solution.
These experiments seem a bit too complicated for me as a non-Linux power user. :-)
Anyway, thanks for your detailed explanation! Really appreciate that!
So far, HyperHDR is now running great and it's already an improvement. Coming from Hyperion having now and then problems, especially in the combination with Home Assistant turning the WLED strip on and off. But this seems to work flawless now. Will now also do the switch on my HTPC.
Perhaps you could modify the "Explanation" message from the screenshot above, so that it is also displayed when starting HyperHDR as a service. Just to prevent others from making the same mistake I did. Will close the issue, thanks again for the tool and the support!
Bug report, debug log and your config file (FULL LOGS ARE MANDATORY)
Steps to reproduce
Video Capturing -> Software Screen Capture -> Device I get only /dev/fb0 instead of my display devices, allthough three monitors are connected.
Perhaps this log line is related to the problem?!
2024-04-28T00:16:29.678Z [DAEMON] The system doesn't support the X11 system grabber
But I'm definitly using X11 (not Wayland).What is expected?
The possibility to select a display as video capturing device.
What is actually happening?
A display device (/dev/fb0) is automatically selected, which only results in a black screen.
System
Let me know, if I need to provide more infos. Thanks! Nico