columbarius

Sry late to the party, but what about changing the design to using a capability/request bitmap instead of a cursor mode? The bitmap would encode what information is requested like:...

Note: gstreamer based clients like cheese will reconnect after a previous stream was stopped, but since the PipeWire-gstreamer plugin doesn't support restarting, the stream will be stalled until the gstreamer...

Sry wanted to rename the branch, but looks like github doesn't support that with open MRs...

> Dumb question from a non-Linux user: Are there Linux apps that expect webcams to come in via Pipewire? That is, if you're using a video chat app, for example,...

Opened https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/1701 to avoid having clients using the gstreamer plugin stalling the stream until closed.

#5383 isn't WIP anymore and gstreamer plugins won't stall us anymore since PipeWire 0.3.39 (don't see it as that big of an issue in previous versions), so this is ready...

> The only issue is that the PipeWire Virtualcam only trigger the `obs_output_begin_data_capture` function when an external program use the virtualcam. > > So it stay like this until a...

> I see 3 solutions: > > * Use the current state with a grey stuck `start virtual cam` > > * Call `obs_output_begin_data_capture` immediately after creation and don't send...

@Conan-Kudo thanks for trying to help. The open question is not PipeWire related but depends on OBS internals. PipeWire has a feedback if clients are connected, which the classic webcam...

For usage with v4l2 apps: * `sudo modprobe v4l2loopback exclusive_caps=1 video_nr=X card_label="OBS PipeWire Virtual Cam"` * start obs from terminal and look in the log for the PipeWire stream id...