Doom9's Forum - View Single Post

kolak · 14th August 2017, 20:19

This info comes from private PorRes header and only way to fix it is to re-encode file with proper interlaced encoding using prores_ks.
It's only mediainfo which checks ProRes private headers. Don't know any other real world app which would do this, so any transcoding etc will use MOV headers.
You can also hex edit 1st ProRes frame, but this info will be in every frame (although mediainfo most likely checks just 1st frame?).
Mediainfo will give you position of 1st PorRes frame in advanced parsing mode.

Proper solution is to use correct ffmpeg command in 1st place.

update: editing ProRes private frame headers may cause "adjusted" frames to be decoded as black or green.

14th August 2017, 20:19	#6 \| Link
kolak Registered User Join Date: Nov 2004 Location: Poland Posts: 2,843	This info comes from private PorRes header and only way to fix it is to re-encode file with proper interlaced encoding using prores_ks. It's only mediainfo which checks ProRes private headers. Don't know any other real world app which would do this, so any transcoding etc will use MOV headers. You can also hex edit 1st ProRes frame, but this info will be in every frame (although mediainfo most likely checks just 1st frame?). Mediainfo will give you position of 1st PorRes frame in advanced parsing mode. Proper solution is to use correct ffmpeg command in 1st place. update: editing ProRes private frame headers may cause "adjusted" frames to be decoded as black or green. Last edited by kolak; 27th August 2017 at 01:21.