Re: [hugin-ptx] Re: CRITICAL: join us to nuke the pesky bug that is plaguing the fast preview
Hullo Greg, On Wed, 27 Jul 2011 14:22:31 +1000, Greg 'groggy' Lehey groog...@gmail.com wrote: On Wednesday, 27 July 2011 at 13:29:52 +1000, Terry Duell wrote: [snip] The licence file in the version bundled with hugin says 2005, so there is a good chance that hugin already uses 2.3.2. Can anyone confirm? Yes, it seems so. I've just run diff on the two trees. There are a couple of minor differences in MutexImpl.h: Thanks for that. It would seem that there isn't likely to much joy in attempting to use the sourceforge tarball for zthread 2.3.2. 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
Re: [hugin-ptx] CRITICAL: join us to nuke the pesky bug that is plaguing the fast preview
On Tue, Jul 26, 2011 at 12:27:19PM -0400, Yuval Levy wrote: 2) as Hugin has evolved, threads have become more widely used and conflicts more likely. Revision 4524 (2010-11-04 18:31:15) is as far back as I went in my investigations so far looking for the use of threads. This is when the ImageCache was transferred to a separate thread, making the application more responsive. In it alone not a problem, but maybe the introduction of later threaded features introduced the conflicts that are becoming apparent now. There have been longstanding bugs that I suspect come from ImageCache. Crashes, image corruption etc. etc. These are very likely to change character when you move the ImageCache part to a separate thread. They might suddenly happen all the time when before they happened only sometimes. Or the other way around. Or a crash might turn in a corruption, etc etc. Roger. -- ** r.e.wo...@bitwizard.nl ** http://www.BitWizard.nl/ ** +31-15-2600998 ** **Delftechpark 26 2628 XH Delft, The Netherlands. KVK: 27239233** *-- BitWizard writes Linux device drivers for any device you may have! --* The plan was simple, like my brother-in-law Phil. But unlike Phil, this plan just might work. -- 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: tweaking enfuse parameters pays
Personally i've had the best results using +1.5 and -0.5 exposure derived from a single raw file. -- 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: tweaking enfuse + hdr
Kay, do you have any examples of images we can see (before / after) showing that this really works? i'd love to see that :) jeffrey On Friday, May 6, 2011 2:28:37 PM UTC+2, kfj wrote: On 19 Apr., 10:31, Erik Krause erik@gmx.de wrote: You can also try slightly smaller values for -wSigma which would avoid using completely over- or underexposed regions. But you might need smaller exposure steps then... enfuse also offers to completely ignore pixels above/below a certain value. This may be more straightforward than to use than sigma and mu. I haven't used this parameter, but I think the description is unmistakable: Expert options: --exposure- cutoff=LOWERCUTOFF[:UPPERCUTOFF[:LOWERPROJECTOR[:UPPERPROJECTOR]]] LOWERCUTOFF and UPPERCUTOFF are the values below or above of which pixels are weighted with zero weight in exposure weighting; append % signs for relative values; default: 0%:100%:anti- value:value I just don't understand what the 'PROJECTOR' values are good for. I think that maybe this option is new - it's not mentioned in the enfuse.pdf I have, but enfuse --help lists it. 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 2011.2.0 release notes - fixed background image
2011/7/26, Yuval Levy goo...@levy.ch: honest and serious: yes please. *everybody*. reporting bugs on Launchpad [0] makes sure that the information is recorded, structured, and does not get lost. The tracker helps prioritize activities and keep an overview of what is going on by importance. dumping a message on hugin-ptx on the other hand it just ends up on top of the pile, but other messages will soon cover it and if it had some really important information it might get missed in action. so please: even for the smallest bug or feature request: if what you are reporting requires a change in the application's behavior (and consequently in the code), please report it on Launchpad. This includes the website. Thanks Yuv [0] https://bugs.launchpad.net/hugin In RC2, I spotted two occurrences of Hugins: in the Images tab, I found Hugins CPFind in the combo, and the Windows tray bar icon hint is Hugins batch processor. Before putting anything in Launchpad, are these were indeed wrong? -- 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] Feature Request: Save Redo/Undo list for replay.
paul womack schrieb am 27.07.11 10:26: Jan Martin wrote: in hugin there are the Redo/Undo buttons that work with a kind of action list. I would like to suggest to add a feature to save the action list. Then have a button to load that list and replay it step-by-step. Including switching tabs. This would be a great tool to teach how to do things, and also help to remember how one actually build that one really great .pto file. Not just have the finished .pto file. I think that anyone making a tutorial could use the GUI record/play features of their OS. Any recommendations for Mac OS X? I think Jan's idea is very interesting in principle, but OTOH that's far beyond what I'd estimate from a feature list of a panorama stitcher. The energy (of the developers and the users alike) is IMHO far better invested in thinking about and creating a GUI that can be used more instinctively. My favourite would be an interface that simplifies the current list of tabs to a threefold of input / editing / output, aimed at those who prefer a more keyboard based under the hood approach. Plus the Fast Preview enhanced to an interface that allows for a very elegant visual (drag and drop?) workflow and would likely supersede the current Assistant tab. 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: tweaking enfuse parameters pays
On 27 Jul., 09:28, Jeffrey Martin 360cit...@gmail.com wrote: Personally i've had the best results using +1.5 and -0.5 exposure derived from a single raw file. Differently processed single raw files are perfect source material - if the scene can be captured with the dynamic range available. I don't know what you have, but my sensor's dynamic range is somewhere in the 12 to 14 bit range, and my landscapes sometimes just don't fit into that. I wish they would. In fact I think the technology to expose the sensor for a fixed period of time and then count the photons is silly. What would be much more sensible is measuring the time it takes each cell to reach saturation. When the exposure is finally stopped, those cells which aren't full can still be photon-counted to define the shadows. Store the result in a floating point format and you end up with a truly HDR raw image without any fuss and then you can proceed by exposure-blending different versions of it instead of the cumbersome tone-mapping. I wonder if that's technically feasible, but why not? Processing happens in the GHz range, that's 2 to the power of 32. Exposure times are in an order of magnitude of thousandth of seconds. So in 2 ^ -10 seconds you should have 2 ^ 22 clock cycles - that should be the dynamic range achievable just by measuring the time- to-satuartion for the cells. If the full cell triggers a store operation on the current clock value, there you go. Like a neuron firing. 2 ^ 22 seems like plenty already (can't be bothered just right now to make dB of it). Wonder if anyone thought of that? 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
[hugin-ptx] Re: tweaking enfuse + hdr
On 27 Jul., 10:16, Jeffrey Martin 360cit...@gmail.com wrote: Kay, do you have any examples of images we can see (before / after) showing that this really works? i'd love to see that :) Mysterious... here you've dug out a resopnse to a thread I made in May. And lo and behold, calling enfuse --help just now the options I quoted aren't there. That took me some figuring out, but I think I know what happened. I was using a bleeding edge version of enfuse then, but it had a bug: https://bugs.launchpad.net/enblend/+bug/787387 So I reverted to an older version, and I suppose that one hasn't got the --exposure-cutoff parameter, even though it makes great sense. So currently, this is just theory and I've got nothing to show demonstrating the efficacy of this option. But I trust it - after all enfuse's statistics are very straightforward. It's just that a cutoff may cause a discontinuity which becomes visible if the step is too large, so cutoffs have to be treated with caution. If the desired effect can be achieved by tweaking mu and sigma, there are no discontinuities in the weighting functions. If using a cutoff is considered, additionally tweaking mu and sigma may lessen the discontinuity's magnitude. 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] CRITICAL: join us to nuke the pesky bug that is plaguing the fast preview
2011/7/26, Yuval Levy goo...@levy.ch: On July 26, 2011 08:10:28 AM Lukáš Jirkovský wrote: I think this is one of the most serious bugs hugin ever had. What makes you reach this judgment? Mainly because of the number of users affected by this issue. Yes, it is growing. And I see two drivers of growth that would confirm your hypothesis that this is a threading issue: 1) as time progresses, people buy newer, better PCs with more threads. If single-thread machines are not affected; dual-thread machines are barely affected; and machines with 4 threads and more are significantly affected, it seems to indicate that this is a threading issue. 2) as Hugin has evolved, threads have become more widely used and conflicts more likely. Revision 4524 (2010-11-04 18:31:15) is as far back as I went in my investigations so far looking for the use of threads. This is when the ImageCache was transferred to a separate thread, making the application more responsive. In it alone not a problem, but maybe the introduction of later threaded features introduced the conflicts that are becoming apparent now. Also the fact that it renders the fast preview, which is IMHO becoming the center of the workflow, unusable makes it more important. Yes, the FPW is becoming the center of the workflow IMHO too, and making it usable is very important. I suspect that getting the threading right will be a big and intensive job. The more I look at recent reports in the bug tracker, the more dots there are to connect and they all seem to lead to the same pesky thing. Could the conflict be related to the use of different threading libraries? we have boost threads since revision 4524 [0] for the images cache and cpfind uses zthread? I still have a mono-processor laptop from 2002 running Windows XP. Would it help if I did a few tests on it? -- 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] Re: Hugin 2011.2.0 release notes - fixed background image
2011/7/27, Carl von Einem c...@einem.net: Frederic Da Vitoria schrieb am 27.07.11 10:16: 2011/7/26, Yuval Levygoo...@levy.ch: so please: even for the smallest bug or feature request: if what you are reporting requires a change in the application's behavior (and consequently in the code), please report it on Launchpad. This includes the website. In RC2, I spotted two occurrences of Hugins: in the Images tab, I found Hugins CPFind in the combo, and the Windows tray bar icon hint is Hugins batch processor. Before putting anything in Launchpad, are these were indeed wrong? Maybe your tray bar icon hint is wrong if it shows information for Hugin's own tray bar icon. On Mac OS there is a second application (in addition to Hugin) PTBatcherGUI.app which is the batch processor and basically is (at least in this current stage) an accompanying tool that processes Hugin's output (one or more projects you want to have stitched). - http://wiki.panotools.org/Hugin_Batch_Processor CPFind is an internal tool that will detect Control Points for your project. - http://wiki.panotools.org/Cpfind So IMHO nothing is wrong with Hugins CPFind as a description. BTW http://wiki.panotools.org/Hugin contains a broad description of the GUI and its features. A very good idea is to add the panotools wiki to your list of search engines in Firefox which works great as a glossary. Sorry, my description wasn't clear enough. My problem is that there aren't several Hugins, there is only one Hugin :-) So it should be Hugin CPFind or Hugin's CPFindinstead of Hugins CPFind and Hugin batch processor or Hugin's batch processor instead of Hugins batch processor. This is very minor of course. -- 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] Re: Hugin 2011.2.0 release notes - fixed background image
Frederic Da Vitoria schrieb am 27.07.11 10:16: 2011/7/26, Yuval Levygoo...@levy.ch: so please: even for the smallest bug or feature request: if what you are reporting requires a change in the application's behavior (and consequently in the code), please report it on Launchpad. This includes the website. In RC2, I spotted two occurrences of Hugins: in the Images tab, I found Hugins CPFind in the combo, and the Windows tray bar icon hint is Hugins batch processor. Before putting anything in Launchpad, are these were indeed wrong? Maybe your tray bar icon hint is wrong if it shows information for Hugin's own tray bar icon. On Mac OS there is a second application (in addition to Hugin) PTBatcherGUI.app which is the batch processor and basically is (at least in this current stage) an accompanying tool that processes Hugin's output (one or more projects you want to have stitched). - http://wiki.panotools.org/Hugin_Batch_Processor CPFind is an internal tool that will detect Control Points for your project. - http://wiki.panotools.org/Cpfind So IMHO nothing is wrong with Hugins CPFind as a description. BTW http://wiki.panotools.org/Hugin contains a broad description of the GUI and its features. A very good idea is to add the panotools wiki to your list of search engines in Firefox which works great as a glossary. 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
Re: [hugin-ptx] Feature request: make post-processing with exiftool optional
David Haberthür kirjoitti viestissään (lähetysaika keskiviikko, 27. heinäkuuta 2011): On 26.07.2011, at 21:51, Tom Sharpless wrote: Like it says. Exiftool can greatly increase stitching time, because it makes a full-size temporary copy of the pano, which typically involves de-compressing and re-compressing the whole thing. But for me there is no payoff -- I really don't need camera settings in my panos, and I don't need a CIE profile either, as I always have to convert from Adobe RGB to sRGB by hand anyhow. I would rather be able to stitch a few more panos per week. I suspect I am not alone. I very much like that the Geotags and Camera settings are copied over from my original photos to the resulting pano, please don't take that away! But as I see you're aiming to provide an option in the preference tab, so I'm just going to keep it set to use exiftool all the time. ICC profiles in the intermediate images are required to use the -c (CIECAM blending) option in enblend/enfuse. Using exiftool to copy metadata is a kludge, I think each program in the processing pipeline should handle the metadata in accordance of the MWG guidelines: http://www.metadataworkinggroup.org/specs/ That would avoid the extra copying and slowdown caused by exiftool. -- Markku Kolkka markku.kol...@iki.fi -- 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] Feature Request: Save Redo/Undo list for replay.
Carl von Einem wrote: paul womack schrieb am 27.07.11 10:26: Jan Martin wrote: in hugin there are the Redo/Undo buttons that work with a kind of action list. I would like to suggest to add a feature to save the action list. Then have a button to load that list and replay it step-by-step. Including switching tabs. This would be a great tool to teach how to do things, and also help to remember how one actually build that one really great .pto file. Not just have the finished .pto file. I think that anyone making a tutorial could use the GUI record/play features of their OS. Any recommendations for Mac OS X? I don't use a Mac, but back when I did (late 80's !!) there was a program that did this. I presume there still is, since the requirment (ergo customer base) is a real one. (a quick google reveals that I must have been using QuickKeys) BugBear -- 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] Website detailing HDR creation and Hugin
Hi there. As part of a research project at the University of Brighton in the UK I have created a website called High Dynamic Range Imaging in Design Education (HIDE) at http://artsresearch.brighton.ac.uk/research/centre/office-for-spatial-research/projects/hide. There are example HDR panoramas on there created with Hugin and documentation on how to create HDR panoramas with Hugin. I would be very pleased if you felt it worthwhile to put a link to my page in the links section of the Huign website. Cheers Ryan -- 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: Website update
Yuv, To answer your questions in your reply: I found it disconcerting because 1) it's unusual behavior and 2) it took a while to convince myself that I wasn't losing the ability to read text because of the image's covering it. Item 2 being the biggie here. JK -- 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] Stitching 4 images with Hugin
Hello. I'm a new member. I've used Hugin in the past to create a panorama (photo from one point rotating about the focal plane) and had pretty good success. Now I'm trying to stitch together 151 photos of a flat floor, mosaic-style, to preserve the layout of PEX tubing now buried in the slab. All photos were taken at 10 ft distance with (I believe) a Sony DSC-P200. I started with four contiguous photos, two rows and two columns. I identified three CPs on each pair of photos (adjacent and kiddy-corner). I expected a rock-solid rendering but when I tried to preview in either previewer, the result was unsatisfactory. I'm not exactly sure what x,y,z etc settings I should be using. (How) shall I upload files so you can see what I have? UnconventionalT wrote: hit Create Panorama, select the name and directory, and go about your merry way. -- View this message in context: http://old.nabble.com/Stitching-4-images-with-Hugin-tp32092859p32148230.html Sent from the hugin ptx mailing list archive at Nabble.com. -- 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: Feature request: make post-processing with exiftool optional
Agree with Nomad that metadata copying should be customisable, and with Markku, that it should be done within the hugin tools, in a way that supports hugin functions first. However both of those sound to me like big projects. I guess I'll take Yuv's advice and just stuff an updated option patch into the Hg trunk, that will affect only the application of exiftool to to the final pano, not to intermediate files. And I'll put in a hook, at least, to allow customizing the exiftool command, if that appears feasible. -- Tom On Jul 27, 5:35 am, Markku Kolkka markku.kol...@iki.fi wrote: David Haberth r kirjoitti viestiss n (l hetysaika keskiviikko, 27. hein kuuta 2011): On 26.07.2011, at 21:51, Tom Sharpless wrote: Like it says. Exiftool can greatly increase stitching time, because it makes a full-size temporary copy of the pano, which typically involves de-compressing and re-compressing the whole thing. But for me there is no payoff -- I really don't need camera settings in my panos, and I don't need a CIE profile either, as I always have to convert from Adobe RGB to sRGB by hand anyhow. I would rather be able to stitch a few more panos per week. I suspect I am not alone. I very much like that the Geotags and Camera settings are copied over from my original photos to the resulting pano, please don't take that away! But as I see you're aiming to provide an option in the preference tab, so I'm just going to keep it set to use exiftool all the time. ICC profiles in the intermediate images are required to use the -c (CIECAM blending) option in enblend/enfuse. Using exiftool to copy metadata is a kludge, I think each program in the processing pipeline should handle the metadata in accordance of the MWG guidelines:http://www.metadataworkinggroup.org/specs/ That would avoid the extra copying and slowdown caused by exiftool. -- Markku Kolkka markku.kol...@iki.fi -- 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.2.0 RC2 32 bits windows crashes.
Yes, I've experience just yesterday the same problem with the 2011.2.0RC2 build under win XP 32bits. On 27 Lug, 17:27, Henk Tijdink h.tijd...@gmail.com wrote: Tested Hugin 2011.2.0 RC2 32bits windows of Matthew Petroff, but Hugin crashes during stitching with an enblend error. The beta version has not that problem. Used the installer, did a clean install with the installer and unpacked the zipfile. In all trials I get the crash. So it don't stitch. In the beta 1 version of Matthew Petroff I don't have that problem. Other windows users having that problem too? Will file a bug report in Launchpad. Kind regards, Henk Tijdink -- 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] Repository acces in time between release candidates
Hello, I have seen, that some last Yuval's commits in 2011.2 branch was translation updates. I have also found, that my Czech translation update from default branch ( 723668d8c4cc ) wasn't one of them. 2011.2 with copy of file from default branch will be fully translated and compilable/ installable/runnable. I can commit it to 2011.2 branch, but I am not sure, if it is a right thing to bypass our release manager in time between release candidates. What's your opinion? Vaclav Cerny -- 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: Website update
Hiya all, Very much a lurker here but I thought I'd chip in my tuppence as well... On Tuesday 26 Jul 2011 23:38:21 Yuval Levy wrote: On July 26, 2011 06:15:34 pm JKEngineer wrote: When I scroll down, more of the panorama comes into view, obscuring the upper portions of the text. As I scroll further down, the panorama locks to the top edge of the window. Don't know if this is deliberate. Yes, this is deliberate, thank you for confirming that technology is working. In some ways it's pretty interesting, but it's also quite disconcerting. Would you care to elaborate on your opinion? What do you find interesting and what do you find disconcerting? I am interested to know how this promotion of an artwork made with Hugin is being perceived. This is subjective and more difficult to understand than the excellent description of what you saw on the page. I must say, I think the overlayed picture is a clever but very odd feature. The thing I mainly dislike about it, is that it covers too much of the screen and it covers the part where I want to read. Scrolling obviously reveals the text but I now have to look at the middle of the screen rather than at the top where I would usually expect to read text. To me, that's annoying. I wouldn't mind a fully expanded version of the pano at the top and maybe another one(the same) at the bottom but they should stay there and scroll off the screen when I scroll up and down. At the moment, it looks like a pop-up ad that I can't even close. As I said, only lurking and hence feel free to disregard my PoV. But thanks for a superb app. Cheers, Steve -- 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] Repository acces in time between release candidates
On July 27, 2011 02:18:10 pm Vaclav Cerny - vatoz wrote: I have also found, that my Czech translation update from default branch ( 723668d8c4cc ) wasn't one of them. 2011.2 with copy of file from default branch will be fully translated and compilable/ installable/runnable. Sorry, this was an oversight. All other translations came in via the tracker [0]. I can commit it to 2011.2 branch Yes please do. In general, I do not move strings or translation from the default branch to the release branch. If you are sure of your PO file, please commit it to both branches in the future. If you are not sure, do what most translators do and attach the file to a tracker ticket. I am not sure, if it is a right thing to bypass our release manager in time between release candidates. Use your judgment. As a general rule: look at the last commit to the release branch. If it is tagged RC, adding another commit to that branch means forcing an extra release cycle. That's something you want to discuss with the release manager indeed. Maybe he is just counting down the hours until he can declare the RC final and open that can of cold beer and you might be interfering with that plan. If it is not tagged RC, as it is now, adding another commit to the branch does not change much. Translations and bug fixes are welcome. New strings and new features are not. Raise a discussion only if you need to add new strings / new features. The current status of the 2011.2 release is that it is suspended. There will be an RC3. I do not know when. 2011.2 is plagued by a nasty bug and there is no prediction how fast it can be fixed, if it is fixable. By now even I agree that it is a show stopper. We have hit the limit of release early release often. Yuv [0] https://bugs.launchpad.net/hugin signature.asc Description: This is a digitally signed message part.
Re: [hugin-ptx] Re: Website update
On July 27, 2011 02:18:44 pm Steve Wesemeyer wrote: At the moment, it looks like a pop-up ad that I can't even close. Got the message. will fix before the release becomes final. Thank you for your honest feedback without which I would not have realized that this was too much in-the-face. Yuv signature.asc Description: This is a digitally signed message part.
Re: [hugin-ptx] Re: Hugin 2011.2.0 RC2 32 bits windows crashes.
Thank you for https://bugs.launchpad.net/hugin/+bug/817104 I got confirmation from Matthew that he used a new SDK to build RC2. It is likely that a number of the newly observed bugs are a consequence of the new SDK. He will get back to Windows users with more information and a strategy moving forward with both Hugin itself and the new SDK. The old SDK had come in age and needed badly an update. Yuv On July 27, 2011 01:28:09 pm cri wrote: Yes, I've experience just yesterday the same problem with the 2011.2.0RC2 build under win XP 32bits. On 27 Lug, 17:27, Henk Tijdink h.tijd...@gmail.com wrote: Tested Hugin 2011.2.0 RC2 32bits windows of Matthew Petroff, but Hugin crashes during stitching with an enblend error. The beta version has not that problem. Used the installer, did a clean install with the installer and unpacked the zipfile. In all trials I get the crash. So it don't stitch. In the beta 1 version of Matthew Petroff I don't have that problem. Other windows users having that problem too? Will file a bug report in Launchpad. Kind regards, Henk Tijdink signature.asc Description: This is a digitally signed message part.
[hugin-ptx] Re: Repository acces in time between release candidates
Thanks. Commited.I am going to continue with bughunt. -- 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: Website update
Hi Yuv, On Wednesday 27 Jul 2011 22:30:51 Yuval Levy wrote: On July 27, 2011 02:18:44 pm Steve Wesemeyer wrote: At the moment, it looks like a pop-up ad that I can't even close. added a button to close it. does it feel better to you? http://hugin.sourceforge.net/releases/2011.2.0/en.shtml Yuv Thanks for the quick fix. It's nice that I can close it now although it's a shame that the picture is gone completely afterwards. Maybe, I'm just old-fashioned but my preference would simply be to have the panorama as part of the text, just above Changes since 2011.0.0 That way, you have - the Hugin Release Notes header at the very top - hugin's motto : more than just a panorama stitcher and then a beautiful example of what one can do with the program before reading about the detailed changes. No fancy CSS and no extra click needed. Cheers, Steve -- 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: Website update
Yuval Levy schrieb am 27.07.11 23:30: On July 27, 2011 02:18:44 pm Steve Wesemeyer wrote: At the moment, it looks like a pop-up ad that I can't even close. added a button to close it. does it feel better to you? http://hugin.sourceforge.net/releases/2011.2.0/en.shtml Yuv I had to allow jquery.com to make it work. That only hides David's panorama but in that case I wonder why I see a different panorama in the header area. How about exchanging the panorama (the one in the header) in the /releases section with with the panorama that is specially featured? 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
Re: [hugin-ptx] CRITICAL: join us to nuke the pesky bug that is plaguing the fast preview
On Tuesday, 26 July 2011 at 9:40:50 -0400, Yuval Levy wrote: On July 24, 2011 11:52:53 PM Greg 'groggy' Lehey wrote: I wasn't able to provoke this bug. Anything else I should try? I am no expert. You probably know better than me, and indeed you seem to be on the right track with the threading thing. What would you suggest we try next? Difficult to say. Everybody has his own procedures, and mine would have been with gdb if I had been able to reproduce the bug. What I'm going to do now is to try it out with Apple and Microsoft and see if I can reproduce it on those platforms with the same data. But if I do, I don't know what I can do about it, at least on Microsoft, where I don't have any development tools. Which version should I be trying? hugin-2011.2_beta? I just tried to apply a strategy that I know from solving finance problems to solve this code problem, helping those who can provoke the bug zero-in on the changeset that introduced it; and trying to find correlations between their specific situations and the buggy behavior while not being able to reproduce it myself. Certainly getting a collection of data on where it happens and where it doesn't might be useful. It seems we need at least: OS, including specific release Way the executable was built (libraries, etc) Number of processors It would also be good to find a standard set of images with which the bug shows itself. Another thing that might be of interest would be to set the preferences to use only one CPU and see if the problem still occurs. It might also be nice to add an option to limit the number of threads, but I suspect that's non-trivial. Greg -- Sent from my real computer Finger g...@freebsd.org for PGP public key. See complete headers for address and phone numbers. This message is digitally signed. If your Microsoft MUA reports problems, please read http://tinyurl.com/broken-mua pgp1DnA2JiyNQ.pgp Description: PGP signature
Re: [hugin-ptx] Re: Website update
On July 27, 2011 05:59:38 pm Carl von Einem wrote: How about exchanging the panorama (the one in the header) in the /releases section with with the panorama that is specially featured? the formats and purposes are completely different and I would not want to add restrictions on the featured splash screen artwork. Banner panorama: Purpose: embellish the website. Requirements won't change much over time. 165px tall, must somewhat repeat seamlessly (although this seems to have been relaxed in some contributions). Splash screen artwork: Purpose: promote the artwork created with Hugin. Requirements somewhat flexible over time as the universe of what can be done with Hugin is expanding. Currently (first crop of submission) requested ratio of approximately 1:3 to fit inside Hugin's logo; displayed on the release notes page at 256px tall. I would rather relax the requirements for the splash screen artwork - there will still be some sort of crop to the given format of the logo, but the artwork itself can expand beyond that and especially on the website I would like to see it stand out, break out of the existing frame the same way that Hugin help its user break free of the sensor or film frame. The frame stands for the limitations that Hugin overcomes. Yuv signature.asc Description: This is a digitally signed message part.
回覆：Re: [hugin-ptx] Stitching 4 images with Hugin
pgreenwood於 2011年7月27日星期三UTC+8下午10時00分34秒寫道： Hello. I'm a new member. I've used Hugin in the past to create a panorama (photo from one point rotating about the focal plane) and had pretty good success. Now I'm trying to stitch together 151 photos of a flat floor, mosaic-style, to preserve the layout of PEX tubing now buried in the slab. All photos were taken at 10 ft distance with (I believe) a Sony DSC-P200. I started with four contiguous photos, two rows and two columns. I identified three CPs on each pair of photos (adjacent and kiddy-corner). I expected a rock-solid rendering but when I tried to preview in either previewer, the result was unsatisfactory. I'm not exactly sure what x,y,z etc settings I should be using. (How) shall I upload files so you can see what I have? Have you seen the tutorial on the website? I believe that the translation optimizer is what you need to create a mosaic picture. http://hugin.sourceforge.net/tutorials/Mosaic-mode/en.shtml Maybe you should add more CPs or use the built-in CPfind. Regards, -- 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
