Hi,
Am 30.08.20 um 14:22 schrieb Chris Shelton:
Some photographers work in jpg only and sometimes I would not
question their creative ability while maybe questioning the
technical choice although I suppose they do avoid the mistake of
overworking and gilding the lily
jpeg is usually preferred when (non exhaustive list):
* users do not want to invest time to lean how to process raw images.
* user see no benefit of raw processing for their use-cases, i.e., they
are just happy with out-of-cam jpegs.
* time constrains do not allow raw processing (photo journalism).
* customers require out-of-cam jpegs (photo journalism).
I thought that the appeal of Darktable could be expanded to include
people like this by having a facility whereby raw images are batch
processed to create a set of jpg images in a similar way to the
way jpg images are created by in-camera processing,
As Aurélien already explained this is not feasible for many reasons. It
would require a tremendous investment in reverse engineering for each
camera model, which usually comes with several picture profiles. It
appears, however, that there is barely a real-world use case for such an
out-of-cam jpeg emulation. Users, who really want the jpegs while still
having the option to tune an image in a raw processor, shoot in raw+jpeg.
Regards,
Heiko
--
-- Number Crunch Blog @ https://www.numbercrunch.de
-- Cluster Computing @ https://www.clustercomputing.de
-- Social Networking @ https://www.researchgate.net/profile/Heiko_Bauke
___________________________________________________________________________
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
