[hugin-ptx] Re: Panini patents?
On Aug 5, 2:49 pm, D M German wrote: > Thomas> I'm sure the trick is doable, but it clearly needs both good > Thomas> legal preparation and good management of the patent rights. > Thomas> Which in turn need to be sustained by some revenue. So it > Thomas> won't happen unless I can actually find some customers who want > Thomas> to build and sell Panini-based products. If I were 20 years > Thomas> younger I'd probably try to start a company to make TV and > Thomas> movie rendering software (and probably lose my shirt) but as it > Thomas> is, someone else is going to have to do that. If any of you > Thomas> wants to volunteer, or knows how to sell new technology to TV > Thomas> or movie producers (or JVC Corporation, for that matter) I > Thomas> would be happy to hear about it. > > I had informal (ie. non legal) conversation with E. Moglen and Bradley > M. Kuhn (Technology Director of Software Freedom Law Center) with regard > to this issue. The FSF would helps us with any questions regarding this > issue. > > I described to them the main issue and it seems that the simplest > solution for everybody (the patent holders and libpano/hugin) is that > you, Tom, re-license the code from its current license (BSD-3 clauses) > to a GPLv3+. That was my conclusion also. Next time I revise the Panini-general code in libpano13 I shall put it under GPLv3. For version 1 of my Panini viewer/perspective tool I am using the Apache license, which is GPLv3 compatible but also allows a bit more restrictive licensing for proprietary uses, and GPLv3 for the parts that don't implement anything I want to patent. > > Our code is GPLv2+ hence, it can link with GPLv3+ as in practice it will > become GPLv3 at build time. > > Now, from a more pragmatic issue, the uncertainty of if a patent is > going to exist or not is an important issue. Tom, your intention is to > patent, and therefore we must take the necessary steps to address this > potential problem. > > Tom, do you make a claim on the Equirectangular Pannini? No, and not panini_general either. As implemented in libpano13, those projections are public domain as far as I am concerned. What I intend to patent is a graphical Pannini engine, like the one in Panini, plus various processes that use it for specific practical purposes like reformatting movies to fit different screen widths. I will claim some aspects of my GPU implementation as inventions, but not the projection itself. Regards, Tom > > --dmg > > -- > Daniel M. German > http://turingmachine.org/http://silvernegative.com/ > dmg (at) uvic (dot) ca > replace (at) with @ and (dot) with . -- 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] Extra Large and Gigapixel help with Hugin
Hi Emaad, On August 21, 2010 03:11:06 am Emad ud din Butt wrote: > I am having problems stitching extra large panoramas with Hugin. I am > forwarding .pto, mk and stitching window files. I looked at the files attached to your message. They raise more questions than answers. > I have successfully created 4000x2000 panoramas. But when I try to make > 8000x4000 or bigger full res panos, hugin just hangs after several hours. > Total number of images is 291. So here I go with a first bunch of questions: 1. how many hard disks does your system have? how much space is free on each one of them? 2. what version of Hugin are you using? and what version of Enblend-Enfuse? I see hugin-2010.1.0.4920 and hugin.win32.5161 in the paths to the executables, but path names can be arbitrary. 3. Did Hugin *hang*, i.e. become non-responsive and you had to kill it in the task manager? or did it *wait* with an error message window for you to copy&paste and then terminate the program normally? From the stitching window output the immediate reason for the stitching process to fail seems to be lack of disk space (emphasis mine): | enfuse: an exception occured | enfuse: enblend: error writing to image swap file. | *Most likely cause: No space for temporary files*. | Make sure that there is enough space in the temporary directory That said, the project shows unusual patterns and there likely are more errors. More information is required to understand: 4. How did you position the camera to shoot the images? Hand held? On a tripod? On a calibrated panoramic head? 5. Did you do exposure-bracketing? Consistently on every shoot? Or only when shooting high contrast areas such as windows? 6. In what mode was the camera? Manual? Automatic? Anything in between? It would help if you could post the following nine pictures, selected in different areas of the project that show anomalies to explain. Please post out of camera originals so that we can analyze the whole EXIF input. P8150053.JPG P8150054.JPG P8150055.JPG P8150132.JPG P8150133.JPG P8150134.JPG P8150135.JPG P8150136.JPG P8150341.JPG The .pto and .mk files seem to be for the 4000x2000 output. From a quick look, at least a few things are not right. Could be at any of the following stages or combination thereof: shooting, cp detection, optimization, stitching. The errors might not show when stitched at 4000x2000 but they will show when stitched at full resolution. I don't want to sound pessimistic but it is highly unlikely that I would call a stitch with the project files you posted a "success" and at this point it is too early to say if it can be fixed. Yuv signature.asc Description: This is a digitally signed message part.
[hugin-ptx] Re: Multi-row pano layout?
What control point detector did you use? You can check which one is default in the preferences. 30 images should not pose a problem really. As far as I understand, APSCpp and Panomatic follow a different approach when it comes to matching images. Panomatic tries to match every pair of images separately, while APSCpp collects all control points in one big tree and matches all images at once, at least the more recent versions by Tom Sharpless. Correct? Anyway 30 images isn't really that big a number, so they should both be able to cope with that. BTW I'm using Panomatic most of the times, and sometimes when I first start up Hugin (on a Windows restart) Panomatic crashes when run. If I then restart Hugin and try again, it works correctly. Not sure if it's a bug or a configuration problem, but could it be you're experiencing the same thing? -- Bart On 20 aug, 23:53, Joel B wrote: > Bart: I tried the "Align" button, and Hugin eventually froze and > became nonrespondent, and I think crashed - I was guessing because of > the sheer number of unmatched pairs it was trying to match. I didn't > know the Layout mode had made it into preview though - thanks, I'll > have to check that out. > > T. Modes: > That sounds very promising! I didn't have that option, but I was > running 2009.04. I found builds from lemur with more recent versions, > and I'll try those options out. Thanks! > > On Aug 19, 10:30 pm, "T. Modes" wrote: > > > > > On 19 Aug., 19:17, Joel B wrote: > > > > I've been working with some multi-row panos, similar to the ones on > > > the multi-row tutorial, > > > actually:http://hugin.sourceforge.net/tutorials/multi-row/en.shtml > > > And when I hit the "align" button, it seems to try to find points in > > > *every* pair of images. In my case, however, I'm doing a 360-degree, > > > two-row panorama, that has 30 or so images, not just the 8 in the demo > > > - so instead of 36 possible pairs of which about a third will be used, > > > it has to match more than 450 possible matches. Is there a way to > > > arrange the images and tell it which ones it should try to match up? > > > Ideal would be an interface similar to a combination of the first and > > > last pictures in the multi-row tutorial, actually, where I could drag > > > the photos around, overlapping them, to specify which photos overlap > > > visually, and have Align just try those pairs. > > > This can be achieved by using a multi-row control point detector > > setting. > > seehttp://wiki.panotools.org/Hugin_Preferences#Control_Point_Detectors > > andhttp://wiki.panotools.org/Hugin_Parameters_for_Control_Point_Detector... > > > If you want to use it with the assistant tab, you need to set the > > multi-row detector as default. > > > 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: Multi-row pano layout?
Bart: I tried the "Align" button, and Hugin eventually froze and became nonrespondent, and I think crashed - I was guessing because of the sheer number of unmatched pairs it was trying to match. I didn't know the Layout mode had made it into preview though - thanks, I'll have to check that out. T. Modes: That sounds very promising! I didn't have that option, but I was running 2009.04. I found builds from lemur with more recent versions, and I'll try those options out. Thanks! On Aug 19, 10:30 pm, "T. Modes" wrote: > On 19 Aug., 19:17, Joel B wrote: > > > I've been working with some multi-row panos, similar to the ones on > > the multi-row tutorial, > > actually:http://hugin.sourceforge.net/tutorials/multi-row/en.shtml > > And when I hit the "align" button, it seems to try to find points in > > *every* pair of images. In my case, however, I'm doing a 360-degree, > > two-row panorama, that has 30 or so images, not just the 8 in the demo > > - so instead of 36 possible pairs of which about a third will be used, > > it has to match more than 450 possible matches. Is there a way to > > arrange the images and tell it which ones it should try to match up? > > Ideal would be an interface similar to a combination of the first and > > last pictures in the multi-row tutorial, actually, where I could drag > > the photos around, overlapping them, to specify which photos overlap > > visually, and have Align just try those pairs. > > This can be achieved by using a multi-row control point detector > setting. > seehttp://wiki.panotools.org/Hugin_Preferences#Control_Point_Detectors > andhttp://wiki.panotools.org/Hugin_Parameters_for_Control_Point_Detector... > > If you want to use it with the assistant tab, you need to set the > multi-row detector as default. > > 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
