Gimp 2 9 Mac

GIMP is an open-source photo editing tool that delivers a decent finished product. GIMP requires macOS 10.9 Maverick or above. Is there a better alternative? Photoshop will be easier to pick up, can do more, and is the industry standard. However, it's significantly more expensive than GIMP.

• Gimp 2 9 Mac Torrent
• Gimp 2 9 Mac Installer
• Gimp 2 Mac
• Gimp 2 9 Mac Download

GIMP (GNU Image Manipulation Program) is a freely distributed software for manipulating images. We can easily optimize the image, convert their type using GIMP. It provides the power and flexibility to designers to transform images into truly unique creations. GIMP is the cross platforms application and available for Linux, Windows, MAC OS, and FreeBSD, etc. This tutorial will help you to install the latest Gimp on macOS using homebrew.

GIMP for Windows. Download GIMP 2.10.22 via BitTorrent Download GIMP 2.10.22 directly. The download links above will attempt to download GIMP from one of our trusted mirror servers. If the mirrors do not work or you would rather download directly from our server, you can get the direct download here. Supported OS: Windows 7 or over. 8/10 (43 点) - mac gimpを無料ダウンロード gimpをインストールすれば優れたツールで好きな絵を描くことが簡単になります、このソフトで様々な写真も編集可能。.

Step 1 – Prerequisites

Before starting the installation of GIMP using this tutorial you must have the following prerequisites

• Terminal: You must have Mac Terminal access and little knowledge about working with the terminal application.
• Homebrew: Homebrew is a popular package management tools used for installing most open-source software like Node. Here is the Homebrew installation tutorial

Step 2 – Install GIMP on macOS

GIMP can be simply installed with the homebrew package installer. However, it is not available in the current repository of homebrew, hence we have to tap into another repository by using the following command.

Then use the following command to install GIMP on macOS system.

Wait for the installation complete.

Step 3 – Launch GIMP Application

You have successfully installed GIMP on macOS. Launch this application on your system.

GIMP 2.9/2.10 is a radical departure from GIMP 2.8, offering:

• New precision options for high bit depth, radiometrically correct editing.
• New color management options.
• New and corrected color space decompositions, blend modes, and conversions to black and white.
• Floating point precision with unclamped editing.

Written November 2015. Updated August 2017. Please note that much of the information on this page is not valid for the recently released GIMP 2.9.6. Hopefully eventually I'll find the time to update this tutorial, but it won't be any time soon.

Introduction: high bit depth GIMP 2.9/2.10

Purpose of this guide

This user's guide introduces you to some of high bit depth GIMP's new editing capabilities that are made possible by GEGL's high bit depth processing. The guide also points out a few 'gotchas' that you should be aware of. Please keep in mind that GIMP 2.9 really is a development branch, so many things don't yet work exactly like they will work when GIMP 2.10 is released.

Useful links: the official GIMP website, builds for Windows and MAC, building GIMP on Linux

• Partha's GIMP 2.9 builds for Windows and MAC, including a portable Windows build of my patched GIMP plus information on compiling GIMP on Windows.
• Precompiled versions of high bit depth GIMP are more or less widely available for the various Linux operating systems. If you run Linux and you'd like to compile high bit depth GIMP yourself, Building GIMP for artists and photographers has step-by-step instructions.

High bit depth GIMP is a work in progress. The primary goal for the GIMP 2.10 release is full 'Geglification' of the GIMP code base.

Editing in sRGB vs editing in other color spaces

For best results when using GIMP 2.9/2.10, only edit sRGB images.

GIMP 2.8 has hard-coded sRGB parameters that make many editing operations produce wrong results for images that are in RGB working spaces other than sRGB. GIMP 2.9 does have — and almost certainly GIMP 2.10 will have — these same hard-coded sRGB parameters.

Full support for editing images in other RGB working spaces likely won't happen at least until GIMP 3.0. However, the next big change for GIMP will be the change-over from GTK+2 to GTK+3 (or GTK+4?), which is a pretty critical step as GTK+2 is on the verge of being retired. GIMP development is a volunteer effort, porting GIMP over to GEGL has required an enormous amount of work, and porting from GTK+2 to GTK+3 isn't exactly a trivial task. More GIMP developers would help a lot, so if you have any coding skills, please consider volunteering. Mac peach orange lipstick.

If you really do want to edit in color spaces other than sRGB, my patched version of GIMP 2.9 ('GIMP-CCE') allows you to edit in any well-behaved RGB working space. However, please be aware that default GIMP has quite a lot of functionality that I've removed from GIMP-CCE.

New high bit depth precision options

Menu for choosing the image precision

As shown by the screenshot below, high bit depth GIMP offers five different image precisions:

• Three integer precisions: 8-bit integer, 16-bit integer, and 32-bit integer.
• Two floating point precisions: 16-bit floating point and 32-bit floating point.

Which precision should you choose for editing?

If you have a fast computer with a lot of RAM, I recommend that you always promote your images to 32-bit floating point before you begin editing. Excel for mac trial version. Here's why:

1. Regardless of which precision you choose, all babl/GEGL/GIMP internal processing is done at 32-bit floating point. Read that sentence three times.
2. There seems to be a small speed penalty for not using 32-bit floating point precision.
3. The Precision menu options dictate how much memory is used to store in RAM the results of internal calculations:
   • Choosing 32-bit floating point precision allows you to take full advantage of GEGL's 32-bit floating point processing.
   • If you are working on a lower-RAM machine, performance will benefit from using 16-bit floating point or integer precision, but of course the price is a loss in precision as new editing operations use the results of previous edits as stored in memory.
   • On very low RAM systems, performance will benefit even more from using 8-bit integer precision. But if you use 8-bit integer precsion, you are throwing away most of the advantages of working with a high bit depth image editor.
   • 64-bit precision is made available mostly to accomodate importing and exporting very high bit precision images for scientific editing. You don't gain any computational precision from using 64-bit precision for actual editing. If you choose 64-bit precision for editing, all you are really doing is wasting system RAM resources.

As discussed in Part 2 of this article, 'Using high bit depth GIMP's floating point precision for unclamped editing' (and depending on your editing style and goals), instead of 32-bit floating point precision, sometimes you might prefer using 16-bit or 32-bit integer precision. But making full use of all of high bit depth GIMP's new editing capabilities does require using floating point precision.

Sometimes people assume that floating point is 'more precise' than integer, but this isn't actually true: At any given bit-depth, integer precision is more precise than floating point precision, but uses about the same amount of RAM:

• 16-bit integer precision is more precise than 16-bit floating point precision, and the two precisions use about the same amount of RAM.
• 32-bit integer is more precise than 32-bit floating point precision, and the two precisions use about the same amount of RAM.

Even though in theory 32-bit integer is more precise than 32-bit floating point, GEGL/GIMP's internal processing always uses 32-bit floating point precision. So for GIMP, even when you choose 32-bit integer precision, the actual precision of the editing operations is still 32-bit floating point.

Using the image precision options when exporting an image to disk

The precision menu options have another extremely important use beside dictating the precision with which the results of editing operations are held in RAM. When you export the image to disk, the precision options allow you to change the bit depth of the exported image.

For example, some image editors can't read floating point tiffs. So if you want to export an image as a tiff file that will be opened in another image editor that can only read 8-bit and 16-bit integer tiffs, and your GIMP XCF layer stack is currently using 32-bit floting point precision, you might want to change the XCF layer stack precision to 16-bit integer before exporting the tiff.

After exporting the image, don't forget to hit 'UNDO' ('Edit/Undo . . . ', or else just use the CNTL-Z keyboard shortcut) to get back to 32-bit floating point precision (or whatever other precision you were using).

New color management options

High bit depth GIMP automatically detects camera DCF information

For reasons only the camera manufacturers know, instead of embedding a proper ICC profile in camera-saved jpegs, usually they embed 'DCF' and 'maker note' information. Whenever a camera manufacturer offers the option to embed a color space that isn't officially supported by the DCF/Exif standards, each manufacturer feels free to improvise with new tags.

High bit depth GIMP does detect and assign the correct color space for most camera-saved jpegs. Like all editing software, GIMP has to play 'catch up' with new tags for new color spaces offered by new camera models.

Tell your camera manufacturer that you want proper ICC profiles embedded in your camera-saved jpegs.

Black point compensation

Unlike GIMP 2.8, GIMP 2.9 does offer black point compensation as an explicit option, and it's enabled by default.

Even though black point compensation is checked by default in high bit depth GIMP, whether you should use black point compensation partly depends on the color management settings provided by the other imaging software that you routinely use. For example, Firefox doesn't provide for black point compensation. So if one of your goals is to make sure that images look the same as displayed in various softwares, you need to make sure all the relevant color management settings match.

What is black point compensation? LCD monitors can't display 'zero light'. There's always some minimum amount of light coming from the screen. Fill your screen with a solid black image, turn out all the lights and close the doors and curtains, and you'll see what I mean.

Gimp 2 9 Mac Torrent

Black point compensation compensates for the fact that RGB working spaces like sRGB allow you to produce colors (for example solid black, R=G=B=0) that are darker than your monitor can actually display. GIMP uses the LCMS2 black point compensation algorithm, which very sensibly scales the image tonality so that 'solid black' in the image file maps to 'darkest dark' in the monitor profile's color gamut.

However, depending on your monitor profile, using or not using black point compensation might not make any difference at all. The only time black point compensation makes a difference is if the Monitor profile you choose in 'Preferences/Color management' actually does have a 'higher than zero' black point.

Gimp 2 9 Mac Installer

New and updated algorithms for converting to Luminance, LAB, and LCH

Converting sRGB images from Color to Black and White using Luma and Luminance

Under 'Colors/Desaturate/Desaturate' (not a typo — 'Desaturate' is one of the items under the 'Colors/Desaturate' menu), GIMP 2.9 offers five options for converting an sRGB image to black and white:

1. Luminance is equal to (the Red channel times 0.213) plus (the Green channel times 0.715) plus (the Blue channel times 0.072), done on RGB encoded linearly.
2. Luma (almost equivalent to the GIMP 2.8 'Luminosity' option) is equal to (the Red channel times 0.213) plus (the Green channel times 0.715) plus (the Blue channel times 0.072), but done on RGB encoded using the sRGB TRC.

   High bit depth GIMP's 'Luma' option uses slightly different multipliers for calculating Luma: (the Red channel times 0.222) plus (the Green channel times 0.717) plus (the Blue channel times 0.061). The GIMP 2.8 multipliers were wrong and the GIMP 2.9 multipliers are correct.

3. Lightness (HSL) adds the lowest and highest RGB channel values and divides the result by two.
4. Average (HSI Intensity) sums all three RGB channel values and divides the result by three.
5. Value (HSV) takes the maximum of R, G, and B.

'Luminance' is short for relative luminance. Luminance is calculated using the same channel multipliers that are used to calculate Luma. The mathematical difference between calculating Luma and Luminance is as follows:

• Luma is calculated using RGB channel values that are encoded using the sRGB TRC.
• Luminance is calculated using linearized RGB channel values, producing a radiometrically correct and physically meaningful conversion from color to black and white.

Gimp 2 Mac

Of the various options in the 'Colors/Desaturate' menu, 'Luminance' is the only physically meaningful way to convert from color to black and white. The Red, Blue, and Green Luminance/Luma channel multipliers are specific to the sRGB color space. These channel multipliers are actually the 'Y' components of the sRGB ICC profile's XYZ primaries. As you might expect, different RGB working spaces have different 'Y' values, and so the high bit depth GIMP 2.9 conversions to Luma and Luminance only produce correct results for sRGB images.

Decomposing from sRGB to LAB

Decomposing to LAB does use hard-coded sRGB parameters and so will produce wrong results in other RGB working spaces.

In GIMP 2.8, decomposing an sRGB image to LAB produced flatly wrong results.

In high bit depth GIMP, decomposing an sRGB image to LAB does produce mathematically correct results. But as of GIMP 2.9.4, if you use 'drag and drop' to pull the decomposed grayscale layers over to your sRGB layer stack, there is still a small error in the resulting RGB layer. Figure 3 below illustrates the problem:

Assuming you start with an image in the regular sRGB color space, then:

• In GIMP 2.9, decomposing a layer to LAB in GIMP 2.9 produces mathematically correct results.

  However, dragging the resulting grayscale channels back to the RGB XCF color stack results in a slightly wrong result. This is because the dropped grayscale layer(s), which don't have an embedded ICC profile, are assumed to be encoded using the sRGB companding curve (Tone Reproduction Curve, 'TRC'), when really they are encoded using the LAB companding curve. This is a color management problem that can be solved by enabling GIMP to do grayscale color management (all that's needed is a little developer time — did I mention that GIMP really does need more developers?).

  As an incredibly important aside, a mathematically correct conversion from sRGB to LAB Lightness and back to sRGB produces exactly the same thing as using GIMP 2.9's 'Colors/Desaturate/Luminance' option to change an sRGB image from color to black and white.

• In GIMP 2.8, decomposing a layer to LAB produces wildly mathematically incorrect results, and dragging the resulting channel(s) back to the RGB XCF color stack also produces wildly mathematically incorrect results. So older GIMP tutorials on using the LAB Lightness channel to convert an image to black and white won't produce anywhere near the same results when using GIMP 2.9/GIMP 2.10.

If you'd like to know more about 'LAB Lightness to black and white', the following two-part article untangles the massive amounts of confusion regarding converting an RGB image to black and white using the LAB Lightness channel:

1. LAB Lightness to black and white using GIMP 2.8.
2. LAB Lightness to black and white using GIMP 2.9 and PhotoShop — the typical PhotoShop tutorial on using the LAB Lightness channel to convert to black and white does produce mathematically incorrect results.

LCH: the actually useable replacement for the entirely inadequate color space known as 'HSV'

HSV ('Hue/Saturation/Value') is a sad little color space designed for fast processing on slow computers, way back in the stone age of digital processing. HSV is OK for picking colors from a color wheel. But it's really wretched for just about any other editing application, because despite the fact that 'HSV' stands for 'Hue/Saturation/Value', you actually can't adjust color and tonality separately in the HSV color space.

'LCH' stands for 'Lightness, Chroma, Hue'. LCH is mathematically derived from the CIELAB reference color space, which in turn is a perceptually uniform transform of the CIEXYZ reference color space. Unlike HSV, LCH is a physically meaningful color space that allows you to edit separately for color and tonality.

Gimp 2 9 Mac Download

Very roughly speaking:

• LCH Lightness corresponds to HSV Value.
• LCH Chroma corresponds to HSV Saturation.
• LCH Hue corresponds to HSV Hue (the names are the same, but the two blend modes are based on very different mathematics).
• LCH Color is a combination of LCH Chroma and Hue, and corresponds to HSV Color, which is a combination of HSV Hue and Saturation (again, the names are the same, but the two blend modes are based on very different mathematics).

LCH blend modes and painting are a game-changing addition to high bit depth GIMP editing capabilities. If you'd like to see examples of what you can do with LCH, that you can't even come close to doing with HSV, I've written a couple of tutorials on using GIMP's LCH color space capabilities:

1. A tutorial on GIMP's very awesome LCH Blend Modes, which shows how to use GIMP's new LCH blend modes to repair a badly damaged image, and then to colorize a black and white rendering of the image.
2. Autumn colors: An Introduction to High Bit Depth GIMP's New Editing Capabilities, which shows how to use GIMP's new LCH blend modes to edit separately for color and tonality.

In GIMP 2.9, LCH calculations do use hard-coded sRGB paramters, and so will produce wrong results in other RGB working spaces.

GIMP 2.9 also provides an LCH color picker, and an LCH 'Hue-Chroma' tool, which can be used in place of the HSV color picker and 'Hue-Saturation' tool. [NEEDS A SCREENSHOT]