Re: [darktable-user] OpenCL intermittant

2020-04-04 Thread angrypixel
I get the following output using the latest version (3.0.1-1) in the arch repos:

0.187739 [opencl_init] opencl related configuration options:
0.187748 [opencl_init]
0.187753 [opencl_init] opencl: 1
0.187755 [opencl_init] opencl_scheduling_profile: 'default'
0.187758 [opencl_init] opencl_library: ''
0.187761 [opencl_init] opencl_memory_requirement: 768
0.187765 [opencl_init] opencl_memory_headroom: 300
0.187767 [opencl_init] opencl_device_priority: '*/!0,*/*/*'
0.187770 [opencl_init] opencl_mandatory_timeout: 200
0.187772 [opencl_init] opencl_size_roundup: 16
0.187775 [opencl_init] opencl_async_pixelpipe: 0
0.18 [opencl_init] opencl_synch_cache: false
0.187779 [opencl_init] opencl_number_event_handles: 25
0.187782 [opencl_init] opencl_micro_nap: 1000
0.187785 [opencl_init] opencl_use_pinned_memory: 0
0.187786 [opencl_init] opencl_use_cpu_devices: 0
0.187788 [opencl_init] opencl_avoid_atomics: 0
0.187790 [opencl_init]
0.187882 [opencl_init] could not find opencl runtime library 'libOpenCL'
0.187924 [opencl_init] could not find opencl runtime library 'libOpenCL.so'
0.187970 [opencl_init] could not find opencl runtime library 'libOpenCL.so.1'
0.187975 [opencl_init] no working opencl library found. Continue with opencl 
disabled
0.187976 [opencl_init] FINALLY: opencl is NOT AVAILABLE on this system.
0.187979 [opencl_init] initial status of opencl enabled flag is OFF.

I do have the opencl-mesa package installed :/

On 4/4/20 7:12 PM, David Vincent-Jones wrote:

> darktable 3.1.0+1076~g6b08bc9a9   Manjaro/Arch/XFCE
> I use the git verson of dt that I update every couple of days. Sometimes 
> OpenCL starts after an update and sometimes not. Since nothing else in my 
> system is changing I am wondering why I am getting this intermittent 
> behavior. Would adding a greater allocation of memory help .. my setup is 
> simply the default.
>
> Is anybody else seing this problem?
>
> [david@dell ~]$ darktable -d opencl
> 0.062803 [opencl_init] opencl related configuration options:
> 0.062811 [opencl_init]
> 0.062812 [opencl_init] opencl: 1
> 0.062813 [opencl_init] opencl_scheduling_profile: 'default'
> 0.062815 [opencl_init] opencl_library: ''
> 0.062816 [opencl_init] opencl_memory_requirement: 768
> 0.062817 [opencl_init] opencl_memory_headroom: 400
> 0.062818 [opencl_init] opencl_device_priority: '*/!0,*/*/*/!0,*'
> 0.062820 [opencl_init] opencl_mandatory_timeout: 200
> 0.062821 [opencl_init] opencl_size_roundup: 16
> 0.062822 [opencl_init] opencl_async_pixelpipe: 0
> 0.062823 [opencl_init] opencl_synch_cache: active module
> 0.062824 [opencl_init] opencl_number_event_handles: 25
> 0.062825 [opencl_init] opencl_micro_nap: 1000
> 0.062826 [opencl_init] opencl_use_pinned_memory: 0
> 0.062827 [opencl_init] opencl_use_cpu_devices: 0
> 0.062828 [opencl_init] opencl_avoid_atomics: 0
> 0.062829 [opencl_init]
> 0.062958 [opencl_init] found opencl runtime library 'libOpenCL'
> 0.062969 [opencl_init] opencl library 'libOpenCL' found on your system and 
> loaded
> 0.064279 [opencl_init] could not get platforms: -1001
> 0.064284 [opencl_init] FINALLY: opencl is NOT AVAILABLE on this system.
> 0.064285 [opencl_init] initial status of opencl enabled flag is OFF.
> David
>  
> darktable user mailing list to unsubscribe send a mail to 
> darktable-user+unsubscr...@lists.darktable.org

darktable user mailing list
to unsubscribe send a mail to darktable-user+unsubscr...@lists.darktable.or

[darktable-user] How to add/tweak support for Olympus OM-D EM5 Mark3

2020-03-08 Thread AngryPixel
Hi!

I just wanted start with saying thanks for all the work you guys have put in to 
this great piece of software. Ok, now to the issue at hand.

I recently got myself a Olympus OM-D EM5 Mark 3 and all the raw files it 
produces have a de-saturated washed out look. No matter how I tweak the color 
white balance.  I can't get it to right colors I see IRL.

I'm currently guessing that there some missing information for this camera? 
I've checked with both Lightroom and RawTherapee and neither seem to suffer 
from this issue.

I've previously used a Sony a6000 and while there was usually a difference 
between the jpeg and raw, it wasn't as bad as the current case.

I've read the contents of 
https://www.darktable.org/2012/10/whats-involved-with-adding-support-for-new-cameras/
 and it seems that I have no choice but to procure a color target and then 
process that information.

That being said, according to online reviews and analysis it seems that the EM5 
Mark3 is basically a mini EM1 Mark2. I was wondering if someone could tell me 
what I need to "trick" Darktable into treating raw files from the EM5 Mark3 as 
originating from EM1 Mark2?

Failing that, is there anything I can do to address this issue? Raw & jpeg can 
be found here 
https://send.firefox.com/download/2578eb97df3378aa/#mJKcFP_USSs24-kp92hRVg 
(valid for 1 day)

Regards

darktable user mailing list
to unsubscribe send a mail to darktable-user+unsubscr...@lists.darktable.or