Hi, short addition to what you have described. The symptom of failed tiling for the shadhi module is known and is caused by the potentially high blur radius. Tiling means that darktable processes the whole image in small chunks/tiles. Between these tiles we need an overlap area to avoid border artifacts. The size of this overlap is governed by the module in question. For shadhi it is higher the bigger the blur radius.
If darktable needs to split the image into many small tiles and if you have a high blur radius almost the complete tile consists of overlap area and no or virutally no useable area remains. This is detected by darktable and tiling is stopped. As a fallback darktable then tries to process the image in one step - and either it works or darktable crashes. Normally having more RAM will only improve the situation in terms of speed (less swapping needed to the HDD); it will not improve the issue described above. Still there are a few options for you to test: a) if you are on a 64-bit system then all you need to do is change the "host memory limit" core option to 1500. This will avoid tiling because it's not needed with 64-bit. Migrating to a 64-bit system is strongly recommended if you want to do serious work with darktable. b) if you are on a 32-bit system you might try to slightly increase the same option to something like 600 or 700. This way tiles get larger and the useable part of tiles gets bigger. You need to try out various values also with history stacks using modules like "equalizer". In the worst case of a too high value darktable crashes due to out-of-memory. c) you may start darktable with '-d dev' and look for the output during export. You will see statistics on tiling. Look for the number of tiles (rows x columns) darktable thinks it needs for shadhi. If the number is high but still reasonable (maybe a few thousands at max) you may increase config parameter maximum_number_tiles from its default 500. This option is mainly meant to allow processing of huge images like panoramas. Hope this helps. Ulrich Am 25.10.2013 18:07, schrieb Samir Rahman: > I have some coming in soon to upgrade my system to 6GB. I'll come back > to tell what ends up happening. This export time issue is really the > only issue in my workflow. If it gets dealt with, than I'm set! Thanks > for the help. > > > > On Friday, October 25, 2013 12:03 PM, Ian Christie > <[email protected]> wrote: > Most likely you could use more RAM. The more, the better. I know how you > feel, I only have 2GB in my system running Ubuntu 12.04. > > --Ian > Sent from my BlackBerry device on the Rogers Wireless Network > > -----Original Message----- > From: Samir Rahman <[email protected] <mailto:[email protected]>> > Date: Fri, 25 Oct 2013 08:53:30 > To: [email protected] > <mailto:[email protected]><[email protected] > <mailto:[email protected]>> > Reply-To: Samir Rahman <[email protected] > <mailto:[email protected]>> > Subject: [Darktable-users] Fw: Problem Exporting Images > > ------------------------------------------------------------------------------ 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=60135991&iu=/4140/ostg.clktrk _______________________________________________ Darktable-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/darktable-users
