[FFmpeg-user] ? About ffmpeg's prores implemention

Phil Rhodes phil_rhodes at rocketmail.com
Fri Aug 28 16:49:39 EEST 2020

 On Friday, 28 August 2020, 09:34:48 BST, Paul B Mahol <onemda at gmail.com> wrote:
> http://git.videolan.org/?p=ffmpeg.git;a=history;f=libavcodec/proresdata.h;hb=HEAD
> http://git.videolan.org/?p=ffmpeg.git;a=history;f=libavcodec/proresdata.c;hb=HEAD
> http://git.videolan.org/?p=ffmpeg.git;a=history;f=libavcodec/proresdec.h;hb=HEAD
> http://git.videolan.org/?p=ffmpeg.git;a=history;f=libavcodec/proresdsp.h;hb=HEAD
> http://git.videolan.org/?p=ffmpeg.git;a=history;f=libavcodec/proresdsp.c;hb=HEAD
> http://git.videolan.org/?p=ffmpeg.git;a=history;f=libavcodec/proresdec2.c;hb=HEAD
> http://git.videolan.org/?p=ffmpeg.git;a=history;f=libavcodec/proresenc_anatoliy.c;hb=HEAD
> http://git.videolan.org/?p=ffmpeg.git;a=history;f=libavcodec/proresenc_kostya.c;hb=HEAD
Do any of those things actually have effects that are likely to affect users? I don't think there is any way to tell without being an expert on the low-level implementation.
If they do, that should be written up in a public-facing manner so that it can be understood by users.
This is not public-facing documentation; these are internal notes for developers. Users cannot be expected to comprehend the real-world results of "infer array length," for instance.
(Well, you can expect people to understand it, but you will be disappointed.)

More information about the ffmpeg-user mailing list