Jack,
Thank you for the clarification. What I wanted to add is that, for the little use I had in dt 4.2, the response time seems OK as-is on my laptop (* configuration details below). My point below was for the response time of the darkroom preview window for dt 4.0. If it works, automated CPU versus GPU resources optimization is certainly welcome. I became aware of this when demonstrating and presenting dt to my friends amateur photographers. For the majority amongst them changing such settings in darktablerc is a difficult obstacle to overcome. So I hope this matter gets cleared for you. The updates to the manual surely can wait till dt 4.4. Regards and happy holidays, Marc. * PS: Laptop configuration CPU : Intel Core i9-9880H Memory : 32 GB Graphics card : NVIDIA GeForce RTX 2080 with Max-Q Design Op vr 30 dec. 2022 02:46 schreef Jack Bowling <jbi...@shaw.ca <mailto:jbi...@shaw.ca> >: On 2022-12-29 12:56, <mailto:marc.ca...@gmail.com> marc.ca...@gmail.com wrote: Dear advanced Users, In dt 4.0 (on Windows) I had tuned the opencl_device_priority in the darktablerc file to ensure that the middle darkroom view and the extra darkroom preview window were executed in the GPU by setting opencl_device_priority=+0,*/!0,*/*/+0,*/+0,*. This worked OK and with a far better response for the darkroom preview window. I have the impression that in dt 4.2 (on Windows) the opencl_device_priority doesn’t influence this anymore like specified in the manual. What I now seem to observe is that the non-zoomed version of the middle darkroom view is fully (re-)calculated in the CPU, the non-zoomed version of the darkroom preview window seems to be partially (re-)calculated in CPU and GPU. Once zooming to 50% or more is done, the GPU jumps in for both the middle darkroom view and the darkroom preview window. Perhaps these opencl_device_priority parameters became obsolete ? So far I don’t have a need to influence/tune this, but this perhaps may be updated in the manual ? Any clarification would be welcome, Thanks, Marc. ____________________________________________________________________________ darktable user mailing list to unsubscribe send a mail to <mailto:darktable-user+unsubscr...@lists.darktable.org> darktable-user+unsubscr...@lists.darktable.org There was an opencl initialization change by developer hanno schwalm a couple of weeks ago which likely impacted this. The intent as far as I understand it was to better automate the opencl settings at dt instantiation. Not sure it was a good idea since my previously working nvidia card is now disabled with an unknown error at dt startup :( Still working that one out. Jack ____________________________________________________________________________ darktable user mailing list to unsubscribe send a mail to <mailto:darktable-user%2bunsubscr...@lists.darktable.org> darktable-user+unsubscr...@lists.darktable.org ____________________________________________________________________________ darktable user mailing list to unsubscribe send a mail to darktable-user+unsubscr...@lists.darktable.org
