10 years ago Redcode footage was supported by FFmpeg, but RED have since encrypted their format to disallow open-source tools from decoding it. Red support makes a lot of sense since the files are computational intensive to decode and there's still no easy way of creating Resolve-internal proxies on a per-timeline basis.
Possible Implementations
There is a Redcode SDK, but it's all written in C++. To comply with legal obligations, the plugin would have to be compiled into a binary file. Even then, changes to the codec will require updated code.
An easier solution would be to use the command line tool developed by RED called "RedLine". It's primarily designed to convert Redcode files into image sequences (which would be terrible for slower network filesystems), but it does support Apple ProRes as an export codec. There are a couple of issues with this:
I cannot distribute this code. End user will have to download themselves.
It would not support chunked encoding since that's done with FFmpeg
Feature Proposal
10 years ago Redcode footage was supported by FFmpeg, but RED have since encrypted their format to disallow open-source tools from decoding it. Red support makes a lot of sense since the files are computational intensive to decode and there's still no easy way of creating Resolve-internal proxies on a per-timeline basis.
Possible Implementations
There is a Redcode SDK, but it's all written in C++. To comply with legal obligations, the plugin would have to be compiled into a binary file. Even then, changes to the codec will require updated code.
An easier solution would be to use the command line tool developed by RED called "RedLine". It's primarily designed to convert Redcode files into image sequences (which would be terrible for slower network filesystems), but it does support Apple ProRes as an export codec. There are a couple of issues with this: