Blender can read Apple ProRes video files.
Is there any way to write to that format?
I use a video workflow with Final Cut Pro X and used Blender for some retouching and compositing and would like to send the clips back to FCP.
Blender Stack Exchange is a question and answer site for people who use Blender to create 3D graphics, animations, or games. It only takes a minute to sign up.
Sign up to join this communityIt is likely wiser to adopt an image based pipeline and assert that all of your color transforms and bit fidelity remain intact.
Using an image as an intermediate will be vastly more effective. The granularity required to handle the color primaries, bit depth, and transfer curve out of a codec correctly is not currently possible within Blender nor many other mainstream applications, and will often result in incorrect output. Well documented issues such as Quicktime's perceptual noise addition, incorrect transfer curve / gamma, inconsistent vendor flag reading, etc. all make for the stuff of nightmare when dealing with codecs.
If you are careful, you can easily step to an intermediate image format and use the Baptiste Coudurier FFMBC project to encode and decode ProRes with much more control, quality, and accuracy.
While it is a fork of FFMPEG, FFMBC extends the needs of the encoding and decoding of ProRes and DNxHD to meet media broadcast needs.
Further links:
I am assuming since it's Apple based software, the format has some ties to QuickTime. The closest option you have is to export a video from Blender (excluding the default AVI formats) are
(formats that can be compiled into blender, not available on all systems)
HDR TIFF EXR MPEG AVICODEC QUICKTIME CINEON DPX
Also, Quicktime support isn't available on Windows or Linux, so these can't read image/video formats supported by Quicktime.
When outputting from blender you have a multitude of options with the FFMPEG libs. It's even been hinted that you can output prores 422 on linux with a patch to the correct library. However, blender is ill suited as an encoder in this respect, most specifically due to the "grey area" in legal issues pertaining to output formats like pro-res. That said, my workflow with blender to prores has followed this pattern in the past: blender output to images (tiff\tga) Folder of images to sequence in FCP or another editor, applying the sound etc, then out to pro-res
This workflow has proven faster at encoding the video, and has even produced higher quality with compressed formats like mp4 (with the same settings). The reason is simple enough. I farm the image rendering, so the time it takes to render the frames is cut down considerably (I have 5 old computers running blender farming in linux, varying distros, and varying power, but still core for core a better option). This produces a full format video similar to a celluloid reel of frames. Placing this into a sequence shows this as fully rendered, applying a sound track lines up perfect (especially when from the original video file). When doing this with source video for multi cam edits, I usually have to allow FCP to create the proxy for use in playback, and in adobe, render a preview. But when this is done from an edl, imported and farmed after the edits are marked, it takes longer to render the images, but shorter overall to then output a finished video from them, and with parallel encodings running, I can output several finished file formats for different types of delivery (everything from youtube and blu-ray to dvd). You are better off using a dedicated apple computer for the encoding of pro-res. Occaisionally, I've even just used compressor to put the two (audio and video) together, though not recently.