[FFmpeg-user] Private Options for prores-ks

[Kevin Wells]

----------------------------------------
> Date: Tue, 2 Jun 2015 15:38:06 +0200
> From: barsnick at gmx.net
> To: ffmpeg-user at ffmpeg.org
> Subject: Re: [FFmpeg-user] Private Options for prores-ks
>
> On Fri, May 22, 2015 at 14:53:52 +0000, Kevin Wells wrote:
>
>> I am using this option but when opening the output file up in
>> Quicktime 10 (Yosemite), the file shows the format as Lavc56.39.101
>> prores_ks instead of Apple Prores 422 HQ. Is there anyway to change
>> this so in Quicktime 10 (Yosemite), it displays Apple Prores 422 HQ.
>> Openig the file in Quicktime 7 Pro correctly displays the format
>> as Apple Prores 422 HQ.
>
> Well, there's only so much we can do, not knowing exactly how Quicktime
> 7 Pro determines what to display. I neither have their sources, nor the
> actual program to experiment.
>
> There's probably some way to check whether ffmpeg is doing what is it
> saying, e.g. by using AtomicParsley to check the MOV atoms.
>
> I have a different idea though: Assuming ffmpeg does the right thing
> (as in the doc you quoted), or that it's not relevant, could it rather
> be that:
>
>> Output #0, mov, to 'out.mov':
>> Metadata:
>> major_brand : qt
>> minor_version : 537199360
>> compatible_brands: qt
>> encoder : Lavf56.33.101
>> Stream #0:0(eng), 0, 1/11988: Video: prores (prores_ks) (apch / 0x68637061), yuv422p10le, 1920x1080 [SAR 1:1 DAR 16:9], q=2-31, 200 kb/s, 23.98 fps, 11988 tbn, 23.98 tbc (default)
>> Metadata:
>> creation_time : 2015-05-22 11:00:20
>> handler_name : Apple Alias Data Handler
>> timecode : 00:57:50:00
>> encoder : Lavc56.39.101 prores_ks
>
> Quicktime 7 Pro may be displaying the "encoder" metadata field of the
> stream? That's exactly what you seem to be seeing, and that's where
> your input file has the "Apple ProRes 422 HQ" you desire.
>
> If so, you can modify the stream metadata (or "kick" the default) by
> adding this to your conversion:
> -metadata:s encoder="Apple ProRes 422 HQ"
> "Works for me(TM)"
>
> Why do you want to lie, anyway? ;-)
>
> Good luck,
> Moritz
> _______________________________________________
> ffmpeg-user mailing list
> ffmpeg-user at ffmpeg.org
> http://ffmpeg.org/mailman/listinfo/ffmpeg-user

Hi Moritz, your fix worked a treat, perfect now in all applications. Many thanks for this.

Cheers.