[FFmpeg-trac] #2690(avcodec:open): Red Cinema r3d files not supported

FFmpeg trac at avcodec.org
Sat Nov 2 23:23:09 CET 2013

#2690: Red Cinema r3d files not supported
             Reporter:  MilosL       |                    Owner:
                 Type:  enhancement  |                   Status:  open
             Priority:  wish         |                Component:  avcodec
              Version:  git-master   |               Resolution:
             Keywords:  r3d j2k      |               Blocked By:
             Blocking:               |  Reproduced by developer:  1
Analyzed by developer:  0            |
Changes (by spookybathtub):

 * cc: elliottbalsley@… (added)


 I'm not sure which would be simpler.  I don't know how to code any of this
 myself, but I am very grateful for all the work done by the ffmpeg
 developers so far.
 I do know that the SDK provides a huge amount of options for how to
 process R3D raw files, and many of these options are essential when
 dealing with RAW — for example you have to set the ISO, white balance,
 etc. before converting to a linear color space.  It seems like it would be
 rather difficult to recreate all these settings.
 I've read that about 3 years ago, RED started using some kind of
 encryption in the files.  See http://ffmpeg.org/pipermail/ffmpeg-

 As an alternative, RED provides a free command line conversion tool called
 REDline, but I can't figure out any way to pipe its output to ffmpeg.  If
 anyone else wants to try, you can get it here:
 If that can be made to work, then there is hardly any reason to develop
 native R3D support in ffmpeg.

 I agree it would not be practical to distribute crippled ffmpeg binaries,
 but is it possible to make some kind of "binary plugin" that doesn't
 reveal the source code, but can be used when compiling ffmpeg?

Ticket URL: <https://ffmpeg.org/trac/ffmpeg/ticket/2690#comment:15>
FFmpeg <http://ffmpeg.org>
FFmpeg issue tracker

More information about the FFmpeg-trac mailing list