Am Sonntag, 27. November 2016, 11:17:27 CET schrieb David Vincent-Jones: > Problem appears to emulate from the cropping .... is there a way to read > the crop values from the sidecar?
Not easily. And in order to get a crop size in pixels instead of percent you need to run the whole pipeline. On the actual image. > David Tobias > On 11/25/2016 01:28 AM, Matthieu Moy wrote: > > ----- Original Message ----- > > > >> I sometimes find that after processing my images get pixelised on the > >> lighttable. If I zoom in or out the problem remains but it is not > >> creating > >> problems on the final output. .... anybody else see this? > > > > If you look closely, you'll see that it's not pixelization : you do see > > large squares, but there are details inside these squares (as opposed to > > a large pixel which obviously doesn't). > > > > This looks very much like an interference pattern due to resizing (e.g. > > subsampling with an "almost integer" factor which results in sampling > > always the R pixels of your sensor for a while, then only the B pixels, > > ...). It's probably not a coincidence that the pattern you see on the > > image is the same as the color pattern on your camera's color filter > > array. > > > > Unfortunately, I don't know the algorithms enough to give a real > > diagnosis, and even less a solution :-(. If you're looking for a > > combination of modules, I'd look at the crop module (the crop factor may > > be the one giving you the "almost integer" factor), and the demosaic > > module. > ____________________________________________________________________________ > darktable user mailing list > to unsubscribe send a mail to [email protected]
signature.asc
Description: This is a digitally signed message part.
