Orash Rahnema

Hi. I have an upcoming project shot on the new arri 35. 

Is there an update for revengrade, otherwise whats the suggested workflow. 

I was thinking Simply to Color transfor from logc4 to logc3  and correspondant colorspace but that kinda defeat the arri 35 pourpose i think. 

Otherwise go to aces. 

I wanted the revengrade option available. 

What do you think?

I'm playing around with Ravengrade and it's working great generally.
Not sure about all the looks, I will have to explore them a lot more and understand when and how to use it at their best since lots of them are quite particular.

I have a question/suggest tho:

would it be possible to bypass completely the look and only have access to the grading controls?
example input: Alexa/logc -> Ravengrade exposure/density/etc.etc -> output: Alexa/logC

I have tried by setting main and sub look to zero but there is still a look applied to it, only the log curve stays relatively untouched

cheers,

Orash

Morning all,

where i am currently working on a project I will have to deliver (and they only accept) prores 422HQ for an HDR10 delivery (rec2020 - P3D65 limited)

I am working on a windows machine in resolve and I can't export prores as you know.

I don't have access to transkoder or anything similiar and I have been proposed to export a dnxHR 444 and then transcode it to prores via adobe media encoder

Since I have never done an hdr transcode in media encoder i have no idea if that could create a problem or not (clipping, colourspace shifts or anything)

Anyone had to go via this route and can tell me if i can trust the workflow, can you suggest anything else in case?

cheers,

Orash

group all the clips you want to be effected and leave that single clip out it it.

Then paste your timline grade to the post group level

Blanking only works on output

in edit or input sizing you have to crop

@Christian Berg-Nielsen ACEScc and cct are the same, where the only difference is that cct has a "toe", so the blacks are a little lifted with a very small "soft clip" 

this has been done because any other flavour of ACES otherwise tend to keep whatever is at 0 level untouched giving a sticky feeling in the blacks that most of the time are a pain to deal with

So most of the user that don't have access different drt gravitates toward ACEScct but it's not mandatory, using ACEScc ensure you that whatever is at 0 stays at 0, so if ones  grading stile has always pure blacks then this might help as one will end up pushing  the whole signal to accomodate those sticky blacks that i was mentioning before

Edit: hdr will look super constrasty but you can do a "contrast" node right befor the ofx nod and fix the curve to have a similar feel, gamma 2.4 it's a lot more steep compare to pq

Hi Glen!

I will assume you will have to grade hdr10 and not dolbyvision as would be a different

Since your lut is placed at the end I will try by replacing the lut with the color space transform ofx setting the output to rec709 and gamma 2.4

For the SDR version i will then chose the tonemapping option in the node for both luminance and saturation, in that way you should have the same result of the lut.

For the HDR version i will leave off the tonemapping option so the ofx will not softclip

I would honestly not tring to convert the gamma to pq or have a bigger colourspace as i you will probably have to redo a good chunk of your grade

living the gamma and the colourspace like the 709 but without clipping then you can go back to your nodes and do a very slight trim pass to push a bit more the hdr version and still both version should be similiar.

Let me know if this works for you

cheers,

Orash

Hi Glen
did you place your lut at the end of the pipe or somewhere in the middle or at the begging?

that is pretty cryptic I would say.

anything that is possibile to know before the 10th?

as per ruler you mena something that can draw a straight line horizontally and vertically and can be arbitrary moved 

or do you need also measurement in pixel or centimeters, like photoshop?
 

for the first one with a bit of time I can try to write a dctl since I was kind of tackling something like this already to excercise, I don't know when will be ready tho

if you need the second one, then no, i can't do it

22 hours ago, Thomas Singh said:

It behaves totally different when you drag the line down, try for yourself. 

Can it be that hue vs Sat works on HSL or some different colour space rhater then the rgb colour space that Sat use.

I belive Sat control works in RGB using 709 primaries, not sure about curves, the same nature of them makes me believe they are in hsl.

But then again i might be wrong

would be interesting to check

Here there is a very interesting tweet about the apple xdr display from Juan Salvo

Hi David

there are few things that should be known before giving a proper answer.

the only thing contaminated are the black bars or does the image looks more contrasty on your display?

a quick things that come in mind is, when the image are desqueeze, the black bars you see are black to start with, but if you really push the level you see that behave like they are part of the image, so if you "pollute" the black with a color cast or the blacks are lifted also the bars will be

The solution would be to blank the frame using output sizing or timeline blanking

that if there are not other problems that I can't see with the info we have.

Last year I have done a 15 min long short movie, shot on a single long take at sunset hour where the 4 subjects kept going in and out a house, so lots of exteriors and interiors with a massive light change.

The DP i have worked with had done a great job "shutter pulling" and that helps a great deal.

First thing I have studied how the light was changing and I found a  "master shot", then I have found all the places where I could hide the dynamics  and balance the whole thing with very simple correction, mostly offset and contrast working with the light changing and not going against it.

I have used the layer mixer and create stream for each change I needed

Then I have worked on the "look" and placed it within the single streams, to use the dynamics I have done before

I have done a general correction after everything also.

After all this I have worked with masks and stuff.

The key is to keep it as simple as you can, things can become messy quite quick.

try to brake it into smaller problems and think it like a multi shot video, that rather to have cuts have  dynamics.

Choose if you want a massive node tree with a layer mixer like a did or to brake the cut in editing using cross dissolve. I don't like that approach as I rather move keyframes that to jump within cuts and fix dissolves.

I hope I was clear enough

no really really sure what you are asking, but using a lut in aces is not a straight forward thing to do and generally not a good idea.

you can try to make it work using lightspace but still it's a workaround that introduce many unpredictable factor and can give you nasty artefacts.

Most of all if you want to go from an sdr odt to an hdr

The lut will clip at 100 nits anyway so it's not going to work

To go from an sdr to hdr there are not workaround (not like a trim dolby vision trim that take you from hdr to sdr)

The only safe way is to grade it for hdr starting from what you already have, after the lut.

in that way you can extend the contrast letting only the very highlight to go above 100nits and keeping most of the signal at a 100 nits where already belong. Also you will have more room to give shadow details, which is really nice.

Red can read cube, as far as I remember, Alexa can't. 

For the Alexa, depending on the model you have to use, on the Alexa xt you can only use a 1d lut and matrix and if I can recall the format is. Xml. 

On Alexa mini, Amira, lf and basically all the arri camera after the Amira you can use a 3d lut and the format is. Aml

I never had problem with a 33*33 lut but since you have to convert your cube lut into an aml you better reduce it to 17*17

I use lattice to convert the cube into the aml. 

I haven't had the chance to look into it

But as a work around you can use the @Paul Dore aces ofx

you can basically build your aces pipeline as a node structure keeping resolve color science in yrgb

that way you should not have any problem with video monitor output lut

Hi Michael

if the lut is placed in the "3d video monitor output" should not give you any problems as it "should" work post ODT.
I might be wrong here tho, maybe its not post odt even if sounds very strange.

To make a 3d lut working in aces your best bet would be to use lightspace, @Steve Shaw can really help you out here.

Check https://www.lightillusion.com/aces_manual.html under "CONVERTING LUTS INTO ACES" section.
 

Lastly, the monitor calibration does have not to be different if you work in aces or unmanaged, since your monitor will still be a 709 monitor.

In aces by choosing the ODT you transform from the aces color space to the choosen one (709 for example) and you have to monitor on the same colorspace you choose with the odt

I hope it make sense

cheers,

Orash

Hi Michael

the problem is where you are placing your lut, most likely

in aces a "normal" lut cannot be used within the node tree, you either convert it to an aces lut, which is not as simple as it said,

Otherwise  since it is a monitor calibration lut I would suggest it to load it to the "3d video monitor output" in the color managment tab (that should come after the odt, so should not create problems) or straight into the monitor.

hope that helps you

Orash

Hi all! 

I'm planning to buy a mini panel and currently bm is giving (in Italy) a 10% discount. 

It's not a lot, but still isn't bad.

Anyway, are there any rumors of a new panel announced after nab? 

Cheers 

Orash

Hi all! 

It's now a couple of months that I have set up my windows workstation. 

So far everything it's fine, in still getting used to few things but it's running smooth. 

I'm finding few bugs here and there and I wanted to check was my problem or it's a common issue. 

For example :

In the deliver page, choosing a render folder, when i right click in the explorer/finder window to create a new folder, DaVinci crashes. 

Once reopened it doesnt happen no more. 

Anyone else has this problem? 

Cheers

Orash

Hi!

I have just tested my new pc with a gtx 1080Ti and trying to export a red clip 8K with a noise reduce I got two errors:

 "The GPU failed to perform image processing because of an error" "Error Code: 33."

 "The GPU failed to perform image processing because of an error" "Error Code: 77."

I'm using Resolve 15.2.2.007

If I disable in the preferences "use GPU for RED debayer" I don't get the errors but of course it slows down quite a lot

Did anyone found a solution for it?

cheers,

Orash

Also, if you don't check Luma and sat mapping but you trim by hand, there is not clipping after the transform

I'm not really a "happy new year" guy but I wanted to take this chache to thank the people behind this forum and the users involved. 

I have to say lowepost has become a great resource of information and I'm thankful of the help, tips and tricks and info I found here.

So I wish to this forum and the users a great new year, full of nice info, tutorial and insights.