Re: [darktable-user] Can't find module Lens Correction
* André Felipe Carvalho [04-18-18 19:44]: > First, I really am thankful for all the help received. The "problem" was > solved. but you do not mention the solution, which was? -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.orgopenSUSE Community Memberfacebook/ptilopteri Registered Linux User #207535@ http://linuxcounter.net Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode darktable user mailing list to unsubscribe send a mail to darktable-user+unsubscr...@lists.darktable.org
Re: [darktable-user] Can't find module Lens Correction
First, I really am thankful for all the help received. The "problem" was solved. Now, some thoughts about the "world we live in": Am I to read the manual ? "man ldconfig", "man ldd"? Just to install something that should have already did the trick (lensfun installation. the problem here was not about dt directly), since I installed it with sudo ? That's Linux. That's the world we live in. One must know about everything, must compile things, must deal with compilations and installations of libraries and installations of installations of libraries ;-)) Don't get me wrong, I'm not pissed of ;-) I'm just thinking about how Linux is still hundred years behind the common user. My mom, for instance. Linux is for the braves. And, for being Linux, nothing really works as it should in every flavour it has. For instance, the ldd command did not work as expected in the case of Patrick Shaman. And he must be much more expert than me in Linux ;-)) You see? Happens with everyone. And we have to deal with it, since it's a world we seems to be building together while it spins. I'm a programmer, also. Java, wicket, html, that kind of stuff. And a linux fan and even more of dt. But ... sometimes... it's so hard to live in this world... Best regards, and thanks again! André (off topic: I'm dealing with making a TP-Link dongle 5ghz to work in my linux machine. At windows, it was a breese) 2018-04-18 11:29 GMT-03:00 Patrick Shanahan : > * Remco Viëtor [04-18-18 08:41]: > > On mercredi 18 avril 2018 14:03:03 CEST Patrick Shanahan wrote: > > > * Remco Viëtor [04-18-18 01:48]: > > > > On mercredi 18 avril 2018 05:40:28 CEST junkyardspar...@yepmail.net > wrote: > > > > > On Tue, Apr 17, 2018, at 18:45, André Felipe Carvalho wrote: > > > > > > I think I need to symlink the library to someplace dt expects. > But... > > > > > > why > > > > > > does it find the library at compilation time, but not when > executing? > > > > > > > > > > Are you sure /usr/local/lib is the right place to be installing on > your > > > > > system, as opposed to, say, /usr/lib64? > > > > > > > > Yes, /usr/local/lib is the usual place for locally installed > libraries. > > > > /usr/lib64 is supposed to hold the libraries installed by your > > > > distribution. And at least on my system, /usr/local/lib and > > > > /usr/local/lib64 are searched by default when loading dynamic > libraries. > > > > > > > > Perhaps it's a permission problem? On my system, all libraries are > marked > > > > as executable, so OP might need to do a > > > > > > > >"sudo chmod a+x /usr/local/lib/liblensfun.so*" > > > > > > why not just look at where the system is looking for dt's libs: > > > #> ldd /usr/bin/darktable > > > > > > or #> ldd > > > > > > then put the lib's in the appropriate place > > > > > > strongly suggest reading "man ldd" > > Small problem with using ldd: > > on my system (where Darktable works with the lensfun database enabled) > > "ldd /usr/bin/darktable | grep -i lens " returns exactly *nothing*. > > I don't know. on my openSUSE Tumbleweed system using darix' build, > /usr/lib64/darktable/plugins/liblens.so > > and there is no /usr/lib/darktable but there is /usr/lib64/darktable. and > dt was NOT installed by my distro, I installed it, and it did not go into > /usr/lib/... > > > > -- > (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri > http://en.opensuse.orgopenSUSE Community Memberfacebook/ptilopteri > Registered Linux User #207535@ http://linuxcounter.net > Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode > > > darktable user mailing list > to unsubscribe send a mail to darktable-user+unsubscribe@ > lists.darktable.org > > -- André Felipe https://www.flickr.com/photos/andrefelipecarvalho/ darktable user mailing list to unsubscribe send a mail to darktable-user+unsubscr...@lists.darktable.org
Re: [darktable-user] GPU advice 2GB or 4GB RAM.
Recently, after serious overheating on a portable system, I installed a Conky panel on my desktop to provide basic system information. I now get visuals on the cpu core loadings and temperatures. Good for my peace of mind. David On 04/18/2018 01:18 PM, Matthieu Moy wrote: > - Original Message - >> From: "frieder" > >> It is darktable 2.2.1 on Debian Linux the higest version I can get at >> the moment. > > You can compile the latest dt relatively easily on a Debian stable. > > You don't _have_ to, but each dt version comes with s many cool features > :-). > darktable user mailing list to unsubscribe send a mail to darktable-user+unsubscr...@lists.darktable.org
Re: [darktable-user] GPU advice 2GB or 4GB RAM.
- Original Message - > From: "frieder" > It is darktable 2.2.1 on Debian Linux the higest version I can get at > the moment. You can compile the latest dt relatively easily on a Debian stable. You don't _have_ to, but each dt version comes with s many cool features :-). -- Matthieu Moy https://matthieu-moy.fr/ darktable user mailing list to unsubscribe send a mail to darktable-user+unsubscr...@lists.darktable.org
Re: [darktable-user] GPU advice 2GB or 4GB RAM.
Am 18.04.2018 um 21:40 schrieb frieder: Am Mittwoch, den 18.04.2018, 18:13 +0200 schrieb Ulrich Pegelow: No, that's not what I would want to see (which version of darktable are you using). The final lines of the output should look something like: It is darktable 2.2.1 on Debian Linux the higest version I can get at the moment. OK, then '-d opencl -d memory' does not give information on GPU peak usage. That feature had been introduced with 2.4. My recommendation: if performance during export plays any role for you then you should go for the higher amount of GPU memory. Ulrich darktable user mailing list to unsubscribe send a mail to darktable-user+unsubscr...@lists.darktable.org
Re: [darktable-user] GPU advice 2GB or 4GB RAM.
Am Mittwoch, den 18.04.2018, 18:13 +0200 schrieb Ulrich Pegelow: > No, that's not what I would want to see (which version of darktable > are > you using). The final lines of the output should look something like: It is darktable 2.2.1 on Debian Linux the higest version I can get at the moment. > Did you combine '-d opencl' with '-d memory'? Yes I did. darktable user mailing list to unsubscribe send a mail to darktable-user+unsubscr...@lists.darktable.org
[darktable-user] passthrough demosaic
If the passthrough (monochrome) option is used in the demosaicing, are the rgb values 'normalized'? I still see grid-like signs that at higher resolutions. David darktable user mailing list to unsubscribe send a mail to darktable-user+unsubscr...@lists.darktable.org
Re: [darktable-user] GPU advice 2GB or 4GB RAM.
No, that's not what I would want to see (which version of darktable are you using). The final lines of the output should look something like: 8,290702 [opencl_summary_statistics] device 'GeForce GTX 1060 6GB' (0): peak memory usage 375014720 bytes 8,290722 [opencl_summary_statistics] device 'GeForce GTX 1060 6GB' (0): 164 out of 164 events were successful and 0 events lost Did you combine '-d opencl' with '-d memory'? Am 18.04.2018 um 14:07 schrieb frieder: Am Mittwoch, den 18.04.2018, 06:51 +0200 schrieb Ulrich Pegelow: This is what I did, and this is the output of the last lines with higest values: > [pixelpipe_process] [full] using device 0 [memory] before pixelpipe process [memory] max address space (vmpeak): 3066560 kB [memory] cur address space (vmsize): 2920820 kB [memory] max used memory (vmhwm ): 656232 kB [memory] cur used memory (vmrss ): 511540 kB [pixelpipe_process] [preview] using device -1 [memory] before pixelpipe process [memory] max address space (vmpeak): 3066560 kB [memory] cur address space (vmsize): 2920820 kB [memory] max used memory (vmhwm ): 656232 kB [memory] cur used memory (vmrss ): 511540 kB [pixelpipe_process] [thumbnail] using device 0 [memory] before pixelpipe process [memory] max address space (vmpeak): 3420044 kB [memory] cur address space (vmsize): 3415376 kB [memory] max used memory (vmhwm ): 656232 kB [memory] cur used memory (vmrss ): 523032 kB [pixelpipe_process] [export] using device 0 [memory] before pixelpipe process [memory] max address space (vmpeak): 3423124 kB [memory] cur address space (vmsize): 3415376 kB [memory] max used memory (vmhwm ): 656232 kB [memory] cur used memory (vmrss ): 523108 kB I have 6 GB main memory and 2 GB on CPU, so it seems darktable is using good half of main memory( ~ 3.2GB) and ~640MB on the GPU. Is this a corret interpretation? I was using a 12 Bit Raw of 16MB from an olympus camera. Btw. does "using device -1" for preview indicate, that CPU instead of GPU is used at all? Yes, device -1 stands for your CPU. Thanks, F. darktable user mailing list to unsubscribe send a mail to darktable-user+unsubscr...@lists.darktable.org
Re: [darktable-user] Can't find module Lens Correction
* Remco Viëtor [04-18-18 08:41]: > On mercredi 18 avril 2018 14:03:03 CEST Patrick Shanahan wrote: > > * Remco Viëtor [04-18-18 01:48]: > > > On mercredi 18 avril 2018 05:40:28 CEST junkyardspar...@yepmail.net wrote: > > > > On Tue, Apr 17, 2018, at 18:45, André Felipe Carvalho wrote: > > > > > I think I need to symlink the library to someplace dt expects. But... > > > > > why > > > > > does it find the library at compilation time, but not when executing? > > > > > > > > Are you sure /usr/local/lib is the right place to be installing on your > > > > system, as opposed to, say, /usr/lib64? > > > > > > Yes, /usr/local/lib is the usual place for locally installed libraries. > > > /usr/lib64 is supposed to hold the libraries installed by your > > > distribution. And at least on my system, /usr/local/lib and > > > /usr/local/lib64 are searched by default when loading dynamic libraries. > > > > > > Perhaps it's a permission problem? On my system, all libraries are marked > > > as executable, so OP might need to do a > > > > > >"sudo chmod a+x /usr/local/lib/liblensfun.so*" > > > > why not just look at where the system is looking for dt's libs: > > #> ldd /usr/bin/darktable > > > > or #> ldd > > > > then put the lib's in the appropriate place > > > > strongly suggest reading "man ldd" > Small problem with using ldd: > on my system (where Darktable works with the lensfun database enabled) > "ldd /usr/bin/darktable | grep -i lens " returns exactly *nothing*. I don't know. on my openSUSE Tumbleweed system using darix' build, /usr/lib64/darktable/plugins/liblens.so and there is no /usr/lib/darktable but there is /usr/lib64/darktable. and dt was NOT installed by my distro, I installed it, and it did not go into /usr/lib/... -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.orgopenSUSE Community Memberfacebook/ptilopteri Registered Linux User #207535@ http://linuxcounter.net Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode darktable user mailing list to unsubscribe send a mail to darktable-user+unsubscr...@lists.darktable.org
Re: [darktable-user] Can't find module Lens Correction
On mercredi 18 avril 2018 14:03:03 CEST Patrick Shanahan wrote: > * Remco Viëtor [04-18-18 01:48]: > > On mercredi 18 avril 2018 05:40:28 CEST junkyardspar...@yepmail.net wrote: > > > On Tue, Apr 17, 2018, at 18:45, André Felipe Carvalho wrote: > > > > I think I need to symlink the library to someplace dt expects. But... > > > > why > > > > does it find the library at compilation time, but not when executing? > > > > > > Are you sure /usr/local/lib is the right place to be installing on your > > > system, as opposed to, say, /usr/lib64? > > > > Yes, /usr/local/lib is the usual place for locally installed libraries. > > /usr/lib64 is supposed to hold the libraries installed by your > > distribution. And at least on my system, /usr/local/lib and > > /usr/local/lib64 are searched by default when loading dynamic libraries. > > > > Perhaps it's a permission problem? On my system, all libraries are marked > > as executable, so OP might need to do a > > > >"sudo chmod a+x /usr/local/lib/liblensfun.so*" > > why not just look at where the system is looking for dt's libs: > #> ldd /usr/bin/darktable > > or #> ldd > > then put the lib's in the appropriate place > > strongly suggest reading "man ldd" Small problem with using ldd: on my system (where Darktable works with the lensfun database enabled) "ldd /usr/bin/darktable | grep -i lens " returns exactly *nothing*. Remco darktable user mailing list to unsubscribe send a mail to darktable-user+unsubscr...@lists.darktable.org
Re: [darktable-user] GPU advice 2GB or 4GB RAM.
- Original Message - > From: "Robert William Hutton" > More memory is good because it allows you to process images through opencl > without tiling them, > which is a lot faster. Of course this depends on the resolution of the images > you need to process, > but I'd always try to get the most video ram possible. Also, at the risk of stating the obvious: more memory is more future-proof. More and more applications are using the GPU for acceleration (window-managers started doing so ~10 years ago, Firefox is working hard on it these days, ...), and camera RAW files are getting bigger and bigger. I don't think 2Gb is really limiting today, but it'd be a pity to save a few bucks today and regret it a few years from now. -- Matthieu Moy https://matthieu-moy.fr/ darktable user mailing list to unsubscribe send a mail to darktable-user+unsubscr...@lists.darktable.org
Re: [darktable-user] Can't find module Lens Correction
* Patrick Shanahan [04-18-18 08:06]: > * Remco Viëtor [04-18-18 01:48]: > > On mercredi 18 avril 2018 05:40:28 CEST junkyardspar...@yepmail.net wrote: > > > On Tue, Apr 17, 2018, at 18:45, André Felipe Carvalho wrote: > > > > I think I need to symlink the library to someplace dt expects. But... > > > > why > > > > does it find the library at compilation time, but not when executing? > > > > > > Are you sure /usr/local/lib is the right place to be installing on your > > > system, as opposed to, say, /usr/lib64? > > > > Yes, /usr/local/lib is the usual place for locally installed libraries. > > /usr/lib64 is supposed to hold the libraries installed by your > > distribution. > > And at least on my system, /usr/local/lib and /usr/local/lib64 are searched > > by > > default when loading dynamic libraries. > > > > Perhaps it's a permission problem? On my system, all libraries are marked > > as > > executable, so OP might need to do a > >"sudo chmod a+x /usr/local/lib/liblensfun.so*" > > why not just look at where the system is looking for dt's libs: > #> ldd /usr/bin/darktable > > or #> ldd > > then put the lib's in the appropriate place > > strongly suggest reading "man ldd" ps: and "man ldconfig" -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.orgopenSUSE Community Memberfacebook/ptilopteri Registered Linux User #207535@ http://linuxcounter.net Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode darktable user mailing list to unsubscribe send a mail to darktable-user+unsubscr...@lists.darktable.org
Re: [darktable-user] GPU advice 2GB or 4GB RAM.
Am Mittwoch, den 18.04.2018, 06:51 +0200 schrieb Ulrich Pegelow: > You may also run darktable with -d opencl -d memory, do some typical > stuff and then close darktable at which point it will tell you the > peak > usage of GPU memory. This is what I did, and this is the output of the last lines with higest values: [pixelpipe_process] [full] using device 0 [memory] before pixelpipe process [memory] max address space (vmpeak): 3066560 kB [memory] cur address space (vmsize): 2920820 kB [memory] max used memory (vmhwm ): 656232 kB [memory] cur used memory (vmrss ): 511540 kB [pixelpipe_process] [preview] using device -1 [memory] before pixelpipe process [memory] max address space (vmpeak): 3066560 kB [memory] cur address space (vmsize): 2920820 kB [memory] max used memory (vmhwm ): 656232 kB [memory] cur used memory (vmrss ): 511540 kB [pixelpipe_process] [thumbnail] using device 0 [memory] before pixelpipe process [memory] max address space (vmpeak): 3420044 kB [memory] cur address space (vmsize): 3415376 kB [memory] max used memory (vmhwm ): 656232 kB [memory] cur used memory (vmrss ): 523032 kB [pixelpipe_process] [export] using device 0 [memory] before pixelpipe process [memory] max address space (vmpeak): 3423124 kB [memory] cur address space (vmsize): 3415376 kB [memory] max used memory (vmhwm ): 656232 kB [memory] cur used memory (vmrss ): 523108 kB I have 6 GB main memory and 2 GB on CPU, so it seems darktable is using good half of main memory( ~ 3.2GB) and ~640MB on the GPU. Is this a corret interpretation? I was using a 12 Bit Raw of 16MB from an olympus camera. Btw. does "using device -1" for preview indicate, that CPU instead of GPU is used at all? Thanks, F. appendix: Open Cl initialisation on startup: -- darktable with -d opencl -d memory [memory] at startup [memory] max address space (vmpeak): 300852 kB [memory] cur address space (vmsize): 300852 kB [memory] max used memory (vmhwm ): 17600 kB [memory] cur used memory (vmrss ): 17600 kB [opencl_init] opencl related configuration options: [opencl_init] [opencl_init] opencl: 1 [opencl_init] opencl_library: '' [opencl_init] opencl_memory_requirement: 768 [opencl_init] opencl_memory_headroom: 300 [opencl_init] opencl_device_priority: '*/!0,*/*/*' [opencl_init] opencl_size_roundup: 16 [opencl_init] opencl_async_pixelpipe: 0 [opencl_init] opencl_synch_cache: 0 [opencl_init] opencl_number_event_handles: 25 [opencl_init] opencl_micro_nap: 1000 [opencl_init] opencl_use_pinned_memory: 0 [opencl_init] opencl_use_cpu_devices: 0 [opencl_init] opencl_avoid_atomics: 0 [opencl_init] opencl_enable_markesteijn: 1 [opencl_init] [opencl_init] could not find opencl runtime library 'libOpenCL' [opencl_init] could not find opencl runtime library 'libOpenCL.so' [opencl_init] found opencl runtime library 'libOpenCL.so.1' [opencl_init] opencl library 'libOpenCL.so.1' found on your system and loaded [opencl_init] found 2 platforms [opencl_init] could not get device id size: -1 [opencl_init] found 2 devices [opencl_init] device 0 `Oland' supports image sizes of 16384 x 16384 [opencl_init] device 0 `Oland' allows GPU memory allocations of up to 1304MB [opencl_init] device 0: Oland GLOBAL_MEM_SIZE: 1924MB MAX_WORK_GROUP_SIZE: 256 MAX_WORK_ITEM_DIMENSIONS: 3 MAX_WORK_ITEM_SIZES: [ 256 256 256 ] DRIVER_VERSION: 1800.11 (VM) DEVICE_VERSION: OpenCL 1.2 AMD-APP (1800.11) [opencl_init] compiling program `demosaic_ppg.cl' .. [opencl_load_program] loaded cached binary program from file `/home/frieder/.cache/darktable/cached_kernels_for_Oland/demosaic_ppg.cl.bin' [opencl_load_program] successfully loaded program from `/usr/share/darktable/kernels/demosaic_ppg.cl' [opencl_build_program] successfully built program [opencl_build_program] BUILD STATUS: 0 BUILD LOG: [] [opencl_init] kernel loading time: 0.0446 [opencl_init] discarding CPU device 1 `AMD Athlon(tm) 64 X2 Dual Core Processor 5600+'. [opencl_init] OpenCL successfully initialized. [opencl_init] here are the internal numbers and names of OpenCL devices available to darktable: [opencl_init] 0 'Oland' [opencl_init] these are your device priorities: [opencl_init] image preview export thumbnail [opencl_init] 0 -1 0 0 [opencl_init] FINALLY: opencl is AVAILABLE on this system. [opencl_init] initial status of opencl enabled flag is ON. darktable user mailing list to unsubscribe send a mail to darktable-user+unsubscr...@lists.darktable.org
Re: [darktable-user] Can't find module Lens Correction
* Remco Viëtor [04-18-18 01:48]: > On mercredi 18 avril 2018 05:40:28 CEST junkyardspar...@yepmail.net wrote: > > On Tue, Apr 17, 2018, at 18:45, André Felipe Carvalho wrote: > > > I think I need to symlink the library to someplace dt expects. But... why > > > does it find the library at compilation time, but not when executing? > > > > Are you sure /usr/local/lib is the right place to be installing on your > > system, as opposed to, say, /usr/lib64? > > Yes, /usr/local/lib is the usual place for locally installed libraries. > /usr/lib64 is supposed to hold the libraries installed by your distribution. > And at least on my system, /usr/local/lib and /usr/local/lib64 are searched > by > default when loading dynamic libraries. > > Perhaps it's a permission problem? On my system, all libraries are marked as > executable, so OP might need to do a >"sudo chmod a+x /usr/local/lib/liblensfun.so*" why not just look at where the system is looking for dt's libs: #> ldd /usr/bin/darktable or #> ldd then put the lib's in the appropriate place strongly suggest reading "man ldd" -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.orgopenSUSE Community Memberfacebook/ptilopteri Registered Linux User #207535@ http://linuxcounter.net Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode darktable user mailing list to unsubscribe send a mail to darktable-user+unsubscr...@lists.darktable.org