On 9/01/13 09:11 AM, David Vincent-Jones wrote:
> I was trying to import a folder that included a dng file with a hdr
> image set that had been created by dt. This crashes dt. I was also
> unable to import any dng file directly.
For the record, this is the stack trace which I saw with
David's xmp
great, thanks. the red channel is slightly too dark to give a good
fit, but looks nice apart from that.
cheers,
jo
On Wed, Jan 9, 2013 at 5:37 PM, thouks wrote:
> Another one...
>
> Hopefully it looks good.
>
> regards
>
> Thorsten
> -
On 9/01/13 09:11 AM, David Vincent-Jones wrote:
> I was trying to import a folder that included a dng file with a hdr
> image set that had been created by dt. This crashes dt. I was also
> unable to import any dng file directly.
>
> If dt can create dng files should it not also be able to import t
cool, so i merged this to master for more testing. if people like it
it can stay :)
-jo
On Tue, Jan 8, 2013 at 10:13 PM, Pascal Obry wrote:
> To me it is clear that this new wavelet algorithm is better. I'm not
> sure we are lossing details, but clearly the "grain" resulting is lot
> smother. I
I don't know if this is the right mailing list (the right list is not specified
in the web page), but I followed the instructions on
http://blog.pcode.nl/2010/06/28/darktable-camera-color-profiling/
and after a few tries ended up with a profile which seems to me to be closer to
what I see than
On 9/01/13 09:11 AM, David Vincent-Jones wrote:
> I was trying to import a folder that included a dng file with a hdr
> image set that had been created by dt. This crashes dt. I was also
> unable to import any dng file directly.
>
> If dt can create dng files should it not also be able to import t
Hi,
You can find a noise profile for D7000 at:
http://ed.gomez.free.fr/vrac/dt-noiseprofile-20130108.tar.gz
I checked it against the current active D5100 profile (same sony
sensor), and my gaussian curve seems smoother than the D5100's one. I
attach a tuned graph2.sh output comparing both
I was trying to import a folder that included a dng file with a hdr
image set that had been created by dt. This crashes dt. I was also
unable to import any dng file directly.
If dt can create dng files should it not also be able to import them?
David
---
oh, thanks. changed it for the e-m5 as well
-jo
On Wed, Jan 9, 2013 at 11:04 AM, José Carlos R. Casimiro
wrote:
> Hello again,
>
> I've been using this, with good results.
>
> I updated my git version and realize that there was no presents any more for
> the E-PL1.
> Some changes have been made.
Hello again,
I've been using this, with good results.
I updated my git version and realize that there was no presents any more
for the E-PL1.
Some changes have been made. Now there's noiseprofiles.h.
The presets are only present now, if the picture was taken with that
camera, right?
When I first
great, these look fine.
pushed to master, thanks
jo
On Wed, Jan 9, 2013 at 1:05 AM, jmsarat wrote:
> Attached the noise profile for Sony SLT-A55V. The profile works well
> particularly with the new wavelet mode.
>
> Jean-Marc Sarat
>
> ---
On Tue, 8 Jan 2013 19:01:08 +1300
johannes hanika wrote:
> On Sat, Jan 5, 2013 at 6:59 PM, johannes hanika wrote:
> > On Sat, Jan 5, 2013 at 4:31 AM, Jan wrote:
> >>> >>> 2) Feature request:
> >>> >>> At the moment it is not possible to give absolute values for the
> >>> >>> border size. Is the
On Tue, Jan 8, 2013 at 8:08 PM, Pascal de Bruijn wrote:
> On Tue, Jan 8, 2013 at 7:19 PM, Pascal Obry wrote:
>> Le 08/01/2013 19:06, Pascal de Bruijn a écrit :
>>> I do however wonder if this might be more suitable as a seperate
>>> migration tool (possibly included in the darktable source tree),
On Tue, Jan 8, 2013 at 7:19 PM, Pascal Obry wrote:
> Le 08/01/2013 19:06, Pascal de Bruijn a écrit :
>> I do however wonder if this might be more suitable as a seperate
>> migration tool (possibly included in the darktable source tree),
>> instead of cluttering the Darktable UI itself with somethi
Le 08/01/2013 19:06, Pascal de Bruijn a écrit :
> I do however wonder if this might be more suitable as a seperate
> migration tool (possibly included in the darktable source tree),
> instead of cluttering the Darktable UI itself with something that is
> basically meant as a use-once kinda thing.
On Tue, Jan 8, 2013 at 7:00 PM, Pascal Obry wrote:
>
> As you probably know now this is my case. I'm migrating. To help this
> and avoid loosing all my work I'm currently working on a way to import
> from Lightroom.
>
> First note that I pretty well understand that this will never be
> perfect, bu
As you probably know now this is my case. I'm migrating. To help this
and avoid loosing all my work I'm currently working on a way to import
from Lightroom.
First note that I pretty well understand that this will never be
perfect, but I do feel that it is lot better than nothing :)
At the moment
On Mon, Jan 7, 2013 at 11:03 PM, Roland Riegel wrote:
> Am Montag, 7. Januar 2013, 18:08:27 schrieb Pascal de Bruijn:
>> I sorted missed "completely freezes my laptop" the first time I read your
>> post.
>>
>> Typically that means faulty hardware. At least most cases turned out to be
>> that.
>>
>
To me it is clear that this new wavelet algorithm is better. I'm not
sure we are lossing details, but clearly the "grain" resulting is lot
smother. I find that I have better results with a strength of 0.9 with
the wavelet algorithm than a strength of 2.0 with non-local means.
I've some years of LR
19 matches
Mail list logo
