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>,
pobrn@protonmail.com
Subject: Re: [RFC PATCH] media: Virtual camera driver
Date: Mon, 6 Apr 2026 15:37:36 +0300 [thread overview]
Message-ID: <20260406123736.GC1268443@killaraus.ideasonboard.com> (raw)
In-Reply-To: <12919433.O9o76ZdvQC@natalenko.name>
On Mon, Apr 06, 2026 at 02:23:46PM +0200, Oleksandr Natalenko wrote:
> On úterý 3. února 2026 21:49:11, středoevropský letní čas Laurent Pinchart wrote:
> > > > Just to share my current state of affairs:
> > > >
> > > > * sender:
> > > >
> > > > $ gst-launch-1.0 pipewiresrc path=<webcam_id> ! video/x-h264, width=1280, height=720, framerate=24/1 ! rtph264pay ! rtpstreampay ! udpsink host=<receiver_host> port=<receiver_port>
> > > >
> > > > * receiver:
> > > >
> > > > $ gst-launch-1.0 udpsrc address=<receiver_host> port=<receiver_port> ! queue ! application/x-rtp-stream,encoding-name=H264 ! rtpstreamdepay ! application/x-rtp,encoding-name=H264 ! rtph264depay ! h264parse ! openh264dec ! pipewiresink mode=provide stream-properties="properties,media.class=Video/Source,media.role=Camera" client-name=VirtualCam
> > > >
>
> > > I'm writing a blog post on this topic, I'll reply with a link when I'll
> > > be done.
> >
> > https://www.ideasonboard.com/news/pipewire-is-the-new-v4l2loopback/
>
> It looks like it's now broken in PipeWire 1.6.x. I've reported it
> here: [1], but I'm not sure what's next.
I haven't tried v1.6.x yet.
> Do you maybe have more info on this?
I don't, but Barnabás may. I think he's OoO this week though (chasing
easter bunnies and chocolate eggs somewhere, most likely), so replies
will likely be delayed.
> Thank you.
>
> [1]: https://gitlab.freedesktop.org/pipewire/pipewire/-/work_items/5165
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2026-04-06 12:37 UTC|newest]
Thread overview: 39+ 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
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-04-06 12:23 ` Oleksandr Natalenko
2026-04-06 12:37 ` Laurent Pinchart [this message]
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=20260406123736.GC1268443@killaraus.ideasonboard.com \
--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=pobrn@protonmail.com \
--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