Hello. I’ve found just another bug (or intended behavior ) in DT4 / Filmic RGB and because I don’t expect it to be fixed given that nobody would use it like that, I just wanted to share this funny feature with you, should you not be able to experience this with your HW and/or OS.
Here’s what happens when I keep all the defaults and turn global brilliance in the color balance rgb module all the way up while shifting mid-tones from -100% towards 0%:
Turning OpenCL on and off makes little difference on my integrated GPU.
And that’s why I’m skeptical when it comes to reporting bugs. Because even the most obvious glitch (such as this one) can be relativized by people like you.
My setting is within the allowed boundaries. What else should I do?
You know, the usual way of using software isn’t based on trying to work out when it works properly. Do you personally expect to see UFOs when fiddling with brightness?
Display-referred implementations of power functions assume that white is at 100%, which removes the need for normalization. For scene-referred purposes this needs to be taken into account.
Ok, now please try to translate this to a regular user who has no idea what’s beneath the UI, and don’t forget to enlighten me on how this relates to UFO. Thank you.
I did and I don’t understand it. It also says that
This is used to normalize the power setting in the 4 ways tab.
I used neither the 4-ways tab nor display-referred modules. Everything’s on default using the scene-referred workflow.
Who is the target audience of this application again? After 3 years of using DT I finally start to see why people avoid it if the manual is the first thing to open (and understand – in its current state). I’m not an idiot, I just don’t have the technical and mathematical background.
I can but I didn’t intend to as this certainly isn’t a #play_raw post. I just found it funny and I think it’s obviously some misbehavior. Which I know how to work around. Attempts to make me look stupid were expected as well. Maybe I’ll learn something in the end.
Now the glitch appears based on the rendering window size and/or position so on the exported image below it looks different. Also note the black area in the middle of the image.
And where do I find that? Because if it’s the filmic RGB white point then it does not work. The eyedrop button doesn’t help that either. No matter what I do, I still can push it so that it breaks.
So the bug exhitbits when cranking up the global brilliance high. I think Aurelian mentioned this bug in a recent video. (or if not, something very like it)
) in DT4 / Filmic RGB and because I don’t expect it to be fixed given that nobody would use it like that, I just wanted to share this funny feature with you, should you not be able to experience this with your HW and/or OS.
