www.ssontech.com

dre4mer · Joined: 21 Apr 2008 Posts: 15

Greetings,

I just got syntheyes, I've been drooling over it's functionality for a loong time and finally i'm getting to work with it. I've worked through the basic tutorials without any problem. Now I'm attempting to work through one of my own shots. The tracking seemed to go fine. Refinement seemed to go fine. I've placed a couple 3D boxes in place and they seem to stick very nicely where they are supposed to in syntheyes.

The problem is the point cloud is WAY more spread out (directly away from the camera) then reality. The shot is a reasonably smooth dolly sideways without any panning. Now I guess this is alright the boxes seems to stay in place in Syntheyes despite the null cloud scale being off. But if I place a box exactly where the box was in syntheyes in my 3D software it seems like due to the vast scale of the whole particle cloud, it's not working at all. The camera barely seems to move at all in relation to the nulls. I've played with the coordinate defining system quite a bit per the manual, but everything I try totally destroys the track the camera bounces wildy and the points go all over the place. Apparently I'm not understanding the way you set the scale of your scene?

I did also make sure that export units was set to centimeters which is what my 3D software uses.

Any help would be appreciated here is a still if that helps any. It might be something completely different then i'm thinking it is that's causing the camera basically not to animate in the 3D software.

http://www.filmweavers.com/Synth/ScreenShot001.jpg

-Ethan

dre4mer · Joined: 21 Apr 2008 Posts: 15

I've been tinkering with it more. I did a overlay graphic and apprently all the nulls are in the right place. So I can size down the camera, fine and I guess the scene is all there the way it should be. But the camera still barely moves. Upon further tinkering I've realized it's spread the animation across 8 minutes instead of 8 seconds in the 3D software! So this is pretty bizzare, there must be some time/frame rate settings out there somewhere. Anyone seen something like this?

-Ethan

dre4mer · Joined: 21 Apr 2008 Posts: 15

ah ha! finally after about 8 hours straight of tinkering with this thing I found what was causing it.. the problem was fixed using an image sequence instead of a video file for the footage. that's strange... but i'm just glad it worked!! Now if someone else else hits the issue they will know.

-Ethan

bendytoons · Joined: 16 Mar 2007 Posts: 7

Ethan-

I just answered you post on the A:M forum.

For anyone else, this issue is because A:M does not run at fractional fps, only whole numbers. When SE exports a project at 29.97 fps (NTSC) it confuses A:M. The simple solution is to tell SE the footage is running at 30 fps. Then it exports the project at 30 fps, and A:M does not get confused.