Denis,
No it is not part of 2.0.6, this will be part of 2.2 release.
--
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
_
sts.darktable.org
Envoyé: Samedi 12 Mars 2016 14:59:49
Objet: Re: [darktable-user] Re: [Darktable-users] Import Adobe compatible xmp
sidecar
Le samedi 12 mars 2016 à 12:50 +0100, Tobias Ellinghaus a écrit :
> Sure, go ahead, I can't test it anyway as I don't have Lr to
Thanks everybody for your understanding and reactivity!
I'll try to check this LR issue with some colleagues who use this
software, and compare the rendering (especially the brightness) with DT.
Cheers
denis
Le 12/03/2016 14:59, Pascal Obry a écrit :
> Le samedi 12 mars 2016 à 12:50 +0100, Tobia
Le samedi 12 mars 2016 à 12:50 +0100, Tobias Ellinghaus a écrit :
> Sure, go ahead, I can't test it anyway as I don't have Lr to compare.
> :-)
Here it is:
https://github.com/darktable-org/darktable/pull/1171
I don't have Lr anymore, but I have checked that the value in the Lr
XMP is now used a
Am Samstag, 12. März 2016, 12:41:26 schrieb Pascal Obry:
> Le samedi 12 mars 2016 à 12:19 +0100, Tobias Ellinghaus a écrit :
> > Did you also export pictures and sample the pixels? That might be
> > more precise
> > than relying on the video stack of a virtualization layer.
>
> Good question, I d
Le samedi 12 mars 2016 à 12:19 +0100, Tobias Ellinghaus a écrit :
> Did you also export pictures and sample the pixels? That might be
> more precise
> than relying on the video stack of a virtualization layer.
Good question, I don't remember. I've done that but can't be sure for
all modules.
> I
Am Freitag, 11. März 2016, 16:25:09 schrieb Denis Testemale:
[...]
> Le 11/03/2016 16:02, Pascal Obry a écrit :
> > 2016-03-11 15:48 GMT+01:00 Denis Testemale :
[...]
> >> - deactivated all parameter (auto blabla, local contrast, highlight
> >> recovery, etc.) which could modify the luminosity
Le vendredi 11 mars 2016 à 16:25 +0100, Denis Testemale a écrit :
> Thanks Pascal, I cc the list if you don't mind.
Sure, it was meant to be sent to the list. Sorry.
--
Pascal Obry / Magny Les Hameaux (78)
The best way to travel is by means of imagination
http://v2p.fr.eu.org
http://w
Thanks Pascal, I cc the list if you don't mind.
I suspect indeed that LR might have been doing something else (and might
still do) that impact the brightness and RGB values. But the base curve
in DT have a similar effect, right?
I guess it all comes from the effort to match LR and DT results, whi
Thanks Tobias,
I don't have access to Lightroom (other than downloading a demo version
and try to run it in Virtualbox).
TL;DR: I think exposure compensation (Exposure2012) should be left as it
is in the LR-compliant xmp files, because it is the only parameter
(maybe color temperature is another
Am Donnerstag, 10. März 2016, 22:10:32 schrieb Denis Testemale:
> The only setting present in the xmp files is the exposure compensation,
> nothing else. And for that matter, you can also get xmp files for Aftershot
> program (that is something that I asked to the developper and he did it).
> The o
Hi,
On 03/10/2016 10:10 PM, Denis Testemale wrote:
> It even has a unit (eV) which itself is not dependent on the program.
Ouch. You are mixing up exposure value and Electronvolt, totally
different things
https://en.wikipedia.org/wiki/Exposure_value
https://en.wikipedia.org/wiki/Electronvolt
Whil
The only setting present in the xmp files is the exposure compensation, nothing
else. And for that matter, you can also get xmp files for Aftershot program
(that is something that I asked to the developper and he did it). The only
differences between those 2 xmp files are the xmp fields (so that
Am Mittwoch, 9. März 2016, 00:07:06 schrieb Denis Testemale:
> Thanks for the answer.
> I don't know for LR, I don't have it. I can understand that you try to match
> exposure between LR and DT for the situations where users want to import
> images and their treatment in DT, and not have to tweak t
Thanks for the answer.
I don't know for LR, I don't have it. I can understand that you try to match
exposure between LR and DT for the situations where users want to import images
and their treatment in DT, and not have to tweak the results too much to obtain
what they had in LR.
The problem I s
Denis,
> Following the topic we discussed one month ago (support of xmp files
> from the Ramperpro timelapse controller), and seeing that DT 2.0.2
> now
> supports this functionality (thanks for the very quick integration!),
> I
> gave a try with some files (one sample below, NEF and xmp). The
>
Am Dienstag, 8. März 2016, 21:46:05 schrieb Denis Testemale:
> Hello!
> Following the topic we discussed one month ago (support of xmp files
> from the Ramperpro timelapse controller), and seeing that DT 2.0.2 now
> supports this functionality (thanks for the very quick integration!), I
> gave a tr
Hello!
Following the topic we discussed one month ago (support of xmp files
from the Ramperpro timelapse controller), and seeing that DT 2.0.2 now
supports this functionality (thanks for the very quick integration!), I
gave a try with some files (one sample below, NEF and xmp). The exposure
correct
18 matches
Mail list logo