- Posts: 7
- Joined: Fri Dec 19, 2014 11:39 am
Mon May 10, 2021 11:41 pm
I grade features using ACES cct, for me it's the easiest way to work on a P3 projection reference and deliver to DCP and other color spaces with no problem, and also keeping a master with no compromises for futures deliveries.
When I had RED media, I used to optimize media the R3D clips to "uncompressed 16 bit float", so it keeps the full tonal and dynamic range of the R3D file (even HDRx). This way I had a 2K clip without the overhead of R3D decoding to work on the grade in real time on a somewhat old classic MacPro.
This workflow was OK up to Resolve V16.X. On Resolve 17 I have several problems:
1- The weird decision to delete the optimized media managing tools on the media pool and not giving a complete alternative using Proxy Media (there's no HDR / floating point codec available).
2- I don't understand why, but when I create optimized media of R3D files, there's a severe gamma / contrast increase, making the clip useless for grading.
3- The weird thing is, when I go to the color tab and set the clip to render cache Fusion Output, it DOES IT RIGHT, with no gamma / contrast shift. Well you could tell me to just use this method, even if Resolve's cache is very fragile. BUT on a specific project I'm working on I have another problem, that I set all clips to render cache Fusion output, but only a few does, leaving many clips with the red line doing nothing. I have not discovered what makes the difference between clips. If I set to render color output it does without. problem, but it's not useful to me to re-render the clip each time I make a color adjustment.
My last working option is to add a cache node at the beginning of each grade (not a great idea for a almost finished feature project), so I would prefer to have the optimize media working as it did before.
I tried messing with the
When I had RED media, I used to optimize media the R3D clips to "uncompressed 16 bit float", so it keeps the full tonal and dynamic range of the R3D file (even HDRx). This way I had a 2K clip without the overhead of R3D decoding to work on the grade in real time on a somewhat old classic MacPro.
This workflow was OK up to Resolve V16.X. On Resolve 17 I have several problems:
1- The weird decision to delete the optimized media managing tools on the media pool and not giving a complete alternative using Proxy Media (there's no HDR / floating point codec available).
2- I don't understand why, but when I create optimized media of R3D files, there's a severe gamma / contrast increase, making the clip useless for grading.
3- The weird thing is, when I go to the color tab and set the clip to render cache Fusion Output, it DOES IT RIGHT, with no gamma / contrast shift. Well you could tell me to just use this method, even if Resolve's cache is very fragile. BUT on a specific project I'm working on I have another problem, that I set all clips to render cache Fusion output, but only a few does, leaving many clips with the red line doing nothing. I have not discovered what makes the difference between clips. If I set to render color output it does without. problem, but it's not useful to me to re-render the clip each time I make a color adjustment.
My last working option is to add a cache node at the beginning of each grade (not a great idea for a almost finished feature project), so I would prefer to have the optimize media working as it did before.
I tried messing with the