Sorry, I misread your comments, looks like you did not say it failed. In
response to your listed issues:
1) I am aware that lens distortion always throws that error, though I don't
know why. For now I just suggest applying lens distortion correction in dt,
either to the source images or the output image
2) I hadn't noticed this before, thank you! There is a significantly
reworked version of this script in progress and these elements have been
removed. So once the new version is merged in to git this will be a
non-issue. Regardless, I appreciate the feedback.
On Fri, Mar 22, 2019 at 10:38 AM Kevin Ertel <ker...@g.clemson.edu> wrote:
> Did the alignment actually fail, or that was just a warning that showed?
> When I run this I always get that warning, but that does not mean the
> alignment actually failed. If the script continued and ran enfuse, then
> imported the image then alignement did NOT fail, and that was just a
> warning for align image stack that it couldn't find lens distortion data.
> You can disable the "optimize lens distortion" option and this warning
> shouldn't show up any more.
>
> I'd suggest apply lens distortion correction to the resultant image in dt
> anyway. Alternately you can apply it to all the source images through dt
> prior to export as well. either way is sufficient.
>
> On Wed, Mar 13, 2019 at 2:08 PM Christian <chris66...@gmx.de> wrote:
>
>> Thanks William,
>>
>> it's working now with small issues.
>>
>> My faults:
>>
>> - wrong script, enfuseAdvanced is fine
>> - did not copy all scripts to lua/official
>>
>> Issues:
>>
>> - Alignement did not work fine ("No valid distortion data found in lens
>> database")
>>
>> - Typos, see: https://up.picr.de/35270979mb.jpg
>>
>> Chris
>>
>>
>> Am 13.03.2019 um 17:37 schrieb William Ferguson:
>>
>> > contrib/enfuseAdvanced is a reworked copy of enfuse_pro that is
>> included
>> > in the repository and works on windows. enfuse_pro may not work on
>> > windows because it was written prior to darktable being able to run on
>> > windows. Since darktable has been able to run on windows, we (the
>> > lua-script developers and maintainers) have spent a lot of time and
>> > effort getting the scripts to be cross platform. The README in the lua
>> > scripts repository shows platform compatibility for each of the scripts.
>> >
>> >
>> > anyway, print-commands in luarc giving no output to the
>> windows-console
>> > seems to be a little bug.
>> >
>> > try redirecting the output to a file, i.e. darktable -d lua > log.txt
>> >
>> >
>>
>> ___________________________________________________________________________
>> darktable developer mailing list
>> to unsubscribe send a mail to
>> darktable-dev+unsubscr...@lists.darktable.org
>>
>>
___________________________________________________________________________
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
