Hey Lucien
Agreed - theres something weird done to the plates that I’m unable to solve my
end.
I can reverse out everything neatly the way i have it - but its messy and i
don’t want to cause problems down the road -
I’ve settled to just using the standard colorspace node: in set to
Hey Neil,
the result you get from this srgb -> arri wide gamut are not surprising but I
dont think they are appropriate in your case.
If you are converting this plate with negative values from srgb to arri wide,
you are essentially saying that the code value of your image which are negative
Hi Kevin
Thanks for help
ok so random frame on one of the pics…
looking through OCIO node converting ARRI V3 LogC(EI800):
log values 74 61 87 across rgb in lowest value…..
and weirdly in superb rights - 0 0 1023 in highest value ……!
-
changing primaries from sRGB to AlexaV3LogC
On 31 October 2016 at 09:10, Neil Scholes wrote:
> 1/ changing primaries from sRGB to AlexaV3LogC - get rid of a ton of
> negatives ( values lower than -1)
> I’m taking a guess here ( shares the same primaries as rec709)
> white point still D65
This certainly sounds
Hi Guys
Thanks very much for the input - very interesting
The plates are 10it DPX
I’m clicking RAW on the read node - so not changing any color
then :
1/ changing primaries from sRGB to AlexaV3LogC - get rid of a ton of negatives
( values lower than -1)
I’m taking a guess here ( shares the
What file format are the raw plates? Quicktime or Arriraw? How did you
try to convert direct from Arri to ACEScg? IE which colorspaces did you use?
On Sun, Oct 30, 2016 at 7:24 AM, Neil Scholes wrote:
> Ok - so thanks for the tips - and the solution
>
> I’ve now got RAW
Ok - so thanks for the tips - and the solution
I’ve now got RAW plates first going through a regular colorspace node - just
changing primaries from sRGB to AlexaV3LogC
Next an add to eliminate the tiniest negatives….
A final OCIO colorspace node going from ARRI V3 LogC (EI800) wide gamut - to
Thanks for that I'll check it out. That might be a solution.
Strange though as the whole point of the IDT is to bring the footage into ACES
without needing to offset etc.
Yesterday I was also made aware that the plate may have peculiar primaries so
I've got a few ideas now to try out
Thanks
Hey Neil,
I had a similar problem than you on a show shot in Arri wide gamut.
The first thing to notice is that Arri Wide gamut have very different primaries
than Aces CG.
In other words, some colors in Arri Wide gamut correspond to negative
chromacities in Aces CG gamut.
Besides this, the
hmmm - weird - ill have a look again with that in mind
cheers
Yeah its amazing to me how plates can get so messed around - worked on a job
recently where everything was super underexposed and grainy to hell because of
it.
Half the job was spent making the picture half decent
weird.
N
I hate to even suggest it but could they have recorded Rec709 instead of LogC?
Or perhaps someone rendered LogC to Rec709 between when it was shot and when it
got to you. Either way, awkward.
Sent from my iPhone
On Oct 28, 2016, at 13:41, Neil Scholes
thanks really appreciate it
I can’t send a pic unfortunately - just signed the NDA etc etc…..
thanks for the snippet - yes they have exactly the same effect - negative
numbers in super brights
interestingly when i change the incoming primary to sRGB rather than
AlexaV3LogC - i get rid of
Here's a little script to compare the default Nuke colorspace result and
the OCIO config result. Looks pretty similar...
HP
set cut_paste_input [stack 0]
version 10.0 v1
Constant {
inputs 0
channels rgb
format "1024 1024 0 0 1024 1024 1 square_1K"
name Constant1
selected true
xpos 1519
Hey yes I do have raw checked…. double checked……
crazy negative values
weird one
I’m having to resort to standard nuke and use the basic colorspace node to
convert from Arri LogC - shame really as i’d prefer ACES.
I think its either a bug or the plate.
Neil Rögnvaldr Scholes
Director |
Hey,
Do you have 'raw data' checked on the read node? If you don't, Nuke apply
it's own linearization when the data is read in, at which point the data
flowing through the graph is no longer LogC encoded.
Not checking that box could lead to problems like you're describing.
HP
On Friday,
Hi
So I’m looking at supposed ARRI LogC footage - dpx's
In ACES (1.0.1) converting from ARRI V3 LogC (EI800) Wide Gamut to ACEScg gives
me horrible negative values …..big ones
So I’m wondering - is there a bug with ARRI V3 LogC and ACES currently?, or
is it likely that the plate is not
16 matches
Mail list logo