[hugin-ptx] [bug#678842] Stitcher canvas size, proportional change not bidirectional
Hi, I was looking at this[https://bugs.launchpad.net/hugin/+bug/678842 ] particular bug description : *Changing the horizontal canvas size in the Stitcher results in a corresponding proportional vertical canvas size just as would be expected. The same is not true when changing the vertical canvas size. A vertical canvas size change does not change the horizontal canvas size and in fact appears to function as a crop.* I have two questions:- 1. Is it really a bug? (read details below). 2. If yes, then please give suggestions how I should rectify it. Initially after looking at Panopanel.cpp[1] file especially function at Canvas Width and Height events(Line 73,74) and then looked for their respective functions i.e. WidthChange[2] and HeightChange[3], I thought there is just a typo in line 686(inside Height()) as it seemed that the author missed to include m_KeepViewOnResize as its present in WidthChange funtion), but build gave invalid parameter error for HeightChange funtion. So, I looked for their declaration and there I saw that the original author has coded it that way( I am assuming that he meant to do it in this way only as it does seems to be *just missed it* case.). Please see the definitions of HuginBase::PanoramaOptions::setWidth[4] and SetHeight[5]. If it needs to be modified, then please suggest me what formula's and condition should I use to modify the horizontal canvas size as I don't have much knowledge of this Regards Neeraj [1] http://hugin.sourceforge.net/docs/html/PanoPanel_8cpp-source.htmlPanoPanel.cpp [2] http://hugin.sourceforge.net/docs/html/PanoPanel_8cpp-source.html#l00662Func-WidthChange [3] http://hugin.sourceforge.net/docs/html/PanoPanel_8cpp-source.html#l00679Func- HeightChange [4] http://hugin.sourceforge.net/docs/html/PanoramaOptions_8cpp-source.html#l00253SetWidth [5] http://hugin.sourceforge.net/docs/html/PanoramaOptions_8cpp-source.html#l00293SetHeight -- 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] [bug#678842] Stitcher canvas size, proportional change not bidirectional
Yes it is necessary to be able to change vertical field of view independently of horizontal field of view - this is the only way to change the panorama aspect ratio. If there is a bug it is that both sliders should be completely independent. -- Bruno On 31 Mar 2011 07:50, Neeraj Gupta neeraj.gu...@nsitonline.in wrote: -- 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] enfuse for tonemapping of a single RAW
It is a GOOD IDEA :-) i can't help thinking that all this debating, the feature could have been built by now ;-))) (not by me though) (not an excuse to simply build features instead of having a good debate, i fully realize.) Jeffrey -- 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] enfuse for tonemapping of a single RAW
On 31 March 2011 09:59, Jeffrey Martin 360cit...@gmail.com wrote: It is a GOOD IDEA :-) i can't help thinking that all this debating, the feature could have been built by now ;-))) (not by me though) (not an excuse to simply build features instead of having a good debate, i fully realize.) Jeffrey Yeah, but it would have been of mediocre quality at best. RAW processing is out of scope of hugin and if it was implemented it would be something as simple as using dcraw to load an image. Nobody (hyperbole) uses dcraw to process their RAWs, because it's too simple to be useful alone. We couldn't compete with applications like Lightroom, Aperture or Rawtherapee. It would probably take a few man years to get there. Lukas -- You received this message because you are subscribed to the Google Groups Hugin and other free panoramic software group. A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ To post to this group, send email to hugin-ptx@googlegroups.com To unsubscribe from this group, send email to hugin-ptx+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/hugin-ptx
Re: [hugin-ptx] Re: [REVIEW] Pushing Hugin changes to VIGRA upstream
2011/3/26 Lukáš Jirkovský l.jirkov...@gmail.com: On 26 March 2011 08:03, Pablo d'Angelo pablo.dang...@web.de wrote: Hi Lukas, Please review them and comment on them, because I'd like to send them to the upstream soon. I'm not sure about copyrights in some cases (eg. canvasSize patch) but I think most of it is Pablo's work. I'll look it up in the subversion history. great, looks good, feel free to submit those to vigra! ciao Pablo Hello Pablo, thank you for giving it the thumbs up, especially given the fact it's mostly your work. I'll wait some time if there was some response from others, meanwhile I'd like to update the copyright headers of the affected files. Have a nice day, Lukas I send the patches upstream today. See the following emails: https://mailhost.informatik.uni-hamburg.de/pipermail/vigra/2011-March/000818.html https://mailhost.informatik.uni-hamburg.de/pipermail/vigra/2011-March/000819.html https://mailhost.informatik.uni-hamburg.de/pipermail/vigra/2011-March/000820.html https://mailhost.informatik.uni-hamburg.de/pipermail/vigra/2011-March/000821.html https://mailhost.informatik.uni-hamburg.de/pipermail/vigra/2011-March/000822.html https://mailhost.informatik.uni-hamburg.de/pipermail/vigra/2011-March/000823.html https://mailhost.informatik.uni-hamburg.de/pipermail/vigra/2011-March/000825.html https://mailhost.informatik.uni-hamburg.de/pipermail/vigra/2011-March/000824.html Lukas -- You received this message because you are subscribed to the Google Groups Hugin and other free panoramic software group. A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ To post to this group, send email to hugin-ptx@googlegroups.com To unsubscribe from this group, send email to hugin-ptx+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/hugin-ptx
[hugin-ptx] Re: How can I get Hugin to use more than 2047 MB memory?
On Mar 20, 12:11 am, dbur dburton@gmail.com wrote: when I try to set the memory usage above 2047 Hugin just changes it to 1MB. the same happens under OS X 10.6.x also, the input fields for the memory usage are tiny, only 2-3 digits are visible. joergen -- 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] OT: the future of enfuse/enblend
sorry about the OT post. It has been very quiet around enfuse/enblend for the last months since the 4.0 release... does anybody know where the project is going, or what plans/developments are coming? joergen -- 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: [REVIEW] Pushing Hugin changes to VIGRA upstream
And all patches have been accepted! I'm still working on some tests, but we are getting closer to a time when Hugin can work with system wide installation of VIGRA. Lukas -- You received this message because you are subscribed to the Google Groups Hugin and other free panoramic software group. A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ To post to this group, send email to hugin-ptx@googlegroups.com To unsubscribe from this group, send email to hugin-ptx+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/hugin-ptx
[hugin-ptx] Re: OT: the future of enfuse/enblend
Joergen - On Mar 31, 3:09 pm, Joergen Geerds jgee...@gmail.com wrote: sorry about the OT post. Hey, it's not OT at all. Does anybody know where the project is going, or what plans/developments are coming? I don't known what my co-developers have up their sleeves, but I have some patches in my queue. Don't hold your breath, though. I've had an idea of a new way to optimize the seam position, which I have passed on to Brent. AFAIK, he is thinking about a twist of the current seam-line optimizer to get rid of those pesky loops: https://bugs.launchpad.net/enblend/+bug/739060 And maybe he'll find a way to improve on the DT: https://bugs.launchpad.net/enblend/+bug/739057 HTH, Chris -- 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] [REVIEW] Pushing Hugin changes to VIGRA upstream – Hugin changes
Hello Yuv, I'm not yet convinced it's a good thing to do at this point in time. Still the users would have to manually apply several patches to VIGRA unless there's a public clone of VIGRA with changes applied so applying one more patch doesn't really hurt anything. I plan to send the patches upstream on Thursday or Friday, so we may find out whether the changes to hugin doesn't go in vain quite soon. Lukas The changes to VIGRA were all accepted upstream. I pushed the branch system_vigra which contains the changes necessary to use the system wide installation of VIGRA. It needs the VIGRA from the VIGRA mercurial repository [1] to compile. At this point everything works with the exception of hugin_hdrmerge. Hugin_hdrmerge depends on some of the VIGRA internals and I'm not sure how to fix it. Also I had to remove the use of ImageCache in the deghosting implementation. Enjoy, Lukas [1] http://www.informatik.uni-hamburg.de/~meine/hg/vigra -- 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: OT: the future of enfuse/enblend
On Mar 31, 11:00 am, cspiel csp...@freenet.de wrote: I don't known what my co-developers have up their sleeves, but I have some patches in my queue. Don't hold your breath, though. Chris, Glad to hear that it's not on hiatus. enfuse is such an integral part of my workflow, that I really would like to see it developed further... is there any decent/good way to submit feature requests, or do you prefer personal emails? joergen -- 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: [REVIEW] Pushing Hugin changes to VIGRA upstream
Nice work! I've been working on getting Hugin to cross-compile from Linux to Windows in my precious spare time, and the stock vigra lib already compiles, so this will definitely help! There are still a few packages missing in the cross-compiling system I'm using (mingw-cross-env [0]), I'd have to check which ones, but I hope that in the end I'll be able to do a full cross-compile. This will make the process of releasing Windows binaries even easier (at least for me). Note that I *really don't* have that much spare time, so it may take a while. Of course anyone interested may take a look as well, we're talking open source here :) [0] http://mingw-cross-env.nongnu.org/ -- Bart -- 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: GSOC 2011 Student Introduction
Hi Flo, welcome back. On 25 Mrz., 19:31, Florian Achleitner florian.achleitner. 2.6...@gmail.com wrote: When I followed the blueprint collection on the mailing list and launchpad I got interested in the vertical-line-horizon-detector blueprint [1]. It could give me the chance to use the courses content beyond examples and exercises. The blueprint says there exists already some work on that. Is it somewhere in the repo? The code is in the repo, folder src/lens_calibrate. This code is for calibrating lenses. As a side effect it could also be used for detection of vertical lines. Thomas -- 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: OT: the future of enfuse/enblend
Joergen - On Mar 31, 5:38 pm, Joergen Geerds jgee...@gmail.com wrote: Glad to hear that it's not on hiatus. Well, taking the current commit rate as a gauge, the Enblend/Enfuse project pretty much is asleep. Is there any decent/good way to submit feature requests, or do you prefer personal emails? The preferred way for any kind of feature request or bug reports is via the LaunchPad bug tracker: https://bugs.launchpad.net/enblend OTOH, if you have got one or more patches against the tip of the hg repo _and_ you manage to convince/sweet-talk me that they are good for all of the whole wide blending/fusing world, you can take a short cut: instead of attaching your patches to the bug tracker's ticket, send them directly to me and I'll apply them (usually only after an intense e-mail discussion that is). Cheers, Chris -- 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: [REVIEW] Pushing Hugin changes to VIGRA upstream
On 31 March 2011 18:06, Bart van Andel bavanan...@gmail.com wrote: Nice work! I've been working on getting Hugin to cross-compile from Linux to Windows in my precious spare time, and the stock vigra lib already compiles, so this will definitely help! There are still a few packages missing in the cross-compiling system I'm using (mingw-cross-env [0]), I'd have to check which ones, but I hope that in the end I'll be able to do a full cross-compile. This will make the process of releasing Windows binaries even easier (at least for me). Note that I *really don't* have that much spare time, so it may take a while. Of course anyone interested may take a look as well, we're talking open source here :) [0] http://mingw-cross-env.nongnu.org/ -- Bart Thank you. I'm glad it could make your work on getting cross-compilation easier. Your work seems very interesting. I wish you luck, this could be very useful for Hugin. Lukas -- You received this message because you are subscribed to the Google Groups Hugin and other free panoramic software group. A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ To post to this group, send email to hugin-ptx@googlegroups.com To unsubscribe from this group, send email to hugin-ptx+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/hugin-ptx
Re: [hugin-ptx] enfuse for tonemapping of a single RAW
well, there are tons of raw developing programs that use dcraw. so what do you mean? no one uses dcraw command line? -- 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] enfuse for tonemapping of a single RAW
On 31 March 2011 20:57, Jeffrey Martin 360cit...@gmail.com wrote: no one uses dcraw command line? That's what I meant. -- 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: OT: the future of enfuse/enblend
Has anyone studied smartblend verbose output to figure out how it works? It is vastly superior to enblend (in terms of seam placement). And it's old, crusty, closed-source, and definitely not going to be updated again. This to me is one of the biggest drawbacks to the hugin collection of software. -- 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: OT: the future of enfuse/enblend
On Mar 31, 1:50 pm, cspiel csp...@freenet.de wrote: Well, taking the current commit rate as a gauge, the Enblend/Enfuse project pretty much is asleep. hmm, unfortunately, I don't know enough about coding, I am more an enduser. The preferred way for any kind of feature request or bug reports is via the LaunchPad bug tracker: https://bugs.launchpad.net/enblend done and posted to the launchpad site... I hope it makes any sense. OTOH, if you have got one or more patches against the tip of the hg repo _and_ you manage to convince/sweet-talk me that they are good for all of the whole wide blending/fusing world, you can take a short cut: instead of attaching your patches to the bug tracker's ticket, send them directly to me and I'll apply them (usually only after an intense e-mail discussion that is). I will fall back to that once I find more important things I would like to see in enfuse (and that would help the world). But thank you so much for the info so far, and thx to everyone on the dev team for coding enfuse... it's awesome. joergen -- 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: [REVIEW] Pushing Hugin changes to VIGRA upstream
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Bart Am 31.03.2011 18:06, schrieb Bart van Andel: Nice work! I've been working on getting Hugin to cross-compile from Linux to Windows in my precious spare time, and the stock vigra lib already compiles, so this will definitely help! I had a look at his, too. However, without being able to actually use the resulting binaries due to my lack of a windows license and my lack of interest to get one, I figured that I won't be able to support this kind of port. On the other side, if I had a windows license and would be willing to create panos on this platform, wouldn't it be more natural to use the (available) free MS development tools for porting? I think that hugin needs to attract some more windows users being able to fend for their OS themselves. Providing binaries that are not tested by the producer and that can not be properly supported, therefore, does not help. Sorry, just my 2 cents. Regards Stefan Peter - -- In theory there is no difference between theory and practice. In practice there is. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJNlODcAAoJEBgqi52L7+L/13kH/ja8c8DNhfUTlPEwXiIdtZVB Pcf0n1rcEqdBTT3GmNks9Hfr9St/m9ct70EPIu5pIPyDWv+d/2M08KaowQphuJ1D 1BxuLod3DlEfNbdTCpJd0JXoG+/pOxAwslPDfMgKX9BB7LKMgx5OLDRtyHcT5T/O NbMqFWmkUVXK7+/sWsjtrPNcT8Xf7kRmcqD0CU+19qX9i5VjXxBS58/t7QSUhnyg q1MJSo2E/5KYU172dfXCEaPCS1zZiok0kvqpdIAdFcU9S3DmJVr/X42/RT5ykS8D oq509Ml8Hv6m4lMCLglNkRWZKzzcFTxE4UUda8TQzzC3czxCknDpOLLt3wviqO8= =WQR/ -END PGP SIGNATURE- smime.p7s Description: S/MIME Cryptographic Signature
[hugin-ptx] Re: OT: the future of enfuse/enblend
Well, I didn't exactly study the verbose output, but some time ago, I sent Michael Norel (the author of Smartblend) a message, asking about SB going open source. This was a follow-up on an email sent earlier and discussed briefly here [0]. Maybe the email and reply are interesting to the group, so here they are: -me (9 Feb 2011)- Hello Michael, It's been almost 2 years since we were last in touch. I imagine you have been very busy. Is there any news on the Smartblend sources and/or any further development? Out of curiosity: what other projects are you involved in? Anything image-related? I found out that you used to have a website about Smartblend, but it has been turned into one of these annoyingly useless search page sites by some domain scraper, unfortunately. Hope to hear from you soon. Best regards, Bart van Andel -Michael Norel (10 Feb 2011)- Hello. Still no development and no plans for SB and no news. But anyone still can contribute to ENBLEND project or related. There a re many good algorithms to use for blending in public domain. psychovisual error + kolmogorov min cut + ENBLEND + subpixel acuracy and pyramid with alpha channel = smartblend Last years my work is Computer Vision , Real Time SFM , Augmented Reality. So i spend my time for very intresting things, more complex than smartblend. Thanks. --- Sorry for not posting this sooner, I kind of forgot about it until I read Jeffrey's post. [0] https://groups.google.com/forum/#!topic/hugin-ptx/5oRw_6uVsoI -- Bart -- 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: [REVIEW] Pushing Hugin changes to VIGRA upstream
Hi Stefan, On Thursday, March 31, 2011 10:15:31 PM UTC+2, Stefan wrote: Am 31.03.2011 18:06, schrieb Bart van Andel: I've been working on getting Hugin to cross-compile from Linux to Windows in my precious spare time, and the stock vigra lib already compiles, so this will definitely help! I had a look at his, too. However, without being able to actually use the resulting binaries due to my lack of a windows license and my lack of interest to get one, I figured that I won't be able to support this kind of port. On the other side, if I had a windows license and would be willing to create panos on this platform, wouldn't it be more natural to use the (available) free MS development tools for porting? I understand your situation, but from my point of view, compiling under Linux is usually a bliss. I like the way things can be automated using the shell in Linux. And this mingw-cross-env thing really takes away a lot of pain. For instance, I can build the required libs (minus some that I still need to add) using a single make command. The system will automatically download the sources for me, including dependencies, and build everything into static libs. The only thing left to do then is to compile Hugin (and Enblend, APSCpp, ...) itself, using cmake and some cross-compiling settings. Pretty easy. I'm using a virtual machine to do this. On the other hand, using the MS path requires many more steps. A whole lot of packages need to be compiled separately. Just take a look at [0] to see what I mean. Ok, if your initial setup is done (building dependencies), building and rebuilding Hugin is not a problem, except when some dependency needs a rebuild... To me, the Linux approach is much simpler. And if the workflow has been setup correctly, Hugin can be built on a (native) Linux machine, QA tested by a few Windows pre-testers, and then distributed. I think that hugin needs to attract some more windows users being able to fend for their OS themselves. Providing binaries that are not tested by the producer and that can not be properly supported, therefore, does not help. I agree about quality assurance. Distributing non-tested binaries is not a good thing. But this kind of testing has to be done for native Windows builds (built on a Windows machine I mean) as well, and depending on the builder, this will happen or not. Sorry, just my 2 cents. No apologies required, your points are valid. [0] http://wiki.panotools.org/Hugin_SDK_(MSVC_2010) -- Bart -- 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: enfuse for tonemapping of a single RAW
Am 31.03.2011 20:57, schrieb Jeffrey Martin: well, there are tons of raw developing programs that use dcraw. Most raw developing programs use dcraw code to read and decode raw files, but very few actually use the dcraw post processing. There are better highlight recovery algorithms, there are far better interpolators, better white balance techniques, denoising and so on. dcraw even treats the camera orientation sensor differently on some cameras (it uses maker notes instead of EXIF) and it delivers a different image size. As I wrote before: A shell script to create three temporary files by varying the dcraw -b parameter and a subsequent enfuse will provide you with the desired functionality. -- Erik Krause http://www.erik-krause.de -- 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: [REVIEW] Pushing Hugin changes to VIGRA upstream
On Thu 31-Mar-2011 at 15:10 +0200, Lukáš Jirkovský wrote: And all patches have been accepted! I'm still working on some tests, but we are getting closer to a time when Hugin can work with system wide installation of VIGRA. Lukáš, thanks for doing this, it has been needed for a long time. Regarding fixing the Hugin sources, there is no need to remove the Hugin copy of the library from the sources if it is possible to build with the system library as an option. vigra now has a vigra-config tool which gives output similar to pkg-config, so it should be possible for cmake to detect if the system vigra is 1.7.1 -- 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: [REVIEW] Pushing Hugin changes to VIGRA upstream
On Friday, April 1, 2011 1:08:29 AM UTC+2, Bruno Postle wrote: Regarding fixing the Hugin sources, there is no need to remove the Hugin copy of the library from the sources if it is possible to build with the system library as an option. Is there a valid point in keeping a local copy of a library if the official one works? If you mean keeping the local copy until the changes are in a release version of Vigra, I can understand, but otherwise? -- Bart -- 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: [REVIEW] Pushing Hugin changes to VIGRA upstream
On Thu 31-Mar-2011 at 16:18 -0700, Bart van Andel wrote: On Friday, April 1, 2011 1:08:29 AM UTC+2, Bruno Postle wrote: Regarding fixing the Hugin sources, there is no need to remove the Hugin copy of the library from the sources if it is possible to build with the system library as an option. Is there a valid point in keeping a local copy of a library if the official one works? If you mean keeping the local copy until the changes are in a release version of Vigra, I can understand, but otherwise? Yes and no, it can't be removed until there is a vigra release, but we don't know when this will be. Also the pressure from Linux distributions is for binary packages to use system libraries, they don't care what unused cruft is in the Hugin tarball. If the latest vigra happens to fix any of the longstanding bugs that keep getting reported in the hugin/enblend trackers then it could even be worth updating the vigra code in hugin/enblend. -- 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
