[hugin-ptx] Re: Might this idea work? scripting process
Salut alouest, On Thursday, 8 November 2012 14:01:32 UTC-6, alouest wrote: 'm using a sotware which can export RGB tiff and 32 bit tiff. I can produce panoramic with hugin of the RGB but not of the 32 bit tiff. If I extract both RGB and 32 bit tiff, then I create my panorama from the RGB pictures and save the project file. Would I be able to use all the settings (and control points, basically everything) used before and apply them to my 32 bit tiff that hugin see totally blank? I tried quickly with nona but it crashed. To summary could hugin or another tool could apply the settings from a working panoramic creation into empty tiff (they off course have the exact same extent). Is that crazy or that could work? To my knowledge, Hugin and its included tools only work with TIFF images that: * use 16 bits per colour channel or less [no 32bpc TIFF, no floating point TIFF], * are RGB or RGBA [no CMYK support], * use only a single image layer [no multi-layers TIFF support], * and must be 4GB in file size [a limitation of base-standard TIFF] What are you using that creates 32-bit [I assume that's per colour channel] output? HDR images from something? Is there a practical reason to maintain that bit depth as far in your processing chain as Hugin? Chances are, even if you're going to be post-processing the images after stitching, 16 bits per channel will be sufficient. My suggestion [which is probably your only option with Hugin, Nona, etc.]: reduce the bit depth of the images to 16bpc or less and use those with Hugin. If you require 16 bit per channel image support, you may need to find other tools to use. Cheers, 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 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] Hugin 2011.4 giving me fits
Harry, I followed the instructions described in the Read me folder, shown in red below. The Installer automatically placed the executables in the following location: User/Library/Application support/Hugin/Autopano. However, when I started Hugin and went to Preferences the executables are listed as Configured, not installed, see the attached screen shot. How do I get Hugin 2012.0 to recognize the location that the Installer selected? I never experienced this problem in any of the previous versions of Hugin. Stan AutoCP binary Installers for Hugin. In this dmg you will you will find: - an Install ... application that will install the binary or binaries - and the binary or binaries itself in the Generator folder. You can either double click the Install.. application or drop the plugin onto the Install application. After installtion you can configure the AutoCP generator. You can create multiple configurations based on one AutoCP generator. You start Hugin, you load your images, select the AutoCP generator configuration of your choice and click Create Control Points to use the plugin. -- 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 inline: Screen Shot 2012-11-08 at 8.08.27 PM.png
Re: [hugin-ptx] Hugin 2011.4 giving me fits
Hi Stan, stan schrieb am 09.11.12 13:35: Harry, I followed the instructions described in the Read me folder, shown in red below. Make sure you follow all the ReadMe files out there: those coming with Hugin and those coming with the CP detectors. The Installer automatically placed the executables in the following location: *User/Library/Application support/Hugin/Autopano. *However, when I started Hugin and went to Preferences the executables are listed as Configured, not installed, see the attached screen shot. What you see as Configured, not installed is a part of the description of that particular CP detector setting. It's what you see in the list of available CP detector settings in the Images tab. These preset names should give the user a hint that they need to be configured. Just double click on it in the Preferences to open a dialog window where you can edit everything just as it is mentioned in the ReadMe. That's also the place where you can edit the description. Hint: just delete that Configured, not installed part. How do I get Hugin 2012.0 to recognize the location that the Installer selected? I never experienced this problem in any of the previous versions of Hugin. It's been there for quite some time. And it's one of the rare cases where I'd like to use the phrase It's not a problem, it's a feature. AutoCP binary Installers for Hugin. In this dmg you will you will find: - an Install ... application that will install the binary or binaries - and the binary or binaries itself in the Generator folder. You can either double click the Install.. application or drop the plugin onto the Install application. After installtion you can configure the AutoCP generator. You can create multiple configurations based on one AutoCP generator. ...means: open the Preferences - CP detectors, click on one setting and click on edit You start Hugin, you load your images, select the AutoCP generator configuration of your choice and click Create Control Points to use the plugin. Carl -- 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: Hugin 2011.4 giving me fits
Surrender not accepted for such a simple partial panorama... ;-) I'm not sure if one can expect good control point detection in the center images of your panorama. Waves are always a changing and yet so similar ;-) For you scenario you'll need some manual alignment via the Fast Preview window. Hope you didn't you zoom during taking the shots? Make sure they all use the same fov. Did you shoot them handheld? Wouldn't be a problem, though. I also had to tweak the foggy horizon of this panorama and carefully select some CPs manually: http://worldwidepanorama.org/wwp_rss/go/n7775 In your case I'd reset all values (Camera and Lens tab) and step by step optimize while looking for some nasty misplaced CPs. How about uploading the complete project somewhere so someone can have a look at it? Cheers, Carl stan schrieb am 09.11.12 14:44: Carl, I surrender! This is white flag time. I got the Autopano-sift to function but it too has trouble finding the CPs, even in locations where there is good contrast and the CP features are sharp. As for the result, take a look at the attached screen shot, there are no words in English to describe this mess. Stan complete (hijacked) thread is here https://groups.google.com/group/hugin-ptx/browse_thread/thread/31ac07859a5ae43a -- 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] Hugin 2011.4 giving me fits
How do you suggest I up load the images, I will change them to JPEG in order to keep the size down. At the risk of blasphemy I went to Photo merge in PS 5.5, this was tediously, creepy, crawly slow (unacceptably, I had time to go up stairs and make a second cup of coffee and finished it before PS completed the operation) but PS found the CPs and the horizon was flat; the color was good too. On Nov 9, 2012, at 9:26 AM, Carl von Einem wrote: Surrender not accepted for such a simple partial panorama... ;-) I'm not sure if one can expect good control point detection in the center images of your panorama. Waves are always a changing and yet so similar ;-) I did not use the waves, I manually selected CP features in the rocks. For you scenario you'll need some manual alignment via the Fast Preview window. Hope you didn't you zoom during taking the shots? (Did not zoom or otherwise alter the FOV) Make sure they all use the same fov. Did you shoot them handheld? I used a home made NPP on my tripod. Wouldn't be a problem, though. I also had to tweak the foggy horizon of this panorama and carefully select some CPs manually: http://worldwidepanorama.org/wwp_rss/go/n7775 I like the shot, it looked more complicated than mine. In your case I'd reset all values (Camera and Lens tab) and step by step optimize while looking for some nasty misplaced CPs. One problem I encountered while manually selecting the CPs was that Hugin kept trying to move them some place other than the feature I selected. How about uploading the complete project somewhere so someone can have a look at it? Cheers, Carl stan schrieb am 09.11.12 14:44: Carl, I surrender! This is white flag time. I got the Autopano-sift to function but it too has trouble finding the CPs, even in locations where there is good contrast and the CP features are sharp. As for the result, take a look at the attached screen shot, there are no words in English to describe this mess. Stan complete (hijacked) thread is here https://groups.google.com/group/hugin-ptx/browse_thread/thread/31ac07859a5ae43a -- 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 -- 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] Hugin 2011.4 giving me fits
Hi Stan, if you put your images available send the place here to the list. I also would like to take a look at them. Cheers, Carlos E G Carvalho (Cartola) http://cartola.org/360 http://www.panoforum.com.br/ 2012/11/9 stan green6...@verizon.net How do you suggest I up load the images, I will change them to JPEG in order to keep the size down. At the risk of blasphemy I went to Photo merge in PS 5.5, this was tediously, creepy, crawly slow (unacceptably, I had time to go up stairs and make a second cup of coffee and finished it before PS completed the operation) but PS found the CPs and the horizon was flat; the color was good too. On Nov 9, 2012, at 9:26 AM, Carl von Einem wrote: Surrender not accepted for such a simple partial panorama... ;-) I'm not sure if one can expect good control point detection in the center images of your panorama. Waves are always a changing and yet so similar ;-) I did not use the waves, I manually selected CP features in the rocks. For you scenario you'll need some manual alignment via the Fast Preview window. Hope you didn't you zoom during taking the shots? (Did not zoom or otherwise alter the FOV) Make sure they all use the same fov. Did you shoot them handheld? I used a home made NPP on my tripod. Wouldn't be a problem, though. I also had to tweak the foggy horizon of this panorama and carefully select some CPs manually: http://worldwidepanorama.org/wwp_rss/go/n7775 I like the shot, it looked more complicated than mine. In your case I'd reset all values (Camera and Lens tab) and step by step optimize while looking for some nasty misplaced CPs. One problem I encountered while manually selecting the CPs was that Hugin kept trying to move them some place other than the feature I selected. How about uploading the complete project somewhere so someone can have a look at it? Cheers, Carl stan schrieb am 09.11.12 14:44: Carl, I surrender! This is white flag time. I got the Autopano-sift to function but it too has trouble finding the CPs, even in locations where there is good contrast and the CP features are sharp. As for the result, take a look at the attached screen shot, there are no words in English to describe this mess. Stan complete (hijacked) thread is here https://groups.google.com/group/hugin-ptx/browse_thread/thread/31ac07859a5ae43a -- 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 -- 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 -- 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] Enblend/Enfuse version 4.1 release candidate 1
Hello everybody! We are glad to announce the first release candidate for Enblend/Enfuse version 4.1. We have put tar-balls of it at http://sourceforge.net/projects/enblend/files/enblend-enfuse/enblend-enfuse-4.1/ The archive files there are derived from revision eb476ced7575 in the Mercurial repository http://enblend.hg.sourceforge.net/hgweb/enblend/enblend/ As a release candidate for Enblend/Enfuse version 4.1, it should be almost ready for final release. However, there still might be a few remaining issues. The purpose of the release candidate is to discover any major issues -- those which have not been recorded in the bug tracker yet -- before the final version. The release candidate may not be suitable for production systems, but it is ready for contributors who want to help with testing and development. For an overview of the changes consult the NEWS file living in the root directory of the distribution source tarball or online at http://enblend.hg.sourceforge.net/hgweb/enblend/enblend/file/eb476ced7575/NEWS Notes 1. To all discriminating photographers These Enblend and Enfuse versions may be right for your seamless (pun intended), fully color managed workflow. 1.1 Both applications now honor ICC profiles embedded into the input images. 1.2 Severely under- and overexposed images are handled gracefully. 1.3 Artifacts of out-of-RGB cube pixels are cleaned up an a photographic way. 1.4 The default primary Graph-Cut seam generator produces superior seams that often do not even need optimizing. 2. To all heat-seekers 2.1 Version 4.1 will be 30%-40% slower than version 4.0 (relying on all default settings for both). Stick with 4.0 for performance. 2.2 Version 4.1 will use more peak memory in the non-ImageCache configuration and stress the ImageCache more in the configuration with ImageCache enabled. Stick with 4.0 on low-memory systems. 3. To all perma-whiners At the stage of a release-candidate series, feature requests or bemoaning of seemingly missed opportunities to fix your favorite bugs are misplaced. They are ok for the 4.2 development versions, which soon will be opened. Your developers (in alphabetical order of their last names) Kornel Mikołaj Thomas Chris /cls -- 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] Hugin 2011.4 giving me fits
Best is to zip your images together with the project file. Either from Finder menu 'File' - 'Create Archive' or use use Clean Archiver from http://www.sopht.jp/cleanarchiver/ which I prefer since it has an option to exclude those .DS-Store and ._* files. They are invisible on Mac but typically confuse users on other platforms. There is a number of free online storage services, some usual suspects are mydrive.ch and dropbox.com Here is a list: http://en.wikipedia.org/wiki/Comparison_of_file_hosting_services Cheers, Carl stan schrieb am 09.11.12 15:45: How do you suggest I up load the images, I will change them to JPEG in order to keep the size down. At the risk of blasphemy I went to Photo merge in PS 5.5, this was tediously, creepy, crawly slow (unacceptably, I had time to go up stairs and make a second cup of coffee and finished it before PS completed the operation) but PS found the CPs and the horizon was flat; the color was good too. On Nov 9, 2012, at 9:26 AM, Carl von Einem wrote: Surrender not accepted for such a simple partial panorama... ;-) I'm not sure if one can expect good control point detection in the center images of your panorama. Waves are always a changing and yet so similar ;-) I did not use the waves, I manually selected CP features in the rocks. For you scenario you'll need some manual alignment via the Fast Preview window. Hope you didn't you zoom during taking the shots? (Did not zoom or otherwise alter the FOV) Make sure they all use the same fov. Did you shoot them handheld? I used a home made NPP on my tripod. Wouldn't be a problem, though. I also had to tweak the foggy horizon of this panorama and carefully select some CPs manually: http://worldwidepanorama.org/wwp_rss/go/n7775 I like the shot, it looked more complicated than mine. In your case I'd reset all values (Camera and Lens tab) and step by step optimize while looking for some nasty misplaced CPs. One problem I encountered while manually selecting the CPs was that Hugin kept trying to move them some place other than the feature I selected. How about uploading the complete project somewhere so someone can have a look at it? Cheers, Carl stan schrieb am 09.11.12 14:44: Carl, I surrender! This is white flag time. I got the Autopano-sift to function but it too has trouble finding the CPs, even in locations where there is good contrast and the CP features are sharp. As for the result, take a look at the attached screen shot, there are no words in English to describe this mess. Stan complete (hijacked) thread is here https://groups.google.com/group/hugin-ptx/browse_thread/thread/31ac07859a5ae43a -- 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 -- 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 -- 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: Might this idea work? scripting process
Thanks for your answer I use FLIR thermal imagery, my TIFF are extracted from a video sequence recorded by plane by this thermal camera. So basically my Tiff is displaying floating values such as temperature in one band. I might be able to create a 16 bit rgb tiff and store the temperature in one of the band, the problem is that for the moment hugin doesn't accept it (it crashes). I don't really know what is the kind of 16 bit tiff structure that hugin is expecting Thanks Le vendredi 9 novembre 2012 02:52:19 UTC-9, dex Otaku a écrit : Salut alouest, On Thursday, 8 November 2012 14:01:32 UTC-6, alouest wrote: 'm using a sotware which can export RGB tiff and 32 bit tiff. I can produce panoramic with hugin of the RGB but not of the 32 bit tiff. If I extract both RGB and 32 bit tiff, then I create my panorama from the RGB pictures and save the project file. Would I be able to use all the settings (and control points, basically everything) used before and apply them to my 32 bit tiff that hugin see totally blank? I tried quickly with nona but it crashed. To summary could hugin or another tool could apply the settings from a working panoramic creation into empty tiff (they off course have the exact same extent). Is that crazy or that could work? To my knowledge, Hugin and its included tools only work with TIFF images that: * use 16 bits per colour channel or less [no 32bpc TIFF, no floating point TIFF], * are RGB or RGBA [no CMYK support], * use only a single image layer [no multi-layers TIFF support], * and must be 4GB in file size [a limitation of base-standard TIFF] What are you using that creates 32-bit [I assume that's per colour channel] output? HDR images from something? Is there a practical reason to maintain that bit depth as far in your processing chain as Hugin? Chances are, even if you're going to be post-processing the images after stitching, 16 bits per channel will be sufficient. My suggestion [which is probably your only option with Hugin, Nona, etc.]: reduce the bit depth of the images to 16bpc or less and use those with Hugin. If you require 16 bit per channel image support, you may need to find other tools to use. Cheers, 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 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] Use of Hugin in remote sensing
I tried, it looks pretty in ArcGis, but hugin doesn't like, it crash. I probably didn't respect the 16 tiff structure that hugin is expecting. Le jeudi 8 novembre 2012 15:30:43 UTC-9, alouest a écrit : That was one of my option, the only problem is the loss in accuracy, since my value are pretty accurate I can't afford to loose the decimal. But maybe I'm wrong? I will dig around this idea! It's pretty frustrating though because I have the pto with all the control points and I just want to stitch the picture together without any further modification put nano or enblend or pTstitch won't let me do that :/ Any way I will try the temperature band Thanks Le jeudi 8 novembre 2012 15:19:46 UTC-9, Frederic Da Vitoria a écrit : Could you generate tiffs where one of the standard colors is replaced with the temperature band? Le vendredi 9 novembre 2012, alouest julien@gmail.com a écrit : Thanks for the answer, Well yes the sub-image might have enough detail to detect control points, the problem is how to include the temperature band in the finale result? I don't need the RGB information, I just need the temperature, I keep the RGB because it's readable by hugin. I have got already a full coverage of my study area with the RGB value but i can't figure out how to include my 32 float data (temperature) in the result. I tried to save the PTO from the rgb process and then apply it on the 32 bit tiff, it works but hugin overwrite the data and put them at zero. Nona by example while it should do a simple crop of the image, set all the value to zero :/. Le jeudi 8 novembre 2012 13:51:04 UTC-9, Frederic Da Vitoria a écrit : Le 8 nov. 2012 08:35, alouest julien@gmail.com a écrit : Hello, Every day user of Hugin in my hobby-life, I'm now trying to use it at work. I saw that Hugin has been use in remote sensing and I would like to use it as well. For the project I'm working on right now, I need to stitch together 5000 thousand 32 bit tiff files and/or 4 band tiff files. Basically I want to create a temperature raster mosaic but in order to stitch the picture together, I need the 3 RBG band, the problem is that I can't figure out a way to do it use hugin. I could as well trying to stitch the 32bit tiff but Hugin see them as blank. Any idea how to resolve that? Does any of your 8 bit sub-image sets have enough details to detect correct control points? If so you could copy 3 times the generated .pto file and then edit the copies with e text editor to make them use the images from one of the other bands. -- Frederic Da Vitoria (davitof) Membre de l'April - « promouvoir et défendre le logiciel libre » - http://www.april.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] Use of Hugin in remote sensing
On Fri 09-Nov-2012 at 08:16 -0800, alouest wrote: I tried, it looks pretty in ArcGis, but hugin doesn't like, it crash. I probably didn't respect the 16 tiff structure that hugin is expecting. Hugin works here with HDR floating-point RGB data, it isn't necessary to map the data to 16bit integer values. You can use TIFF or EXR containers for your HDR data. -- 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] Use of Hugin in remote sensing
On Fri 09-Nov-2012 at 11:15 -0800, alouest wrote: When I process my file (32 float point) it gives me a tiff filled with the value 1. Can you see your float images in Hugin? i.e. start Hugin, load one image, open the 'old preview' (View - Preview Window) and set Output to HDR and click Update. You should see a crudely tonemapped version of your image. -- 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] Use of Hugin in remote sensing
On Fri 09-Nov-2012 at 11:39 -0800, alouest wrote: Yes, I see them without problem. I tried with 3 32 floating point tiff, the process went smoothly, the only problem is that the result is empty or filled with the value one. I'm not an expert so maybe I don't use the good settings? A funny things, if I try to import my result and open the preview hugin crash So if you can see the images tonemapped in the preview, you need to look at the intermediate files created by nona before blending. In the Stitcher tab, select Panorama Outputs - High Dynamic Range, and Remapped Images - High Dynamic Range, and click the Stitch! button at the bottom right. This should create several files, are any of these ok? -- 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: Introducing Pannellum - an HTML5 Panorama Viewer
I also get a black screen on my 2008 white macbook. By the way, can you use the Krpano xml specification for this player? It is good, and you would get more uptake probably because it would allow more people to easily use your player with their existing data. On Friday, October 12, 2012 5:18:24 PM UTC+2, Matthew Petroff wrote: Pannellum might support GIF files, although I've never tested it. I would not recommend using it though, as it is uncompressed and limited to an 8-bit color space. Just because a proprietary piece of software does something some way does not make it a standard, although adaptive dynamic range looks quite interesting. I might add it in the future, but the image pyramid support I'm currently working on is a higher priority in my opinion. Animated objects are a very low priority for me (I think they're gaudy). -Matthew On Friday, October 12, 2012 12:35:23 AM UTC-4, Emaad wrote: Mathew is it possible that Pannellum can support Gif file format? Basically I want to animate only one of image cubes. For example I edit Nadir image cube, convert it to gif format and make some animated effects over it. Now If Pannelum support gif format than animated object will be working. You are doing very nice work. Pannelum is a very good platform. Please! Consider standards set by Spi-V shockwave player. ADR is a Spiv feature, which has not be replicated in any flash or html5 based viewers. Please! See if it can be done. Spi-V also supported animated objects. On Wed, Oct 10, 2012 at 12:02 AM, Matthew Petroff mat...@mpetroff.netwrote: No, there isn't. -Matthew On Tuesday, October 9, 2012 2:55:52 AM UTC-4, Emaad wrote: Is there any way we can add animated objects in panorama using Pannellum? On Mon, Oct 8, 2012 at 8:23 PM, Matthew Petroff mat...@mpetroff.netwrote: The most likely cause is the texture size being to large for your graphics card / driver. Does an error get printed to Chome's JavaScript Console? -Matthew On Sunday, October 7, 2012 11:20:43 PM UTC-4, Rasmus Schultz wrote: All I see is a black screen - using Chrome 22.0.1229.79 m. I've had no other problems with WebGL-based applications on this machine... On Wednesday, May 30, 2012 12:03:45 AM UTC-4, Matthew Petroff wrote: Thanks for the reports! It should work in recent desktop versions of Firefox and Chrome with proper driver support. Safari needs WebGL to be manually enabled, and Opera won't support it until Opera 12. Mobile support is much more spotty. As for the reports of a black screen, I think it is due to buggy WebGL implementations; when I first started working on this last year, I got the occasional black screen, but with more recent browser updates, this is no longer the case for me. I can certainly change the text from Load Panorama to Click to Load Panorama. As for translations, there is no client side way for detecting language that I know of, so it's a bit of a moot point; if one wants to host it on a page in a different language, one can just change the strings in the hosted copy. I might consider changing the base implementation and adding some sort of image pyramid support in the future, but I don't plan on adding new feature or developing it much more until WebGL support matures more. -Matthew On May 28, 11:49 pm, Matthew Petroff matt...@mpetroff.net wrote: After a year of on and off development, Pannellum, a free and open source panorama viewer for the web, is ready for release. Built using HTML5, CSS3, JavaScript, and WebGL, it is plug-in free. The lightweight viewer, just 18kB gzipped, can be deployed using a single file and displays full equirectangular panoramas. One can easily embed panoramas in web pages as an iframe, using code generated by the included configuration utility. For more information and an example, see: http://www.mpetroff.net/archives/2012/05/28/introducing-pannellum/ Or the project page:https://bitbucket.org/mpetroff/pannellum/ I've tested it across a range of browsers, but I'd appreciate any feedback or bug reports. -Matthew -- 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 hugi...@googlegroups.com To unsubscribe from this group, send email to hugin-ptx+...@googlegroups.com For more options, visit this group at http://groups.google.com/group/hugin-ptx -- *Emaad* www.flickr.com/emaad -- 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 hugi...@googlegroups.com To unsubscribe from this group,
Re: [hugin-ptx] Use of Hugin in remote sensing
I wasn't able to run hugin on those settings, it crash saying that Precondition violation! exportImage(): file format does not support requested number of bands (color channels) C:/Program Files/Hugin/bin/nona -r hdr -m EXR_m -o bruno_try_hdr__hdr_ -i 1 C:/Users/JSCHRO~1/AppData/Local/Temp/hug8C6B.tmp ContractViolation: Precondition violation! exportImage(): file format does not support requested number of bands (color channels) So i ran the nona standalone which gave me 3 empty tiff. I guess that my file are not traditionnal data and hugin or just nona doesn't know how to handle them -- 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] Hugin 2011.4 giving me fits
Carl, I've given up for now. I was able to start at the left and create a fairly decent pano using 6 images. When I added the 7th image the pano folded back on its self. I then went to the right side and created a pano using 6 images, not too bad but it became clear that the waves were causing weird results in spite of manually selecting the CPs. I was planning to send the pile garbage to you via DropBox but DropBox has locked up my machine. Bottom line, I will take a new set of shots (without waves) and try again later. Thanks for you help, Stan -- 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] Use of Hugin in remote sensing
On Fri 09-Nov-2012 at 12:07 -0800, alouest wrote: I wasn't able to run hugin on those settings, it crash saying that Precondition violation! exportImage(): file format does not support requested number of bands (color channels) C:/Program Files/Hugin/bin/nona -r hdr -m EXR_m -o bruno_try_hdr__hdr_ -i 1 C:/Users/JSCHRO~1/AppData/Local/Temp/hug8C6B.tmp The problem is that your HDR TIFF files have only one channel. The Hugin tools actually support this, but HDR stitching using Hugin uses EXR files as intermediate images - and apparently these don't support a single channel. You can stitch on the command line using TIFF intermediate images, I'll attach a .pto project for your three pictures, stitch it like this: nona -m TIFF_m -o temp Rec-000825_50-Rec-000825_150.pto enblend -o temp.tif temp.tif temp0001.tif temp0002.tif -- 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 # hugin project file #hugin_ptoversion 2 p f0 w699 h891 v54 E0 R1 nTIFF_m c:LZW r:CROP m g1 i0 f0 m2 p0.00784314 # image lines #-hugin cropFactor=1 i w640 h480 f0 v50 Ra0 Rb0 Rc0 Rd0 Re0 Eev0 Er1 Eb1 r-0.165167142928385 p-10.3957432895672 y-0.566840920194418 TrX0 TrY0 TrZ0 j0 a0 b0 c0 d0 e0 g0 t0 Va1 Vb0 Vc0 Vd0 Vx0 Vy0 Vm5 Rt1 nRec-000825_50.tif #-hugin cropFactor=1 i w640 h480 f0 v=0 Ra=0 Rb=0 Rc=0 Rd=0 Re=0 Eev0 Er1 Eb1 r-0.353146083325907 p2.24067170355037 y0.350837689232161 TrX0 TrY0 TrZ0 j0 a=0 b=0 c=0 d=0 e=0 g=0 t=0 Va=0 Vb=0 Vc=0 Vd=0 Vx=0 Vy=0 Vm5 Rt1 nRec-000825_100.tif #-hugin cropFactor=1 i w640 h480 f0 v=0 Ra=0 Rb=0 Rc=0 Rd=0 Re=0 Eev0 Er1 Eb1 r-0.217026550579806 p13.3641170531987 y0.596663517300591 TrX0 TrY0 TrZ0 j0 a=0 b=0 c=0 d=0 e=0 g=0 t=0 Va=0 Vb=0 Vc=0 Vd=0 Vx=0 Vy=0 Vm5 Rt1 nRec-000825_150.tif # specify variables that should be optimized v r1 v p1 v y1 v r2 v p2 v y2 v # control points c n0 N1 x103.950255391367 y57.2938036679381 X88.9596120866872 Y208.380557442996 t0 c n0 N1 x152.7419876518 y104.289818004 X138.476445046596 Y256.570918457423 t0 c n0 N1 x112.853347578993 y156.51711541469 X97.9230173107695 Y309.093356944706 t0 c n0 N1 x66.4473854620143 y214.717245472465 X50.9298446572006 Y368.263909559231 t0 c n0 N1 x133.529544016685 y271.123798563837 X120.323826101043 Y425.745060745291 t0 c n0 N1 x188.446735435606 y62.7538316897661 X174.314570055983 Y214.488086426416 t0 c n0 N1 x185.17237180208 y110.909249659819 X171.598217356795 Y263.993687753127 t0 c n0 N1 x262.3158411624 y140.153541859171 X249.845480333406 Y293.59525756641 t0 c n0 N1 x223.965956881806 y229.42211803516 X210.08272423536 Y385.675118248205 t0 c n0 N1 x165.469949863746 y247.709997397152 X152.095402730339 Y401.999629302328 t0 c n0 N1 x377.825831083697 y80.337753304767 X364.753788129548 Y232.883349734231 t0 c n0 N1 x362.270513884796 y136.588148095714 X349.938624450315 Y289.790943916235 t0 c n0 N1 x369.065278072151 y153.95560970741 X356.443106405721 Y307.468820748626 t0 c n0 N1 x376.546370789279 y193.921386035317 X364.18228572 Y348.097321317384 t0 c n0 N1 x356.259099724765 y253.017340495956 X344.047416476953 Y407.737167586604 t0 c n0 N1 x487.678287356034 y43.1780565239335 X475.462199356675 Y194.91707058027 t0 c n0 N1 x421.007731687183 y91.0750420959119 X408.449060193072 Y244.963041266381 t0 c n0 N1 x446.198713660721 y149.912175686104 X434.315605181239 Y303.312216874344 t0 c n0 N1 x389.23106484808 y219.791961835007 X377.429182491646 Y374.166458646913 t0 c n0 N1 x450.687309871055 y270.252405812848 X439.471459638493 Y425.31745558231 t0 c n0 N1 x506.057761456043 y35.901634149673 X493.987313348825 Y187.046142298863 t0 c n0 N1 x585.312321017347 y97.1068325642985 X572.614382247536 Y249.872188923869 t0 c n0 N1 x516.954436128497 y184.669502429287 X506.556992456126 Y338.04632588682 t0 c n0 N1 x611.872594121361 y201.022311228551 X602.211965624246 Y355.34873213473 t0 c n0 N1 x582.887902618172 y248.858420607281 X572.061972733346 Y403.878982646532 t0 c n1 N2 x43.7676169823029 y49.4203345872781 X36.8265737304733 Y182.689699427826 t0 c n1 N2 x61.0824188734288 y102.285417838258 X55.3539310920958 Y236.309241044921 t0 c n1 N2 x135.131055036341 y164.839488525181 X130.45851085654 Y300.30581171 t0 c n1 N2 x138.145708200256 y205.801682682025 X134.290108344165 Y341.716776771311 t0 c n1 N2 x113.933617083295 y255.149892320969 X110.108586822036 Y391.526518484375 t0 c n1 N2 x185.160975348077 y67.0081159327115 X179.725837970576 Y200.513297980875 t0 c n1 N2 x240.247009368284 y121.768088784844 X235.693418136414 Y256.344242811182 t0 c n1 N2 x177.687382897183 y181.575372007461 X173.114009187907 Y315.873669828866
Re: [hugin-ptx] Use of Hugin in remote sensing
That is amazing! Thanks a lot!! Le vendredi 9 novembre 2012 12:13:01 UTC-9, Bruno Postle a écrit : On Fri 09-Nov-2012 at 12:07 -0800, alouest wrote: I wasn't able to run hugin on those settings, it crash saying that Precondition violation! exportImage(): file format does not support requested number of bands (color channels) C:/Program Files/Hugin/bin/nona -r hdr -m EXR_m -o bruno_try_hdr__hdr_ -i 1 C:/Users/JSCHRO~1/AppData/Local/Temp/hug8C6B.tmp The problem is that your HDR TIFF files have only one channel. The Hugin tools actually support this, but HDR stitching using Hugin uses EXR files as intermediate images - and apparently these don't support a single channel. You can stitch on the command line using TIFF intermediate images, I'll attach a .pto project for your three pictures, stitch it like this: nona -m TIFF_m -o temp Rec-000825_50-Rec-000825_150.pto enblend -o temp.tif temp.tif temp0001.tif temp0002.tif -- Bruno # hugin project file #hugin_ptoversion 2 p f0 w699 h891 v54 E0 R1 nTIFF_m c:LZW r:CROP m g1 i0 f0 m2 p0.00784314 # image lines #-hugin cropFactor=1 i w640 h480 f0 v50 Ra0 Rb0 Rc0 Rd0 Re0 Eev0 Er1 Eb1 r-0.165167142928385 p-10.3957432895672 y-0.566840920194418 TrX0 TrY0 TrZ0 j0 a0 b0 c0 d0 e0 g0 t0 Va1 Vb0 Vc0 Vd0 Vx0 Vy0 Vm5 Rt1 nRec-000825_50.tif #-hugin cropFactor=1 i w640 h480 f0 v=0 Ra=0 Rb=0 Rc=0 Rd=0 Re=0 Eev0 Er1 Eb1 r-0.353146083325907 p2.24067170355037 y0.350837689232161 TrX0 TrY0 TrZ0 j0 a=0 b=0 c=0 d=0 e=0 g=0 t=0 Va=0 Vb=0 Vc=0 Vd=0 Vx=0 Vy=0 Vm5 Rt1 nRec-000825_100.tif #-hugin cropFactor=1 i w640 h480 f0 v=0 Ra=0 Rb=0 Rc=0 Rd=0 Re=0 Eev0 Er1 Eb1 r-0.217026550579806 p13.3641170531987 y0.596663517300591 TrX0 TrY0 TrZ0 j0 a=0 b=0 c=0 d=0 e=0 g=0 t=0 Va=0 Vb=0 Vc=0 Vd=0 Vx=0 Vy=0 Vm5 Rt1 nRec-000825_150.tif # specify variables that should be optimized v r1 v p1 v y1 v r2 v p2 v y2 v # control points c n0 N1 x103.950255391367 y57.2938036679381 X88.9596120866872 Y208.380557442996 t0 c n0 N1 x152.7419876518 y104.289818004 X138.476445046596 Y256.570918457423 t0 c n0 N1 x112.853347578993 y156.51711541469 X97.9230173107695 Y309.093356944706 t0 c n0 N1 x66.4473854620143 y214.717245472465 X50.9298446572006 Y368.263909559231 t0 c n0 N1 x133.529544016685 y271.123798563837 X120.323826101043 Y425.745060745291 t0 c n0 N1 x188.446735435606 y62.7538316897661 X174.314570055983 Y214.488086426416 t0 c n0 N1 x185.17237180208 y110.909249659819 X171.598217356795 Y263.993687753127 t0 c n0 N1 x262.3158411624 y140.153541859171 X249.845480333406 Y293.59525756641 t0 c n0 N1 x223.965956881806 y229.42211803516 X210.08272423536 Y385.675118248205 t0 c n0 N1 x165.469949863746 y247.709997397152 X152.095402730339 Y401.999629302328 t0 c n0 N1 x377.825831083697 y80.337753304767 X364.753788129548 Y232.883349734231 t0 c n0 N1 x362.270513884796 y136.588148095714 X349.938624450315 Y289.790943916235 t0 c n0 N1 x369.065278072151 y153.95560970741 X356.443106405721 Y307.468820748626 t0 c n0 N1 x376.546370789279 y193.921386035317 X364.18228572 Y348.097321317384 t0 c n0 N1 x356.259099724765 y253.017340495956 X344.047416476953 Y407.737167586604 t0 c n0 N1 x487.678287356034 y43.1780565239335 X475.462199356675 Y194.91707058027 t0 c n0 N1 x421.007731687183 y91.0750420959119 X408.449060193072 Y244.963041266381 t0 c n0 N1 x446.198713660721 y149.912175686104 X434.315605181239 Y303.312216874344 t0 c n0 N1 x389.23106484808 y219.791961835007 X377.429182491646 Y374.166458646913 t0 c n0 N1 x450.687309871055 y270.252405812848 X439.471459638493 Y425.31745558231 t0 c n0 N1 x506.057761456043 y35.901634149673 X493.987313348825 Y187.046142298863 t0 c n0 N1 x585.312321017347 y97.1068325642985 X572.614382247536 Y249.872188923869 t0 c n0 N1 x516.954436128497 y184.669502429287 X506.556992456126 Y338.04632588682 t0 c n0 N1 x611.872594121361 y201.022311228551 X602.211965624246 Y355.34873213473 t0 c n0 N1 x582.887902618172 y248.858420607281 X572.061972733346 Y403.878982646532 t0 c n1 N2 x43.7676169823029 y49.4203345872781 X36.8265737304733 Y182.689699427826 t0 c n1 N2 x61.0824188734288 y102.285417838258 X55.3539310920958 Y236.309241044921 t0 c n1 N2 x135.131055036341 y164.839488525181 X130.45851085654 Y300.30581171 t0 c n1 N2 x138.145708200256 y205.801682682025 X134.290108344165 Y341.716776771311 t0 c n1 N2 x113.933617083295 y255.149892320969 X110.108586822036 Y391.526518484375 t0 c n1 N2 x185.160975348077 y67.0081159327115 X179.725837970576 Y200.513297980875 t0 c n1 N2 x240.247009368284 y121.768088784844 X235.693418136414 Y256.344242811182 t0 c n1 N2 x177.687382897183 y181.575372007461 X173.114009187907 Y315.873669828866 t0 c n1 N2 x167.634473318949 y217.145166891086 X163.18701372117 Y352.965171778593 t0 c n1 N2 x171.598217356795 y263.993687753127 X167.998374076801
Re: [hugin-ptx] Use of Hugin in remote sensing
Almost done! i process this on about 5000 pictures, is there a way to do enblend -o temp.tif temp.tif temp0001.tif temp0002.tif without writing all the files one by one? Something like a mask would be great like enblend -o temp.tif temp000* Thanks Le vendredi 9 novembre 2012 12:55:11 UTC-9, alouest a écrit : That is amazing! Thanks a lot!! Le vendredi 9 novembre 2012 12:13:01 UTC-9, Bruno Postle a écrit : On Fri 09-Nov-2012 at 12:07 -0800, alouest wrote: I wasn't able to run hugin on those settings, it crash saying that Precondition violation! exportImage(): file format does not support requested number of bands (color channels) C:/Program Files/Hugin/bin/nona -r hdr -m EXR_m -o bruno_try_hdr__hdr_ -i 1 C:/Users/JSCHRO~1/AppData/Local/Temp/hug8C6B.tmp The problem is that your HDR TIFF files have only one channel. The Hugin tools actually support this, but HDR stitching using Hugin uses EXR files as intermediate images - and apparently these don't support a single channel. You can stitch on the command line using TIFF intermediate images, I'll attach a .pto project for your three pictures, stitch it like this: nona -m TIFF_m -o temp Rec-000825_50-Rec-000825_150.pto enblend -o temp.tif temp.tif temp0001.tif temp0002.tif -- Bruno # hugin project file #hugin_ptoversion 2 p f0 w699 h891 v54 E0 R1 nTIFF_m c:LZW r:CROP m g1 i0 f0 m2 p0.00784314 # image lines #-hugin cropFactor=1 i w640 h480 f0 v50 Ra0 Rb0 Rc0 Rd0 Re0 Eev0 Er1 Eb1 r-0.165167142928385 p-10.3957432895672 y-0.566840920194418 TrX0 TrY0 TrZ0 j0 a0 b0 c0 d0 e0 g0 t0 Va1 Vb0 Vc0 Vd0 Vx0 Vy0 Vm5 Rt1 nRec-000825_50.tif #-hugin cropFactor=1 i w640 h480 f0 v=0 Ra=0 Rb=0 Rc=0 Rd=0 Re=0 Eev0 Er1 Eb1 r-0.353146083325907 p2.24067170355037 y0.350837689232161 TrX0 TrY0 TrZ0 j0 a=0 b=0 c=0 d=0 e=0 g=0 t=0 Va=0 Vb=0 Vc=0 Vd=0 Vx=0 Vy=0 Vm5 Rt1 nRec-000825_100.tif #-hugin cropFactor=1 i w640 h480 f0 v=0 Ra=0 Rb=0 Rc=0 Rd=0 Re=0 Eev0 Er1 Eb1 r-0.217026550579806 p13.3641170531987 y0.596663517300591 TrX0 TrY0 TrZ0 j0 a=0 b=0 c=0 d=0 e=0 g=0 t=0 Va=0 Vb=0 Vc=0 Vd=0 Vx=0 Vy=0 Vm5 Rt1 nRec-000825_150.tif # specify variables that should be optimized v r1 v p1 v y1 v r2 v p2 v y2 v # control points c n0 N1 x103.950255391367 y57.2938036679381 X88.9596120866872 Y208.380557442996 t0 c n0 N1 x152.7419876518 y104.289818004 X138.476445046596 Y256.570918457423 t0 c n0 N1 x112.853347578993 y156.51711541469 X97.9230173107695 Y309.093356944706 t0 c n0 N1 x66.4473854620143 y214.717245472465 X50.9298446572006 Y368.263909559231 t0 c n0 N1 x133.529544016685 y271.123798563837 X120.323826101043 Y425.745060745291 t0 c n0 N1 x188.446735435606 y62.7538316897661 X174.314570055983 Y214.488086426416 t0 c n0 N1 x185.17237180208 y110.909249659819 X171.598217356795 Y263.993687753127 t0 c n0 N1 x262.3158411624 y140.153541859171 X249.845480333406 Y293.59525756641 t0 c n0 N1 x223.965956881806 y229.42211803516 X210.08272423536 Y385.675118248205 t0 c n0 N1 x165.469949863746 y247.709997397152 X152.095402730339 Y401.999629302328 t0 c n0 N1 x377.825831083697 y80.337753304767 X364.753788129548 Y232.883349734231 t0 c n0 N1 x362.270513884796 y136.588148095714 X349.938624450315 Y289.790943916235 t0 c n0 N1 x369.065278072151 y153.95560970741 X356.443106405721 Y307.468820748626 t0 c n0 N1 x376.546370789279 y193.921386035317 X364.18228572 Y348.097321317384 t0 c n0 N1 x356.259099724765 y253.017340495956 X344.047416476953 Y407.737167586604 t0 c n0 N1 x487.678287356034 y43.1780565239335 X475.462199356675 Y194.91707058027 t0 c n0 N1 x421.007731687183 y91.0750420959119 X408.449060193072 Y244.963041266381 t0 c n0 N1 x446.198713660721 y149.912175686104 X434.315605181239 Y303.312216874344 t0 c n0 N1 x389.23106484808 y219.791961835007 X377.429182491646 Y374.166458646913 t0 c n0 N1 x450.687309871055 y270.252405812848 X439.471459638493 Y425.31745558231 t0 c n0 N1 x506.057761456043 y35.901634149673 X493.987313348825 Y187.046142298863 t0 c n0 N1 x585.312321017347 y97.1068325642985 X572.614382247536 Y249.872188923869 t0 c n0 N1 x516.954436128497 y184.669502429287 X506.556992456126 Y338.04632588682 t0 c n0 N1 x611.872594121361 y201.022311228551 X602.211965624246 Y355.34873213473 t0 c n0 N1 x582.887902618172 y248.858420607281 X572.061972733346 Y403.878982646532 t0 c n1 N2 x43.7676169823029 y49.4203345872781 X36.8265737304733 Y182.689699427826 t0 c n1 N2 x61.0824188734288 y102.285417838258 X55.3539310920958 Y236.309241044921 t0 c n1 N2 x135.131055036341 y164.839488525181 X130.45851085654 Y300.30581171 t0 c n1 N2 x138.145708200256 y205.801682682025 X134.290108344165 Y341.716776771311 t0 c n1 N2 x113.933617083295 y255.149892320969 X110.108586822036 Y391.526518484375 t0 c n1 N2 x185.160975348077 y67.0081159327115 X179.725837970576 Y200.513297980875 t0 c n1 N2
Re: [hugin-ptx] Re: Might this idea work? scripting process
On 11/09/2012 01:52 AM, dex Otaku wrote: Salut alouest, On Thursday, 8 November 2012 14:01:32 UTC-6, alouest wrote: 'm using a sotware which can export RGB tiff and 32 bit tiff. I can produce panoramic with hugin of the RGB but not of the 32 bit tiff. If I extract both RGB and 32 bit tiff, then I create my panorama from the RGB pictures and save the project file. Would I be able to use all the settings (and control points, basically everything) used before and apply them to my 32 bit tiff that hugin see totally blank? I tried quickly with nona but it crashed. To summary could hugin or another tool could apply the settings from a working panoramic creation into empty tiff (they off course have the exact same extent). Is that crazy or that could work? To my knowledge, Hugin and its included tools only work with TIFF images that: * use 16 bits per colour channel or less [no 32bpc TIFF, no floating point TIFF], * are RGB or RGBA [no CMYK support], * use only a single image layer [no multi-layers TIFF support], * and must be 4GB in file size [a limitation of base-standard TIFF] Yes. I understand there's an effort to come up with a TIFF standard that allows larger sizes. What are you using that creates 32-bit [I assume that's per colour channel] output? HDR images from something? I don't know what the original poster means by it. Windows claims a 32-bit image format, but I think it's actually 8-bit RGB with 8-bit alpha-transparency. Is there a practical reason to maintain that bit depth as far in your processing chain as Hugin? Chances are, even if you're going to be post-processing the images after stitching, 16 bits per channel will be sufficient. I get better color when I stitch using 48-bit TIF (16-bit per channel). I convert them from my camera's 48-bit RAW files. 48-bit is minimal HDR, because 16-bits per channel gives a greater color gamut than can be displayed or printed with existing technology. My suggestion [which is probably your only option with Hugin, Nona, etc.]: reduce the bit depth of the images to 16bpc or less and use those with Hugin. If you require 16 bit per channel image support, you may need to find other tools to use. I know of one Hugin tool that doesn't work with 16-bit per channel images: linefind. Unless that's been fixed in the new release? Cheers, D -- Gnome Nomad gnomeno...@gmail.com wandering the landscape of god http://www.clanjones.org/david/ http://dancing-treefrog.deviantart.com/ http://www.cafepress.com/otherend/ -- 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
