[FFmpeg-user] replacement of old encode/decode APIs with an N:M-based API - affect on FrameMD5 report values

[Henderson, Ian]

Hi,

Re: FFmpeg (5.0) since the "Lorentz"<https://ffmpeg.org/download.html#release_5.0> release...

Unfortunately I can't run any tests at the moment so perhaps you can advise.
The release information states that the old encode/decode APIs were replaced with an N:M-based API. Does this affect production of Frame MD5  - would FrameMD5s generated by releases from Lorentz onwards produce different values from older versions of FFMPEG when run against the same AV files?

Many thanks,
Ian Henderson


Please don't print this e-mail unless you really need to. ----------------------------------------------------------------------------------- National Archives Disclaimer This email and any files transmitted with it are intended solely for the use of the individual(s) to whom they are addressed. If you are not the intended recipient and have received this email in error, please notify the sender and delete the email. Opinions, conclusions and other information in this message and attachments that do not relate to the official business of The National Archives are neither given nor endorsed by it. ------------------------------------------------------------------------------------