AVS › AVS Forum › 3D Central › 3D Source Components › When small interaxials just don't cut it!
New Posts  All Forums:Forum Nav:

When small interaxials just don't cut it! - Page 32

post #931 of 1087
Thread Starter 
Quote:
Originally Posted by Wolfgang S. View Post

Frank, I am still not sure what this test shows me.
I mean, the important point would be to have each of the fields from 1080 60i footage shifted to the upper or lower part of the top-bottom frame. Without recompression if that is possible - and for sure without new calculation/interpolation of the fields.
So, if you take the 60 positions in a second in the timeline, and if you render that to 60p, you will end up with the situation that every second frame must be interpolated. Simply, because you have 30 fields for the top, and 30 fields for the bottom part of the top-bottom-footage. So maybe it would be better to render to 30p, and disable resampling. And set deinterlacing to none.
We can only hope that this works. I am not sure if your test can show that this has worked out really?

This test was quite interesting for me because I learned a little bit about how Vegas handles fields and de-interlacing. As it turns out, every frame in that video was interpolated.
When I observed the paused frames and switched between de-interlacing modes the results surprised me somewhat.
For example when the number 1 was at 12:00 in the odd field and the even field was at 3:00 and I enabled interpolated de-interlacing the 1 moved to the 1:30 position. When switching to "blend" mode you could see the individual fields superimposed with 1/2 the 1 at 12:00 and the other half at 3:00.
The clear interpolated frame got me wondering just how good the de-interlacing is so I decided to do some further experiments to try to find out.
post #932 of 1087
Quote:
Originally Posted by Frank View Post

For example when the number 1 was at 12:00 in the odd field and the even field was at 3:00 and I enabled interpolated de-interlacing the 1 moved to the 1:30 position. When switching to "blend" mode you could see the individual fields superimposed with 1/2 the 1 at 12:00 and the other half at 3:00.
Interpolation algorithms thrive on smooth continuous motion. Throw them some random motion, and the predicted motion becomes unpredictable. biggrin.gif
Edited by MLXXX - 6/28/12 at 3:50pm
post #933 of 1087
Thread Starter 
Quote:
Originally Posted by MLXXX View Post

Interpolation algorithms thrive on smooth continuous motion. Throw them some random motion, and the predicted motion becomes unpredictable. biggrin.gif
Random motion coming up in my next test...
post #934 of 1087
Thread Starter 
I uploaded a short clip from my initial de-interlace test.
I used interpolated de-interlacing with Vegas and encoded at 60P top/bottom.
The 3D divergence that occurs during the shaking is odd. I'm not sure what caused it.
I'm thinking it is because the cameras were zoomed in quite a bit and the OIS might move a little bit under these conditions. I don't think the cameras moved relative to each other.
de-interlace test
post #935 of 1087
Quote:
Originally Posted by Don Landis View Post

[For my use, I will be shooting motion in my ultra wide angle twin NEX 5n's using a 6" IA and the 12mm lenses. I got my first test lens in today and will be laying out the geometry to see if this is wide enough to capture my wide stage. If not wide enough, Sony has a fisheye lens I can use but that one has considerable geometry distortion and I wanted to avoid that. The geometry distortion of the 12mm is not really that bad. The motion involved will be the fountains at the Bellagio so sharpness is not a real concern.
As a lover of 3D, I really enjoy scenes involving water droplets, or waves. (Or schools of small fish for that matter.)

My only reservation is that if the IA is very wide, some scenes can lose their impact. I don't imagine that would be an issue with the fountains at Bellagio with a 6" IA but it could be an issue if using a large IA to capture a choppy sea. The apparent height of the choppiness can be much reduced so that the sea looks more like a calm lake, in 3D!
post #936 of 1087
Jeff- the math is pretty well defined in stereography. The stereo base used is a relative function of the stage size to put it simply. I have not yet calculated the range of stereobase for optimum 3D range for that stage but with wider angle lens the range of stereobase permitted is wider too. 6" was my best guess based on the memory of the nearest key fountain directly in front. When I do the actual computation, it may turn out to be optimum at 4" or 8" Going too wide can cause diverging disparities too great for eye comfort and I have learned my lesson at guessing now and won't be making that mistake again. I will use the stereo base calculators and the distance range finder for a better SB choice.

In your example, a choppy sea can look small and flat if it is of great distance and shooting wide angle. If you zoom in on the sea at great distance, then increase the SB you will get better z depth, not less. If you shoot too close and the SB is too wide, then the sea simple diverges and you see double images.
post #937 of 1087
Don, I noticed unnaturally flat water in my own 3D still of the view from an ocean liner leaving Port Canaveral [using frames extracted from 2D video footage] ; and in a video of Frank's involving yachts/boats. As you say, if zooming in on water, the parameters would change.

A difficulty arises when the main subject is distant, requiring a higher IA, and there is at the same time water visible in the near foreground not far from the camera position. The water in the near foreground will look unnaturally flat because of the dwarfism effect introduced by the high IA.

I think the beauty and grandeur of fountains is in the water spraying through the air. I don't think a degree of dwarfism in the appearance of the ripple of waves in the pond into which the sprays of water drop would be of too much concern; though excessive divergence of LEFT ad RIGHT must of course always be avoided. [ As you say, calculations can avoid disappointment.]
post #938 of 1087
Thread Starter 
Quote:
Originally Posted by MLXXX View Post

Don, I noticed unnaturally flat water in my own 3D still of the view from an ocean liner leaving Port Canaveral [using frames extracted from 2D video footage] ; and in a video of Frank's involving yachts/boats. As you say, if zooming in on water, the parameters would change.
A difficulty arises when the main subject is distant, requiring a higher IA, and there is at the same time water visible in the near foreground not far from the camera position. The water in the near foreground will look unnaturally flat because of the dwarfism effect introduced by the high IA.
I think the beauty and grandeur of fountains is in the water spraying through the air. I don't think a degree of dwarfism in the appearance of the ripple of waves in the pond into which the sprays of water drop would be of too much concern; though excessive divergence of LEFT ad RIGHT must of course always be avoided. [ As you say, calculations can avoid disappointment.]
I agree 100 percent. I had to throw away a lot of sailboat video because of too much water in the foreground.
post #939 of 1087
Thread Starter 
I have been trying to acquire some 3D video of some bald eagles that have been hanging around and I jury rigged a temporary setup to feed live video from the yard into my house.
The live 3D eagle watching rig

I'm attempting to make an adjustable tilting bracket for this application. Hopefully I can hack one together this afternoon.
post #940 of 1087
In a best case scenario, the eagle would grab the stranded copter and drop it, gently, in front of the jury rig.Though pigs flying seems more likely.
post #941 of 1087
Quote:
Originally Posted by Frank View Post

This test was quite interesting for me because I learned a little bit about how Vegas handles fields and de-interlacing. As it turns out, every frame in that video was interpolated.
When I observed the paused frames and switched between de-interlacing modes the results surprised me somewhat.
For example when the number 1 was at 12:00 in the odd field and the even field was at 3:00 and I enabled interpolated de-interlacing the 1 moved to the 1:30 position. When switching to "blend" mode you could see the individual fields superimposed with 1/2 the 1 at 12:00 and the other half at 3:00.
The clear interpolated frame got me wondering just how good the de-interlacing is so I decided to do some further experiments to try to find out.

I see what you try to test. Was not here for some days, but without testing I think following. If this idea is worthwile really, an interpolation should not be necessary.

Let me explain why I think so. The deinterlacing could take place simply by shrinking down the 1080 lines in a field to 540. So, if you take out every second line of a frame in an uff footage, you end up deinterlaced.

If we are successfull to do that for both fields, it would be great - since then you do not loose quality due to the deinterlacing and interpolation steps.

But that is my thinking. I do not know if it works out really.
post #942 of 1087
Thread Starter 
Quote:
Originally Posted by Wolfgang S. View Post

I see what you try to test. Was not here for some days, but without testing I think following. If this idea is worthwile really, an interpolation should not be necessary.
Let me explain why I think so. The deinterlacing could take place simply by shrinking down the 1080 lines in a field to 540. So, if you take out every second line of a frame in an uff footage, you end up deinterlaced.
If we are successfull to do that for both fields, it would be great - since then you do not loose quality due to the deinterlacing and interpolation steps.
But that is my thinking. I do not know if it works out really.
Correct. This is what I thought I could do with Vegas. Unfortunately, Vegas will not do it. When squeezing the frame into half vertical size, it automatically samples from both fields and there seems to be no way to prevent it.
I looked at AVISYNTH and it seems possible to do it with that but the programming required is not something I'm prepared to tackle at the moment.
post #943 of 1087
Frank,

With your "eagle watching rig", what are you using for the wireless HDMI transmission?
post #944 of 1087
Thread Starter 
Quote:
Originally Posted by JStegin View Post

Frank,
With your "eagle watching rig", what are you using for the wireless HDMI transmission?
WHDI 5G 1080P
cool.gif
post #945 of 1087
Quote:
Originally Posted by Frank View Post

Vegas will not do it. When squeezing the frame into half vertical size, it automatically samples from both fields and there seems to be no way to prevent it.
I looked at AVISYNTH and it seems possible to do it with that but the programming required is not something I'm prepared to tackle at the moment.
VitrualDub can give a quick result, provided it can actually open the source video file (it prefers AVIs) . These internal filters could be used:

1 . To get half-height 30p from 60i:-
Filter: deinterlacer
Deinterlacing mode: discard fields
Field order: Keep top field, interploate/discard bottom field

2. To get half-height 60p from 60i:-
Filter: bob doubler
Field order: Top field first
Deinterlacing method: None - alternate fields

I have used the MVC to AVI converter at http://www.3dtv.at/Products/MvcConverter/Editions_en.aspx to obtain decoded Left and Right AVI files (uncompressed, so very large) from Sony HDR-TD10 files.

Quote:
Originally Posted by Wolfgang S. View Post

... . Was not here for some days..
Wolfgang, I was wondering whether you'd had a chance to look at my timing mismatch video from post #924, The Ungoverned Anniversary Clock, at http://www.youtube.com/watch?v=k_m4ETc-ydY

I'm seeking feedback on whether an optical illusion of the orbs appearing to fly further outwards for one direction of movement, and then further inwards for the reverse direction of movement (compared with watching in 2D) is perceived. (I see the illusion myself even at the minimum timing discrepancy of 4.17mS, beginning at 3m 15s into the video.)
post #946 of 1087
Quote:
Originally Posted by MLXXX View Post

1 . To get half-height 30p from 60i:-
Filter: deinterlacer
Deinterlacing mode: discard fields
Field order: Keep top field, interploate/discard bottom field
2. To get half-height 60p from 60i:-
Filter: bob doubler
Field order: Top field first
Deinterlacing method: None - alternate fields

I have used the MVC to AVI converter at http://www.3dtv.at/Products/MvcConverter/Editions_en.aspx to obtain decoded Left and Right AVI files (uncompressed, so very large) from Sony HDR-TD10 files.

Yes,such an approach would work out. My idea was to do that in Vegas, by rendering the L and R stream as separate files to 1920x540, with no deinterlacing. The field drop is the way how it has to be done, but I have not tested that yet really.

Quote:
Originally Posted by MLXXX View Post

Wolfgang, I was wondering whether you'd had a chance to look at my timing mismatch video from post #924, The Ungoverned Anniversary Clock, at http://www.youtube.com/watch?v=k_m4ETc-ydY

Sorry, I was so busy that I have not found the time to analyse that. I would love to do so, but time is pressing at the moment here.
post #947 of 1087
No worries Wolfgang.

___


Actually I see that Vegas can be set to the following for rendering:
Video for Windows, 1920x1080, 29.97i, Upper field first, Uncompressed.

Perhaps Vegas would leave the interlacing intact for such rendering settings. On the assumption that that would be the case:-

If the project were set to LEFT, a short segment could be rendered as an AVI and that loaded into Virtualdub. Then the project setting could be changed to RIGHT and another AVI could be created.

VirtualDub could be set to produce full height bob-deinterlaced frames. These could then be loaded back into Vegas as full height LEFT and full height RIGHT and paired as a stereoscopic pair. [Or an AVISYNTH script could be used to combine half height source frames, of a clip 1 and clip 2, using the function: stackvertical(clip1, clip2).]

I'm not suggesting this as a usual work flow, but as a way of creating a short 3D test file of bob-deinterlaced video to see whether it really is an improvement over blended/interpolated.


VirtualDub is great for these types of exercises as you can step through the AVI frame by frame and inspect any detail closely. It can also produce a compressed version of the file pretty quickly (XviD MPEG-4).

I'm not retired (yet) and I don't have as much time as I'd like to experiment with some of these things myself.
post #948 of 1087
Shot the Jacksonville Fireworks Wednesday. Just finished editing it.

This experiment was to shoot with the twin TD10's using 1080 60p ( Sony PS Mode) The stereo base was set at 18 inches and the distance to the barge on the River was measured to be 1239 yards. The near object in my shot was mostly too dark to detect but on occasion it was illuminated by the fireworks and was a boat at 340 yards. By these measurements I could have used my 1 meter slide bar to separate the two TD 10's. As such the z depth wasn't as good as I had hoped for but there is always next time. Last Winter I use a 9" and 12" Stereo Base. Anyway the event nearly got rained out as the thunderstorms gave us a break about 20 minutes before the show started.

The shooting and pairing went fine in Vegas (build 595) Playback could not keep up with the 60p ( Double NTSC) timeline and only played single clips at 25-28 FPS. This made my edit decisions a little more time consuming. The performance was supposed to have been synced to a music sound track that was to be played on the Riverbanks PA system but for some reason that never happened so I added my own music appropriate for the 4th of July event. ( Remember, this is for me and family as my target audience. ) Cost me $130 sync rights! Being retired from the TV business, I no longer have my blanket license for BMI and ASCAP. library so now I have to pay per song. So if any of you have a suggestion for cheap good quality music, let me know. There used to be a company with good prices on YT rights but they stopped doing it.

I think the biggest issue I observed working with 1080 60p is the rendering time. A video shot in 1080 24p on this length and effects added would take about 40 minutes to render but the 1080 60p takes about 2 hours! When I watched the video the motion smoothness didn't look obviously better than the 24p, but then my 24p presentation has always looked quite smooth on my monitors with the Sony a bit smoother than the Vizio. (240Hz vs 60 Hz refresh rate) Last night I rendered the show to an iso file at 1080 24p template in Vegas and the action looked very smooth so shooting the 60p and converting it to 24p for blue ray doesn't seem to be a problem. The onkly really good way I can see the native 1080 60p from the timeline is to set my Dynamic Ram to about 8Gb and then do a shift B render for ram playback. Unfortunately the time I get on this is only about 10 seconds!

I should have a compressed version of the Fireworks show uploaded by this evening on YT.
post #949 of 1087
Don,

I don't know if you've checked out the Smartsound Library. They have fully customizable music that you can buy on a per song, per album or mutiple-album basis. It covers a wide range of genres, classical to hard rock, and music with vocals, too. I got 28 albums for $500 last year. I still haven't downloaded all 28 (I have a year to download the ones I want). They also have sound effects albums. I bought all 6 (100's of effects) for $100 recently. It's not for everyone, but a LOT of professionals use it. You can hear samples just by going to their web site. Their program is called Sonic Fire Pro, which is available for $100, and you get a couple of sampler albums with it. One really cool thing about it is that you can create custom audio-follows-video tracks. You're not limited to creating just stand-alone custom length music, although you can do that if you want to.
post #950 of 1087
The Jacksonville Independence Day Fireworks is up now.

On my Vizio it looks best in 1080p using SBS half. LIne interleave looks fair and anaglyph is not good at all on mu Vizio. On the computer monitor in window it is better but some colors do not work well for anaglyph. The Wells Fargo bright amber often glows double.

The windows Media video I used for YT upload seems to soften the image too, compared to m2ts or MP4 rendering here. But the m2ts file size was 2.6 Gb.



Edited by Don Landis - 7/6/12 at 1:54pm
post #951 of 1087
[Don, I think you should check the vertical alignment at around the 10 minute mark; and in the opening few seconds.]

Don, I always like the pacing of your videos!

I thought the orchestral music a nice accompaniment to the fireworks.

Regarding interaxial distance, I think the 18" you chose was the right distance, in order to be able to include the foreground water in the opening section of the video. (For my own vision, I think any more than that could have made viewing of the foreground water uncomfortable.)
Edited by MLXXX - 7/6/12 at 5:45pm
post #952 of 1087
Thanks Jeff for your help on this. As I said in the PM and for others to learn from I have this current version uploaded with some auto correct errors. Starting with the opening shot, I accidentally unchecked the auto correct and then never rechecked it before rendering the video. Making the corrections took a few minutes but the rendering of this will be about 2 hours before uploading. I should have the new version up tomorrow morning.

Glad you liked the music. Had to pay some healthy coin ( on my budget) for the sync rights.

On the stereo base. I'm still trying to achieve some Fireworks negative parallax. I have only seen this done with those Fireworks simulation display programs and that isn't real. I want to create a fireworks star field in the center of my home theater in front of the screen. For the next local Fireworks, maybe Labor Day, I plan to use the 1 meter rail and then zoom in tight on the explosions. According to my SB calculator, the distances involved could work with a Hyper SB of up to 20 meters! Minimum distance can be no closer than 500 meters and the lens set for 135mm ( A little less than half the TD 10 range ) To do the water and wide shots, I can just slide the cameras closer together, then edit out the manipulation. Our shows seem to have plenty of opportunity where they have a break for about 10 seconds so that's when I can make the change in SB.
post #953 of 1087
Don, I have downloaded the video as sbs half and have seen it on my 50-inch HDTV. Looks great so far.

My recommendation: I would tend to adjust the parallax at the level of the firework to a small figure. Especially a firework tends to ghosting, given the strong contrasts - so parallax should be low here really.
post #954 of 1087
Yes I have been finding it useful to adjust parallax so that the main part of the subject of interest is nil or near to nil. It can make viewing more relaxing, as well as reducing ghosting.
Quote:
Originally Posted by Don Landis View Post

On the stereo base. I'm still trying to achieve some Fireworks negative parallax. I have only seen this done with those Fireworks simulation display programs and that isn't real. I want to create a fireworks star field in the center of my home theater in front of the screen. For the next local Fireworks, maybe Labor Day, I plan to use the 1 meter rail and then zoom in tight on the explosions.

Yes Don I think that would have to be the way to go to get dramatic 3D for the fireworks and still be able to include some wide angle shots of the surrounding terrain.
_______

On the question of timing there may occasionally be some momentary mismatches between Left and Right with asynchronous capture because fireworks can produce a very short-lived but brilliant flash. Here's a side-by-side frame from Don''s original version of the Independence Day fireworks illustrating this (frame 375):

338

The Left frame includes a brilliant flash illuminating the water, and the Right frame does not. Frames 374 and 376 (Left and Right) both show the water in darkness. This was a short-lived flash!
post #955 of 1087
It might be interesting to try to edit that flash into the right frame. It would no doubt require some careful work to get the angle right, but since it's so short it should be doable. smile.gif
post #956 of 1087
The sync between the left and right cameras was initially set with the Lanc Shepherd and was noted to be 1/120 in my shooting slate. The clapboard was then used after rolling cameras about 5 seconds and once again about 10 seconds before pausing cameras. The sound pulse on the edit wave form was lined up first and then during several places the the fireworks were checked left and right to see if the two clips were in sync between the cameras, about center of the recording. I saw a very close match up of the sparks pin points and felt there was no cause for concern. The sound and video misalignment on full expansion of the timeline was about 1/8 of a frame both in the beginning clap board and at the end. The distance to the Wells Fargo building was 1240 yards as measured by the Bushnell Range finder. This distance was assumed to be close to the barge where the fireworks were set off and also about same as the distance to secondary explosions high in the air. Sound travels at 1100 ft per second so I assume the missync of sound is about 3+ seconds. I did not slide the audio timelines with the video because I didn't feel the multiple explosions sync was worth the effort.

According to some stereographer experts I've read, when there is a missync of a strobe light flash between left and right cameras, the visual simply loses one of the eyes and loses 3D effect but if the light is sustained for both eyes to see the light then the visual will show the 3D illusion. If that statement is accurate and it seems to me to be so, then the moment of light first seen from an individual explosion particle would lose it's 3D but only for a tiny fraction of a frame exposure.
I think this topic is interesting from a theoretical angle but in reality, I'm not so interested in defining sync down to the nanosecond. If out by more than a frame I will correct. In my shooting, I'm happy with 1/3 frame accuracy. IMO, camera alignment is a much bigger issue to worry about with wide stereo base shooting.

BTW- the corrected upload is going on right now. When up, I will delete the first one with the errors.

New link will be:
post #957 of 1087
Quote:
Originally Posted by Joseph Clark View Post

It might be interesting to try to edit that flash into the right frame. It would no doubt require some careful work to get the angle right, but since it's so short it should be doable. smile.gif
From Don's updated version I made a loop of 100 frames with frame 375 in the middle of the loop [VirtualDub labels the first frame of a clip as zero, so this would be frame 376 in some other software]. This was to test whether frame 375 would "stick out" for my vision when repeatedly playing the loop: it didn't. So I think repair would be unnecessary, at least for me. The discrepancy was too brief to be noticeable. Also, this could have been a perfectly correct disparity if there had been an obstruction between the light source and the Right camera. The brain would need time to analyse that...

I did however notice "watery" effects occasionally and when I stopped the playback sure enough there was a mismatch between Left and Right in the part of the image that looked watery. It would not be the main part of the firework "constellation" that had just exploded into visibility but a "rogue star" that was moving downwards much faster than the other points of light in the constellation

But I am very sensitive to stereoscopic 3D. I suspect that most people wouldn't notice the small timing mismtach effect, or if they did it wouldn't bother them.
____________

A few comments, having now seen the updated YouTube version:-

Enjoyable video. Really liked the music that went with it. Interesting to see the partly hidden fireworks going off behind the building on the left. They really did look "behind it" stereoscopically.

It's quite impressive what standard of pyrotechnics is available today: very complex patterns, precisely coordinated.

What more could we ask for? A wider IA? biggrin.gif
post #958 of 1087
Continued to make another major correction for a very subtle improvement after the latest upload. This improvement exists on my BluRay iso file rendering. All it did was deepen the blacks and sharpen the image slightly at tyhe moment of the biggest explosions. Here's what I did--
I noticed several times where I looked for them that the right camera seemed to have a brighter flash than the left. I think this was due to my manual exposure setting just a tad higher than the left camera. While I believe you may be interpreting this to be a timing problem the position of the point light was identical between left and right. Too close to change by sliding the left and rights by one frame length. Taking a different approach, I added two instances of Brightness / contrast effects where one was left view checked and the other was right view checked. Now I can adjust the brightness and contrast of each individually after pairing. That's all it took and I was able to match the brightness and the resulting glow of the explosions precisely between the left and right cameras. I made that correction after uploading the YT version but before rendering my Blu Ray version.

One of the problems we had that night was the heavy rain and thunderstorms for 3 hours just prior to the Fireworks. This caused a bit of ground fog over the river. Between that and the smoke, the diffusion of light was severe. Another serious photographer was next to me and had commented that the fog and heavy smoke patches lingering ruined most of his shots as compared to a clear night in January.

I think the only way to achieve the kind of sync perfection you seek Jeff is to use genlocked cameras or a frame store synchronizer like what Frank just bought. The Lanc Shepherd hopes to achieve sync between the two cameras by simply turning them both on as close to the same moment in time as by chance. So, in my opinion, any attempts to quibble over the intra frame timing mismatches with this Lanc technology is like trying to control the roll of the dice to get double sixes on every roll, because that is exactly how this Lanc system timing works. One keeps powering up over and over until the start times are closer than before, maybe get lucky and achieve perfection. At least in genlock you have a single clock to time both cameras. In frame store the equipment delays one video in reference to the other for electronic alignment and once matched, sends the video pair to the output.
post #959 of 1087
Thread Starter 
Just watched it and enjoyed it very much.
Nice job Don.
Maybe next time you'll have a 6 foot bench with 6 or 8 TD10's. biggrin.gif
For two years in a row I've just missed my change to shoot the local Jully 4th fireworks.
Last years because I will ill prepared.
This time I missed by two days.
I just closed on my business property on the 6th which is just down the road from where the fireworks are set off.rolleyes.gif
post #960 of 1087
Thanks, Frank. There is not one time, I am out shooting with this twin camera system that I don't say a thank you for talking me into this wide stereo base end of the hobby. It's not that I can use it to make the image more real to life, but that I can add to it for presentation.
Quote:
Maybe next time you'll have a 6 foot bench with 6 or 8 TD10's. biggrin.gif

Now there's an idea, pick and choose any pair camera set to see which stereo base looks the best.

Soon, if my plans work out, I will have two rigs, one with TD10's and one with a pair of wide angle NEX5n's. I do plan to set up all 4 on the bench to have two focal lengths to shoot these events next year. Then I can switch between the two in post. The TD10's will be able to zoom but the wide angle NEX5n's will be locked in 12mm wide angle. Both shooting at 1080 60p and all 4 synced with the clap board. How's that? Just pray the stock market keeps me funded so I can buy this stuff. smile.gif
New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: 3D Source Components
AVS › AVS Forum › 3D Central › 3D Source Components › When small interaxials just don't cut it!