I’m new to darktable but have used the stand alone Hugin program for several years. I added git for windows and cloned in the lua scripts and added the required code to the luarc file. Hugin shows up as an export choice and when I sent it several images to create a panorama darktable indicates that it is exporting image 1 of 3, 2 of 3, 3 of 3. then there is a flash of the pto and the image assistant. But when it is finished I don’t see a "fused.tif image file. When I ask to open the gui, it opens put I don’t see any of the exported images as when I run it stand alone. Just to check I ran the stand alone program and it ran as usual. Is anyone able to use the hugin lua script with the current version of windows 10?
If you use the gui, then go to Add Image in the Edit menu and select the images you want to stitch. When the file selector window opens, the exported files should be there. Stitch them as you normally would, accepting the suggested filenames. When hugin is done stitching, just close the hugin windows. The stitched file should be imported into the collection.
I’ll look at why the files aren’t showing up in the gui. We’re still learning the ins and outs of spawning programs on windows so maybe it’s time to revisit this and see if anything I’ve learned since the last time will help.
Bill
I use hugin.lua in linux. Here I can choose to start Hugin gui at the point shown by the image. After that Hugin opens up and I can use it in the normal way.
thank you now I have it working.
thank you, now I have it working and the fused tiff showed up just fine. Now I’m back in the fused exposure-panorama work flow all within Darktable.
1 Like
I thought it was working but I reread you response and the exported files are not there in the add image and it’s not re-importing them back. I have been using the enfuse_pro_2 lua script, which also link to several files in the hugin directory and with that I can select file from the lighttable, they get exported into the enfuse program, processed, and re-import the result back into darktable. Back to the hugin script: after the export several black windows flash momentarily and I only have time to read “can’t open” before it closes. I guess I was hoping to use the hugin lua script more automatically otherwise I could just use hugin manually as I have been doing for the last several years. Where would I find the darktable error log from these hugin runs? I like to see why it cannot open the exported images.
run darktable from the command line with
“C:\Program Files\darktable\bin\darktable.exe” -d lua > log.txt
and that will output the debugging messages in log.txt.
Semiautomatic:
Save in hugin to same folder where are the originals. In Darktable re-open folder.