[prev in list] [next in list] [prev in thread] [next in thread]
List: kde-kimageshop
Subject: Re: Impasto discussion
From: Dmitry Kazakov <dimula73 () gmail ! com>
Date: 2010-07-09 20:01:06
Message-ID: AANLkTimbA6AXuH0k_-9LwiYTwlXU5rLVvCOgqy-e_Gx3 () mail ! gmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
> I think, instead of rendering every layer, it is better to use
> > COMPOSITE_ALPHA_DARKEN for impasto channel. It'll be much cheaper. In
> such a
> > case, the final impasto value of the point on projection will be equal to
> > the value of the most opaque layer.
>
> No, that doesn't work well, as I explained:
> > That technique has obvious problems, since it effectively amounts to
> > carving an alpha-mask-shaped hole in the underlying layers' impasto,
> > rather than letting the layer as a whole float above the layers beneath.
>
Well, maybe I don't understand something... I meant the following:
* every layer has an impasto channel
* let's have three layers:
Layer1: alpha=transparent; impasto=100;
Layer2: alpha=opaque; impasto=125;
Layer3: alpha=transparent; impasto=50;
The result impasto value will be: 125
Isn't it what expected?
> (Also, it lets you do things like assign different materials to each
> layer. Different light source, even, though I don't know why you would
> want to do that. But I could see different materials.)
>
Yeah, different material is a good point for per-layer impasto.
PS:
Btw, if we manage to implement impasto as a filter, per-layer impasto will
be easily achieved with a usual Filter Mask.
--
Dmitry Kazakov
[Attachment #5 (text/html)]
<br><br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin: 0pt \
0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: \
1ex;"><div><div class="h5"> > I think, instead of rendering every layer, it is \
better to use<br> > COMPOSITE_ALPHA_DARKEN for impasto channel. It'll be much \
cheaper. In such a<br> > case, the final impasto value of the point on projection \
will be equal to<br> > the value of the most opaque layer.<br>
<br>
</div></div>No, that doesn't work well, as I explained:<br>
<div class="im">> That technique has obvious problems, since it effectively \
amounts to<br> > carving an alpha-mask-shaped hole in the underlying layers' \
impasto,<br> > rather than letting the layer as a whole float above the layers \
beneath.<br></div></blockquote><div><br>Well, maybe I don't understand \
something... I meant the following:<br>* every layer has an impasto \
channel<br>
* let's have three layers:<br><br>Layer1: alpha=transparent; \
impasto=100;<br>Layer2: alpha=opaque; impasto=125;<br>Layer3: alpha=transparent; \
impasto=50;<br><br>The result impasto value will be: 125<br><br>Isn't it what \
expected?<br> </div><div> </div><blockquote class="gmail_quote" style="margin: 0pt \
0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"><div \
class="im"> </div>
(Also, it lets you do things like assign different materials to each<br>
layer. Different light source, even, though I don't know why you would<br>
want to do that. But I could see different \
materials.)<br></blockquote></div><br>Yeah, different material is a good point for \
per-layer impasto.<br><br>PS:<br>Btw, if we manage to implement impasto as a filter, \
per-layer impasto will be easily achieved with a usual Filter Mask.<br> <br><br>-- \
<br>Dmitry Kazakov<br>
_______________________________________________
kimageshop mailing list
kimageshop@kde.org
https://mail.kde.org/mailman/listinfo/kimageshop
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic