[hugin-ptx] Re: How to fill black areas of a panorama?
I did some tests with the 'resynthesize' gimp plugin. Actually, you can use it in two differents ways. - Smart remove selection on an empty area. Just select the area then activate the function. It provide interesting results mostly for small areas. - The other way is to resynthesize a texture to a selected area. This is particularly useful for the grass on the ground or part of the sky. In case the area is not homogeneous enought in terms of texture, it is better to split it and run the process on each sub-division of the area. Results may be very good. In both cases, the result can be almost perfect. Unfortunately, this is not always the case, there are many situations which provides poor results. Obviously, the problem of filling black areas does not have a unique solution. Depending of each case, on solution can provide better results than the other. The best is probably to practice and get experienced in every solutions in order to use the most appropriate for each image. Thanks, PH -- 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] hugin plugin interface - developers please liaise
Hi all! Continuing my work on interfacing hugin with Python, I have reached another of my goals: I have figured out how to use plugins written in Python from programs that use hugin's type corpus - or at least the subset that is wrapped in the hugin scripting interface. This means that there is now a possibility to call arbitrary Python code with objects like HuginBase::Panorama, do some processing on them in Python and return to the caller. Don't be fooled into thinking this is a mere 'execute a script file' approach: the interface maintains the object- oriented interface, but the Python code actually accesses and manipulates the binary data held in the C++ application. What I'd like to do now is link this code into hugin and test it at it's destined place. To do so, I need a good point to link it in, and some easy way of triggering the call to Python with data from hugin. The code to use Python is encapsulated in two C++ classes that could either be put straight into a cpp file somewhere or be included as a header. I'd welcome some support from the hugin developers here. Also, I don't intend to provide any GUI elements to deal with plugins (at least for now), mainly because I don't have wxWidgets experience and don't know the GUI code, but also because I feel that the GUI isn't really my domain, I'm more of a backend programmer. Never mind the GUI, having a breakout option to call Python for quick hacks or rapid prototyping might be a welcome facility for the developers even without any formal introduction of a plugin GUI. Since all the terminology for data types and methods is identical in Python to that in C++, switching to using Python on the data is easy. I also need information on what to do if the Python code has modified hugin's content. I am aware that there are mechanisms to notify the application of such changes, and I also know that a certain protocol has to be used to make sure all actions can be undone. What I don't know is the precise nature of these mechanisms and how to serve them with appropriate information. Again, help from the developers would be welcome. Once I've test-run the code from hugin I'll publish through the usual channel. So far there has been so little echo to my work that I am getting the feeling that hardly anyone actually reads my posts or is at all interested. This is regrettable, since I am certain that my path to Python integration is opening up very interesting new possibilities. Let me name but a few: - plugins can provide glue to closely cooperate with other applications - other code can be glued in without having to link it - code contribution from users is made much easier - optional functionality can be accessed on on demand - Python code can be used to do advanced maths (see numpy, SciPy) 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 plugin interface - developers please liaise
Hi Kay, 2011/1/16 Pablo d'Angelo pablo.dang...@web.de Hi Kay, The full benefits might not be obvious to everybody, so don't let the lack of feedback disapoint you. As Pablo already mentioned: This is a really technical subject. I really like to test the new things in Hugin but I have worked with Thomas last week to get the new fast preview with the gsoc2010 panorama overview working on OSX. Yesterday and today I spent time on the cpfind modifications by Pablo. I'd like to spend time on your Python interface as well, but unlike Pablo I know nothing of python (next to that: unlike Pablo I know nothing of C++ either). Note that it is a steep learning curve if you know nothing of python and you are now required to do something with the first (your python interface) and couple it to the other (hugin). I'm not a developer. I'm a builder. Please give us some time. Your efforts are really appreciated. Hoi, Harry -- 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 plugin interface - developers please liaise
Kay, I read all your posts, but can not help you, as I am not a programmer at all. From the outside, it looks like you are doing good work, and creating a useful interface. I say, keep up the good work! Thanks, Roger Goodman On 1/16/2011 12:32 PM, kfj wrote: Hi all! Continuing my work on interfacing hugin with Python, I have reached another of my goals: I have figured out how to use plugins written in Python from programs that use hugin's type corpus - or at least the subset that is wrapped in the hugin scripting interface. This means that there is now a possibility to call arbitrary Python code with objects like HuginBase::Panorama, do some processing on them in Python and return to the caller. Don't be fooled into thinking this is a mere 'execute a script file' approach: the interface maintains the object- oriented interface, but the Python code actually accesses and manipulates the binary data held in the C++ application. What I'd like to do now is link this code into hugin and test it at it's destined place. To do so, I need a good point to link it in, and some easy way of triggering the call to Python with data from hugin. The code to use Python is encapsulated in two C++ classes that could either be put straight into a cpp file somewhere or be included as a header. I'd welcome some support from the hugin developers here. Also, I don't intend to provide any GUI elements to deal with plugins (at least for now), mainly because I don't have wxWidgets experience and don't know the GUI code, but also because I feel that the GUI isn't really my domain, I'm more of a backend programmer. Never mind the GUI, having a breakout option to call Python for quick hacks or rapid prototyping might be a welcome facility for the developers even without any formal introduction of a plugin GUI. Since all the terminology for data types and methods is identical in Python to that in C++, switching to using Python on the data is easy. I also need information on what to do if the Python code has modified hugin's content. I am aware that there are mechanisms to notify the application of such changes, and I also know that a certain protocol has to be used to make sure all actions can be undone. What I don't know is the precise nature of these mechanisms and how to serve them with appropriate information. Again, help from the developers would be welcome. Once I've test-run the code from hugin I'll publish through the usual channel. So far there has been so little echo to my work that I am getting the feeling that hardly anyone actually reads my posts or is at all interested. This is regrettable, since I am certain that my path to Python integration is opening up very interesting new possibilities. Let me name but a few: - plugins can provide glue to closely cooperate with other applications - other code can be glued in without having to link it - code contribution from users is made much easier - optional functionality can be accessed on on demand - Python code can be used to do advanced maths (see numpy, SciPy) 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] hugin plugin interface - developers please liaise
Hi Kay, On January 16, 2011 12:32:53 pm kfj wrote: So far there has been so little echo to my work that I am getting the feeling that hardly anyone actually reads my posts or is at all interested. apology for not getting back to you. I love what you are doing and look forward for the next Hugin GUI to be Python scripted. I am currently swamped at work (and with swamped I mean: 8am-2am with a few short breaks in between. This week I am not even able to catch up with Hugin on the weekend). When this contract ends, I'll be more than happy to play with your work. It would help if you would work within the Hg repo and publish your Hg branch. This does not have to be through SourceForge. I assume you branched Hugin locally on your machine with something like hg pull hg branch python_scripting and that you now switch between your scriptable hugin and mainstream with hg up -C python_scripting and hg up -C default you can push your Hg repository anywhere there is Hg hosting. so just tell us where you are going to push it, and we'll follow you. keep up the good work. sorry I can't be of more help. Yuv signature.asc Description: This is a digitally signed message part.
[hugin-ptx] Error creating a panorama
Hi, I can't create a panorama and get this error: http://paste.ubuntu.com/554857/ Is there anything I can do? Regards, Tobias -- 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: Error creating a panorama
When I've gotten this error it's because I have two images that are positioned pretty much the same in the stitch. Couple things you can try: 1- add --fine-mask' to the enblend commandline 2. add -a to the enblend commandline 3. removing the panorama0001.tif image from the stitch. Normally it's the last one loaded/processed that's causing the problem. On Jan 16, 3:59 pm, Tobias tobias.jak...@googlemail.com wrote: Hi, I can't create a panorama and get this error:http://paste.ubuntu.com/554857/ Is there anything I can do? Regards, Tobias -- 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: Show Stopper? (was Re: Re: 2010.4.0-beta1 Win32 test)
Hi all, Am 25.12.2010 19:26, schrieb Yuval Levy: I have started a tracker ticket: https://bugs.launchpad.net/hugin/+bug/694329 I have improved cpfind to be much more reliable when using fisheye images. Most tests so far have been positive, except for images with very little overlap. If there are still problems with the latest development version (hg: 3da7ecaa2dea), please comment on the above bug request. ciao Pablo -- 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: clustered hugin
On Sun 16-Jan-2011 at 06:10 -0800, kevin wrote: For a real increase in speed with enblend it'd need to be designed so that the problem it's solving can be broken into pieces that don't require all the information of the entire image. That way when those pieces are worked on by remote machines it wouldn't require all the remote machines to have a large amount of main memory. Thanks for this, yes the bottleneck to distributed stitching is that enblend has to assemble the final image and this requires a lot of memory. One experiment we tried a long time ago was to split the enblend job up, i.e. instead of blending images 0,1,2,3 in one go, you can blend 0,1 and 2,3 as separate processes and then blend these together as a third process. The disadvantage of this is there is more IO and processing, and the final blend still requires lots of memory. The advantage is that due to the way Hugin uses 'cropped TIFF' intermediate files, the other blends use less memory and some of the processing can be distributed. -- 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-ptx] Re: cpfind rocks!
Hi Emad, and all, On Jan 15, 7:24 am, Emad ud din Btt xyzt...@gmail.com wrote: Cpfind is default Cp generator with latest hugin windows 32bit builds. CPfind is no doubt one of the best Cp generator now. Great. Now please, publish a URL for a current windows release package. Everyone says it exists, no-one will say where :- I'm currently running 2010.2. Got cpfind from a zip of 2010.3 (bin directory only) that has defective Hugin, but working cpfind. Cheers, Tom -- 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 plugin interface - developers please liaise
Hi Terry, Thanks for your help. It WORKED! I loaded cpfind. Is this your recommended CP generator? Thanks again, Stan On Jan 16, 2011, at 5:14 PM, Terry Duell wrote: Hullo Stan, On Mon, 17 Jan 2011 09:11:21 +1100, stan green6...@verizon.net wrote: Harry, I just downloaded Hugin 2010.4.0 and I must be having a senior moment because the CP generator got lost. Where do I go to get them again and how do you recommend I install them? Try saving your '.hugin' file, then go to preferences Control point Detectors and select 'Load defaults', and see if that fixes the problem. Cheers, -- Regards, Terry Duell -- 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: PTS files
Bruno, On Jan 12, 1:35 pm, Bruno Postle br...@postle.net wrote: Hugin can import ptgui .pts files and save them as Hugin .pto projects, though if you have any cropped photos in the project you will need to fiddle with the crop and reoptimise. When I give it a PTS file from PTGui 9, my copy of 2010.2 (Win32) displays the lens type and number of control points, then crashes (loops forever) apparently while trying to load images. My guess it that this has to do with PTGui's dummy image, that is used as a reference for common parameters, but has no file name. Does anyone know better? Is the ability to load PTS files a current Hugin specification, or just something it once did? Cheers, Tom -- 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: cpfind rocks!
Hi Tom, Am 16.01.2011 23:28, schrieb Tom Sharpless: Great. Now please, publish a URL for a current windows release package. Everyone says it exists, no-one will say where :- I'm currently running 2010.2. Got cpfind from a zip of 2010.3 (bin directory only) that has defective Hugin, but working cpfind. Sorry, I don't use Windows, but I have just commited some major improvements to the feature detector used by cpfind, so anything from 2010.3 is a bit outdated (and I'm suprised that it worked so well for you). ciao Pablo -- 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: PTS files
On Sun 16-Jan-2011 at 14:37 -0800, Tom Sharpless wrote: On Jan 12, 1:35 pm, Bruno Postle br...@postle.net wrote: Hugin can import ptgui .pts files and save them as Hugin .pto projects, though if you have any cropped photos in the project you will need to fiddle with the crop and reoptimise. When I give it a PTS file from PTGui 9, my copy of 2010.2 (Win32) displays the lens type and number of control points, then crashes (loops forever) apparently while trying to load images. My guess it that this has to do with PTGui's dummy image, that is used as a reference for common parameters, but has no file name. I don't have PTGui, but I have seen recent reports that this function still works. The dummy image always existed in PTGui .pts projects, so this isn't likely to be the cause of the problem. If you have some .pts files that fail then it would useful to attach them to a bug report in launchpad: https://bugs.launchpad.net/hugin -- 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: cpfind rocks!
On January 16, 2011 05:28:16 pm Tom Sharpless wrote: Now please, publish a URL for a current windows release package. Everyone says it exists, no-one will say where :- http://sourceforge.net/projects/hugin/files/hugin/hugin-2010.4/ the most obvious place... Yuv signature.asc Description: This is a digitally signed message part.
Re: [hugin-ptx] Re: PTS files
Earlier when I posted my many screenshot links about CPFind and it's failure on my system, I also was using a *.pts as a base. However it was a *.pts file I'd generated from Autopano Pro rather than PTGui it self. When I attempted the pano with Hugin directly with CPFind itself, it did not fail, however, the photos were a jumbled ... Dale On Sun, 2011-01-16 at 22:48 +, Bruno Postle wrote: On Sun 16-Jan-2011 at 14:37 -0800, Tom Sharpless wrote: On Jan 12, 1:35 pm, Bruno Postle br...@postle.net wrote: Hugin can import ptgui .pts files and save them as Hugin .pto projects, though if you have any cropped photos in the project you will need to fiddle with the crop and reoptimise. When I give it a PTS file from PTGui 9, my copy of 2010.2 (Win32) displays the lens type and number of control points, then crashes (loops forever) apparently while trying to load images. My guess it that this has to do with PTGui's dummy image, that is used as a reference for common parameters, but has no file name. I don't have PTGui, but I have seen recent reports that this function still works. The dummy image always existed in PTGui .pts projects, so this isn't likely to be the cause of the problem. If you have some .pts files that fail then it would useful to attach them to a bug report in launchpad: https://bugs.launchpad.net/hugin -- 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 plugin interface - developers please liaise
Hullo Stan, On Mon, 17 Jan 2011 09:37:39 +1100, stan green6...@verizon.net wrote: Hi Terry, Thanks for your help. It WORKED! Good. I loaded cpfind. Is this your recommended CP generator? It is the CP Generator that is provided with Hugin, so I guess it is the recommended one. You probably should try some of the others to see what suits your projects best. Cheers, -- Regards, Terry Duell -- 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] 2010.5.0.43b89d002e11 Segmentation fault when clicking Identify or Show control points in Fast Panorama preview
Hi all, 2010.5.0.43b89d002e11 Segmentation fault when clicking Identify or Show control points in Fast Panorama preview Operating System: Linux 2.6.32-27-generic i686 Architecture: 32 bit Free memory: -1904988 kiB Hugin Version: 2010.5.0.43b89d002e11 Path to resources: /usr/share/hugin/xrc/ Path to data: /usr/share/hugin/data/ So I run it from the command line: me@ubuntu:~$ hugin /home/me/DIY-streetview/20110111/out/pto/000110.pto MainFrame::RestoreLayoutOnNextResize() Number of images 5 Image: /usr/share/hugin/xrc/data/transparent.png CacheEntry: 2last access: 1 8bit: 1 16bit: 1 float: 1 mask: 1 Image: /usr/share/hugin/xrc/data/transparent.png CacheEntry: 2last access: 1 8bit: 1 16bit: 1 float: 1 mask: 1 Image: /usr/share/hugin/xrc/data/transparent.png CacheEntry: 2last access: 1 8bit: 1 16bit: 1 float: 1 mask: 1 Image: /usr/share/hugin/xrc/data/transparent.png CacheEntry: 2last access: 1 8bit: 1 16bit: 1 float: 1 mask: 1 Image: /usr/share/hugin/xrc/data/transparent.png CacheEntry: 2last access: 1 8bit: 1 16bit: 1 float: 1 mask: 1 Image: /usr/share/hugin/xrc/data/transparent.png CacheEntry: 2last access: 1 8bit: 1 16bit: 1 float: 1 mask: 1 Image: /usr/share/hugin/xrc/data/transparent.png CacheEntry: 2last access: 1 8bit: 1 16bit: 1 float: 1 mask: 1 Image: /usr/share/hugin/xrc/data/transparent.png CacheEntry: 2last access: 1 8bit: 1 16bit: 1 float: 1 mask: 1 Image: /usr/share/hugin/xrc/data/transparent.png CacheEntry: 2last access: 1 8bit: 1 16bit: 1 float: 1 mask: 1 Image: /usr/share/hugin/xrc/data/transparent.png CacheEntry: 2last access: 1 8bit: 1 16bit: 1 float: 1 mask: 1 Image: /usr/share/hugin/xrc/data/transparent.png CacheEntry: 2last access: 1 8bit: 1 16bit: 1 float: 1 mask: 1 Image: /usr/share/hugin/xrc/data/transparent.png CacheEntry: 2last access: 1 8bit: 1 16bit: 1 float: 1 mask: 1 Image: /usr/share/hugin/xrc/data/transparent.png CacheEntry: 2last access: 1 8bit: 1 16bit: 1 float: 1 mask: 1 Image: /usr/share/hugin/xrc/data/transparent.png CacheEntry: 2last access: 1 8bit: 1 16bit: 1 float: 1 mask: 1 Image: /usr/share/hugin/xrc/data/transparent.png CacheEntry: 2last access: 1 8bit: 1 16bit: 1 float: 1 mask: 1 Image: /usr/share/hugin/xrc/data/transparent.png CacheEntry: 2last access: 1 8bit: 1 16bit: 1 float: 1 mask: 1 Image: /usr/share/hugin/xrc/data/transparent.png CacheEntry: 2last access: 1 8bit: 1 16bit: 1 float: 1 mask: 1 Image: /usr/share/hugin/xrc/data/transparent.png CacheEntry: 2last access: 1 8bit: 1 16bit: 1 float: 1 mask: 1 Image: /usr/share/hugin/xrc/data/transparent.png CacheEntry: 2last access: 1 8bit: 1 16bit: 1 float: 1 mask: 1 Image: /usr/share/hugin/xrc/data/transparent.png CacheEntry: 2last access: 1 8bit: 1 16bit: 1 float: 1 mask: 1 Image: /usr/share/hugin/xrc/data/transparent.png CacheEntry: 3last access: 1 8bit: 1 16bit: 1 float: 1 mask: 1 Image: /usr/share/hugin/xrc/data/transparent.png CacheEntry: 3last access: 1 8bit: 1 16bit: 1 float: 1 mask: 1 Image: /usr/share/hugin/xrc/data/transparent.png CacheEntry: 3last access: 1 8bit: 1 16bit: 1 float: 1 mask: 1 Image: /usr/share/hugin/xrc/data/transparent.png CacheEntry: 3last access: 1 8bit: 1 16bit: 1 float: 1 mask: 1 Image: /usr/share/hugin/xrc/data/transparent.png CacheEntry: 3last access: 1 8bit: 1 16bit: 1 float: 1 mask: 1 Image: /usr/share/hugin/xrc/data/transparent.png CacheEntry: 3last access: 1 8bit: 1 16bit: 1 float: 1 mask: 1 Image: /usr/share/hugin/xrc/data/transparent.png CacheEntry: 3last access: 1 8bit: 1 16bit: 1 float: 1 mask: 1 Image: /usr/share/hugin/xrc/data/transparent.png CacheEntry: 3last access: 1 8bit: 1 16bit: 1 float: 1 mask: 1 Image: /usr/share/hugin/xrc/data/transparent.png CacheEntry: 3last access: 1 8bit: 1 16bit: 1 float: 1 mask: 1 Image: /usr/share/hugin/xrc/data/transparent.png CacheEntry: 3last access: 1 8bit: 1 16bit: 1 float: 1 mask: 1 Image: /usr/share/hugin/xrc/data/transparent.png CacheEntry: 3last access: 1 8bit: 1 16bit: 1 float: 1 mask: 1 Image: /usr/share/hugin/xrc/data/transparent.png CacheEntry: 3last access: 1 8bit: 1 16bit: 1 float: 1 mask: 1 Image: /usr/share/hugin/xrc/data/transparent.png CacheEntry: 3last access: 1 8bit: 1 16bit: 1 float: 1 mask: 1 Image: /usr/share/hugin/xrc/data/transparent.png CacheEntry: 3last access: 1 8bit: 1 16bit: 1 float: 1 mask: 1 Image: /home/me/DIY-streetview/20110111/in/left/left_000110.jpg CacheEntry: 3last access: 3 8bit: 1 16bit: 1 float: 1 mask: 1 Image: /usr/share/hugin/xrc/data/transparent.png CacheEntry: 3last access: 1 8bit: 1 16bit: 1 float: 1 mask: 1 Image: /home/me/DIY-streetview/20110111/in/left/left_000110.jpg CacheEntry: 3last access: 4 8bit: 1 16bit: 1 float: 1 mask: 1 Image: /usr/share/hugin/xrc/data/transparent.png CacheEntry: 3last access: 1 8bit: 1 16bit: 1 float: 1 mask: 1 Image: /home/me/DIY-streetview/20110111/in/left/left_000110.jpg CacheEntry: 3last access: 4 8bit: 1 16bit: 1 float: 1 mask: 1 Image: /usr/share/hugin/xrc/data/transparent.png CacheEntry: 3last access: 1 8bit: 1 16bit: 1 float: 1 mask: 1 Image:
