What's up /p/haggots? Happy cum guzzling new year. Why

Tits or gtfo

>>2992468
no

Parallax

>>2992478
could that not be compensated for in post?

>>2992481
No. Parallax is not fixable in post. The two cameras are seeing two completely different scenes.

It would jump back and forth nauseatingly and syncing them would be hard

File: IMG_0229.jpg (71KB, 953x776px) Image search: [Google]

71KB, 953x776px

Why then is parallax not an issue with panoramas and 360 degree vr videos?

Also could one of the shots not be shifted to line up proper with the sacrifice of a black bar?

Needless to say my knowledge is limited.

[EXIF data available. Click here to show/hide.]

Camera-Specific Properties:
Image-Specific Properties:
Comment	Screenshot
Color Space Information	sRGB
Image Width	953
Image Height	776

>>2992485
What if one lens and prism it to two sensors?

>>2992501
Woah..............

>>2992501
you gotta sync the sensors' refresh rate which is probably more trouble

File: IMG_2574.jpg (1MB, 2048x1357px) Image search: [Google]

1MB, 2048x1357px

Bump

[EXIF data available. Click here to show/hide.]

Camera-Specific Properties:
Image-Specific Properties:
Horizontal Resolution	72 dpi
Vertical Resolution	72 dpi
Color Space Information	sRGB
Image Width	2048
Image Height	1357
Scene Capture Type	Standard

>>2992499
>panoramas
it IS an issue if not taken from exactly the same spot. it is less noticeable when the subject is far away, which tends to be the case on most landscape panoramas.
>360°
parallax is not an issue there because cameras are litterally opposite to eachother. issues in stitching come from having a gap in-between, which is not really the same thing.
>lifted up
theoretical story, but then your footage would only partially cover eachother, the super-slo-mo effect you want would only be on the interlapping middle. and even if we crop the rest to keep only that... well you still haven't fixed the parallax issue.
>>2992501
in theory, that would be a solution. maybe >>2992509 refresh rates sync can be troublesome, but something programmed to launch them with the appropriate delay would fix it.
I think encoding could end up becoming a problem anyway. Since the 2 videos are recorded and encoded separately, keyframes might not be the same, and it might be hard to fully reconstruct each frame to interlace them in the final product. At the very least, it'll take a lot of processing power.

>>2992501
So like technicolor then?

File: _57304459_bottle.jpg (3KB, 304x171px) Image search: [Google]

3KB, 304x171px

>>2992466
That's kinda how M.I.T did it. They made a camera will a trillion frames per second shutter speed.

http://www.bbc.com/news/technology-16163931

File: stereoscopic_images_06.gif (401KB, 720x450px)

401KB, 720x450px

this

>>2992466
It is a matter of the Frames Per Second. You can use two cameras, but so long as they are shooting at the same speed that will not change. All that will change is their perspective of the scene since they both cannot see it exactly the same. The faster the FPS the more you can slow the action down, that is all there is to it.

This is how they take those "cannon shell flies through the air" videos.

>>2993077
no

File: 155mm_shell.webm (2MB, 1280x720px) Image search: [Google]

2MB, 1280x720px

Also, netgeo has a camera for thunder photography, which is big like a wan. Its ~20 cameras in a circle, pointing in the middle, where a rotatimg "mirror" send the picture to the sensors. (its overly simplified version of the real gear)

Also, pic related