On May 23, 5:17 am, Tom Glastonbury <[email protected]> wrote: > On 22/05/2010 11:11 PM, dex Otaku wrote:> Had no problems with your first > posted binaries until the current, > > Hugin-2010.1.0.645a8acc3d37-PreRelease-Win-x64-20100517, which has > > this issue [here]. > > Can you confirm that going back to one of my earlier builds still works > fine, and can you work out the simplest test case that reliably > reproduces this problem? Eg, load one arbitary image, save project - > takes 30 seconds.
At somewhat of a loss here. I've tried your builds 5145 and 5154 as well as 645 .. they now -all- do the same thing. I can't help but feel this has something to do with my machine [or more likely, installation of Windows] in particular, given that everything was working normally and then it turned. Notes: * it depends on the size of the project file, or more precisely, it seems to depend on the number of control points in it. Very small panos save quickly without a problem. My 36+ image spherical panos take 20-30 seconds to save. * I've been looking at the results of saving a file in Hugin with sysinternals process monitor: I'm not an expert on the info it can give but other than constant "FAST IO DISALLOWED" messages for every write made, nothing weird appears to be happening. Last example: saved at 11:57:08.xx and there's a gap between a number of initial writes and it starting to finish the job at 11:57:34.xx. At both times the actual writing job is less than .5 sec in length. * other processes occurring during the gap in saving are not consistent [across logging events during 10 saves], so it would appear that the issue isn't something else that's running * this all started after i upgraded versions .. which also caused an issue with Windows' "open with" menu, not allowing me to point the association for .pto files at hugin. I tried deleting all hugin- related registry entries and starting over again with the last installer version available [2009.10] among other things, but nothing except forcing the association with 3rd party tools [the equivalent of editing the registry entries directly] would work. It's almost as though the path Hugin is at got poisoned somehow by overwriting the binaries in place. * running as an administrator [with the thinking that this may be a permissions issue] does not change anything. Again, it would appear this has something to do with my machine/ Windows install, not Hugin. No idea what to try now. D -- You received this message because you are subscribed to the Google Groups "hugin and other free panoramic software" group. A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/hugin-ptx
