Participant

Answered

P: Having text on screen makes video brighter.

Forum|Forum|5 years ago
July 18, 2020
15 replies
15272 views

I post gameplay videos on YouTube, and I've noticed that when I add text to the video, it makes the screen a tad brighter while the text is on screen. It's not a disaster, but it's definitely a little irritating. I've added a short video for an example.

As far as I can tell, it doesn't change the video brightness within Premiere- just Windows Media Player and YouTube, so I suspect it has to do with my export settings.

2020-08-30_18-19-22.zip

This topic has been closed for replies.

Correct answer WesleyWasTaken

Discovered this strange bug today. The solution André0D45 posted worked for me, so I went looking for something related that might make it easier. I believe I may have found it:

In your export settings, select the Effects tab.
Check the box for Lumetri Look / LUT.
Make sure None is selected in the drop-down.

After I did this, none of my clips with text overlays changed brightness, and I didn't have to apply Lumetri Color with Basic Correction unchecked to individual clips.

D

Daniel37084469jk41

Participant

I started to have this same issue right now, only when rendering 1080 videos. Working fine with 720. Using Premiere Rush (mobile phone version)

Weird that I've used to render 1080 with no issues on titles just a couple of weeks ago. The only difference is that I've experienced some storage issues since then but I've already made space available so it should be solved now.

Any clues?

R

Red-Cor

Participant

I've been using Premiere Pro for at least 7 years, and for the past 3ish years I've encountered this issue where if I add any type of text (whether generated in Graphics or open captions/subtitles), any type of subtitle or caption, it creates this hazy/washed out/brighter adjustment on top, and each time a text appears on screen, it makes the image flicker in and out of this seeming filter. I have tried every single solution I found on forums and nothing worked, I am using the most up to date version of Premiere (24.1), I export in h.264 always, I resetted my preferences too. I followed what these links said:

https://community.adobe.com/t5/premiere-pro-discussions/subtitles-change-the-brightness-of-my-video/td-p/11297393

https://community.adobe.com/t5/premiere-pro-discussions/brightness-issues-subtitles-premiere-pro-2021/m-p/12031173

https://community.adobe.com/t5/premiere-pro-discussions/having-text-on-screen-makes-video-brighter/td-p/11398704/page/2

I ran out of ideas. Adobe please help me fix this bug.

THE ONLY SOLUTION I found, was if I used WHITE captions. Normally I like to add yellow subtitles because they are less distracting. I NEED to be able to use coloured captions without this bug.

Please does anyone have any solutions, it doesn't seem like a common bug but it exists and for me it's lasted for years. Help I want to be able to make my films the way I envision them and text is a big part of them! Thank you!!

R

Red-Cor

Participant

Edit: I exported the film I'm working on now thinking that I have found a solution by only using white captions, but it is doing the same error, it was less noticeable initially. So no solutions on my end.

A

AOE

Participant

Hi all,

Sorry if this has been asked already, but I have issues with exporting subtitles in Premiere Pro 2021. Subtitles changed in this new version to create a caption track with a new format/style. I chose the format ''subtitle'' and style ''none''. Vanity settings are: fill ''white'', background ''75% opacity, 13pt size''. I exported my sequence via software only in H.264 format. In the exported .mp4 (not visible in the sequence in Premiere Pro) there's a brightness change whenever there is a subtitle. It has a greyish overlay/lower brightness setting over the entire screen. Brightness turns back to normal if there are no subtitles in the image. It's extremely annoying to look at all of those brightness changes in a video.

I can't change the export settings to the recommended as I get the well-known compiling error, or I would try. Does anyone know a fix that doesn't mean that I have to redo everything in text?

Working on:

Macbook Pro

MacOS Big Sur

Intel Core i5 processor

Intel Iris Plus Graphics 645, 1536 MB

Almost 1TB left in storage

davids38282229

Participant

Ever resolve this? A friend is having similar issues that I'm trying to help figure out.

R Neil Haugen

Legend

This has popped up from time to time. If I remember correctly, a few people could export in say ProRes and not get this, then did their H.264/5 deliverables from that 'master' ProRes in Handbrake, ShutterEncoder, or ffmpeg.

But ... that's a remembrance and I don't guarantee it will work.

Neil

Everyone's mileage always varies ...

W

WesleyWasTakenCorrect answer

Participant

Discovered this strange bug today. The solution André0D45 posted worked for me, so I went looking for something related that might make it easier. I believe I may have found it:

In your export settings, select the Effects tab.
Check the box for Lumetri Look / LUT.
Make sure None is selected in the drop-down.

After I did this, none of my clips with text overlays changed brightness, and I didn't have to apply Lumetri Color with Basic Correction unchecked to individual clips.

K

keeldog

Participant

I had followed the instructions of André0D45, and that worked for individual clips, but this solution worked for the whole video. Thank you! I wish there was a better way to upvote solutions like you can on Stack Exchange. Greatly appreciated!

Stan Jones

Community Expert

> I wish there was a better way to upvote solutions...

You inspired me to experiment. I'm not a moderator, but I found that I had the option to select the WesleyWasTaken solution as the correct answer.

Stan

G

Griobhtha

Participant

I noticed this artifact when exporting for the first time and I believe I found a fix.

Go to File -> Project Settings -> General

Then at the top you see a panel for "Video Playback and Rendering"

Make sure you choose "GPU Acceleration" for final exporting.

I've had issues in premiere rendering some effects with "GPU acceleration" and so sometimes toggle back and forth between "GPU acceleration" and "Software only" rendering. I forgot to toggle back to "GPU acceleration" before exporting and noticed this strange brightening (its sort of like a desaturation, actually) with not only text overlay, but when some other elements were overlapped as well, such as nests overlapping other unseen footage (bad practice, I know, but easy way to use audio from a clip without delinking, etc).

A

André0D4517751676

Participant

Hi, I was having a similar problem and none of the solutions proposed here worked for me, but I just tried something that worked perfectly (let me know if it worked for you). I unchecked "basic correction" in the top of the color menu after selecting each clip that was changing brightness due to the presence of a text box (there is probably a smarter way to do this part, but I didn't dig it). The changes in brightness disappeared after that. Apparently, premiere was making an automatic correction everytime I inserted a text box in my video (strangely it was only visible after exporting the video). Hope this helps!

M

Matthew5D51

Participant

You are a god send thank you so much! None of these solutions worked but I tried this and it did!! I've been struggling with this problem for a while and this fricking worked! I literally made this account just to thank you!!!

A

AustinSpomer

Participant

Running into the same annoying issue when adding text layers to the video. Adds a bit of brightness to the overall image, which looks like a white opaque layer. Very annoying. Checking off composite in linear color did nothing for my exports. Please help, Adobe!

E

ExoTheFlyingFishAuthor

Participant

Hi all. I'm not sure why there's a "correct answer" listed here, on my own post. I never confirmed in any way that it fixed my issue.

Garbage website management aside...

For unrelated reasons, I completely reset Premiere, and I've not had the issue since.

If the issue comes back, I'll be sure to give updates.

Until then, I can only recommend resetting Premiere as a working solution.

L

LuoAndOrder

Participant

I had this exact same problem running on Premiere v14.6. Tylerm's solution didn't work for me at all. The only thing that worked for me was to downgrade from v14.6 to v13.1.5. This issue only reproed when I was trying to encode with H.264 so I suspect there's either a bug with the encoder in v14.6 or with how Premiere renders text in that version. Hopefully Adobe fixes this.

L

LuoAndOrder

Participant

I've narrowed down the version where this issue first started to Premiere v14.2. This was the version where hardware accelerated HEVC/H.264 encoding was introduced. https://helpx.adobe.com/premiere-pro/user-guide.html/premiere-pro/using/whats-new/2020-2.ug.html

I'm using an Nvidia 1080 Ti and double checked my Nvidia Control Panel settings to make sure it's using the full dynamic range as originally suggested by this video: https://www.youtube.com/watch?v=t61b6Nk-YPw&list=PLA05pELl8mMiABtsCSEB4XdivVupnYcyc&index=5&t=229s

It still feels like a bug on the Adobe side but at least I know I can safely use version 14.1 until this is fixed. Hope this helps others who stumble upon this post.

R Neil Haugen

Legend

Do NOT listed to every dude on YouTube, that guy is just wrong.

Premiere is NOT at all "full" OR "limited" ... never has been! Premiere was designed to be used on pro broadcast standards system, with PRO media standards. Nearly all Rec.709 media is limited, and Premiere will treat that as limited. Because that is correct.

A few format/codecs are full, nearly all of them 12-bit image sequences like DPX. Premiere will treat them as full.

Does this mean your monitor then displays them wrong? NO!

As long as your monitor is set correctly, while in Premiere ... both 'full' DPX clip and 'limited' Rec.709 will display on the monitor from 0-255.

Why? "Full" and "limiited" have absolutely nothing whatever to do with the display of the media, but with the encoding expectation of the playback system! Set that Nvidia card as that dude wrongly says to do, you will crush the blacks in all Rec709 media that is properly encoded. And any true full media you've got is unusably mangled.

He does't actuallly understand color management at all.

Set the Nvidia card back to video (which it thinks of as Rec709) back to limited/16-235. That, as all pro colorists will use it, is the correct way.

And solve your system's color management. Which requires some work on a PC, and is very difficult with a Mac ... as the ColorSync utility on Macs only applies the scene transform function, it does not apply the expected and required other half, the display transform function, So on Macs, the display of much Rec709 is performed using incorrect gamma.

Within Premiere, they added the "Display color managment" option, which tells Premiere to look at the ICC profile of a monitor, and attempt to remap the image to correct Rec709 within that monitor's working setup. It does a fairly decent job.

And all Mac users and most PC folk should use that Display Color Management option. If your system like mine has been calibrated/profiled through the entire setup correctly, it's not useful.

But Premiere can not over-ride the system outside of it's own playback. So after exporting, depending on what OS, monitor, browser or player is in use, that image will vary from what was seen inside Premiere.

However, if that media is then shown on a properly color managed system, it will look correct.

On the LLG forum (LiftGammaGain, pro colorists) recently one colorist made an extensive testing of color management across apps and OSs. He's Resolve based, and that app decided to make Mac users happy by giving an option for the Rec.709A setting, which adds a tag that gets ColorSync to actually apply the display transform for that clip, and voila it looks "right" on QT player, Chrome, and Safari ... and wrong on everything else on that Mac.

Plus, it's "wrong" on any full b-cast system, and nearly all PC based systems.

Creating a Rec709 file without that tag ... it showed better (though not perfectly) in Firefox on a Mac, and correct on all b-cast systems and some properly setup basic PCs.

On "devices" like tablets & phones, both were all over the freaking map.

Yea, color management is a freaking mess. All pro colorists can do, is set up a system that is to correct broadcast standards. As then, anything they deliver will look on any machine out there ... relatively to that machine ... like all other pro material.

And on no machine/device made will it ever look exactly like it did on their system.

If you go outside that practice, your material may look better in one small niche of gear. But it will guaranteed look worse on everything else out there.

Yea, that's frustrating.

Neil

Everyone's mileage always varies ...

tylerm26107622

Participant

I found a solution that worked for me! Was having the exact same issue as you. What I did was go to the sequence tab at the top of premier, go to sequence settings and uncheck the box that says composite in linear color, then hit ok. After changing this I renderred the exact same clip and the issue was gone. Now, if you open up a new project and go into sequence settings, the box is checked again. I have not found a way to automastically apply these changes to every sequence, but this is at least a fix, although it may be inconvienient to have to change it each time. Good luck!