Images transferred from another computer showing as black box

Hello,

First off, thank you for this application. As someone who sparingly shoots, it is wonderful to have a powerful tool that doesn’t come at a steep price.

I am curious if there is a proper way to transfer my styles and LUTs to a new computer. While traveling in Europe, I had my laptop, which was enough to get me by. However, now that I am home I desire to use my much more powerful desktop (and 45" 4k monitor) to process the photos that I took.

Upon moving the photos to the desktop (including the .xmp metadata files), I found that select images were presenting as black squares rather than the displaying the photo. As we can see, the photo data is still there - the preview pane in top left and nav bar in the bottom both display it proudly:

I came to realize that this is because of either missing styles and/or LUTs. I received a notice ONCE upon loading a photo in darkroom, where it notified me that a LUT was missing, but I have not been able to reproduce that.

Unfortunately, exporting all styles from my Macbook causes DT to crash. As such, I dumped all styles from DB and imported to DT on my Linux machine. This appears to have worked fine, I can apply various styles and see that they are taking effect. Comparing style paths shows no difference, so I have a decent level of confidence that the transfer went off without a hitch. I also have come to conclusion that styles, being presets for built-in configuration settings, wouldn’t really have this effect if missing - the configuration options are the things that matter and I see those contained within the XMP files.

As such, I discerned that missing LUTs is probably the culprit. Accordingly, I tarred and moved the LUTs folder to the desktop, setting it (as it was on the Macbook) to the specific folder containing the LUTs.

However, the images remain black, even after an application restart.

I am curious if there is a happy path to take to restore the images with the edits that I had made earlier on the Macbook. Clearing edits from photos returns them to view, however that is less than ideal for obvious reasons.

If anyone has ideas, I am all ears :slight_smile:. If there are alternative approaches (for example, being able to discern the LUT applied to each photo for manual re-implementation), I’d be happy to run that down - I am very comfortable with the terminal. In fact, I did try running that down, but it doesn’t appear the .xmp files contain reference to the LUT used, only that a LUT was applied (or at least, that’s what I am assuming).

↪ rg lut -c
08-innsbruck/PA314840.ORF.xmp:1
01-warsaw/PA120298.ORF.xmp:1
11-venice/PB075625.ORF.xmp:2
11-venice/PB086203.ORF.xmp:1
...

↪ cat 08-innsbruck/PA314840.ORF.xmp | grep -i lut
   darktable:iop_order_list="rawprepare,0,invert,0,temperature,0,rasterfile,0,highlights,0,cacorrect,0,hotpixels,0,rawdenoise,0,demosaic,0,denoiseprofile,0,bilateral,0,rotatepixels,0,scalepixels,0,lens,0,hazeremoval,0,cacorrectrgb,0,ashift,0,overlay,0,enlargecanvas,0,flip,0,clipping,0,liquify,0,spots,0,retouch,0,exposure,0,mask_manager,0,tonemap,0,toneequal,0,crop,0,graduatednd,0,profile_gamma,0,equalizer,0,colorin,0,channelmixerrgb,0,censorize,0,primaries,0,negadoctor,0,blurs,0,nlmeans,0,colorchecker,0,defringe,0,atrous,0,lowpass,0,highpass,0,sharpen,0,lut3d,0,colortransfer,0,colormapping,0,channelmixer,0,basicadj,0,diffuse,0,colorbalance,0,colorequal,0,colorbalancergb,0,rgbcurve,0,rgblevels,0,basecurve,0,filmic,0,sigmoid,0,agx,0,filmicrgb,0,colisa,0,tonecurve,0,levels,0,shadhi,0,zonesystem,0,globaltonemap,0,relight,0,bilat,0,colorcorrection,0,colorcontrast,0,velvia,0,vibrance,0,colorzones,0,bloom,0,colorize,0,lowlight,0,monochrome,0,grain,0,soften,0,splittoning,0,vignette,0,colorreconstruct,0,colorout,0,clahe,0,finalscale,0,overexposed,0,rawoverexposed,0,dither,0,borders,0,watermark,0,gamma,0"
...

All told I think there are only about 50 impacted photos, so this isn’t the end of the world:

↪ rg lut -c | wc -l
50

However, I suspect I am being dense and there is an easy solution at hand that I am just unaware of - maybe? :slight_smile:

Thanks!
Jonathan

The history doesnt show any LUTs module, so I dont think that’s your problem. The image shows in the upper left corner but not in the main view. I think you should start the troubleshooting by turning off opencl. If that doesnt return the black image, then post the output from darktable -d common.

1 Like

Regrettably, disabling OpenCL did not resolve the issue.

Here is the output from darktable -d common:

↪ darktable -d common
darktable 5.4.0
Copyright (C) 2012-2025 Johannes Hanika and other contributors.

Compile options:
  Bit depth              -> 64 bit
  Exiv2                  -> 0.28.7
  Lensfun                -> 0.3.4
  Debug                  -> DISABLED
  SSE2 optimizations     -> ENABLED
  OpenMP                 -> ENABLED
  OpenCL                 -> ENABLED
  Lua                    -> ENABLED  - API version 9.6.0
  Colord                 -> ENABLED
  gPhoto2                -> ENABLED
  OSMGpsMap              -> ENABLED  - map view is available
  GMIC                   -> ENABLED  - Compressed LUTs are supported
  GraphicsMagick         -> ENABLED
  ImageMagick            -> DISABLED
  libavif                -> ENABLED
  libheif                -> ENABLED
  libjxl                 -> ENABLED
  LibRaw                 -> ENABLED  - Version 0.22.0-PreRC1
  OpenJPEG               -> ENABLED
  OpenEXR                -> ENABLED
  WebP                   -> ENABLED

See https://www.darktable.org/resources/ for detailed documentation.
See https://github.com/darktable-org/darktable/issues/new/choose to report bugs.

     0.0001 [dt starting]
 darktable -d common
     0.0001 application_directory: /usr/bin
     0.0001 darktable.datadir: /usr/share/darktable
     0.0001 darktable.plugindir: /usr/lib/darktable
     0.0001 darktable.localedir: /usr/share/locale
     0.0001 darktable.sharedir: /usr/share
     0.0002 darktable.configdir: /home/jweaver/.config/darktable
     0.0002 darktable.cachedir: /home/jweaver/.cache/darktable
     0.0002 darktable.tmpdir: /tmp
     0.0002 new_xdg_data_dirs: (null)
     0.1261 [dt_worker_threads] using 7 worker threads
     0.1433 [dt_configure_runtime_performance] found a sufficient 64-bit system with 63444 Mb ram and 24 cores
     0.1433 [dt_get_sysresource_level] switched to `default'
     0.1433   total mem:       63444MB
     0.1433   available mem:   31722MB
     0.1433   singlebuff:      495MB
     0.1433   mipmap cache:    7930MB
     0.1690 [opencl_init] opencl disabled via darktable preferences
     0.1691 [opencl_init] opencl library 'libOpenCL' found on your system and loaded, preference 'default path'
     0.1851 [opencl_init] found 1 platform
     0.1851 [check platform] platform 'NVIDIA CUDA' with key 'clplatform_nvidiacuda' is NOT active
[opencl_init] found 0 device
     0.1851 [opencl_init] FINALLY: opencl PREFERENCE=OFF is NOT AVAILABLE and NOT ENABLED.
     0.2610 [dt_worker_threads] using 7 worker threads

Please attach the log as a txt file after you at least open an image in the darkroom.

1 Like

Also, go ahead and take one image and start turning off modules one at a time starting from the top. Let see if that points us in the right direction.

2 Likes

I think I once had the same issue, and resetting the demosaic module fixed it in my case.

1 Like

I am more awake now. Lets use -d pipe along with -d common. The histogram and preview are showing but not the center view.

Also, how did you transfer the images from one PC to the other one? just the raw/xmp or you tried to move the library.db?

1 Like

Thank you to the both of you for your help.

Oddly enough, I had somewhat of the inverse behavior today - upon a fresh start of DT, problematic photos were showing fine in the main view and preview window (top left), but were not appearing in the darkroom bottom nav bar.

I cleared the demosaic module settings on one of the problematic images, and this fixed that image. I tested on a second image, and had the same result.

In an effort to capture logs in case this was a software bug or something that would be useful to the devs, I then closed darktable and re-opened it. Upon re-opening, all problematic images were now restored.

I’m not really sure what to make of this, but I am happy with the outcome.

FWIW, I transferred the images by tarring up the entire directory, which included RAWs and metadata files - nothing in the folder structure changed.

:man_shrugging:

One of my pet peeves is when problem resolve themselves without my understanding the fix, but I will simply take the win where I can!

Again, thanks for the help @g-man and @deekay! Here are a couple photos from my trip as a sign of my appreciation!

Budapest:

Prague:

2 Likes