I reported a bug like this a while back. Some images would work and some would not. It was an Aquarius moment for me also. The difference between the working and not working images were the image canvas sizes that I assumed were the same because these images were created by another application in what I thought were identical image boundary conditions. That application is silverFast 8. I found I could reliably predict a non working image by examining the dimension numbers.
I noticed you mentioned your images are created from another application. Perhaps it is capable of producing strange image dimensions like silverFast 8 does. Years ago the application NoiseNinja would exhibit a crash behavior related to some image dimension situations. The developer acknowledged the issue in the application notes. In my case the error message seen in Hugin is true because the process step right before enblend fails to produce the intermediate image that enblend is to work on. For some arcane reason the cause was the dimension number, perhaps related to a division rounding. That process failure condition is not checked prior to assembling the commands sent to enblend, hence the enblend error message. It might seem ridiculous at first but surely the process before enblend is certainly not creating the file enblend is to be working on. Keep in mind "the computer is always right” when troubleshooting a computer situation. That “image0000.tif” did not get created. Hugin assumed it had without explicitly checking for the file. > On Aug 19, 2019, at 8:58 AM, Vegard Brenna <[email protected]> wrote: > > > >> On 19 Aug 2019, at 15:51, AKS-Gmail-IMAP <[email protected] >> <mailto:[email protected]>> wrote: >> >> >>> On Aug 19, 2019, at 8:21 AM, Vegard Brenna <[email protected] >>> <mailto:[email protected]>> wrote: >>> >>> >>>>> enblend: failed to open "image0000.tif": No such file or directory >>>> >>>> This could be a problem with file permissions, does Hugin have permission >>>> to write in the output folder? >>> >>> Since this varies by the time of day, the weather and whether Jupiter >>> aligns with Mars, I don't think this is the problem. It is random. But yes, >>> I've seen this exact problem with another app. >>> >> >> It could be related to one or both of the image dimensions being an odd >> number. Check the image dimensions and then shave it down by cropping it to >> slightly smaller but different dimensions. Try to get even numbers. > > Absolutely ridiculous, but cool! :D > I'll try when I've finished with Bruno's suggestions. > > Vegard Brenna > [email protected] <mailto:[email protected]> > > > > > > -- > A list of frequently asked questions is available at: > http://wiki.panotools.org/Hugin_FAQ <http://wiki.panotools.org/Hugin_FAQ> > --- > You received this message because you are subscribed to the Google Groups > "hugin and other free panoramic software" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected] > <mailto:[email protected]>. > To view this discussion on the web visit > https://groups.google.com/d/msgid/hugin-ptx/73411420-A1B0-4117-AE6B-16EC79384E61%40online.no > > <https://groups.google.com/d/msgid/hugin-ptx/73411420-A1B0-4117-AE6B-16EC79384E61%40online.no?utm_medium=email&utm_source=footer>. -- A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ --- You received this message because you are subscribed to the Google Groups "hugin and other free panoramic software" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/hugin-ptx/33C31FFF-D264-40A5-A595-34153ACA9FF2%40gmail.com.
