"Yet people love them because marketing expenses make up for dev mediocrity and overall stupidity."
It's like VHS v Betacam or Windoze v Linux all over again! 😃 Cheers, Bruce Williams. ---------- Forwarded message --------- From: Aurélien Pierre <rese...@aurelienpierre.com> Date: Mon, 31 Aug 2020, 09:09 Subject: Re: [darktable-dev] idea to consider To: <darktable-dev@lists.darktable.org> 1. that still doesn't give you the jpeg cooking recipe, which is more complicated than building an ad-hoc LUT or a tonecurve if local filters are applied (and there are), 2. what is it with people editing jpegs ? That's nonsensical ! Not the same workflow, not the same maths, not the same filters, not the same pipeline, not the same software. A raw is an output-agnostic linearly encoded master picture that you can still salvage from the beginning, a jpeg is already non-linearly cooked for display assuming dim viewing conditions (as per sRGB standard) and firmware blackboxes. People need to stop dealing with image processing as if everyone was right and correctness didn't matter. It's not a silly magic game of pixels values, there are assumptions to assert underneath the hood. Sometimes I wish image processing could kill people, as civil engineering or medicine do, so people would start taking it seriously and check the theory behind before doing shit carelessly. That kind of silly workflow will blow up in your face 50 % of times because there is zero reliability in handling pre-baked jpegs with all the firmwares discrepancies in a software designed to unroll image operations on raw files. Then I will let you deal with users who don't understand why the workflow is so unpredictable. Indulging bad habits of users is not a solution, especially since we don't sell anything/whore ourselves out. Let's be rigorous about pixels operations and do things properly. Want to edit jpegs ? Use bloody Photoshop and the likes. They are good at doing shit, don't care about color consistency, don't care about light emissions, don't even do associated alpha occlusion properly. Yet people love them because marketing expenses make up for dev mediocrity and overall stupidity. Le 30/08/2020 à 17:05, Jason Polak a écrit : Another possibility is shooting Raw+JPEG. With this option you can still tune the JPEG engine in the camera somewhat with most models, and if you need to edit you can go to the Raw file. Also, you can make some minor edits directly on a JPEG file. Also, for people who are already working in JPEG, why would they suddenly switch to Raw format just to batch process Raw files to get what the camera would give them anyway? On 30/08/2020 08.22, Chris Shelton wrote: 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 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 set of jpg images in a similar way to the way jpg images are created by in-camera processing, maybe in the light table module; there would still be the option to work on a raw image as normal. ___________________________________________________________________________ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org ___________________________________________________________________________ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org ___________________________________________________________________________ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
