Re: [darktable-dev] New module: mosaic

2018-01-02 Thread François Tissandier
He has a point here... :-)

Le 2 janv. 2018 20:31, "Mark Feit"  a écrit :

> Maurizio Paglia wrote:
>
>>
>> I think this function is not exactly related to raw development but
>> rather a
>> more generic operation that an image manipulation software (like GIMP) can
>> take care.
>>
> The same argument could be made about the watermark, framing, liquefy and
> spot removal modules.
>
> --Mark
>
> 
> ___
> darktable developer mailing list
> to unsubscribe send a mail to darktable-dev+unsubscribe@list
> s.darktable.org
>
>

___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org



Re: [darktable-dev] New module: mosaic

2018-01-02 Thread Aurélien PIERRE
Am Dienstag, 2. Januar 2018, 19:29:54 CET schrieb Aurélien PIERRE:
>> because I'm able to deconvolve it :-P
> I'd like to challenge that claim. Please deconvolve this image:
>
> https://houz.org/tmp/img_0001.pfm
Never challenge the power of my algorithms :
https://photo.aurelienpierre.com/wp-content/uploads/sites/3/2018/01/img_0001.jpg
>> *Aurélien PIERRE*
>> aurelienpierre.com 
>>
>> 
>>
>> Le 2018-01-02 à 12:44, Pascal Obry a écrit :
>>> Le mardi 02 janvier 2018 à 12:38 -0200, Jefferson Ferreira a écrit :
 I finish my first module called "mosaic". This module creates a
 mosaic over the image to hide some confidential information (use
 masks to restrict the area).
>>> Why using a gaussian mask over confidential information isn't enough?
>>> I'm not sure to understand the purpose of this module.
> Tobias
>
> [...]


___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: [darktable-dev] New module: mosaic

2018-01-02 Thread Tobias Ellinghaus
Am Dienstag, 2. Januar 2018, 19:29:54 CET schrieb Aurélien PIERRE:
> because I'm able to deconvolve it :-P

I'd like to challenge that claim. Please deconvolve this image:

https://houz.org/tmp/img_0001.pfm

> *Aurélien PIERRE*
> aurelienpierre.com 
> 
> 
> 
> Le 2018-01-02 à 12:44, Pascal Obry a écrit :
> > Le mardi 02 janvier 2018 à 12:38 -0200, Jefferson Ferreira a écrit :
> >> I finish my first module called "mosaic". This module creates a
> >> mosaic over the image to hide some confidential information (use
> >> masks to restrict the area).
> > 
> > Why using a gaussian mask over confidential information isn't enough?
> > I'm not sure to understand the purpose of this module.

Tobias

[...]

signature.asc
Description: This is a digitally signed message part.


Re: [darktable-dev] New module: mosaic

2018-01-02 Thread Maurizio Paglia
In data martedì 2 gennaio 2018 19:29:54 CET, Aurélien PIERRE ha scritto:
> because I'm able to deconvolve it :-P
> 
> *Aurélien PIERRE*
> aurelienpierre.com 
> 
> 
> 
> Le 2018-01-02 à 12:44, Pascal Obry a écrit :
> > Le mardi 02 janvier 2018 à 12:38 -0200, Jefferson Ferreira a écrit :
> >> I finish my first module called "mosaic". This module creates a
> >> mosaic over the image to hide some confidential information (use
> >> masks to restrict the area).
> > 
> > Why using a gaussian mask over confidential information isn't enough?
> > I'm not sure to understand the purpose of this module.
> > 
> >> - link to download the module
> >> https://www.dropbox.com/s/i9sn3lrek67m56p/mosaic.c?dl=0
> >> 
> >> - copy this file to /src/iop
> >> 
> >> - in /src/iop/CMakeLists.txt, add the red line below:
> >> 
> >> add_iop(finalscale "finalscale.c")
> >> add_iop(globaltonemap "globaltonemap.c")
> >> add_iop(bilat "bilat.c")
> >> add_iop(denoiseprofile "denoiseprofile.c")
> >> add_iop(defringe "defringe.c")
> >> add_iop(ashift "ashift.c")
> >> add_iop(hazeremoval "hazeremoval.c")
> >> add_iop(mosaic "mosaic.c")
> >> 
> >> - recompile and installing the darktable
> > 
> > Sounds wrong to distribute a new module. Can you do a commit and a
> > pull-request? Using some random code download on same random server is
> > certainly not something I would do anyway.
> > 
> > Regards,
> 
> ___
> darktable developer mailing list
> to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org


I think this function is not exactly related to raw development but rather a 
more generic operation that an image manipulation software (like GIMP) can 
take care.
Maurizio

___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org



Re: [darktable-dev] New module: mosaic

2018-01-02 Thread Aurélien PIERRE
because I'm able to deconvolve it :-P

*Aurélien PIERRE*
aurelienpierre.com 


Le 2018-01-02 à 12:44, Pascal Obry a écrit :
> Le mardi 02 janvier 2018 à 12:38 -0200, Jefferson Ferreira a écrit :
>> I finish my first module called "mosaic". This module creates a
>> mosaic over the image to hide some confidential information (use
>> masks to restrict the area).
> Why using a gaussian mask over confidential information isn't enough?
> I'm not sure to understand the purpose of this module.
>  
>> - link to download the module
>> https://www.dropbox.com/s/i9sn3lrek67m56p/mosaic.c?dl=0
>>
>> - copy this file to /src/iop
>>
>> - in /src/iop/CMakeLists.txt, add the red line below:
>>
>> add_iop(finalscale "finalscale.c")
>> add_iop(globaltonemap "globaltonemap.c")
>> add_iop(bilat "bilat.c")
>> add_iop(denoiseprofile "denoiseprofile.c")
>> add_iop(defringe "defringe.c")
>> add_iop(ashift "ashift.c")
>> add_iop(hazeremoval "hazeremoval.c")
>> add_iop(mosaic "mosaic.c")
>>
>> - recompile and installing the darktable
> Sounds wrong to distribute a new module. Can you do a commit and a
> pull-request? Using some random code download on same random server is
> certainly not something I would do anyway.
>
> Regards,
>


___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: [darktable-dev] New module: mosaic

2018-01-02 Thread Pascal Obry
Le mardi 02 janvier 2018 à 12:38 -0200, Jefferson Ferreira a écrit :
> I finish my first module called "mosaic". This module creates a
> mosaic over the image to hide some confidential information (use
> masks to restrict the area).

Why using a gaussian mask over confidential information isn't enough?
I'm not sure to understand the purpose of this module.
 
> - link to download the module
> https://www.dropbox.com/s/i9sn3lrek67m56p/mosaic.c?dl=0
> 
> - copy this file to /src/iop
> 
> - in /src/iop/CMakeLists.txt, add the red line below:
> 
> add_iop(finalscale "finalscale.c")
> add_iop(globaltonemap "globaltonemap.c")
> add_iop(bilat "bilat.c")
> add_iop(denoiseprofile "denoiseprofile.c")
> add_iop(defringe "defringe.c")
> add_iop(ashift "ashift.c")
> add_iop(hazeremoval "hazeremoval.c")
> add_iop(mosaic "mosaic.c")
> 
> - recompile and installing the darktable

Sounds wrong to distribute a new module. Can you do a commit and a
pull-request? Using some random code download on same random server is
certainly not something I would do anyway.

Regards,

-- 
  Pascal Obry /  Magny Les Hameaux (78)

  The best way to travel is by means of imagination

  http://www.obry.net

  gpg --keyserver keys.gnupg.net --recv-key F949BD3B
___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org



[darktable-dev] New module: mosaic

2018-01-02 Thread Jefferson Ferreira
Hello,

I finish my first module called "mosaic". This module creates a mosaic over
the image to hide some confidential information (use masks to restrict the
area).

- link to download the module
https://www.dropbox.com/s/i9sn3lrek67m56p/mosaic.c?dl=0

-
​ copy this file to /src/iop


- in /src/iop/CMakeLists.txt, add the red line below:

add_iop(finalscale "finalscale.c")
add_iop(globaltonemap "globaltonemap.c")
add_iop(bilat "bilat.c")

add_iop(denoiseprofile "denoiseprofile.c")
add_iop(defringe "defringe.c")
add_iop(ashift "ashift.c")
add_iop(hazeremoval "hazeremoval.c")
add_iop(mosaic "mosaic.c")
​

- recompile and installing the darktable

​Best regards.​

-- 
Jefferson Ferreira

___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org