Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Marcus B Spencer <marcus@marcusspencer.xyz>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH v10] avcodec: add farbfeld encoder, decoder and demuxer
Date: Fri, 07 Jun 2024 19:33:32 +0000
Message-ID: <7IxwhGiC47ZM5hYHws1Xn1GN5ugU3zdktX6-cmzpKBbhiMHNn1Xa7ky7AgQZ0Olawg_hpZxOAMgaBmhKQPLA36SRcf12_vr-0Jv6iv7aDa8=@marcusspencer.xyz> (raw)
In-Reply-To: <d79e8940-0c6c-436c-bf26-dda41e00d3d7@lynne.ee>






On Friday, June 7th, 2024 at 1:12 PM, Lynne via ffmpeg-devel <ffmpeg-devel@ffmpeg.org> wrote:

> Since the "codec" is essentially just raw data, you should just make the
> demuxer output native RGBA64, and the muxer accept RGBA64. There's no
> reason to have this as a codec, since the header field is completely
> redundant with the fields an AVFrame contains.

There is no specific farbfeld muxer. The muxers are just "image2" and "image2pipe".

There IS a specific farbfeld pipe demuxer called "farbfeld_pipe".

Also the reason to have this as a codec is for image2 syntax support.
_______________________________________________
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-06-07 19:33 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-07 17:47 Marcus B Spencer
2024-06-07 18:12 ` Lynne via ffmpeg-devel
2024-06-07 19:33   ` Marcus B Spencer [this message]
2024-06-07 20:56     ` Lynne via ffmpeg-devel
2024-06-07 20:22   ` Paul B Mahol
2024-06-07 20:58     ` Lynne via ffmpeg-devel
2024-06-07 22:07       ` Paul B Mahol

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='7IxwhGiC47ZM5hYHws1Xn1GN5ugU3zdktX6-cmzpKBbhiMHNn1Xa7ky7AgQZ0Olawg_hpZxOAMgaBmhKQPLA36SRcf12_vr-0Jv6iv7aDa8=@marcusspencer.xyz' \
    --to=marcus@marcusspencer.xyz \
    --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