Bug 444598 - Video feed freezes permanenty when the pipewire video feed is disconnected and reconnected
Summary: Video feed freezes permanenty when the pipewire video feed is disconnected an...
Status: RESOLVED FIXED
Alias: None
Product: kamoso
Classification: Applications
Component: general (show other bugs)
Version: 21.08.2
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Aleix Pol
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-10-29 10:27 UTC by Antti Savolainen
Modified: 2023-11-28 08:16 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Antti Savolainen 2021-10-29 10:27:24 UTC 
SUMMARY
Demonstrative video: https://youtu.be/1m-jBdtOXG8
When you disconnect the pipewire video feed from kamoso it stays frozen permanently, even if you reconnect the nodes. If this is a pipewire bug, let me know and I'll go pester them.

STEPS TO REPRODUCE
1. Use kamoso with pipewire
2. Disconnect kamoso from the video feed
3. Reconnect the nodes

OBSERVED RESULT
The video freezes permanently until something on the software side resets the connection

EXPECTED RESULT
The video should be unfrozen once the connection returns

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Arch Linux
(available in About System)
KDE Plasma Version: 5.23.2
KDE Frameworks Version: 5.87.0
Qt Version: 5.15.2
Comment 1 Aleix Pol 2021-11-01 01:51:45 UTC 
And why would you do that?

In any case, this is probably an issue upstream in pipewire gstreamer integration. We are just using "wrappercamerabinsrc", there's not much we can do about it from kamoso.
Comment 2 Antti Savolainen 2021-11-01 02:39:19 UTC 
No practical reason. I was only testing the rerouting possibilities of pipewire video feeds. Although now that I think about it, there could be a reason to do so if in the future you want to reroute video through some simple effect program before connecting it back to kamoso. 

Anyways, I'll go file a pipewire bug.
Comment 3 Antti Savolainen 2023-11-28 08:16:41 UTC 
This seems to have been fixed in upstream pipewire.