Hi, thanks. 500 leads to ... [opencl_pixelpipe] couldn't copy image to opencl device for module colorin [opencl_pixelpipe] failed to run module 'colorin'. fall back to cpu path [opencl_pixelpipe (b)] late opencl error detected while copying back to cpu buffer: -5 [opencl] frequent opencl errors encountered; disabling opencl for this session! ...
lowering opencl_number_event_handles (!) leads to (tried 15 and 5) ... [opencl_pixelpipe] couldn't copy image to opencl device for module letsgofloat [opencl_pixelpipe] failed to run module 'letsgofloat'. fall back to cpu path [opencl_pixelpipe (b)] late opencl error detected while copying back to cpu buffer: -5 [opencl] frequent opencl errors encountered; disabling opencl for this session! [pixelpipe_process] [full] falling back to cpu path ... I have no idea what I'm talking about, but given the strange colour effects I see on screen, it apperas to me as if darktable was trying to write stuff into parts of the GPUs memory that should actually be handling the display...? Jonas On 01.06.2015 19:53, Ulrich Pegelow wrote: > You could try an even higher values of opencl_memory_headroom of 500. > > If this does not help please try with lower settings for > opencl_event_handles. > > Ulrich > > Am 31.05.2015 um 23:37 schrieb joeni: >> Hi, >> >> thanks. Tried that. Same, or similar, result (and I'm seeing colour >> effects where parts of some lines of pixels anywhere on the screen turn >> strange colours) >> ------------------------------------------------------------------------------ _______________________________________________ darktable-devel mailing list darktable-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/darktable-devel
