[FFmpeg-user] How to set 3 specific metadata flags (ITU601/displayoffset) in FFmpegs IMX50 MXF-OP1a encoding?
nichot20 at yahoo.com
Thu Mar 19 11:07:39 CET 2015
On 18/03/15 09:46, Christoph Gerstbauer wrote:
> I am testing with ffmpeg the IMX50 D10 encoding, and I am very close to
> my target but I have to create 3 metadata values in the MXF header which
> is standard in most IMX50 MXF ecndodings:
> + SIGNAL STANDARD = 1 (ITU 601)
> + display y offset = 32 - I am encoding 720x608 sources with included
> VBI area (32 lines high at the top) -> the offset 32 defines the active
> picture -> 720x576
> + Color siting = 4 (Rec 601)
> Is it possible to encoded with ffmpeg in a way that these values can be
> If yes, which syntax should I add to my used syntax?
> If no, could the option be implemented in future?
> My used ffmpeg syntax is:
> ffmpeg -i <inputfile> -map 0:v -map 0:a -c:v mpeg2video -r 25 -pix_fmt
> yuv422p -aspect 4:3 -minrate 50000k -maxrate 50000k -b:v 50000k -intra
> -flags +ildct+ilme+low_delay -intra_vlc 1 -non_linear_quant 1 -ps 1
> -qmin 1 -qmax 3 -top 1 -dc 10 -bufsize 2000000 -rc_init_occupancy
> 2000000 -rc_buf_aggressivity 0.25 -tag:v mx5p -c:a pcm_s24le -ar 48000
> -f mxf_d10 <outpufile.mxf>
Don't know if its relevant but your coding parameters are slightly
different to the one's I use for D10, and I wonder if this affects the
automatic metadata insertion..
Well ilme seems kind of redundant for I frame only coding but probably
irrelevant for mxf, but again probably harmless.
I use the following which you do not:-
and you use the following that I do not:-
"-qmax 3 -rc_buf_aggressivity 0.25"
I don't know what difference, if any, those changes make, but the values
I use create D10 files that BBC R&D looked at and thought were OK.
Perhaps worth a try?
Key Fingerprint 38CF DB09 3ED0 F607 8B67 6CED 0C0B FC44 8B0B FC83
More information about the ffmpeg-user