Carlos, thank you for your answer! Let me explain the situation once again and answer the questions you asked. Forgive me if i'll miss some important details, as i said, i'm not expert in this area, so feel free to ask for information.
Earlier when we used our old device (that's one our own design), we put in server Hugin .opt that we had got from desktop Hugin after stitching panoramas of this device. And thanks to that .opt we got good results. That device had only one camera module and was rotated by panohead (another one our own design). And that stitching was pretty good. Then we've made our custom assembly, that has 4 5MP camera models with fisheye lens. There are 60 degrees between the central axis of the lens of horisontal and vertical pairs of camera modules. <https://lh3.googleusercontent.com/-KLx3ulYzNw4/VjcvvjVmE5I/AAAAAAAAAPY/-AGgQRDQ4ok/s1600/10562_44189746_3_4.jpg> Assemble doesn't imply a panohead, all 4 modules are placed as close to each other as it's possible and are rotated on monopod around the least point of parallax. We've chose this way, 'cause it make shooting process faster. We tried to use old .opt, but it didn't work well. That's why we are searching for hugin expert. So if this information helps you to get good results, we'll glad to work with you, and we are waiting for your proposals about the cost of co-operation and timing of your work. воскресенье, 25 октября 2015 г., 18:46:38 UTC+3 пользователь Lada написал: > > Hello! > > We are looking for the HUGIN Server Process expert. > Previously we liked results of HUGIN web service API work, but after > changing the device that takes pictures for panoramas, panoramas stitch > became very bad. Now the device consist of 4 camera module located as close > to each other as possible. When photographer press a button all 4 cameras > take a picture. After that, photographer turns the device 120 degrees and > pushes a button (+ 4 pictures), rotates 120 and presses again (+ 4 > pictures). Thus we have 12 pictures to stitch the panorama. > Although cameras are positioned as close as possible, there are problems > with parallax. Because of this, problems with detecting control points > exist. However, other software (Autopano) gives good results. > We are looking for someone who can help us adjust HUGIN api to get results > not worse than we are now receiving from the Autopano. > I attached a link to 5 folders with source pictures for the panoramas and > the results we got when had stitched them with the Autopano. > https://drive.google.com/drive/u/1/folders/0B7LQ8sYQPdl7RXhLTWpNWEt1LTg > > Please try to make panoramas, and if you find the parameters that can be > set in HUGIN Server Process for good automatically stitching, contact me by > e-mail (----), we will be happy to cooperate with you. Please write in a > letter to the desired reward, what time you'll need and attach the results > of stitching that you will got. > -- A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ --- You received this message because you are subscribed to the Google Groups "hugin and other free panoramic software" group. To unsubscribe from this group and stop receiving emails from it, send an email to hugin-ptx+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/hugin-ptx/bf3ea0e9-e61f-46fc-9af3-2a63b01748a9%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
