[Matt Stoltz] “where do you check all that at ?? “
Resolve allows you to pick between the two ranges (although the default is “Auto”) both incoming and outgoing– but I have noted that some NLEs don’t scrutinize the incoming media necessarily, and sometimes it will assume that what went out is how its coming back in, which isn’t always true. You could be editing an RGB codec in Premiere (or whatever) and one would think it would be fine to render in DNx or ProRes to come back, but the NLE might assign RGB ranging incorrectly to the now linearized media, since that is how the sequence was set up in the first place. Ive seen this both in Media Composer and Premiere, and FCP7 used to do it as well.
If you have a waveform/vectorscope available, either outboard or within the editor, the first telltale symptom is either clipped/crushed blacks or floating up around 10 IRE…
This isn’t always fixable on the return trip. Some NLEs allow a range re-assignment, but not all, and the latter forces a re-render in Resolve picking the “other” option.
jPo, CSI
“I always pass on free advice — its never of any use to me” Oscar Wilde.