public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Gergo Koteles <soyer@irl.hu>
Cc: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
	Oleksandr Natalenko <oleksandr@natalenko.name>,
	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>
Subject: Re: [RFC PATCH] media: Virtual camera driver
Date: Mon, 2 Feb 2026 13:40:12 +0200	[thread overview]
Message-ID: <20260202114012.GA4173464@killaraus> (raw)
In-Reply-To: <0fc43020620f211a7962a819c617056fbb499d86.camel@irl.hu>

On Mon, Feb 02, 2026 at 12:36:44PM +0100, Gergo Koteles wrote:
> On Mon, 2026-02-02 at 02:02 +0100, Mauro Carvalho Chehab wrote:
> > On Mon, 02 Feb 2026 00:25:37 +0100
> > Oleksandr Natalenko <oleksandr@natalenko.name> wrote:
> > 
> > > Date: Mon, 02 Feb 2026 00:25:37 +0100
> > > From: Oleksandr Natalenko <oleksandr@natalenko.name>
> > > To: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
> > > Cc: Laurent Pinchart <laurent.pinchart@ideasonboard.com>, 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>
> > > Message-ID: <13939245.uLZWGnKmhe@natalenko.name>
> > > 
> > > On pondělí 2. února 2026 0:17:20, středoevropský standardní čas Mauro Carvalho Chehab wrote:
> > > > No. At the machine with the camera, obs can read from a V4L2 input,
> > > > generate a mpeg TS stream, and listen to a UDP port (for instance). 
> > > > 
> > > > At the remote machine, you can just pass the URL to ffmpeg.  
> > > 
> > > I can't, I have to feed the stream into Firefox somehow for it to see the stream as a virtual webcam.
> > 
> > Motioneye could be used on such scenario. It has a proper web
> > interface, allows multiple users to watch, has login control accepts
> > multiple cameras.
> > 
> 
> WebRTC in browsers isn't that bad. Firefox and Chrome also have
> PipeWire video support. 
> 
> 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.

-- 
Regards,

Laurent Pinchart

  reply	other threads:[~2026-02-02 11:40 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 [this message]
2026-02-02 11:45                       ` Oleksandr Natalenko
2026-02-03  1:23                         ` Laurent Pinchart
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=20260202114012.GA4173464@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=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