[hugin-ptx] Re: Typo in en.po
Is you will lost correct? --- The list contains not processed possible panorama.\n If you close the dialog, you will lost them.\n Continue anyway? -- 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 hugin-ptx@googlegroups.com To unsubscribe from this group, send email to hugin-ptx+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/hugin-ptx
Re: [hugin-ptx] why is vertical line detection so hard?
At one point, during the automatic lens correction summer of code project, Tim had a working tool for detecting vertical lines and creating a .pto script for levelling. It didn't work for all projections, but I think the ideal command-line tool would just work with single equirectangular files and calculate the roll,pitch,yaw rotation for correction. -- Bruno -- 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 hugin-ptx@googlegroups.com To unsubscribe from this group, send email to hugin-ptx+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/hugin-ptx
Re: [hugin-ptx] Re: hugin Fast Panorama preview code for a lot faster stitching?
Regarding speeding up stitching with nona, there has been very little optimisation of the code over the years. For instance nona still does a full panorama calculation for every pixel in the output, where it could easily interpolate most of these values. -- Bruno -- 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 hugin-ptx@googlegroups.com To unsubscribe from this group, send email to hugin-ptx+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/hugin-ptx
Re: [hugin-ptx] why is vertical line detection so hard?
Where to find the tool? How to reach Tim? Jan On Sat, Dec 18, 2010 at 11:28 AM, Bruno Postle brunopos...@googlemail.comwrote: At one point, during the automatic lens correction summer of code project, Tim had a working tool for detecting vertical lines and creating a .pto script for levelling. It didn't work for all projections, but I think the ideal command-line tool would just work with single equirectangular files and calculate the roll,pitch,yaw rotation for correction. -- Bruno -- 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 hugin-ptx@googlegroups.com To unsubscribe from this group, send email to hugin-ptx+unsubscr...@googlegroups.comhugin-ptx%2bunsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/hugin-ptx -- http://www.DIY-streetview.org -- 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 hugin-ptx@googlegroups.com To unsubscribe from this group, send email to hugin-ptx+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/hugin-ptx
[hugin-ptx] Re: Blending very large numbers of files
Okay, third one in a row. With a bit more guesswork I've managed to stitch a reasonable product. this looks fine without any vignetting correction, which fits well with my initial judgement that the slight background brightness variations should be hardly noticable in the output. I have a suspicion about the source of your brightness variations. I suspect you have not masked out the bright spots that occur in one corner of every plate. These are often white, sometimes orange, sometimes mulicoloured, and it is seemingly arbitrary in which corner they occur. I did a trial stitch where I did not mask them out and the result looked quite like http://www.google.com/url?sa=Dq=http://porpoisehead.net/images/dss_blend_needed.jpgusg=AFQjCNEp9PMwvLRVsiuPw76sGDXRLE9AUw When I did mask the bright corners out (manually did that for 100 images around the N pole, where is N001, anyway?) the brightness fluctuations were gone. Please doublecheck if this is maybe the cause of your problem. Keep in mind that a multi-resolution blender (like enblend) will produce the seeming 'bleeding' of bright areas to surrounding areas, so their effect extends beyond the extent of the bright area. with regards Kay -- 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 hugin-ptx@googlegroups.com To unsubscribe from this group, send email to hugin-ptx+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/hugin-ptx
Re: [hugin-ptx] Re: hugin Fast Panorama preview code for a lot faster stitching?
Bruno, care to estimate what kind of speed improvement optimizing the code would be good for? What would it need to get it done? Who is qualified to do it? Jan On Sat, Dec 18, 2010 at 11:59 AM, Bruno Postle brunopos...@googlemail.comwrote: Regarding speeding up stitching with nona, there has been very little optimisation of the code over the years. For instance nona still does a full panorama calculation for every pixel in the output, where it could easily interpolate most of these values. -- Bruno -- 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 hugin-ptx@googlegroups.com To unsubscribe from this group, send email to hugin-ptx+unsubscr...@googlegroups.comhugin-ptx%2bunsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/hugin-ptx -- http://www.DIY-streetview.org -- 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 hugin-ptx@googlegroups.com To unsubscribe from this group, send email to hugin-ptx+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/hugin-ptx
Re: [hugin-ptx] Re: hugin Fast Panorama preview code for a lot faster stitching?
I've no idea how easy it is to speed up nona. Code optimisation should always follow profiling, but this is straightforward with nona as it only does one thing. -- Bruno -- 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 hugin-ptx@googlegroups.com To unsubscribe from this group, send email to hugin-ptx+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/hugin-ptx
Re: [hugin-ptx] Re: hugin Fast Panorama preview code for a lot faster stitching?
On 18 December 2010 16:22, Jan Martin janmar...@diy-streetview.org wrote: Bruno, care to estimate what kind of speed improvement optimizing the code would be good for? What would it need to get it done? Who is qualified to do it? Jan I think it would be quite difficult. I remeber I looked at the nona code quite some time ago (bit it didn't really change since that time). Most of the code is generated at compile time from templates so sometimes it's a bit difficult to really understand what it does and especially how to optimize it. But I guess that a big slowdown is caused by vigra. Yeah, it allows to write completelly generic code like the nona code is but for a price. I know it from my experiments with hugin deghosting. Vigra's types are due to extensive polymorphism usage slow, even the simple ones like RGBsomethingsomething (I had too much vine to remeber that) or vector types like tinyvector. Also the reason of the slowdown is operator overloading. As I said, it allows you to write generic code but at a price. For example you can do things like a + b and it translates to a + b for one component data (eg. grayscale image) or (a[0] + b[0], a[1] + b[1], a[2] + b[2]) for RGB or Lab or whatever type which is a 3-component vector. The problem is code generated by the compiler when you add more together. For example a * b + c is, for three component data, implemented as somethinglike for (i=0; i 3; i++) tmpres[i] = a[i] + b[i] for (i = 0; i 3; i++) res[i] = tmpres[i] + c[i] You can see that there these loops can be shrinked to one, but compiler won't do this. But there are some possibilities how to make compiler to make it in one loop but it's a black magic. If you implement all this manually (ie. you implement different code for vector types and scalar types) you can gain quite some speed but I wouldn't like to mutilate nona - this code is just too sexy. ciao, Lukas -- 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 hugin-ptx@googlegroups.com To unsubscribe from this group, send email to hugin-ptx+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/hugin-ptx
[hugin-ptx] Magnifier in control point editor panel
I have already noticed a 'strange' behaviour of the magnifier in the control point editor panel ( but never understood it ). Today I loaded in hugin a few astronomical images ( see thread [1] ), and while adding a few cp I noticed that when the magnifier was positioned on the dark background ( no bright stars in the fov of the magnifier ) it showed a 'bright and dark texture', I couldn't understand where it came from. Searching in the code found that before being displayed the magnifier is 'contrast enhanced' ( the darkest part of the image is converted to back, the brightest part is converted to 255, max brightness ). This is to help identifying 'features' in the images. But when the magnifier is placed on a low contrast part of the image ( a generic image, not the astronomical image I refered above ) this amplification ( contrast enhancement ) could be very high and this seems a little bit confusing to me ( I mean the magnifier show a very high contrast on a part of the image which has very low contrast ). I think we could/should limit the maximum contrast enhancement. in file CPImageCtrl.cpp line 601 // transform to range 0...255 vigra::transformImage(vigra::srcImageRange(magImg), vigra::destImage(magImg), vigra::linearRangeMapping( VT(minmax.min), VT(minmax.max), // src range VT(0), VT(255)) // dest range ); [1] http://groups.google.com/group/hugin-ptx/browse_thread/thread/06c616c5f57c6787# [2] http://www.davidefabbri.net/files/panorama/magnifier.zip -- 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 hugin-ptx@googlegroups.com To unsubscribe from this group, send email to hugin-ptx+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/hugin-ptx
Re: [hugin-ptx] Magnifier in control point editor panel
I agree that more sophisticated behavior would be helpful. Sometimes, the view in the magnifier is so enhanced that it no longer looks much like the area the cursor is over. This makes it difficult to determine which feature you might *actually* be selecting. Sometimes, more contrast isn't really the best choice. Often, simply lighter would do nicely. And for very light areas more contrast often results in a hard to read blown out look. eo On Dec 18, 2010, at 2:29 PM, davidefa wrote: I have already noticed a 'strange' behaviour of the magnifier in the control point editor panel ( but never understood it ). Today I loaded in hugin a few astronomical images ( see thread [1] ), and while adding a few cp I noticed that when the magnifier was positioned on the dark background ( no bright stars in the fov of the magnifier ) it showed a 'bright and dark texture', I couldn't understand where it came from. Searching in the code found that before being displayed the magnifier is 'contrast enhanced' ( the darkest part of the image is converted to back, the brightest part is converted to 255, max brightness ). This is to help identifying 'features' in the images. But when the magnifier is placed on a low contrast part of the image ( a generic image, not the astronomical image I refered above ) this amplification ( contrast enhancement ) could be very high and this seems a little bit confusing to me ( I mean the magnifier show a very high contrast on a part of the image which has very low contrast ). I think we could/should limit the maximum contrast enhancement. in file CPImageCtrl.cpp line 601 // transform to range 0...255 vigra::transformImage(vigra::srcImageRange(magImg), vigra::destImage(magImg), vigra::linearRangeMapping( VT(minmax.min), VT(minmax.max), // src range VT(0), VT(255)) // dest range ); [1] http://groups.google.com/group/hugin-ptx/browse_thread/thread/06c616c5f57c6787# [2] http://www.davidefabbri.net/files/panorama/magnifier.zip -- 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 hugin-ptx@googlegroups.com To unsubscribe from this group, send email to hugin-ptx+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/hugin-ptx
