Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Anton Khirnov <anton@khirnov.net>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH] avdevice/v4l2: add limited support for multiplanar API
Date: Mon, 01 Jul 2024 16:15:57 +0200
Message-ID: <171984335759.21847.10548656552450078755@lain.khirnov.net> (raw)
In-Reply-To: <CALweWgA5epMnq2hS=ersb8Nyz-N0URU-1arbV16YOQ7t_bZb5g@mail.gmail.com>

Quoting Ramiro Polla (2024-06-28 13:47:13)
> On Thu, Jun 27, 2024 at 6:06 PM Anton Khirnov <anton@khirnov.net> wrote:
> > Quoting Ramiro Polla (2024-06-27 16:13:24)
> > > Is anyone fundamentally opposed to this approach to implement limited
> > > support for multiplanar API? I figure it could still be useful even
> > > when full multiplanar API support is implemented, because multiple
> > > memory buffers per packet will likely mean memcpy()s, which can be
> > > avoided if the plane count is one.
> >
> > Ideally this should be turned into a lavfi source, then multiple planes
> > can be exported individually.
> 
> Good idea. Is there any kind of roadmap on how this conversion from
> input device to source filter should take place, or is this something
> that still lacks consensus?

AFAIK there is a wide consensus that this is something that should be
done in general, though of course that does not directly translate into
volunteers actually doing the conversion.

> I assume we want to keep the functionality from the command line (so
> that "-i /dev/video0" would still use the lavfi source internally
> somehow). Would the code be shared between libraries, or would it be
> moved to lavfi and a wrapper written in lavd instead?

V4L2 is trickier than most devices, since it can also produce compressed
video. So at least that part of the functionaity will have to stay as a
demuxer.

-- 
Anton Khirnov
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel

To unsubscribe, visit link above, or email
ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".

  reply	other threads:[~2024-07-01 14:16 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-20 15:40 Ramiro Polla
2024-06-25  9:19 ` Anton Khirnov
2024-06-25 11:56   ` Ramiro Polla
2024-06-27 14:13     ` Ramiro Polla
2024-06-27 16:05       ` Anton Khirnov
2024-06-28 11:47         ` Ramiro Polla
2024-07-01 14:15           ` Anton Khirnov [this message]
2024-06-28 12:54       ` Ramiro Polla
2024-07-01 17:38         ` Ramiro Polla

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=171984335759.21847.10548656552450078755@lain.khirnov.net \
    --to=anton@khirnov.net \
    --cc=ffmpeg-devel@ffmpeg.org \
    /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

Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel

This inbox may be cloned and mirrored by anyone:

	git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \
		ffmpegdev@gitmailbox.com
	public-inbox-index ffmpegdev

Example config snippet for mirrors.


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git