Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Nicolas George <george@nsup.org>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [RFC] A file format to store generic raw image/video files
Date: Wed, 18 Oct 2023 00:19:39 +0200
Message-ID: <ZS8Ie13A3HtcDVox@phare.normalesup.org> (raw)
In-Reply-To: <CAEb0MffVJ5Pz-kux5FWo8FfLRag6y+AT1UdtBUSt7F78DjOD3w@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 993 bytes --]

Chema Gonzalez via ffmpeg-devel (12023-10-17):
> # RFC: A file format to store generic raw image/video files
> 
> Context: Developers and researchers often want to use raw image/video
> files, as they avoid the effects of encoding. Dealing with raw

Looks like a XY problem.

> We propose a new raw image/video format, R4M, that extends Y4M to support:

Please explain why you think storing raw video or any other lossless
codec into a standard container format like Matroska or Nut does not
satisfy your needs.

> * (a) every `pix_fmt` that ffmpeg supports. The implementation would
> support generic AVPixFmtDescriptor's, so any new pixel format based on
> it will be automatically supported. This includes
> planar/packed/semiplanar, yuv/rgb/bayer, and others.

This does not make any sense. Please mediate on the fundamental
difference between in-memory representations and permanent storage
representations.

PS: do not Cc me.

Regards,

-- 
  Nicolas George

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 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-10-17 22:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-17 22:11 Chema Gonzalez via ffmpeg-devel
2023-10-17 22:19 ` Nicolas George [this message]
2023-10-18  1:06 ` Lynne

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=ZS8Ie13A3HtcDVox@phare.normalesup.org \
    --to=george@nsup.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