Windows 10: Gamebar records videos too bright. Any fixes for this?

I mean for example, a video game I'm playing, and I'll record using gamebar. When I pause the video and compare it with the game, the brightness is always higher in the recorded video. How can I fix this? I know it's a problem because when I used different software like OBS or Radeon Relive to record, they look the same. Not brighter. I just like Gamebar better because it just works for me where I had issues with the others. This is the only problem I'm having with Gamebar.

submitted by /u/kibbblz
[link] [comments]

:)

 

Gamebar process problem

Yeah, Like many people here have commented I have disabled everything in relation to Windows Game mode, gamedvr and gamebar in the settings menu. When that failed to fix the issue, I disabled everything in the registry in relation to game mode, gamedvr and
gamebar. That stupid gamebar presence process was still there. Then I used powershell to remove the xbox app. Still there. It only started doing this today. Please get rid of this crap and give me back control over what runs on my own computer.

Thanks.

 

Gamebar process problem

Hi,

The Gamebar Presence Writer is automatically enabled on your computer if you opened the Game bar and play a game. This process allows you to record video clips from your games.

If you are playing a game and you want to disable the Gamebar Presence Writer, follow the steps below:

• Click Start, and then type Task Manager in the search box.
• Select Task Manager.
• Under Processes, look for Gamebar Presence Writer, and then press the
  End task button.

To disable Game bar, here are the steps:

• Launch Xbox app, and then go to Settings
  
  .
• Click Game DVR.
• Turn off Record game clips and screenshots using Game DVR.

If you have further queries, feel free to contact us anytime.

 

Gamebar

When I'm recording with gamebar, if i'm recording game sounds then the whole video is freezing every second or two. However, If i don't record with sound then the recording is fine. Any way to fix this? (This wasn't happening on windows version 1709.)