Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: metamuffin <metamuffin@disroot.org>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH] avdevice/pipewire_dec: pipewire video capture
Date: Mon, 24 Apr 2023 09:21:06 +0200
Message-ID: <acba0a89-2b42-e928-9a82-cadbe648207a@disroot.org> (raw)
In-Reply-To: <168231816356.3843.9636378638988629877@lain.khirnov.net>


[-- Attachment #1.1.1.1: Type: text/plain, Size: 817 bytes --]

On 23-04-24 08:36, Anton Khirnov wrote:

Thanks for your reply!

 > Also, your email client mangled your patch.

Sorry for that, I will resend the updated patch soon. (hopefully using 
git send-mail)

 > This seems like it should be a lavfi source instead.

If you mean libavfilter, then I am confused. I thought about either 
submitting to libavformat or libavdevice. I chose the latter because 
pulse is already in there and is very similar to pipewire in that sense.

Also, now that I have a message to note this, I am planning to also 
implement pipewire video output, audio input and output as well in the 
near future. Should I first accumulate all commits or submit the working 
parts gradually? I am also not sure, whether or not pipewire support is 
even wanted in ffmpeg.

~metamuffin

[-- Attachment #1.1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 677 bytes --]

[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 236 bytes --]

[-- Attachment #2: Type: text/plain, Size: 251 bytes --]

_______________________________________________
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:[~2023-04-24  7:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-23 12:24 metamuffin
2023-04-24  6:36 ` Anton Khirnov
2023-04-24  7:21   ` metamuffin [this message]
2023-04-24  7:47     ` Anton Khirnov

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=acba0a89-2b42-e928-9a82-cadbe648207a@disroot.org \
    --to=metamuffin@disroot.org \
    --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