set of cameras for pano pictures

classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|

set of cameras for pano pictures

PanoTools NG mailing list
Hi all,I am new tothis forum.I aminterested in taking pano pictures for VT for educational purposes and I am abeginner in this field. I wouldtake pictures with (also) moving subjects.I would usea set of action cams (like gopro) because they are light and with wide anglelenses.I am tryingHugin for stitching pictures.
 
1) thecameras would have a fixed relative configuration (let's say, 5 along the sidesof a pentagon and one for the zenith): Is there any methods to enter parametersof the configuration, for instance yaw and relative position?
 
2) Thecameras would have a parallax error but the distance of the nodal points of thecameras is known. Would it be useful to pass these data to Hugin? If yes, how?
 
3) I amtrying with a cheap cam (Xiaomi yi). I took 5 pictures, 0 degrees pitch, oneper 72 degrees around the nodal point. Thestitching results are strange: I may suppose the main reason is that Hugin does not know the data ofthe lenses of the camera. It assumesHfov is 70 degrees.Accordingto cam specs: focal length is 2,73 mm (which Hugin also assumes), D(iagonal ?)FOV is 155degrees, sensor size (Sony Exmor R bi) is 1/2.3 inch. Would it bepossible from these data to obtain the focal length,35 mm equivalent, theHfov(v) or the crop factor? Would it be considered a fisheye, full frame, lens?
 
Sorry forso many questions.Thank youin advance.Giuseppe
Reply | Threaded
Open this post in threaded view
|

Re: set of cameras for pano pictures

PanoTools NG mailing list
Am 18.06.2015 um 20:45 schrieb giuseppe porciani
[hidden email] [PanoToolsNG]:

> 1) thecameras would have a fixed relative configuration (let's say, 5
> along the sidesof a pentagon and one for the zenith): Is there any
> methods to enter parametersof the configuration, for instance yaw and
> relative position?

You can apply a project file as a template.

> 2) Thecameras would have a parallax error but the distance of the
> nodal points of thecameras is known. Would it be useful to pass these
> data to Hugin? If yes, how?

No. There is no way to automatically fix parallax errors. BTW: The term
"Nodal Point" is not correct, it names a different point on the optical
axis. Better use "No-Parallax-Point".

> 3) I amtrying with a cheap cam (Xiaomi yi). I took 5 pictures, 0
> degrees pitch, oneper 72 degrees around the nodal point. Thestitching
> results are strange: I may suppose the main reason is that Hugin does
> not know the data ofthe lenses of the camera. It assumesHfov is 70
> degrees.Accordingto cam specs: focal length is 2,73 mm (which Hugin
> also assumes), D(iagonal ?)FOV is 155degrees, sensor size (Sony Exmor
> R bi) is 1/2.3 inch. Would it bepossible from these data to obtain
> the focal length,35 mm equivalent, theHfov(v) or the crop factor?
> Would it be considered a fisheye, full frame, lens?

 From 155° diagonal FOV I would assume a fisheye lens. Unfortunately the
sensor inch values don't tell anything about the real sensor dimensions,
hence the crop factor can't be calculated. Hugin can find out the
correct values for you, if you let it optimize them. However, the better
place for detailed hugin questions would probably be the hugin mailing
list: https://groups.google.com/forum/#!forum/hugin-ptx

Erik Krause


------------------------------------

------------------------------------

--
<*> Wiki: http://wiki.panotools.org
<*> User Guidelines: http://wiki.panotools.org/User_Guidelines
<*> Nabble (Web) http://panotoolsng.586017.n4.nabble.com/
<*> NG Member Map http://www.panomaps.com/ng
<*> Moderators/List Admins: [hidden email]

------------------------------------

Yahoo Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/PanoToolsNG/

<*> Your email settings:
    Individual Email | Traditional

<*> To change settings online go to:
    http://groups.yahoo.com/group/PanoToolsNG/join
    (Yahoo! ID required)

<*> To change settings via email:
    [hidden email]
    [hidden email]

<*> To unsubscribe from this group, send an email to:
    [hidden email]

<*> Your use of Yahoo Groups is subject to:
    https://info.yahoo.com/legal/us/yahoo/utos/terms/

Reply | Threaded
Open this post in threaded view
|

Re: set of cameras for pano pictures

PanoTools NG mailing list
Thank you very much for quick answer.I will contact  https://groups.google.com/forum/#!forum/hugin-ptxas you advised.
I also found the diagonal of the sony sensor is 7,77 mm. I will try to input a good data for the lenses.

Giuseppe



     On Friday, June 19, 2015 1:18 PM, "Erik Krause [hidden email] [PanoToolsNG]" <[hidden email]> wrote:
   

 Am 18.06.2015 um 20:45 schrieb giuseppe porciani
[hidden email] [PanoToolsNG]:

> 1) thecameras would have a fixed relative configuration (let's say, 5
> along the sidesof a pentagon and one for the zenith): Is there any
> methods to enter parametersof the configuration, for instance yaw and
> relative position?

You can apply a project file as a template.

> 2) Thecameras would have a parallax error but the distance of the
> nodal points of thecameras is known. Would it be useful to pass these
> data to Hugin? If yes, how?

No. There is no way to automatically fix parallax errors. BTW: The term
"Nodal Point" is not correct, it names a different point on the optical
axis. Better use "No-Parallax-Point".



> 3) I amtrying with a cheap cam (Xiaomi yi). I took 5 pictures, 0
> degrees pitch, oneper 72 degrees around the nodal point. Thestitching
> results are strange: I may suppose the main reason is that Hugin does
> not know the data ofthe lenses of the camera. It assumesHfov is 70
> degrees.Accordingto cam specs: focal length is 2,73 mm (which Hugin
> also assumes), D(iagonal ?)FOV is 155degrees, sensor size (Sony Exmor
> R bi) is 1/2.3 inch. Would it bepossible from these data to obtain
> the focal length,35 mm equivalent, theHfov(v) or the crop factor?
> Would it be considered a fisheye, full frame, lens?

 From 155° diagonal FOV I would assume a fisheye lens. Unfortunately the
sensor inch values don't tell anything about the real sensor dimensions,
hence the crop factor can't be calculated. Hugin can find out the
correct values for you, if you let it optimize them. However, the better
place for detailed hugin questions would probably be the hugin mailing
list: https://groups.google.com/forum/#!forum/hugin-ptx

Erik Krause


------------------------------------

------------------------------------

--
------------------------------------

Yahoo Groups Links





 
Reply | Threaded
Open this post in threaded view
|

Re: set of cameras for pano pictures

PanoTools NG mailing list
giuseppe porciani [hidden email] [PanoToolsNG] wrote:
>
>
> Thank you very much for quick answer.
> I will contact https://groups.google.com/forum/#!forum/hugin-ptx
> as you advised.
> I also found the diagonal of the sony sensor is 7,77 mm. I will try to input a good data for the lenses.

If you can take a good, well overlapping set of images,
Hugin will work out the numbers for you, and for
YOUR lens, not just a "typical example" of your lens.

And you don't need to worry (too much)
about the no-parallax point for this calibration
as long as your subjects are a good distance away.

  BugBear

Reply | Threaded
Open this post in threaded view
|

Re: set of cameras for pano pictures

PanoTools NG mailing list
Thank you for the hints.
Letting  Hugin do everything would be fine for me but it did not work in my test case. 

I took 5 images, 0 degrees pitch, one per 72 degrees around the no parallax  point. The images overlap about 50%.
I input the images in Hugin.According to cam specs: focal length is 2,73 mm (which Hugin also assumed), D(iagonal ?)FOV is 155 degrees.
Hugin assumed a Hfov(v) of 71,6
Cp detection missed to find CP between two overlapping images.I manually input the  CP in the two overlapping images.I optimised (defalt: position, LDR).
In the assembler tab the calculated field (equirectangular projection) was 72 x 57.
The outcome was completely wrong.

I changed the objective from standard to fisheye, and  input a Hfov closer to the cam specs: the results were not good but anyway Hugin detected CP in all the contiguous images and the outcomes were  panos with some errors.

I assume that it would be important to to input proper data of the lcam lens.
Any hints? 







   

  On Friday, June 19, 2015 3:53 PM, "paul womack [hidden email] [PanoToolsNG]" <[hidden email]> wrote:
   

     giuseppe porciani [hidden email] [PanoToolsNG] wrote:
>
>
> Thank you very much for quick answer.
> I will contact https://groups.google.com/forum/#!forum/hugin-ptx
> as you advised.
> I also found the diagonal of the sony sensor is 7,77 mm. I will try to input a good data for the lenses.

If you can take a good, well overlapping set of images,
Hugin will work out the numbers for you, and for
YOUR lens, not just a "typical example" of your lens.

And you don't need to worry (too much)
about the no-parallax point for this calibration
as long as your subjects are a good distance away.

BugBear

  #yiv5023964922 -- #yiv5023964922ygrp-mkp {border:1px solid #d8d8d8;font-family:Arial;margin:10px 0;padding:0 10px;}#yiv5023964922 #yiv5023964922ygrp-mkp hr {border:1px solid #d8d8d8;}#yiv5023964922 #yiv5023964922ygrp-mkp #yiv5023964922hd {color:#628c2a;font-size:85%;font-weight:700;line-height:122%;margin:10px 0;}#yiv5023964922 #yiv5023964922ygrp-mkp #yiv5023964922ads {margin-bottom:10px;}#yiv5023964922 #yiv5023964922ygrp-mkp .yiv5023964922ad {padding:0 0;}#yiv5023964922 #yiv5023964922ygrp-mkp .yiv5023964922ad p {margin:0;}#yiv5023964922 #yiv5023964922ygrp-mkp .yiv5023964922ad a {color:#0000ff;text-decoration:none;}#yiv5023964922 #yiv5023964922ygrp-sponsor #yiv5023964922ygrp-lc {font-family:Arial;}#yiv5023964922 #yiv5023964922ygrp-sponsor #yiv5023964922ygrp-lc #yiv5023964922hd {margin:10px 0px;font-weight:700;font-size:78%;line-height:122%;}#yiv5023964922 #yiv5023964922ygrp-sponsor #yiv5023964922ygrp-lc .yiv5023964922ad {margin-bottom:10px;padding:0 0;}#yiv5023964922 #yiv5023964922actions {font-family:Verdana;font-size:11px;padding:10px 0;}#yiv5023964922 #yiv5023964922activity {background-color:#e0ecee;float:left;font-family:Verdana;font-size:10px;padding:10px;}#yiv5023964922 #yiv5023964922activity span {font-weight:700;}#yiv5023964922 #yiv5023964922activity span:first-child {text-transform:uppercase;}#yiv5023964922 #yiv5023964922activity span a {color:#5085b6;text-decoration:none;}#yiv5023964922 #yiv5023964922activity span span {color:#ff7900;}#yiv5023964922 #yiv5023964922activity span .yiv5023964922underline {text-decoration:underline;}#yiv5023964922 .yiv5023964922attach {clear:both;display:table;font-family:Arial;font-size:12px;padding:10px 0;width:400px;}#yiv5023964922 .yiv5023964922attach div a {text-decoration:none;}#yiv5023964922 .yiv5023964922attach img {border:none;padding-right:5px;}#yiv5023964922 .yiv5023964922attach label {display:block;margin-bottom:5px;}#yiv5023964922 .yiv5023964922attach label a {text-decoration:none;}#yiv5023964922 blockquote {margin:0 0 0 4px;}#yiv5023964922 .yiv5023964922bold {font-family:Arial;font-size:13px;font-weight:700;}#yiv5023964922 .yiv5023964922bold a {text-decoration:none;}#yiv5023964922 dd.yiv5023964922last p a {font-family:Verdana;font-weight:700;}#yiv5023964922 dd.yiv5023964922last p span {margin-right:10px;font-family:Verdana;font-weight:700;}#yiv5023964922 dd.yiv5023964922last p span.yiv5023964922yshortcuts {margin-right:0;}#yiv5023964922 div.yiv5023964922attach-table div div a {text-decoration:none;}#yiv5023964922 div.yiv5023964922attach-table {width:400px;}#yiv5023964922 div.yiv5023964922file-title a, #yiv5023964922 div.yiv5023964922file-title a:active, #yiv5023964922 div.yiv5023964922file-title a:hover, #yiv5023964922 div.yiv5023964922file-title a:visited {text-decoration:none;}#yiv5023964922 div.yiv5023964922photo-title a, #yiv5023964922 div.yiv5023964922photo-title a:active, #yiv5023964922 div.yiv5023964922photo-title a:hover, #yiv5023964922 div.yiv5023964922photo-title a:visited {text-decoration:none;}#yiv5023964922 div#yiv5023964922ygrp-mlmsg #yiv5023964922ygrp-msg p a span.yiv5023964922yshortcuts {font-family:Verdana;font-size:10px;font-weight:normal;}#yiv5023964922 .yiv5023964922green {color:#628c2a;}#yiv5023964922 .yiv5023964922MsoNormal {margin:0 0 0 0;}#yiv5023964922 o {font-size:0;}#yiv5023964922 #yiv5023964922photos div {float:left;width:72px;}#yiv5023964922 #yiv5023964922photos div div {border:1px solid #666666;height:62px;overflow:hidden;width:62px;}#yiv5023964922 #yiv5023964922photos div label {color:#666666;font-size:10px;overflow:hidden;text-align:center;white-space:nowrap;width:64px;}#yiv5023964922 #yiv5023964922reco-category {font-size:77%;}#yiv5023964922 #yiv5023964922reco-desc {font-size:77%;}#yiv5023964922 .yiv5023964922replbq {margin:4px;}#yiv5023964922 #yiv5023964922ygrp-actbar div a:first-child {margin-right:2px;padding-right:5px;}#yiv5023964922 #yiv5023964922ygrp-mlmsg {font-size:13px;font-family:Arial, helvetica, clean, sans-serif;}#yiv5023964922 #yiv5023964922ygrp-mlmsg table {font-size:inherit;font:100%;}#yiv5023964922 #yiv5023964922ygrp-mlmsg select, #yiv5023964922 input, #yiv5023964922 textarea {font:99% Arial, Helvetica, clean, sans-serif;}#yiv5023964922 #yiv5023964922ygrp-mlmsg pre, #yiv5023964922 code {font:115% monospace;}#yiv5023964922 #yiv5023964922ygrp-mlmsg * {line-height:1.22em;}#yiv5023964922 #yiv5023964922ygrp-mlmsg #yiv5023964922logo {padding-bottom:10px;}#yiv5023964922 #yiv5023964922ygrp-msg p a {font-family:Verdana;}#yiv5023964922 #yiv5023964922ygrp-msg p#yiv5023964922attach-count span {color:#1E66AE;font-weight:700;}#yiv5023964922 #yiv5023964922ygrp-reco #yiv5023964922reco-head {color:#ff7900;font-weight:700;}#yiv5023964922 #yiv5023964922ygrp-reco {margin-bottom:20px;padding:0px;}#yiv5023964922 #yiv5023964922ygrp-sponsor #yiv5023964922ov li a {font-size:130%;text-decoration:none;}#yiv5023964922 #yiv5023964922ygrp-sponsor #yiv5023964922ov li {font-size:77%;list-style-type:square;padding:6px 0;}#yiv5023964922 #yiv5023964922ygrp-sponsor #yiv5023964922ov ul {margin:0;padding:0 0 0 8px;}#yiv5023964922 #yiv5023964922ygrp-text {font-family:Georgia;}#yiv5023964922 #yiv5023964922ygrp-text p {margin:0 0 1em 0;}#yiv5023964922 #yiv5023964922ygrp-text tt {font-size:120%;}#yiv5023964922 #yiv5023964922ygrp-vital ul li:last-child {border-right:none !important;}#yiv5023964922