Downloads:

444

Downloads of v 1.05:

444

Last Update:

19 Feb 2017

Package Maintainer(s):

Software Author(s):

  • Ramzi Sabra (a.k.a yasamoka)

Tags:

color-sustainer admin color sustainer ICC profile monitor gamma

Color Sustainer

1.05 | Updated: 19 Feb 2017

Downloads:

444

Downloads of v 1.05:

444

Maintainer(s):

Software Author(s):

  • Ramzi Sabra (a.k.a yasamoka)

Color Sustainer 1.05

All Checks are Passing

2 Passing Test


Validation Testing Passed


Verification Testing Passed

Details

To install Color Sustainer, run the following command from the command line or from PowerShell:

>

To upgrade Color Sustainer, run the following command from the command line or from PowerShell:

>

To uninstall Color Sustainer, run the following command from the command line or from PowerShell:

>

NOTE: This applies to both open source and commercial editions of Chocolatey.

1. Ensure you are set for organizational deployment

Please see the organizational deployment guide

  • Open Source or Commercial:
    • Proxy Repository - Create a proxy nuget repository on Nexus, Artifactory Pro, or a proxy Chocolatey repository on ProGet. Point your upstream to https://chocolatey.org/api/v2. Packages cache on first access automatically. Make sure your choco clients are using your proxy repository as a source and NOT the default community repository. See source command for more information.
    • You can also just download the package and push it to a repository Download

3. Enter your internal repository url

(this should look similar to https://chocolatey.org/api/v2)

4. Choose your deployment method:


choco upgrade color-sustainer -y --source="'STEP 3 URL'" [other options]

See options you can pass to upgrade.

See best practices for scripting.

Add this to a PowerShell script or use a Batch script with tools and in places where you are calling directly to Chocolatey. If you are integrating, keep in mind enhanced exit codes.

If you do use a PowerShell script, use the following to ensure bad exit codes are shown as failures:


choco upgrade color-sustainer -y --source="'STEP 3 URL'" 
$exitCode = $LASTEXITCODE

Write-Verbose "Exit code was $exitCode"
$validExitCodes = @(0, 1605, 1614, 1641, 3010)
if ($validExitCodes -contains $exitCode) {
  Exit 0
}

Exit $exitCode

- name: Ensure color-sustainer installed
  win_chocolatey:
    name: color-sustainer
    state: present
    version: 1.05
    source: STEP 3 URL

See docs at https://docs.ansible.com/ansible/latest/modules/win_chocolatey_module.html.

Coming early 2020! Central Managment Reporting available now! More information...


chocolatey_package 'color-sustainer' do
  action    :install
  version  '1.05'
  source   'STEP 3 URL'
end

See docs at https://docs.chef.io/resource_chocolatey_package.html.


Chocolatey::Ensure-Package
(
    Name: color-sustainer,
    Version: 1.05,
    Source: STEP 3 URL
);

Requires Otter Chocolatey Extension. See docs at https://inedo.com/den/otter/chocolatey.


cChocoPackageInstaller color-sustainer
{
   Name     = 'color-sustainer'
   Ensure   = 'Present'
   Version  = '1.05'
   Source   = 'STEP 3 URL'
}

Requires cChoco DSC Resource. See docs at https://github.com/chocolatey/cChoco.


package { 'color-sustainer':
  provider => 'chocolatey',
  ensure   => '1.05',
  source   => 'STEP 3 URL',
}

Requires Puppet Chocolatey Provider module. See docs at https://forge.puppet.com/puppetlabs/chocolatey.


salt '*' chocolatey.install color-sustainer version="1.05" source="STEP 3 URL"

See docs at https://docs.saltstack.com/en/latest/ref/modules/all/salt.modules.chocolatey.html.

5. If applicable - Chocolatey configuration/installation

See infrastructure management matrix for Chocolatey configuration elements and examples.

This package was approved by moderator AdmiringWorm on 19 Feb 2017.

Description

Introduction

Color Sustainer (ICC Profile Enforcer). Color Sustainer is an application that allows you to associate color profiles with particular display modes

These profiles are loaded automatically for their respective modes as you:

  • switch displays on and off
  • add and remove displays
  • change display modes - from Windows, games, media players, this application, or any other application
  • load up full-screen applications (e.g. games) that reset and override (but not ignore) set color profiles.

Change display color profile association mode

Right-click a display in mode-specific mode (default) and click "Change to Global" to associate a single global color profile to the display. Right-click a display in global mode and click "Change to Mode-specific" to associate color profiles to specific display modes.

This application requires the Microsoft Visual C++ 2010 redistributable to be installed. Please check up on this forum thread for questions and more info.


tools\Changelog.txt
1.05:

Resolved the following issues:

-Fixed profile parsing. Now all profiles that can be loaded into the graphics card (have a video card gamma table) work. Thanks to imyrno for the detailed steps for profile parsing.

-Fixed the memory leak that occurs when the application is started and looping.

-Fixed an update checking bug whereby newer versions yet unreleased to the public are not deemed newer than the latest version released.


1.04.2:

-Removed "by yasamoka" in title, "Donate" section under "Help", added "About Color Sustainer" section under "Help".

Resolved the following issues:

-Made the update system smarter; now it properly compares version numbers and does not only check for mismatch.

-The "Check for updates periodically" checkbox is unchecked if the settings window is shown, an update is available, and "Never remind me again" is pressed.

-Tray icon context menu now gets drawn upwards rather than downwards the first time the tray icon is right-clicked with the taskbar placed at the bottom.

-LUT Bit Depth Clamp now works for monitors in global color profile association mode.

-Start / Stop main window action button text now first shows "Stop" instead of "Start" if Color Sustainer is started via "-start" argument.

-The version field in the Settings file has to be at the top else loading the settings fails.

-An invalid settings keyword no longer causes settings loading to fail. (Useful for using older versions with settings files produced by newer versions)

-Changing one monitor from global to mode-specific color profile association mode then selecting a second monitor that is in global mode now clears the Resolutions list.

-Resolutions are now automatically detected after changing a monitor from global to mode-specific color profile association mode.

-Startup settings now get checked and updated upon application launch.

-Deleting a monitor in global color profile association mode now hides all the widgets related to associating a color profile / predefined tint.

-The README file now accomodates changes made since v1.04.1.


1.04.1:
-Emergency v1.04 hotfix


1.04:

Resolved the following issues:

-Color profile association section remains visible after a monitor in global mode is deleted

-Disabled buttons (greyed out) instead of hiding them

-Delete All Button gets disabled when there is nothing to delete

-Disabled the ability to resize windows (adds empty space)

-Tree no longer gets saved directly after being loaded (even successfully)

-Used a higher-resolution icon for the application windows

-Revamped the settings section

-Separated the tray icon modes from the application (going to be included in a sister application later on)

New features:
-Software update checking system
-Donate button


1.03.3:

Resolved the following issues:

-Debug line shows up in display list

-Log shows v1.03 at application launch

-Associating a new replacement color profile for an active display mode for an active monitor while the loop is running does not change the profile.

-Display Device Enumeration issue: on calling EnumDisplayDevices, assumed that only one display can be detected per device, used if statement instead of while loop


1.03.2:

Resolved the following issues:

-Removing a profile association from an active monitor in Global mode while the loop is running does not set the current profile to NULL.

-Setting a color profile (or changing from such color profile to a pre-defined tint) to an inactive mode for an active monitor in Mode-specific mode will set the current profile's ramp but not name to that color profile.

-Changed title to v1.03.2 (was 1.03 for v1.03.1)

1.03.1:

New feature:
-Change a monitor between Global mode / Mode-specific mode.


1.03:

Resolved the following issues:

-Display mode X is selected in the list and is the active display mode. Windows / external application changes the active mode. Now display mode X is not the active mode. Right-clicking on the already-selected display mode X does not show a "Change to Mode" option.

-Trying to associate a color profile that cannot be parsed results in logging "Failed to parse..." followed by "Associating color profile...". The (now null / random) gamma ramp then fails to load or be preserved.

-Color profiles now get closed after they are parsed (success / fail), instead of remaining open as long as Color Sustainer is running.

-Detect button shows for display mode and not for resolution when an inactive display is chosen

Changes:

-Log application launch

-Log success or failure for mode request changes

-Close to Tray instead of Minimize to Tray

-Tray icon now changes when started or stopped

-Added separate detect and delete options for monitors, resolutions, modes

New Feature:

-Tray Icon Display Modes: You can now add display modes to the tray icon, for quick switching between display modes straight from the tray. Right-click, hover over a monitor, and click on the display mode and the monitor should switch to that mode.



1.02:

Release
tools\chocolateyInstall.ps1
$fileName = "color-sustainer.exe"
$linkName = "Color Sustainer.lnk"
$destdir = $(Split-Path -parent $MyInvocation.MyCommand.Definition)

#install start menu shortcut
$programs = [environment]::GetFolderPath([environment+specialfolder]::Programs)
$shortcutFilePath = Join-Path $programs $linkName
$targetPath = Join-Path $destdir $fileName
Install-ChocolateyShortcut -shortcutFilePath $shortcutFilePath -targetPath $targetPath -RunAsAdmin

#make usable in commandline
Install-ChocolateyPath $destdir
tools\chocolateyUninstall.ps1
$linkName = "Color Sustainer.lnk"
$programs = [environment]::GetFolderPath([environment+specialfolder]::Programs)
$shortcutFilePath = Join-Path $programs $linkName

if(Test-Path $shortcutFilePath) {
    del $shortcutFilePath
}
tools\color-sustainer.exe
md5: 67D6FAA7C56A8D80A8263380D1416554 | sha1: B294CC37BAB58D4BD7D1EC19F8EEB6986E148460 | sha256: 55B15AB8F71D024A66AD37DA76231B77FEE917833EC2179003743A26A4A9AFCB | sha512: 99F2BDC6F9F70C465A6C808705AB4EF6925C6015622D74FD0CD44CF56D80458968545CC2B3D3124D95C1E33B6B76696F2E72F1A0F2D3410F99DF3EB1F0BE7D8E
tools\color-sustainer.exe.gui
 
tools\QtCore4.dll
md5: 7B5F259BCAB7339C078E3AB82376329F | sha1: 6B075E27DBFC9FA83AF6E25EB115D0275C37BF6A | sha256: BAD830336E84A65D11599F26FFDBA20300B985FA571523F8F633F05DE48B8915 | sha512: 8ADA247CCE975020A4ADFB9675A1913D2FCB77722D17B17B587134BBCB7878B8FC26D720C8A7FBB87A78FC865947A03DD55D742A94749911690635A5C2DCF0AD
tools\QtGui4.dll
md5: 831BA3A8C9D9916BDF82E07A3E8338CC | sha1: 6C89FD258937427D14D5042736FDFCCD0049F042 | sha256: D2C8C8B6CC783E4C00A5EF3365457D776DFC1205A346B676915E39D434F5A52D | sha512: BEDA57851E0E3781ECE1D0EE53A3F86C52BA99CB045943227B6C8FC1848A452269F2768BF4C661E27DDFBE436DF82CFD1DE54706D814F81797A13FEFEC4602C5
tools\QtNetwork4.dll
md5: 8A2E025FD3DDD56C8E4F63416E46E2EC | sha1: 5F58FEB11E84AA41D5548F5A30FC758221E9DD64 | sha256: 52AE07D1D6A467283055A3512D655B6A43A42767024E57279784701206D97003 | sha512: 8E3A449163E775DC000E9674BCA81FFABC7FECD9278DA5A40659620CFC9CC07F50CC29341E74176FE10717B2A12EA3D5148D1FFC906BC809B1CD5C8C59DE7BA1
tools\README.docx
 
tools\VERIFICATION.pdf
 

In cases where actual malware is found, the packages are subject to removal. Software sometimes has false positives. Moderators do not necessarily validate the safety of the underlying software, only that a package retrieves software from the official distribution point and/or validate embedded software against official distribution point (where distribution rights allow redistribution).

Chocolatey Pro provides runtime protection from possible malware.

Version Downloads Last Updated Status

1.05

Resolved the following issues:
  • Fixed profile parsing. Now all profiles that can be loaded into the graphics card (have a video card gamma table) work. Thanks to imyrno for the detailed steps for profile parsing.
  • Fixed the memory leak that occurs when the application is started and looping.
  • Fixed an update checking bug whereby newer versions yet unreleased to the public are not deemed newer than the latest version released.
NOTICE:

Users may have been recently notified that a Color Sustainer update is available when there is none. The notification will not go away unless you press "Never remind me again" which may deprive you in the future of being notified of important updates to Color Sustainer.

A hotfix is on its way to fix the issue at hand, but meanwhile, merely editing the Color Sustainer settings text file and changing updateAvailable=1 to updateAvailable=0 will fix the issue given the server for the version update check is back online the next time Color Sustainer checks for an update (upon application launch / 24 hours after last check if Color Sustainer remains running). Thank you for your understanding and apologies for any annoyances caused by this confusion.

Discussion for the Color Sustainer Package

Ground Rules:

  • This discussion is only about Color Sustainer and the Color Sustainer package. If you have feedback for Chocolatey, please contact the Google Group.
  • This discussion will carry over multiple versions. If you have a comment about a particular version, please note that in your comments.
  • The maintainers of this Chocolatey Package will be notified about new comments that are posted to this Disqus thread, however, it is NOT a guarantee that you will get a response. If you do not hear back from the maintainers after posting a message below, please follow up by using the link on the left side of this page or follow this link to contact maintainers. If you still hear nothing back, please follow the package triage process.
  • Tell us what you love about the package or Color Sustainer, or tell us what needs improvement.
  • Share your experiences with the package, or extra configuration or gotchas that you've found.
  • If you use a url, the comment will be flagged for moderation until you've been whitelisted. Disqus moderated comments are approved on a weekly schedule if not sooner. It could take between 1-5 days for your comment to show up.
comments powered by Disqus