Project looks way different after upgrading to R17

Hello,

I had a database on R16. Upgraded to R17. Now a project that was already graded looks way different. I rendered it out - and luckily caught the difference. It contains this node with these curves: https://ibb.co/186QNHK

On my R16 grade everything was nice with a little blue. On Resolve 17 even the skin has blue patches.

Is this a known bug?

I've seen a couple other posts reporting this. I haven't seen the issue myself, though.

different, incompatible or missing plugins?

incompatible LUT?

different color science?

different, incompatible or missing plugins?

incompatible LUT?

different color science?

- no plugins used
- no LUT used
- same project settings.

It gets down either to curves or qualifiers, but now I had to rollback.
So be careful because on some projects it is super hard to notice the difference, I've only spotted it because one project was very blueish.

Here you can see a test... Same project, same grade, only difference is Resolve version.
On the left skin is OK, on the right blue patches appear.

I see the same blue in both versions, just more pronounced in 17. Like 16 had a reduced Opacity or something.

I see the same blue in both versions, just more pronounced in 17. Like 16 had a reduced Opacity or something.

it's still different as you can see on the vectorscope.

Resolve 16

vector_r16.jpg (99.39 KiB) Viewed 1119 times

Yeah, it's like 17 has more saturation, making those blues more pronounced.

Yeah, it's like 17 has more saturation, making those blues more pronounced.

yes. Which can be a pretty big problem, if you just want to open an older project and render out, expecting the same look.

- same project settings.

what are these settings? And are you using any Color Space Transforms in the grade? If so, which?

I would think this would be a huge problem for a professional post studio. Could you imagine the disaster if you upgraded to v17 and a client just wants to cut out a shot in a project graded in v16? You’d have to go through every shot and regrade them.

POST HOUSES BEWARE!

"Never upgrade your hardware or software during a project". I got this advice from an older editor. It was true during the tape to tape era as it is tiday.

"Never upgrade your hardware or software during a project". I got this advice from an older editor. It was true during the tape to tape era as it is tiday.

That’s right, but if a client wants one simple change on an old project after you’ve upgraded?

"Never upgrade your hardware or software during a project". I got this advice from an older editor. It was true during the tape to tape era as it is tiday.

That’s right, but if a client wants one simple change on an old project after you’ve upgraded?

Then the professional post house can just load or restore their old database, simple

Then the professional post house can just load or restore their old database, simple

I think it would be better to fix v17 so it is 100% backward compatible with v16 projects.

We have encountered situations where opacity and tracking in ResolveFX weren't coming through from 16 to 17. What's interesting is that I always grab a Gallery still from every shot as a final step after we deliver a project, and if I copy the grade over from the Gallery still, it seems to be fine. This may not work in your case, but it's a suggestion.

I tend to only use Custom Curves and secondaries, and so far those come through just fine for me.

"Never upgrade your hardware or software during a project". I got this advice from an older editor. It was true during the tape to tape era as it is tiday.

That’s right, but if a client wants one simple change on an old project after you’ve upgraded?

Then the professional post house can just load or restore their old database, simple

This doesn't solve the problem, as loading the old database/project will still have a different look. Only way would be to reinstall old davinci, restore old database, export. This is pretty bad for a post house to do every time they have to render out something from an old project.

We have encountered situations where opacity and tracking in ResolveFX weren't coming through from 16 to 17. What's interesting is that I always grab a Gallery still from every shot as a final step after we deliver a project, and if I copy the grade over from the Gallery still, it seems to be fine. This may not work in your case, but it's a suggestion.

I tend to only use Custom Curves and secondaries, and so far those come through just fine for me.

I think this could work, but checking every shot with stills is just very hit and miss. What if at that frame I don't see any problem, but the other parts of the shots are different.

Also the troublesome node uses curves and qualifier. So I'm more worried about what they changed that made these work differently.

[Rohit Singhal]

Hello,

I had a database on R16. Upgraded to R17. Now a project that was already graded looks way different. I rendered it out - and luckily caught the difference. It contains this node with these curves: https://ibb.co/186QNHK

On my R16 grade everything was nice with a little blue. On Resolve 17 even the skin has blue patches.

Is this a known bug?

Hi Laszlo Gaal,

For this issue, can you send us a sample project with media which can show the issue please?

Send a project archive (.dra) through a link of any file sharing website like dropbox etc.

Hello,

I had a database on R16. Upgraded to R17. Now a project that was already graded looks way different. I rendered it out - and luckily caught the difference. It contains this node with these curves: https://ibb.co/186QNHK

On my R16 grade everything was nice with a little blue. On Resolve 17 even the skin has blue patches.

Is this a known bug?

Hi Laszlo Gaal,

For this issue, can you send us a sample project with media which can show the issue please?

Send a project archive (.dra) through a link of any file sharing website like dropbox etc.

Hello,

sorry, I didn't see the message until now. Yes, I'll prepare a samle footage for you with source, stills, and project files! (or maybe stills and drx is enough too). thank you for taking a look!

Hello,

I had a database on R16. Upgraded to R17. Now a project that was already graded looks way different. I rendered it out - and luckily caught the difference. It contains this node with these curves: https://ibb.co/186QNHK

On my R16 grade everything was nice with a little blue. On Resolve 17 even the skin has blue patches.

Is this a known bug?

Hi Laszlo Gaal,

For this issue, can you send us a sample project with media which can show the issue please?

Send a project archive (.dra) through a link of any file sharing website like dropbox etc.

Rohit, can I share it directly to you? I just don't want to upload the source/still on a public forum.

So how can we follow this up?

I'd love to have an update on this as well.

As I'm waiting upgrading to 17 till I hear this is fixed.
Unfortunately we have many large projects at the same time that overlap.
At some point I have to upgrade mid project and I'd like to make sure, this isn't a problem anymore..
As this seems like a problem, which is not easily detectable/fixable.

Ps (we make project/database backups before upgrading)

The first iteration of v17 had in Linux an odd bug where occasionally a lut was placed in the output settings of the project even if that project did not have one.

1) check the project settings
2) is fixed in 17.2.1

The first iteration of v17 had in Linux an odd bug where occasionally a lut was placed in the output settings of the project even if that project did not have one.

1) check the project settings
2) is fixed in 17.2.1

Thank you for letting me know, that sounds like a weird bug but at least its easy to know where to look at.
Is that bug the same as the bug that is mentioned above?

@Walter you seem to have switched to v17 on Linux, is that right? Is everything running pretty smooth
from your point of view?

thx

The first iteration of v17 had in Linux an odd bug where occasionally a lut was placed in the output settings of the project even if that project did not have one.

1) check the project settings
2) is fixed in 17.2.1

Thank you for letting me know, that sounds like a weird bug but at least its easy to know where to look at.
Is that bug the same as the bug that is mentioned above?

@Walter you seem to have switched to v17 on Linux, is that right? Is everything running pretty smooth
from your point of view?

thx

Yes it is smooth (17.2.1). Only complain is that it seems they tinkered with the window tracker in the color page and it is appreciably slower: a 4K file that I was tracking almost in realitime in V16 now drop to 2-3 FPS of tracking speed… that is annoying.

The first iteration of v17 had in Linux an odd bug where occasionally a lut was placed in the output settings of the project even if that project did not have one.

1) check the project settings
2) is fixed in 17.2.1

Thank you for letting me know, that sounds like a weird bug but at least its easy to know where to look at.
Is that bug the same as the bug that is mentioned above?

@Walter you seem to have switched to v17 on Linux, is that right? Is everything running pretty smooth
from your point of view?

thx

Yes it is smooth (17.2.1). Only complain is that it seems they tinkered with the window tracker in the color page and it is appreciably slower: a 4K file that I was tracking almost in realitime in V16 now drop to 2-3 FPS of tracking speed… that is annoying.

Thank you walter! Apprectiate the help!