On 10/10/2013 11:20 PM, Patrick Shanahan wrote: > * Max Killer <[email protected]> [10-10-13 14:45]: >> On 10/08/2013 05:16 PM, Patrick Shanahan wrote: >>> Presently running darktable-1.3_1107_g83b15db_git-2.1.TM.x86_64. >>> >>> Adjusting denoise profiled strength, image displayed does not match >>> exported image. Exported image (jpg) shows much more noise at the same >>> display size. Makes it very difficult and time consuming to adjust noise >>> strength level to match desired viewing size for best quality. >>> >>> Or am I doing something wrong? >>> Screen size is 1920x1200 >>> >>> see screen dump @ >>> http://wahoo.no-ip.org/~pat/DarktableScreenshot.jpg >>> and jpg exported @ >>> http://wahoo.no-ip.org/~pat/130924_201112_dsd_7131_dt.jpg >>> >>> tks, >> Could you please upload a file for inspection together with the xmp? So >> we could have a look at the file and the output and try to reproduce.... > the original nef and the xmp file are at: > http://wahoo.no-ip.org/~pat/130924_201112_dsd_7131.nef > http://wahoo.no-ip.org/~pat/130924_201112_dsd_7131.nef.xmp > > note that I do not observe or have not observed the same situation with > today's issue: darktable-1.3_1111_g4995137_git-2.1.TM.x86_64 > > But, exporting *anything* with *any* noise reduction is now taking a lot > of time, not documented or timed, just impression. I know feelings are > relative and not subjective and the shots lately have been in increasingly > insufficient light. > > I work primarily documenting High School Soccer games and work on sets of > 700-1300 shots. And while I dislike some of the processing requirements > of darktable's workflow, the output from darktable is *much* better than > AfterShotPro release "Fri 28 Jun 2013 01:16:02 AM EDT" v1.2.0.7, which is > listed as the latest. And any of the earlier versions of "AfterShotPro". > It was much better when it was BibblePro5, but not as good as the current > Darktable. > > <rant> > Having to leave darkroom to lighttable to apply tags to current file is > ridiculous, especially when the current file in darkroom does not become > the current file or display in lightroot. And then having to return to > darkroom mode and not knowing for sure that the same or next file will be > displayed is really a problem when working *many* files in a group. > > But I have commented about this in the past. :^( > </rant> > > > I appreciate what I have and the developer's efforts to provide it. > Thankyou. > Hello,
the effect you observed is still present in the current git version, and I would be surprised if not. You were comparing two different things in your first email. You compared a "quick" resized image (dt viewport) with a full format export. What you can compare is the quick resized view to a same size export interpolated with the same interpolator. To make it short, if you _disable_ the high quality export and export the image to, lets say 1500x1500, the output is more or less the same. More or less because I didn't analyze it on the pixel level, but it looks the same. Please be aware that the image viewer you are using is also important. Eog for example uses another interpolator than geeqie (which I use mainly). Now to the conclusion: 1. Develop the images for the size you need them. If you need the full res images, check the view in 100% mode regularly. The zoomed out view uses an interpolator which can change the overall view. 2. "Play" with the options, for example full res output. This also depends on the iops used. Using high res output with your denoise settings shows a grainier image. As a side effect, the image now exports very fast... So long, hal ------------------------------------------------------------------------------ October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register > http://pubads.g.doubleclick.net/gampad/clk?id=60134071&iu=/4140/ostg.clktrk _______________________________________________ Darktable-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/darktable-users
