Project

General

Profile

Bug #11903

Export Problem

Added by B K 10 months ago. Updated 9 months ago.

Status:
New
Priority:
Low
Assignee:
-
Category:
Lighttable
Target version:
-
Start date:
01/01/2018
Due date:
% Done:

0%

Estimated time:
21.25 h
Affected Version:
2.4.0rc0
System:
Windows
bitness:
64-bit
hardware architecture:
amd64/x86

Description

Trying see if I will like this better than rawtherapee. When exporting, I only get a partial export...just the top of the picture. The rest is black. I'm running this on a brand new computer; amd A12 processor with Radeon R7 graphics. It works fine on my work laptop which is an Intel i5 and Intel 520 graphics. I've attached the xmp file and the exported jpg

IMG_0403 - Copy.CR2.xmp (1.76 KB) B K, 01/02/2018 04:13 AM

IMG_0403 - Copy_02.jpg (1.41 MB) B K, 01/02/2018 04:13 AM

IMG_0453.CR2.xmp (3.84 KB) B K, 01/04/2018 05:54 AM

IMG_0453.jpg (2.2 MB) B K, 01/04/2018 05:55 AM

IMG_0453.CR2 (22.9 MB) B K, 01/04/2018 05:55 AM

History

#1 Updated by B K 10 months ago

Should also note the system has 8GB of RAM installed.

#2 Updated by Peter Budai 10 months ago

Please upload the original RAW/CR2 file as well

#3 Updated by B K 10 months ago

My apologies...I thought I did. I don't have the original raw with me. Here's another example....xmp, cr2, and jpg

#4 Updated by Peter Budai 9 months ago

I have tried the supplied CR2 with the uploaded xmp, and was just working fine:

[dev] took 0.187 secs (0.188 CPU) to load the image.
[export] creating pixelpipe took 0.144 secs (0.172 CPU)
[dev_pixelpipe] took 0.000 secs (0.000 CPU) initing base buffer [export]
[dev_pixelpipe] took 0.047 secs (0.000 CPU) processed `raw black/white point' on GPU, blended on GPU [export]
[dev_pixelpipe] took 0.031 secs (0.000 CPU) processed `white balance' on GPU, blended on GPU [export]
[dev_pixelpipe] took 0.031 secs (0.000 CPU) processed `highlight reconstruction' on GPU, blended on GPU [export]
[dev_pixelpipe] took 0.078 secs (0.031 CPU) processed `hot pixels' on CPU, blended on CPU [export]
[dev_pixelpipe] took 0.243 secs (0.031 CPU) processed `demosaic' on GPU, blended on GPU [export]
[dev_pixelpipe] took 19.175 secs (2.062 CPU) processed `denoise (profiled)' on GPU, blended on GPU [export]
[dev_pixelpipe] took 0.240 secs (0.000 CPU) processed `exposure' on GPU, blended on GPU [export]
[dev_pixelpipe] took 0.164 secs (0.047 CPU) processed `base curve' on GPU, blended on GPU [export]
[dev_pixelpipe] took 0.171 secs (0.062 CPU) processed `input color profile' on GPU, blended on GPU [export]
[dev_pixelpipe] took 0.471 secs (0.188 CPU) processed `sharpen' on GPU, blended on GPU [export]
[dev_pixelpipe] took 0.165 secs (0.016 CPU) processed `output color profile' on GPU, blended on GPU [export]
[dev_pixelpipe] took 0.209 secs (0.141 CPU) processed `gamma' on CPU, blended on CPU [export]
[dev_process_export] pixel pipeline processing took 21.033 secs (2.578 CPU)
[export_job] exported to `C:\Users\peterbud\Pictures\Darktable/darktable_exported/IMG_0453.jpg'

If it works fine on your laptop, might be the Radeon GPU driver is the difference. Do you have OpenCL switched on? Or only using CPU? You can give a try and start darktable with -d perf command line parameter, and see what is in the the darktable-log file as described here:
https://www.darktable.org/about/faq/#faq-windows-logs

#5 Updated by B K 9 months ago

Open CL is enabled in darktable. Logs from the last attempt are below. It did work a couple times without any changes to the process, but then it stopped again. So it did work with the card at one point, but I don't know what was different at that time because I hadn't run it with the -d perf switch

========================================
version: darktable 2.4.0
start: 2018:01:04 20:44:39

[dev] took 0.237 secs (0.250 CPU) to load the image.
[export] creating pixelpipe took 0.219 secs (0.250 CPU)
[dev_pixelpipe] took 0.000 secs (0.000 CPU) initing base buffer [export]
[dev_pixelpipe] took 0.047 secs (0.000 CPU) processed `raw black/white point' on GPU, blended on GPU [export]
[dev_pixelpipe] took 0.094 secs (0.000 CPU) processed `white balance' on GPU, blended on GPU [export]
[dev_pixelpipe] took 0.031 secs (0.000 CPU) processed `highlight reconstruction' on GPU, blended on GPU [export]
[dev_pixelpipe] took 0.547 secs (0.062 CPU) processed `hot pixels' on CPU, blended on CPU [export]
[dev_pixelpipe] took 0.574 secs (0.000 CPU) processed `demosaic' on GPU, blended on GPU [export]
[dev_pixelpipe] took 25.890 secs (0.406 CPU) processed `denoise (profiled)' on GPU, blended on GPU [export]
[dev_pixelpipe] took 0.328 secs (0.000 CPU) processed `exposure' on GPU, blended on GPU [export]
[dev_pixelpipe] took 0.313 secs (0.000 CPU) processed `base curve' on GPU, blended on GPU [export]
[dev_pixelpipe] took 0.266 secs (0.000 CPU) processed `input color profile' on GPU, blended on GPU [export]
[dev_pixelpipe] took 0.641 secs (0.000 CPU) processed `sharpen' on GPU, blended on GPU [export]
[dev_pixelpipe] took 0.281 secs (0.000 CPU) processed `output color profile' on GPU, blended on GPU [export]
[dev_pixelpipe] took 6.313 secs (0.109 CPU) processed `gamma' on CPU, blended on CPU [export]
[dev_process_export] pixel pipeline processing took 35.341 secs (0.578 CPU)
[export_job] exported to `C:\Users\User\Pictures\Processed\IMG_0453_03.jpg'

#6 Updated by B K 9 months ago

Interesting note. I didn’t think about OpenCL until you mentioned it, but I turned it off and got some exports. The program also seems to be more responsive without it. CPU obviously spikes during an export, but he export process seems to be more reliable and faster without it. I know there’s multiple R7 versions, so maybe the version/driver I have is bugged? I’ll monitor and for a bit.

#7 Updated by Peter Budai 9 months ago

I believe not all OpenCL implementations are having the same maturity. Glad that the CPU path works for you (even though it might be slower)

Also available in: Atom PDF