Replies: 14 comments
-
Please provide FULL logs. Thank you. HyperHDR depends heavily on the authentication token that should be provided by the portal. Without the token such portal implementation (missing true Portal protocol 4 specification despite reporting it) is useless for HyperHDR usage. |
Beta Was this translation helpful? Give feedback.
-
@awawa-dev sure no problem, here are the logs from a run where this happened. I've restarted pipewire in the middle of it as you can see. |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
Thanks. Didn't know that it's possible for user to overcome that behavior when Portal ask you every time to select and confirm which monitor to capture (and save it for later usage, that crucial option is provided by properly implemented protocol 4, currently works only in Gnome Portal implementation I think). Beside that missing token logs looks normal, the Pipewire stream seems OK and HyperHDR is receiving "something" from Pipewire because it holds to priority 245 (system grabber in your case). |
Beta Was this translation helpful? Give feedback.
-
@awawa-dev Super weird then. Can I increase the log level or something so that we can find out why exactly the screen capture stops working? |
Beta Was this translation helpful? Give feedback.
-
For the application the stream is active, the portal error callback was not invoked so everything is "fine" and there is no way to increase log level by some settings: everything in that grabber is set to high level and logs to console almost everything. But you can add a line to to make sure something indeed is received e.g.std::cout << "Pipewire: new frame is received" << std::endl;
|
Beta Was this translation helpful? Give feedback.
-
Alright thanks, will do that and report back ! |
Beta Was this translation helpful? Give feedback.
-
One more thing: 3840 x 2160 is quite a lot but it should work if there are necessary resources. Try to test it with 1080p and lower capturing rate to 10 or something. |
Beta Was this translation helpful? Give feedback.
-
@awawa-dev How do I lower that? In the settings it is already 512px. |
Beta Was this translation helpful? Give feedback.
-
I meant your OS desktop resolution to test it and rule out resouces. Framerate you can set in HyperHDR. Observe |
Beta Was this translation helpful? Give feedback.
-
Oh my cpu usage is absolutely fine with the capturing, this is a pretty beefy desktop pc. |
Beta Was this translation helpful? Give feedback.
-
Maybe something gets messed up during transport to my WLED instance? But hyperion-ng did that without problems so it should work here as well. I guess I will try and log the pipewire frame and then go from there. |
Beta Was this translation helpful? Give feedback.
-
The problem could be not in CPU. It's worth to test it. Forget WLED or any other LED driver, for 99% it's not related but you can set LED driver to debug/file if you want. |
Beta Was this translation helpful? Give feedback.
-
Because there is no trace of the crash or any other HyperHDR problem in the logs, I move it to the discussion. |
Beta Was this translation helpful? Give feedback.
-
Bug report, debug log and your config file (FULL LOGS ARE MANDATORY)
Steps to reproduce
Use HyperHDR with pipewire sceen capture on Nixos Sway
What is expected?
Screen grabbing works
What is actually happening?
After about 10 seconds the screen grabbing stops working
System
In OBS and other application the pipewire screen capture works without problems.
Beta Was this translation helpful? Give feedback.
All reactions