View Issue Details

IDProjectCategoryView StatusLast Update
0003066DCP-o-maticBugspublic2025-08-13 22:15
ReporterEarring2392 Assigned Tocarl  
PriorityurgentSeveritymajorReproducibilityalways
Status resolvedResolutionfixed 
PlatformLinuxOSRocky 9OS Version9.8
Product Version2.18.19 
Target Version2.18.22 
Summary0003066: Setting Color=None still applies a conversion
Description

Likely related to this thread https://dcpomatic.com/forum/viewtopic.php?t=2735 and this changelog in "Fix incorrect colours with ‘no colourspace conversion’ sources in some cases. "

DoM will apply a colour space conversion despite being told to bypass.

In the link below you will find several files that demonstrate the issue and to reproduce my test and confirm I do not have any methodology errors:

https://cloud.hunter.camera/s/EnttKKpoo8Lqy6J

  1. CountDown_24fps_2k_scope_ProRes444_Rec709.mov
    • A rec709 G2.4 ProRes444 Mov file
  2. CountDown_24fps_2k_scope_ProRes444_DCI-X'Y'Z'.mov
    • A DCI X'Y'Z' ProRes 444 mov file created in Davinci Resolve
  3. A DPX 12 bit sequence
    • A DCI X'Y'Z' DPX image sequence created in Davinci Resolve
  4. CountDown_24fps_2k_scope_H264_DCI-X'Y'Z'.mov
    • A DCI X'Y'Z' H264 mov file created in Davinci Resolve
  5. The DoM Project and resulting DCP that show:
    i. The settings used to create the test DCP
    ii. That the Rec709 file and the DCI X'Y'Z' files display as expected
    iii. When the rendered DCP is played back in DoM Player, the Rec709 source file is converted to and from DCI X'Y'Z' and displays as expected.
    iiii. The DCI X'Y'Z' source files in multiple formats are not passed through unchanged. If Colour = None was passing the files through unchanged, the Rec907 and DCI X'Y'Z' should look the same.
  6. The Davinci Resolve 20 project file used to create the DCI X'Y'Z' samples.
Tagsgit
Branch
Estimated weeks required
Estimated work requiredUndecided

Activities

Earring2392

2025-07-17 12:36

reporter   ~0007054

I propose the following:

  1. The “Colour” menu be relabelled “Source Colourspace” to better reflect what the menu options are doing.
  2. The None menu option be replaced by a “ DCI X’Y’Z’ ” option that is a complete bypass of any colour transform for any input regardless of how FFmpeg reports the pixel format.
  3. The ‘Level’ menu is unchanged as that refers to how the values are encoded in the container codec and is format specific. DoM should take hints from FFmepg but allow the user to override.

carl

2025-07-22 00:11

administrator   ~0007055

I see what you mean - I tried to fix a similar case of a YUV-tagged input undergoing conversion, but I think that broke your case.

Your UI suggestions also sound good.

carl

2025-08-13 22:15

administrator   ~0007063

Incorrect colours in 98a8023dd774fd82c144a68039e0ea3131fb9142, UI suggestions in the next two commits.

Issue History

Date Modified Username Field Change
2025-07-16 19:59 Earring2392 New Issue
2025-07-16 21:07 carl Assigned To => carl
2025-07-16 21:07 carl Status new => acknowledged
2025-07-16 21:07 carl Tag Attached: git
2025-07-17 12:36 Earring2392 Note Added: 0007054
2025-07-22 00:11 carl Note Added: 0007055
2025-07-22 00:11 carl Status acknowledged => confirmed
2025-07-22 00:12 carl Target Version => 2.18.22
2025-07-22 00:12 carl Estimated work required => Undecided
2025-08-13 22:15 carl Note Added: 0007063
2025-08-13 22:15 carl Status confirmed => resolved
2025-08-13 22:15 carl Resolution open => fixed