bro just ANSWER THE QUESTION jesus christ
Mod note: Title changed
It's a complicated situation with several "ifs ... " and within that, I answered directly and gave some context.
If working in SDR, which is Rec.709 and still nearly everything done ... certainly professionally ... ignore it.
Is that too complex for you to understand? I certainly hope not.
Then I give the one circumstance it would be needed to set ... an actaul HDR workflow ... and that 203 would be the typical value.
I don't see my answer as anything but direct, and further, that it adds additional information useful to many readers.
To recap, here's the extremely simple question Bellon (and everyone viewing this thread!) wants answered:
"Hey, Adobe just pushed a new update that adds a confusing new HDR encoding setting to the Export screen. This toggle provides 3 options, all of which are completely inscrutable technical jargon to 99% of Premiere users - and we're being required to choose one of these options on every single export, even if we're not exporting an HDR video. Like virtually every Premiere user on the planet, I'd just like to export a normal SDR video, the same way I always have. Which of the "HDR Graphics White (Nits) option should I pick?"
It turns out, the answer is simple: if you're exporting a non-HDR video, it doesn't matter which you pick - you can safely ignore the new "HDR Graphics White (Nits)" setting that was added in the Premiere Pro 2022 update. As bizarre and counter-inuitive as it is that Adobe is suddenly forcing us to choose an HDR nit brightness for our non-HDR videos, it won't actually affect your SDR output.
(...I'm providing this straightforward answer above for the people who, like me, inevitably find their way to this thread from a Google search and actually want a direct answer to the original posters' questions about how this setting affects non-HDR video, rather than sifting through a 10-paragraph-long rant about how colorists these days aren't correctly following DolbyLabs' guidance on the proper implementation of HDR or whatever.)
In closing, this thread is a fantastic example of the phenomenon described in the below image. Have a great week! 😚
That is exactly what has been said repeatedly in posts above this one ... Sigh.
I will say (as someone who arrived here looking for an answer to the same question), when I read "ignore it", it sounds like they are saying either "don't turn that setting on" or "leave it at default", neither of which is helpful in this particular case. I discovered today that my project (standard HD1080p) was currently set to 203. I wasn't sure if I should switch it to 100, which seemed to me like the non-HDR setting. All the suggestions to "ignore it" made me think they were maybe saying to leave it at 100, which my project was not set at? Or were they saying to leave it at 203???
What nickr21371816 clarified, and everyone else did not, is that I can ignore it BECAUSE it does not apply to, nor have any effect on non-HDR workflows. And now I know that I can actually "ignore it." Haha.
My first sentence, in the first reply to the OP ...
This is ONLY of use if you are working full HDR projects ... which very few are. For most things, ignore it.
I'm curious, what part of that wasn't clear? It states right at the beginning it's ONLY an issue IF you are working in HDR.
I thought that was pretty simple, straight, and direct ... 😉
You're not wrong. I just read your first sentence as, "If you are not working in HDR, do not change this setting," when I was concerned that I might have accidentally changed that setting and didn't know where to set it back to. I suppose I just needed to hear that the setting has zero effect on non-HDR media, and as such, it doesn't matter what it is set to.
And also I'm hugely appreciative of you and others taking the time to answer these kinds of questions.
These NLE apps are pretty complex and complicated beasts. Anything that can be done, can be done at least four ways it seems. But every different pathway to doing something seems to have ... implications, right?
So it's so freaking easy to fear the worst and over-think some of the things that are really not at all complicated. Do it all the time myself.
And then I'll get bit by an implication I hadn't thought of with something else. Sigh.
That attachment is incredible. There's one certain old mustachioed curmudgeon on the Creative Cow forums who I think we are probably all familiar with, who posts SO PRODIGIOUSLY I've been amazed at what percentage of threads I've scrolled through that he's popped up in. The b*tch of it is he often has good advice, you just have to make it through the belittling and judgment from a guy who does graphics packages for a midwestern local news station.
That said, I enjoyed Neil's perspective in this thread. I'm ready to make the transition to an HDR workflow and future proof both my live production pipeline and post... it just feels like it's still 5 years away from being properly accessible even for a pro with 10+ years experience.
LOL. Russ, you made me laugh out loud for real. I've been on the "cow" for maybe 20 years, and thought maybe I was the only one who felt a little annoyed. His oft-unhelpful responses always struck me as that kid who really wants to have something to say but doesn't always have something PRODUCTIVE to say! There's seemingly no end to his answers that go something like, "Well, I don't really know about that, so it's probably not possible." Clearly this guy is just trying to get his face in the pole position of frequent responders. Hey, maybe it's getting him work.
After reading this thread, you "R Neil Haugen" need your "adobe community ptofessional" title revoked.
If the answer you are giving isn't readily understoof by the questioner, then you've failed at your task of answering said question.
So please, stay off of the forums.
Might have some that will disagree with you on that. Such as the folks struggling with the color changes of the 2022 build. Which have had a whole slug of people thanking me. I've gone way outta my way to get clips from people and test their issues, getting back with answers.
I've filed things with the engineers and got several acknowledged bugs from the crew. And posted two FAQs that also get a ton of thanks from users.
You might check how many answer's I've been credited with also, helping out people here. I never mark myself correct ... and my numbers there don't reflect a lot of "points" I lost when they switched forum providers a couple years back.
And I don't know how many times at NAB or MAX I've had someone come up to me, recognize me from my avatar, and say thanks, you've saved my job with X answer ...
No, I' think I'll stick around. 😉
thank you for your answer and thanks everybody for the entertaining thread.
Coming back to Neil, sorry but I disagree with this (and not only this) Adobe choice.
Why add an information that regard just few projects in the first interaction that user meet?
This is a total failure of User Experience.
You should focus and guide User interactions, previewing different levels of interaction, contextualizing (as you did in the thread) specifically on the user needs and consequent flow.
Why do people choose Figma instead of AdobeXD?
It's only an exemplary case of how and why UX design is not well-done in Adobe software. As this thread demonstrates.
If I can suggest something useful, take the example from Spotify Ideas ( https://community.spotify.com/t5/Ideas/ct-p/newideas ), use your large and strong community full of professionists to share and test ideas and suggestions.
Listening to the users.
First, I hope you realize that I and all the other "Community Professionals" are ... users.
We're not staffers. Those all have "Adobe employee" type badges here.
Second, the app is designed (realistically) for full on professional production work. So the engineers assume users have a pretty fair understanding of professional post processing. And should, realistically.
And the volunteers like myself help people with struggles figure out how to get something done.
You should submit a feedback to Adobe directly about these stupid forum titles. They cone across as you are an employee. Someone who is new here would not know that only employees get "Adobe employee" tag. I know I didn't. It's EXTREMELY confusing for a beginner.
One reason I think what it is the way it is is that Adobe does want me to think you guys are employees so I don't feel helpless and abandoned. It's a psychological manipulation to make me think that plenty of "official" help is available when in reality it's not the case whatsoever.
It shouldn't be hard to add (not employee) or something that clarifies you are just a regular user like us.
Except they're very different from "regular users" like you in that they know what the hell they're talking about.
Nobody asked for your uneducated opinion. Go troll somewhere else with your "New Here" account.
I've been a whatchamacallit for a number of years now. And every so often, Adobe's M&E people and legal legions decide something is confusing, and change names and terminology across the board.
At one time, "we" were Adobe Community Experts" ... but the have the Adobe Certified Experts process for people who've taken tests, so they decided that was confusing and came up with "Adobe Community Professionals" .
But now that's considered confusing, and it looks like we might go back to ACE's.
It's the "Community" thing that's supposed to indicate we're part of "the community" rather than "Adobe".
But do understand, most of the Adobe upper brass don't have a clue what we ACP or ACE types do for them. Really.
The program heads do and love us across the board. Way up above? Well, they don't really know that much about the user apps like these programs. Those are only one part of the massive Adobe brand, and not really the biggest profit center for Adobe.
Beyond content, this thread is wildly entertaining to the rest of us, so thanks. Might be the only time I've chuckled from an adobe forum post.
"Hi. I know you spent fifteen to thirty minutes crafting a reply to my question, but I'm really not interested in all that stuff. I just want the answer to my specific problem and I don't want to sift through all the other junk you put in your post. I don't care if it might help someone later on who may be trying to learn what is going on. This is about me and the fact that I want someone to tell me what I want NOW. I mean really. Do you actually expect me to take the time to read what you wrote to try and find something that will help me? You're being really inconsiderate, you know."
Just sayin' Neil. 🙂
@Demis98C6 Does this affect image quality or color? Simple answer, No.
Which one is the best option for your editing? Simple answer, It doesn't matter. If you care to learn more please read Mr. Haugen's thorough and thoughtful explanation.
@R Neil Haugen Do not throw your pearls before pigs, lest they trample them underfoot and turn to attack you. ~Jesus Christ
@nickr21371816 First spanking goes to you for being an arrogant troll. Well articulated words were Hitler's specialty you jerk. Use your intelligence to make the world a better place. Shame on you.
@KevinLaytonMcAllister Triple spanking for you because your name is Kevin. Use spell check next time you type words you "ptofessional" little troll. Shame on you.
The rest of you get a light spanking, because you don't have the patience to read a few paragraphs. Well articulated responses from a very kind man who answered the meta questions ontop of the obvious ones asked.
Forgive me for assuming you pricks are Gen Z, but if you're not, double shame on you, you're behaving like them.
If you had the patience to read this far, congratualtions.
@Demis98C6 Reddit has kinder people answering your question: https://www.reddit.com/r/colorists/comments/ivsnay/confused_about_premieres_new_hdr_graphic_white/
To the prickly little impatient trolls, the link I provided contains more words which will require reading, and reading comprehension skills.