View Bug Details

IDProjectCategoryView StatusLast Update
0001103DCP-o-maticFeaturespublic2021-10-07 23:01
Reportercarl Assigned To 
Status acknowledgedResolutionopen 
Summary0001103: Export options

Output image size, frame rate (including interlaced).

Estimated weeks required
Estimated work requiredUnknown


related to 0001146 closedcarl Export multiple reels to separate files 
related to 0001075 closedcarl Stereo mixdown option in export 
related to 0001331 new Option to create custom export templates 
related to 0001332 closedcarl Export 3D DCPS to separate L/R files 



2017-08-21 01:11

administrator   ~0001773

What does "framerate" mean here? An arbitrary export framerate different from what the DCP was specified as?


2017-08-21 12:36

manager   ~0001774

Just my opinion - the export function is a functional side track in DOM. Adding every imaginable option to the export means much work. I think it is completely okay if DOM offers only two options - a 'low quality' (screener), and a high quality (re-use), plus optional audio mixdown. Everything else can be created by other tools with a more dedicated feature set (e.g. handbrake).

  • Carsten


2017-08-23 21:43

reporter   ~0001775

100% w/Carsten,
we could even abandon the .mov conversion (which btw still doesn’t work on MacOs 10.12.5 & 2.11.19)
in favor of mp4 (which works, including soft-subtitles size and position), and is half as heavy for about the same image
quality. Remember that the main purpose of the DCP to MP4 conversion is to let people perform
fast-forward film previews.


2017-08-24 12:33

manager   ~0001776

I think it is necessary to have a high quality 'reuse' export option, which the MOV option using ProRes is currently targeting. Some people would say uncompressed/lossless image series would be more appropriate.

I noticed that the MP4 export creates unusually high bit rates, some of my lighter machines can not play without frame losses. I guess it makes sense to lower the bitrate for MP4 (or, sigh, make it selectable (low/mid/high), thus making a higher quality ProRes more useful for those who need it.

  • Carsten


2017-08-25 09:56

reporter   ~0001780

Everything else can be created by other tools with a more dedicated feature set (e.g. handbrake).

Hi Carsten, don’t bet on Handbrake for DCP to MP4 conversion. Last year I tried (and failed) to convince its stubborn developer team.
Being stuck to Libav*, they are still unable to convert XYZ to rgb/yuv color space, something that FFmpeg offered to DoM
and the world for years.

  • weird result of the 2011 FFmpeg internal war and split.


2017-08-25 10:31

manager   ~0001782

I don't count on handbrake to convert from DCP, but to all the other formats mentioned above FROM the exports DOMs creates, so, either from MP4 or Prores.

  • Carsten

2018-10-23 12:26

reporter   ~0002733

I think also the option -preset needs to be able to be selected. When I used CRF 17, I got a 100 GB file, which I was able to convert to about 12GB without any perceptible loss in quality.

In the future, exporting to HEVC (x265) might become useful, though it is fairly slow on my computer.

Also, what are the settings for audio? VBR or CBR? What encoder DOM uses, libfdk_aac or aac?

2021-08-02 16:00

reporter   ~0004490

BTW: is not seeting the image size equivalent to this: (there fore that one would be duplicate of this one).

I would add to this, after almost three years, that export would deserve a bit of imrovement. As discussed here, it is quite slow:
and it produces big files. I am not sure what options are used internally for the Prores and MP4 options. When Carsten speaks above about screeners, I think this option is now missing as both mp4 and Prores seem to be more for reuse case.

A screener option would produce a smaller file faster.

Moreover, the naming of the options is confusing - ProRes is a codec (exported to MOV?) and MP4 is a container - I presume the codec used is x264?

I would not care if the default options are tweaked internally to produce a smaller and faster encode, but another way to speed things up would be to use hardware acceleration for this. In my case, I have an NVidia card that could do this via h264_nvenc. An option that would work for me would be being abel to set a custom ffmpeg codec (video, above all) specification. Something like this in my case: "-c:v h264_nvenc -b:v 0 -rc vbr_hq -cq 19 -preset slow -profile:v main". Or "-c:v libx264 -preset slow -crf 16".

2021-08-12 13:41

reporter   ~0004499

I opened two bugs about the name of the codecs here: suer
and a suggestion to improve documentation here:

Not sure if I shold open a new bug for the custom ffmpeg commands? I think it could be something set in the preferences. If DOM is run from the console, I guess any erros from ffmpeg would get caught.

Bug History

Date Modified Username Field Change
2017-07-24 10:33 carl New Bug
2017-07-24 15:49 carl Relationship added related to 0001075
2017-08-15 23:11 carl Target Version => 2.12.0
2017-08-21 01:10 carl Status new => acknowledged
2017-08-21 01:10 carl Target Version 2.12.0 => 2.14.0
2017-08-21 01:11 carl Note Added: 0001773
2017-08-21 12:36 Carsten Note Added: 0001774
2017-08-23 21:43 Cantar4 Note Added: 0001775
2017-08-24 12:33 Carsten Note Added: 0001776
2017-08-25 09:56 Cantar4 Note Added: 0001780
2017-08-25 10:31 Carsten Note Added: 0001782
2018-06-10 00:41 carl Relationship added related to 0001146
2018-06-28 23:53 carl Relationship added related to 0001331
2018-06-28 23:53 carl Relationship added related to 0001332
2018-10-23 12:26 Note Added: 0002733
2019-01-08 23:55 carl Target Version 2.14.0 =>
2021-08-02 16:00 Note Added: 0004490
2021-08-12 13:41 Note Added: 0004499
2021-10-07 23:01 carl Tag Attached: export