public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Oleksandr Natalenko <oleksandr@natalenko.name>
Cc: Gergo Koteles <soyer@irl.hu>,
	Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
	Jarkko Sakkinen <jarkko@kernel.org>,
	linux-media@vger.kernel.org, jani.nikula@linux.intel.com,
	anisse@astier.eu, Mauro Carvalho Chehab <mchehab@kernel.org>,
	Hans Verkuil <hverkuil@kernel.org>,
	Sakari Ailus <sakari.ailus@linux.intel.com>,
	Jacopo Mondi <jacopo.mondi@ideasonboard.com>,
	Ricardo Ribalda <ribalda@chromium.org>,
	open list <linux-kernel@vger.kernel.org>,
	Nicolas Dufresne <nicolas@ndufresne.ca>
Subject: Re: [RFC PATCH] media: Virtual camera driver
Date: Tue, 3 Feb 2026 03:23:13 +0200	[thread overview]
Message-ID: <20260203012313.GA280953@killaraus> (raw)
In-Reply-To: <22989766.EfDdHjke4D@natalenko.name>

Hi Oleksandr,

(Cc'ing Nicolas Dufresne)

On Mon, Feb 02, 2026 at 12:45:15PM +0100, Oleksandr Natalenko wrote:
> On pondělí 2. února 2026 12:40:12, středoevropský standardní čas Laurent Pinchart wrote:
> > > If I understand correctly, it would be more forward-thinking to develop
> > > virtual camera support in PipeWire rather than in the kernel.
> > 
> > I don't think there's even a need for development in PipeWire
> > 
> > $ gst-launch-1.0 \
> > 	videotestsrc ! \
> > 	video/x-raw,format=YUY2 ! \
> > 	pipewiresink mode=provide stream-properties="properties,media.class=Video/Source,media.role=Camera"
> > 
> > This gives me a virtual camera in Firefox. Extending the GStreamer
> > pipeline to get the video stream from the network should be quite
> > trivial.
> 
> So far, I came up with this:
> 
> * sender:
> 
> $ gst-launch-1.0 pipewiresrc path=<webcam_id> ! image/jpeg, width=1280, height=720, framerate=24/1 ! rndbuffersize max=1400 ! udpsink host=<receiver_host> port=<receiver_port>
>
> * receiver:
> 
> $ gst-launch-1.0 udpsrc address=<receiver_host> port=<receiver_port> ! queue ! image/jpeg, width=1280, height=720, framerate=24/1 ! jpegparse ! jpegdec ! pipewiresink mode=provide stream-properties="properties,media.class=Video/Source,media.role=Camera" client-name=VirtualCam
>
> Please let me know if I do something dumb here. Trial and error to
> make this work took a couple of hours for me, but it seems to provide
> what I need.

There's nothing dumb at all, especially given that it works :-) I have
been able to reproduce it locally (using a different pipeline on the
sender side).

I compared your pipelines with another JPEG-over-UDP setup I used a
while ago, which used an rtpjpegpay element before udpsink on the sender
side to encapsulate the payload in RTP packets, and an rtpjpegdepay
element on the receiver side after udpsrc. This helps the receiver
synchronize with the sender if the sender is started first. The full
pipelines are

* Sender:

gst-launch-1.0 \
	v4l2src ! \
	video/x-raw,pixelformat=YUYV,size=640x480 ! \
	jpegenc ! \
	rtpjpegpay ! \
	udpsink host=192.168.10.200 port=8000

* Receiver:

gst-launch-1.0 \
	udpsrc port=8000 ! \
	application/x-rtp,encoding-name=JPEG,payload=26 ! \
	rtpjpegdepay ! \
	jpegdec ! \
	video/x-raw,pixelformat=YUYV,size=640x480 ! \
	queue ! \
	pipewiresink mode=provide \
	       stream-properties="properties,media.class=Video/Source,media.role=Camera" \
	       client-name="Remote Camera"

Unfortunatley this doesn't work, when the pipewire client connects to
the stream on the receiver side I get

ERROR: from element /GstPipeline:pipeline0/GstPipeWireSink:pipewiresink0: stream error: no more input formats

Nicolas, would you have any wisdom to share about this and tell me if I
did something dumb ? :-) There's no hurry.

-- 
Regards,

Laurent Pinchart

  reply	other threads:[~2026-02-03  1:23 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-01 13:33 [RFC PATCH] media: Virtual camera driver Jarkko Sakkinen
2026-02-01 18:20 ` Laurent Pinchart
2026-02-01 19:04   ` Jarkko Sakkinen
2026-02-01 20:06     ` Laurent Pinchart
2026-02-01 20:14       ` Oleksandr Natalenko
2026-02-01 20:21         ` Mauro Carvalho Chehab
2026-02-01 20:26           ` Oleksandr Natalenko
2026-02-01 23:17             ` Mauro Carvalho Chehab
2026-02-01 23:17               ` Mauro Carvalho Chehab
2026-02-01 23:25               ` Oleksandr Natalenko
2026-02-02  1:02                 ` Mauro Carvalho Chehab
2026-02-02  7:16                   ` Oleksandr Natalenko
2026-02-02 11:41                     ` Laurent Pinchart
2026-02-02  9:05                   ` Jarkko Sakkinen
2026-02-02  9:19                     ` Jarkko Sakkinen
2026-02-02 11:43                       ` Laurent Pinchart
2026-02-02 11:36                   ` Gergo Koteles
2026-02-02 11:40                     ` Laurent Pinchart
2026-02-02 11:45                       ` Oleksandr Natalenko
2026-02-03  1:23                         ` Laurent Pinchart [this message]
2026-02-03 14:38                           ` Oleksandr Natalenko
2026-02-03 14:53                             ` Laurent Pinchart
2026-02-03 20:36                               ` Laurent Pinchart
2026-02-03 21:39                                 ` Oleksandr Natalenko
2026-02-03 21:49                                   ` Laurent Pinchart
2026-02-03 20:49                               ` Laurent Pinchart
2026-02-01 20:22         ` Laurent Pinchart
2026-02-01 20:27           ` Oleksandr Natalenko
2026-02-01 20:41             ` Laurent Pinchart
2026-02-01 20:35       ` Jarkko Sakkinen
2026-02-01 20:54         ` Jarkko Sakkinen
2026-02-01 21:09           ` Laurent Pinchart
2026-02-02  1:44             ` Jarkko Sakkinen
2026-02-01 21:01         ` Laurent Pinchart
2026-02-01 22:03           ` Jarkko Sakkinen
2026-02-03  9:50       ` Jani Nikula
2026-02-03 15:06         ` Laurent Pinchart

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20260203012313.GA280953@killaraus \
    --to=laurent.pinchart@ideasonboard.com \
    --cc=anisse@astier.eu \
    --cc=hverkuil@kernel.org \
    --cc=jacopo.mondi@ideasonboard.com \
    --cc=jani.nikula@linux.intel.com \
    --cc=jarkko@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab+huawei@kernel.org \
    --cc=mchehab@kernel.org \
    --cc=nicolas@ndufresne.ca \
    --cc=oleksandr@natalenko.name \
    --cc=ribalda@chromium.org \
    --cc=sakari.ailus@linux.intel.com \
    --cc=soyer@irl.hu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox