Do not guess. Check in order.

Because the Rec.709 label does not describe the whole playback chain. Transfer/display assumptions, video/full range, metadata tags, OS colour management, monitor calibration and viewing environment all affect appearance. Compare the signal state and display path, not only the gamut name.

They share RGB primaries and a D65 white point, so their gamut geometry is the same. Transfer/display conventions and typical viewing contexts differ. An sRGB file is not automatically a correct Rec.709 master merely because the primaries match.

No. Rec.2020 defines wide-gamut primaries and part of the UHD signal framework. HDR commonly uses BT.2100 with Rec.2020 primaries plus PQ or HLG and an appropriate rendering/display context. Rec.2020 SDR is possible, and HDR requires more context than a gamut label.

Log is a scene-oriented encoding, not finished display rendering. If its code values are shown directly on an SDR monitor, contrast and saturation look low. Use the correct input interpretation and a viewing/output transform rather than an arbitrary contrast boost.

More levels improve precision, but there is no universal rule that 10 bits is sufficient. ARRI LogC4, for example, specifies a 12-bit minimum. Under identical encoding, 10 bits normally gives smaller steps than 8, yet noise, compression and missing detail remain. Repacking an 8-bit source into 10 bits does not recover lost precision.

It depends on the operation. Bit depth usually matters more for tonal gradients, log/HDR and aggressive grading; spatial chroma detail matters more for chroma keying, fine coloured text and compositing. 10-bit 4:2:0 and 8-bit 4:4:4 address different limits.

No. Y′CbCr is a way of representing nonlinear RGB through luma-like and colour-difference components. Primaries, transfer, matrix coefficients and range are still needed to recover colour meaning. A YCbCr label alone does not specify the gamut.

CST is useful when you want explicit local transforms in the node tree. RCM is convenient for Resolve-centric project-level management. ACES is useful as a standardised cross-application architecture. Choose based on the project pipeline rather than assuming one is always 'better'.

These are different levels of description. DWG is a working RGB basis; Intermediate is its common encoding partner. ACES is a broader system with several representations and output transforms. Compare configured workflows for interchange, tool behaviour and approved output, rather than declaring one universally nicer or more correct.

In a manual scene-referred chain, an Input CST usually normalises camera source into the working space before the main grade, while the Output CST/DRT follows scene-referred creative work. Display-specific trims may intentionally occur after the output transform. Know the state of each node rather than memorising a position as dogma.

A duplicated technical transform is a hypothesis, not a diagnosis from appearance. Project management, CSTs, LUTs or viewing settings may overlap. Wrong transfer or range can look similar. On a test copy, bypass one known stage at a time and compare the same frame rather than resetting the whole chain.

No. RAW describes a family of early camera representations and decoding controls; Log describes an encoding. RAW can involve nonlinear storage and partial processing, as BRAW does. A decoder can produce a log/gamut pair or another representation. RAW does not guarantee no compression, full reversibility or identical available controls.

First interpret each source pair correctly and bring the media into a common working state through managed input transforms or individual CSTs. Perform balance and matching after technical normalisation. Visually matching different camera encodings before normalisation is harder and less robust.

Finished graphics have defined encoding and visual intent. Treating them as camera scene data or rendering them again can alter appearance. Check their input profile, compositing position, output target and straight/premultiplied alpha. Assigning sRGB alone does not guarantee unchanged colour after every look or output transform.

PQ is an absolute display-luminance encoding commonly used for mastered/on-demand HDR. HLG is a relative broadcast-oriented system with a system gamma and suits some live/broadcast chains. The delivery specification should decide; one cannot be replaced by the other with a simple tag change.

203 cd/m² is a nominal HDR Reference White production anchor under the ITU conditions, not a universal ceiling. A neutral 75% HLG signal is about that luminance on a 1000 cd/m² reference display at system gamma 1.2 with the adopted black-level model. Do not assume the equality under different display conditions. Highlights and objects have their own creative purposes.

A display or player may map the image to its capabilities. Algorithm, settings, metadata and actual content affect the result; identical appearance across TVs is not guaranteed. Mastering-display peak and maximum content light are distinct. Validate the approved target and representative viewing paths rather than blindly changing a master for one screen.

No. 10,000 cd/m² is the mathematical design ceiling of ST 2084. A real master may use a 600-, 1000-, 4000-nit or other approved peak. PQ code values retain absolute luminance meaning within the system, but the mastering display need not reach the ceiling.

No. That only re-encodes or reinterprets the signal relationship and does not automatically create a new scene/display rendering. A proper HDR trim/master requires decisions about reference white, highlight allocation, colour volume, tone/gamut mapping and monitoring target.

The first suspect is a full/video range mismatch or incorrect data-level interpretation. Also check transfer assumptions and the player path. A range error changes code-value mapping to black/white and can look like washed or crushed blacks without any creative grade change.

Check the Y′CbCr matrix and primary interpretation, as well as the transfer and preceding processing. Test matrix errors on coloured samples: equal R′=G′=B′ can remain neutral under different NCL weights. Locate the first mismatch before trying to fix it with Hue or Saturation.

Different applications can use different colour-management/display paths, interpret tags differently and output through different OS APIs. Compare the master on a controlled reference path, then test consumer playback separately. A screenshot from one browser is not a reference measurement of the master signal.

Usually not: metadata describes how values should be interpreted, while a colour transform mathematically changes the values. A player can nevertheless display the same bytes differently after seeing different tags. Retagging and transforming/transcoding are different operations.

They answer different questions. Scopes measure the signal representation, while a calibrated monitor shows the perceptual/rendered result. Creative colour cannot be judged from a waveform alone, just as levels/tag mismatches should not be diagnosed only by eye on an unknown display.

No. Management and viewing transforms mathematically prepare a signal; the physical display must match the target within its capabilities. Calibration adjusts behaviour, profiling describes it, and measurement verifies it. Neither a profile nor RCM gives a panel arbitrary gamut or luminance.

Not necessarily. In wide-gamut floating-point scene-referred transforms, such values can be a valid intermediate state. The problem occurs when they are sent to a limited display output without appropriate gamut/tone mapping or clipping policy.