You're correct that I'm primarily interested in uncompressed data and not raw bayer sensor data. However, it seems like the "-c:v rawvideo" option is the convention in other formats to generate uncompressed video data. I'm just trying to follow the pattern and reuse what is already there. If there is a better option, then please suggest one.
If ISO/IEC 23001-17:2024 requires its own .c file, then perhaps that filename should use the term "uncompressed" instead of "raw". For example, mpeg_unc_enc.c On Fri, Oct 4, 2024 at 5:54 AM martin schitter <ms+...@mur.at> wrote: > > > On 04.10.24 01:33, Devon Sookhoo wrote: > > Once completed, I envision the following command to work: > > > > $ ffmpeg -i input.mp4 -c:v rawvideo output.mp4 > > Why do you choose the term "raw" instead of uncompressed? > > Using this format for "raw" bayer CFA data is just one possible > application of ISO/IEC 23001-17:2024. But it would need a rather > uncommon setup in this case. Implementing all these necessary pixel > format related configuration options, which are nearly indispensable for > useful encoding, and supporting at least an acceptable subset of all the > possible variants declared by this standard will be the real challenge > of your project. > > martin > _______________________________________________ > 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". > _______________________________________________ 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".
