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: signature.asc
Description: PGP signature

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

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

Reply via email to