Re: [Gimp-developer] [Crédit Agricole] Windows 10 - Migration

2019-08-18 Thread Alexandre Prokoudine via gimp-developer-list
It works, but we recommend upgrading your version of GIMP, it's out of date.

Alex

вс, 18 авг. 2019 г., 17:12 GIEBG Coordination Etude W10 <
coordination.etude@ca-ts.fr>:

> Hello,
>
> As part of migration of Windows 10 version 1709 to 1809, we ask you as
> software publisher to know:
> 1. The adhesions between your software(s) below and the Windows OS?
> 2. Are the version(s) of your software(s) compatible with version 1809 of
> Windows 10?
>
> We thank you in advance for your quick return ideally by 30th of August,
> please.
>
> GIMP - 2.10.8
>
> Cordialement, Regards,
>
> Pôle Produit Entreprise Numérique
> Tribu Environnement de travail & Outils collaboratifs
>
> Alexandre BORJA
> Sarah CANELLAS-GUILLE
> Florent JULLIEN
> Sébastien MOTTE
> Elodie PACAUD
> Petra SIVERBRANT
> Rémi VOYANT
>
> @: coordination.etude@ca-ts.fr
>
> Ce message et toutes les pieces jointes (ci-apres le "message") sont
> etablis a l'attention exclusive de ses destinataires.
> Si vous recevez ce message par erreur, merci de le detruire et d'en
> avertir immediatement l'expediteur par e-mail.
> Toute utilisation de ce message non conforme a sa destination, toute
> diffusion ou toute publication, totale ou partielle, est interdite, sauf
> autorisation expresse.
> Les communications sur Internet n'etant pas securisees, l'expediteur
> informe qu'il ne peut accepter aucune responsabilite quant au contenu de ce
> message.
>
> This mail message and attachments (the "message") are solely intended for
> the addressees.
> It is confidential in nature .
> If you receive this message in error, please delete it and immediately
> notify the sender by e-mail.
> Any use other than its intended purpose, dissemination or disclosure,
> either whole or partial, is prohibited except if formal approval is granted.
> As communication on the Internet is not secure, the sender does not accept
> responsibility for the content of this message.
> ___
> gimp-developer-list mailing list
> List address:gimp-developer-list@gnome.org
> List membership:
> https://mail.gnome.org/mailman/listinfo/gimp-developer-list
> List archives:   https://mail.gnome.org/archives/gimp-developer-list
>
___
gimp-developer-list mailing list
List address:gimp-developer-list@gnome.org
List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list
List archives:   https://mail.gnome.org/archives/gimp-developer-list


[Gimp-developer] Bug?

2019-08-18 Thread Mario Sottile - Marionetas Mey via gimp-developer-list
I have the same layer. One with alpha blocked and the other with alpha 
transferred to mask. I paint both with a very soft white airbrush in 
bottom-right corner. In this image, we can see that there is a soft 
white peculiar stripe vertically and horizontally:


When I disable mask in one layer and transfer alpha to mask in the other 
(and disable that mask), I realize that the soft airbrush painted a lot 
outside the permitted zone. That is where alpha is close to 0.


The same with any color.

Is this a bug?

--
Marionetas Mey

Mario Sottile - Director
(011) 15.6283.1576
www.mariomey.com.ar
i...@mariomey.com.ar

___
gimp-developer-list mailing list
List address:gimp-developer-list@gnome.org
List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list
List archives:   https://mail.gnome.org/archives/gimp-developer-list


[Gimp-developer] [Crédit Agricole] Windows 10 - Migration

2019-08-18 Thread GIEBG Coordination Etude W10
Hello,

As part of migration of Windows 10 version 1709 to 1809, we ask you as software 
publisher to know:
1. The adhesions between your software(s) below and the Windows OS?
2. Are the version(s) of your software(s) compatible with version 1809 of 
Windows 10?

We thank you in advance for your quick return ideally by 30th of August, please.

GIMP - 2.10.8

Cordialement, Regards,

Pôle Produit Entreprise Numérique
Tribu Environnement de travail & Outils collaboratifs

Alexandre BORJA
Sarah CANELLAS-GUILLE
Florent JULLIEN
Sébastien MOTTE
Elodie PACAUD
Petra SIVERBRANT
Rémi VOYANT

@: coordination.etude@ca-ts.fr

Ce message et toutes les pieces jointes (ci-apres le "message") sont etablis a 
l'attention exclusive de ses destinataires.
Si vous recevez ce message par erreur, merci de le detruire et d'en avertir 
immediatement l'expediteur par e-mail.
Toute utilisation de ce message non conforme a sa destination, toute diffusion 
ou toute publication, totale ou partielle, est interdite, sauf autorisation 
expresse.
Les communications sur Internet n'etant pas securisees, l'expediteur informe 
qu'il ne peut accepter aucune responsabilite quant au contenu de ce message.

This mail message and attachments (the "message") are solely intended for the 
addressees.
It is confidential in nature .
If you receive this message in error, please delete it and immediately notify 
the sender by e-mail.
Any use other than its intended purpose, dissemination or disclosure, either 
whole or partial, is prohibited except if formal approval is granted.
As communication on the Internet is not secure, the sender does not accept 
responsibility for the content of this message.
___
gimp-developer-list mailing list
List address:gimp-developer-list@gnome.org
List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list
List archives:   https://mail.gnome.org/archives/gimp-developer-list


Re: [Gimp-developer] Is there any kind of documentation on the new layer blend modes?

2019-08-18 Thread Ell via gimp-developer-list
On 8/16/19 10:31 AM, Ofnuts wrote:
> Specifically, I'm wondering about the "Split", "Merge", and the group
> "Passthrough" modes.
> 
> The only relevant Google answer is a paying video tutorial.
> 
> Of course I have checked the online doc...

There's indeed no organized documentation for all the new layer modes
yet, unfortunately.

For Pass Through mode, see:

  https://docs.gimp.org/2.10/en/glossary.html#glossary-pass-through

Merge and Split are complementary modes, as their names suggest.  They
are similar to Normal and Erase modes, respectively, but they handle
alpha values differently.  The short version is that (when using their
default composite modes) Merge adds the alpha values of the input
layers, while Split subtracts them.  In other words, if the alpha values
of the bottom and top layers are A and B, respectively, the resulting
alpha values for Merge and Split are `min (A + B, 100%)`
and `max (A - B, 0%)`, respectively.

--- Wall-of-text warning.  Skip to the end for practical examples. ---

The slightly more advanced version has to do with how alpha values are
interpreted.  Alpha values can be seen as a property of the sub-pixel
geometry of a pixel; they specify how much of a pixel's area is covered
by the layer's content.  For example, when you rasterize an ideal shape,
such as a circle, pixels along the circumference will only be partially
covered by it; their alpha values specify how much of their area is
covered by the circle.  It's even more instructive to think of alpha
values in terms of probability: when picking a random point within a
pixel, the alpha value specifies the *probability* of the point
belonging to the layer.

The information conveyed by the alpha value is, of course, only partial:
while it tells you *how much* of a pixel's area is covered by its
content, it doesn't tell you exactly *which* portion of the pixel is
covered.  The latter becomes relevant when you combine multiple layers,
though: two layers having a pixel with 50% alpha each, when overlaid on
top of each other, can result in a pixel having anywhere between 50%
alpha (if the areas covered by both layers coincides exactly) to 100%
alpha (if the areas covered by both layers don't coincide at all).
There is no correct answer here: we have to make a certain assumption
about the relationship between the two layers.

The "ordinary" assumption, used by most layer modes, is that the two
layers are independent (in the probabilistic sense): whether a given
point within a pixel belongs to one layer doesn't affect the probability
of it belonging to the other layer as well; this leads to the familiar
`A + B - AB` formula for combining alpha values.  I call this the
"diffuse" assumption.  While it's a reasonable assumption in the general
case, in can lead to artifacts when applied inappropriately.  Most
notably, it can lead to semitransparent "seams" between opaque objects
that should, in theory, intermesh perfectly.  That's a common problem
with Inkscape, for example; it happens because Inkscape renders each
object separately, throwing away the actual sub-pixel geometry in favor
of alpha values, and then combining the alpha values with the (wrong)
assumption that the objects are independent of each other.

There are at least two other simple assumptions we can make about the
layers: the "complement" assumption, where the two layers are thought to
be mutually exclusive (i.e., to *complement* each other), and the
"coincide" assumption, where the two layers are thought to occupy the
same area (i.e., to *coincide* with each other).  Note, however, that
this formalism places some restrictions on the layers' alpha values
(namely, that `A + B <= 100%` for "complement", and that `A = B` for
"coincide").  A more precise formalism is that with "complement" the
intersection of the two layers is as small as possible, and with
"coincide" the intersection is as big as possible.

One day, GIMP might allow this assumption to be controlled separately
from the layer mode, through an additional layer attribute.  For now,
Merge and Split are singled out as two useful cases of non-diffuse
modes: Merge is simply Normal mode with the "complement" assumption, and
Split is Erase mode with the "coincide" assumption.

---

Merge mode should be used when combining layers that are, logically,
separate parts of a whole.  The archetypical example is that of cutting
an antialiased selection, and pasting as a new layer.  When using Normal
mode for the pasted layer, there's usually a semitransparent "seam"
around the selection's boundary (as mentioned above).  Using Merge mode
instead fixes the issue, as the two layers are two parts of one whole,
reproducing the original image.

Split mode is complementary to Merge: it allows you to erase one of the
parts out of the whole, producing its complement; the two parts can then
be combined using Merge mode to reproduce the original.  For example,
you can split an image into two layers by first isolating one of