• It will change your digital vibrance level to your desired in-game-level when you are in-game.
  
• When you tab out to your desktop, the vibrance level will be turned back to your default-level.
  
• The program will continue to run and observe (preferably minimized in tray) until you decide to close it.
  
• Autostart when you turn your computer on.
  
• Save configuration data for an unlimited amount of games.
  
  Optional (useful when playing in display mode "Borderless Windowed"):
  
• Resolution Change to your desired in-game-resolution when you switch into a game.
  
• Resolution Change to your Windows default resolution when you switch back to Windows.

Digital Vibrance/Saturation will give you an advantage in Counter-Strike: Global Offensive, as it will ease spotting enemies in the game. It will help you to be able to better distinguish between elements of the map and player models. Many professional players use Digital Vibrance/Saturation nowadays. Some examples: GeT_RiGhT, f0rest, friberg, ScreaM, Hiko. For more information, check out the videos listed in the section "vibranceGUI Videos". If you're still unsure about the benefits of Digital Vibrance/Saturation, go ahead and look them up on the CS:GO subreddit.

• Note that not all NVIDIA Laptops are supported.
  Make sure to have the option "Digital Vibrance" in your NVIDIA Control Panel. If you do not have the option in your driver, NVIDIA decided to disable Digital Vibrance for your mobile GPU. You can not use vibranceGUI because of that.
  
  
• Note that all Laptops with Intel integrated GPU are not supported.
  Intel Laptops are not supported because there is no public API for their integrated GPU.
  
  
• AMD Laptops should work fine.

1. Download the .zip file from http://vibrancegui.com/.
   
2. Extract the .zip file to a folder of your choice. Do not start vibranceGUI.exe out of the archive!
   
3. Start the program.
   
   Optional:
   
4. Press the "Autostart vibranceGUI" checkbox to have vibranceGUI started every time you boot your computer.

1. Add running games with the "Add" button. A process explorer window will be opened and all active processes will be listed.
   
2. Double click the desired game. The selected game will then be added to your game list in the main window of vibranceGUI.
   
3. Adjust the settings for the game and press "Save".

For games that are not actively running on your computer follow these steps:

1. Click "Add manually". A file explorer will be opened.
   
2. Navigate to the game installation folder.
   
3. Select the .exe file of the game and press "Accept". The selected game will then be added to your game list in the main window of vibranceGUI.
   
4. Adjust the settings for the game and press "Save".

Newly added features will be released as Beta first. The latest Beta version is always available at http://vibrancegui.com/vibrance/beta. The Beta will come as an unpacked .exe file.

Do not forget to report possible problems and bugs to @juvlarn on twitter.

Note that this video is showing an outdated version of vibranceGUI. The colors shown in the video are still accurate though.
Credits to BananaGaming.

Credits to Tasorrog.

• You need the Visual C++ Redistributable for Visual Studio 2015.
  
• Make sure to take the x86 version, even if you have a x64 Windows.
  
• Download it here: https://www.microsoft.com/en-us/download/details.aspx?id=48145

• Intel Laptops are not supported because there is no public API for their integrated GPU. VibranceGUI can not run on your laptop.
  
• NVIDIA laptops need to have the Digital Vibrance option in the NVIDIA Control Panel. If you do not have it, NVIDIA decided to disable Digital Vibrance for your mobile GPU. VibranceGUI can not run on your laptop.
  
  
• Did you recently switch your graphics card?
  
  1. Completely uninstall the old driver.
     
  2. Make sure you do not have leftovers from your previous driver:
     
     • If you are now using AMD: remove/rename "nvapi.dll" file in your Windows folder.
       
     • If you are now using NVIDIA: remove/rename "atiadlxx.dll" and "atiadlxy.dll" files in your Windows folder.
  3. Restart vibranceGUI
  
  
• Update Windows.

• The AMD algorithm tends to add green artifacts when setting the value > 200. This is due to how the algorithm calculates the visual output. Using a lower value should reduce green color artifacts.
  
• When you use 60 Hz, try forcing your Monitor to 75 Hz. A few users told me that this fixed their issue with greenish artifcats. Also switching between 4:3 and 16:9 resolutions might fix the green color artifacts.
  
• For CS:GO, you can force your monitor from 60 Hz to 75 Hz by adding the start parameter "-freq 75". If it does not work for you, e.g. because your monitor can not handle 75 Hz, just revert this start parameter setting.

• We're investigating issues where some games are not picked up in the Process Explorer. For example, this happened to some users when trying to add H1Z1 to the application list.
  
• Refer to the following section of this guide: "Download and Installation instructions" -> "Adding non-running Games to vibranceGUI"

• No! vibranceGUI was built with performance in mind. The program will use as low CPU cycles, you will never notice this program running. Starting from version 2.0, it is completely event-driven, meaning that not even an observer thread is needed anymore.
  
• Head over to the technical breakdown section if you're interested in how the program works.

• No, the application will not open any connection to the internet.
  
• Some people have asked for an update-notification when the program starts. We might consider this for a future release, but it is not planned at the moment.

vibranceGUI has not caused any VAC bans since February 2014. Besides being legit to use in VAC-secured Matchmaking, there have been no bans on the named leagues/services since the initial launch of the program. Keep in mind that vibranceGUI is not a hack/cheat. All it does is automating graphic driver settings for your comfort. ESEA and CEVO officials have also approved the legal use of vibranceGUI on their platforms. You can review the posts here: ESEA[play.esea.net], CEVO[cevo.com]

There is absolutely no way that vibranceGUI should trigger a VAC ban. It does not directly access or interact with the monitored games at all:

• it does not load a dll into the game, actually it does not load anything into the game
  
• it does not read the process memory
  
• it does not write the process memory
  
• it does not alter game files

VAC relies on signature scanning when trying to determine if a process is a hack. This means they take hashes of chunks of the process memory or from the file system to check them back on their server for known cheats. When the sent signatures do not match any signatures in their database for known hacks, there is a chance that the file will be manually analyzed. Due to the fact that VAC is only effective against so called "public hacks" - and that vibranceGUI has thousands of users (which I'm really happy about btw), I think it's safe to say that you can be sure vibranceGUI has already been manually analyzed and been found legitimate.

You may ask yourself "why are you so sure about it?". Well, the program has been around since over two years now, has tons of users and has never been banned for. That's it, really. Public Hacks are shortlived as VAC is effective against programs that are used by many people over a short period of time. These hacks are then analyzed and added to the hack database on Valves server. Anyone that runs these public hacks will then be banned sooner or later in a VAC banwave.

Whilst the complete source code of vibranceGUI and all of its components is open source[github.com], a short technical breakdown of how the program works will be given to emphasize why vibranceGUI should never trigger a ban on any modern anti-cheat.

Determining whether a game of interest is running and being displayed in the foreground is the only part where vibranceGUI needs to rely on process interop. After retrieving the data needed to decide whether the vibrance settings need to be changed in the current environment, all following computation will be done local to the vibranceGUI process. The change of colors is done through utilizing the APIs of the attached graphics card driver. No game process will ever be touched directly, no handle to the game will be created.

The game itself does not even know the colors are changed as Digital Vibrance and Saturation is a post-process effect. After the complete frame has initially been sent from the OS to the GPU, the frame will be intercepted and additional shaders will be added on top of the original frame. This is also the reason why you can not take a screenshot or record in-game-footage with the changed vibrancy on the recorded image/video. To be able to record your in-game-footage with the more vibrant colors, you will need a dedicated capture card.

vibranceGUI version 1.x
The first version of vibranceGUI relied on manually checking whether a game was running by utilizing FindWindow[msdn.microsoft.com] and whether it is running in foreground with GetForegroundWindow[msdn.microsoft.com]. A background thread was launched upon program startup and was periodically checking whether a desired game process was 1) running and 2) actively displayed on the monitor.

vibranceGUI version 2.x and above
The second version of vibranceGUI makes use of intercepting a system-wide event that will be fired when the foreground process is changed. This is also a more efficient way to reacting to changes to the top-most window in Windows. Actually, the approach is far superior in all regards to the one used in version 1.x.

You will see that vibranceGUI will instantly change the vibrancy added to your monitor when switching through different processes. Several processes such as Spotify cause Windows to fire these events wrongfully on some occasions. VibranceGUI will try to make sure that you will not see any screen flickering. For more information, refer to the MSDN docs of SetWinEventHook[msdn.microsoft.com] as well as WinEventProc callback[msdn.microsoft.com].