ProRes Export on Windows systems

Can we please get the QuickTime ProRes codec as an export codec on windows systems.

I would be willing to pay a subscription fee or a one time fee to unlock this capability.

I'm already paying $70 a month to adobe so I can convert my DNxHR files to ProRes for client deliverables.

And yes I know about other ProRes converters for windows and they all suck.
They do not pass a professional QC.

Thanks
Josiah

I'd rather see ProRes in the MXF container, like Avid.

You can't because of Apple licensing (get bent apple).

export DNxHR or anther high qualify codec, and then transcode to prores with ffmpeg.

You can't because of Apple licensing (get bent apple).

export DNxHR or anther high qualify codec, and then transcode to prores with ffmpeg.

Well for the Apple licensing that is not actually true.
Adobe, Avid, Redcine X, Insta360, ext all let you encode Quicktime ProRes on Windows systems.

I'm currently exporting DNxHR then using Adobe media encoder to transcode for delivery specs.

My Problem is I do not want to spend the extra time going to another program.

and ffmpeg is not good. Media encode quality is best out of all the programs I've tried.
I've even tried a Linux render server with ffmpeg as my watch folder and the quality just wasn't the same.

And yes I know about other ProRes converters for windows and they all suck.
They do not pass a professional QC.

You can use the free Voukoder plugin for Resolve Studio to export ProRes (it is using ffmpeg).
When you say they do not pass professional QC - which error messages do you get?
To my knowledge those QC errors are all about wrong metadata...

Andrew Kolakowski here on the forum (who has a very deep knowledge about this) has said that you need this:

For ProRes you want to add extra bits to ffmpeg command ( I assume you're adding color space, etc. already), so it looks more like Apple encode:

-metadata:s "encoder=Apple ProRes 422" -c:v prorers_ks -vendor apl0 -bitexact -movflags write_colr

These should be correct encoder names:

Apple ProRes 422 Proxy
Apple ProRes 422 LT
Apple ProRes 422
Apple ProRes 422 HQ
Apple ProRes 4444
Apple ProRes 4444 XQ

for interlaced encoding (this will properly set ProRes private frame header as well) also add:

-vf "setfield=1, fieldorder=tff/bff" " -flags "ildct+ilme"

prores_ks is much slower but keeps bitrate in better control (still not perfectly as Apple encoder and affects quality a bit).

prores encoder is much faster, but it doesn't really restrict bitrate in the same way as Apple encoder. It will be most likely around 10-20% higher than Apple reference (but also quality is closer to Apple).

When it comes to PAL/NTSC aspect ratio just pass -aspect 16:9/4:3 and ffmpeg does set it properly by default based on frame size.

When you get timecode working then:

-timecode 10:00:00:00 -metadata:s reel_name=ABCD123

Source

Also, you can render to DNx, and transcode the file to ProRes (or QT animation if you need an alpha) using a Shutter Encoder for free.

You can't because of Apple licensing (get bent apple). export DNxHR or anther high qualify codec, and then transcode to prores with ffmpeg.

I think there are political problems between Apple and BMD, but I don't know the root cause or how/if it can be changed. I'm puzzled as to how Adobe Premiere for Windows (which has many times the user base of Resolve) can render to ProRes, but not Resolve for Windows.

I think if it were only a question of money, it would have been solved a long time ago.