Martin, thanks again, I find your comments very helpful. I will do some more research to determine what the best CLI arguments would be.
On Fri, Oct 4, 2024 at 7:55 PM martin schitter <ms+...@mur.at> wrote: > > > On 04.10.24 18:10, Devon Sookhoo wrote: > > I thought the option "-c:v rawvideo" was the way to go because it's > used > > to generate an uncompressed avi file: > > $ ffmpeg -i input.mp4 -c:v rawvideo out.avi > > For the older simpler file formats, where only a rather small set of > supported image format configurations were available, this kind of > handling may indeed have worked sufficient. But even under this rather > limited circumstances, you always had to take care of the actually used > pixel format and very often set/correct/enforce it explicitly. > > In principle you could adapt such a combination of -c:v rawvideo and > -pix_fmt for this kind of mp4 content as well, but I doubt that it will > work satisfactorily in practice. The range of possible configuration > variants is huge and not all of them correspond in a strict one-to-one > relation already defined ffmpeg pixel formats. > > A more format specific video codec specifier (= -c:v ...) and suitable > options for all the format specific export configuration parameters > looks much more useful to me -- but I may be wrong. > > 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".
