Hi,
I have noticed that gimp has a different concept of sRGB, upon import it asks
me if I want to convert to its version of sRGB, and that conversion causes
changes especially in lightness.
I understand the licencing issue, but it would be great if the oss tools would
agree on one version of sRGB.
Anyway, thanks for your work!
Cheers
Michael
On 3. März 2014 16:52:28 MEZ, Tobias Ellinghaus <[email protected]> wrote:
>Am Montag, 3. März 2014, 10:30:21 schrieb Rich:
>> Hi
>
>Hi.
>
>> I'm using a profiled display and I believed that Darktable was
>writing
>> sRGB jpegs, but it turns out it's writing "Darktable sRGB".
>>
>> When using one of these images on Blogger for my photography blog,
>the
>> colours go very wrong.
>>
>> I expect that Blogger is completely ignoring the colour profile and
>just
>> stripping it out, but the results are not good.
>>
>> I have added sRGB.icm (found a few copies of this on my system,
>although
>> annoyingly they're all slightly different - hmmm) into
>> ~/.config/darktable/color/out/ and re-saved my work using that.
>>
>> This appears to result in output that is truer to the version seen in
>> darktable.
>>
>> Does this sound like the right thing to do?
>>
>> Shouldn't DT ship with a standard
>> <http://www.color.org/srgbprofiles.xalter#v2> sRGB profile?
>>
>> What's the DT sRGB anyway?
>
>darktable creates its own copy of the profile for licensing reasons.
>Thus the
>fancy name. Same happens for our AdobeRGB profile. However, they are
>supposed
>to be identical to the "original" profiles (*), just the name differs.
>
>That being said I have no idea what Blogger does to your images. Could
>you
>maybe export a tiny image (300x200 pixel would be enough) using
>darktable's
>sRGB profile, upload it to Blogger and also attach it to a mail here
>and give
>us the URL? Maybe we can make some sense from it.
>
>> Thanks,
>>
>> Rich
>
>Tobias
>
>(*) this is true for AdobeRGB. For sRGB however there are a couple
>contradicting definitions of how the profile should look like. We use
>the most
>common/accepted version.
>
>------------------------------------------------------------------------
>
>------------------------------------------------------------------------------
>Subversion Kills Productivity. Get off Subversion & Make the Move to
>Perforce.
>With Perforce, you get hassle-free workflows. Merge that actually
>works.
>Faster operations. Version large binaries. Built-in WAN optimization
>and the
>freedom to use Git, Perforce or both. Make the move to Perforce.
>http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk
>
>------------------------------------------------------------------------
>
>_______________________________________________
>Darktable-users mailing list
>[email protected]
>https://lists.sourceforge.net/lists/listinfo/darktable-users
------------------------------------------------------------------------------
Subversion Kills Productivity. Get off Subversion & Make the Move to Perforce.
With Perforce, you get hassle-free workflows. Merge that actually works.
Faster operations. Version large binaries. Built-in WAN optimization and the
freedom to use Git, Perforce or both. Make the move to Perforce.
http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk
_______________________________________________
Darktable-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/darktable-users
