Log In | Register | Contact | Search


Forum Home  >  Electric Image Animation System  >  EIAS General Forum  >  Thread
Search      Advanced Search
   
 
EIAS and camera tracking data - still stuck after a week…
Posted: 05 May 2008 07:51 AM   [ Ignore ]  
Newbie
Avatar
Rank
Total Posts:  2
Joined  2008-04-28

First up, apologies for the repeating of roughly the same problem I posed last week, and thanks to Ian and Magic for their responses. I am still struggling to get my head around bringing camera tracking data from SynthEyes into EI, even resorting to going from SynthEyes to Maya to EI in an attempt to get a useable camera path.

The gist of the problem is this, I have 44 seconds of aerial footage of a site that i need to overlay with a fly-over animation of a proposed development. I can track this easy enough in SE, although my complete lack of experience in that field made that a bit like pulling teeth as well! The main problems arise when I take the data I exported from SE in to EI. When we go ANIMATION > IMPORT MOTION > blahblah.OBM, the resulting motion path ends up with the camera in the wrong place, pointing in the wrong direction, and the camera path is completely different to the preview in SE. I can change the starting point of the camera by manually inputting the starting co-ordinates from the .OBM file, however these don’t tie up with the preview either....

Although I am quite comfortable using EI for photomatched renders and self-contained animations, this attempting to integrate ‘real’ video has me completely stuck, emailing the guys that made SE hasn’t been much help either, does anyone have an ‘idiot’s guide’ to getting this to work as I’m getting sick of tweaking settings and never finding something that is even close to a working solution!

any assistance is greatly appreciated guys & gals!

Profile
 
 
Posted: 06 May 2008 02:25 PM   [ Ignore ]   [ # 1 ]  
Member
Avatar
RankRankRank
Total Posts:  72
Joined  2007-03-07

I have found that most of my camera tracking errors comes from not defining the x-y-z planes correctly in SE (or any other Matchmoving software for that matter :P)

Check to see if the frame rate in EI is the same as in the video before you import the data.

Profile