After Effects - Motion Tracking 4.5K WS Footage - Error

[William Schultz]

Hi,

I'm having an error come up when I'm trying to motion track some footage that was brought into After Effects via Dynamic Linking. I'm unsure whether or not this issue arises through importing the .r3d file through the standard workflow (File>Import) or not but I'm willing to bet it will.

Here's what happens,

1.) I dynamic link my .r3d file from Premeire Pro CS5.5 to After Effects CS5.5,

2.) It creates a new composition as usual (Still don't understand why it wraps the .r3d file in a composition of it's own... seems pointless.)

3.) Go into the pre-comp that the .r3d file lives in, copy it, paste it into the top-level composition so all the dynamically-linked composition has in it is the raw .r3d file.

4.) Open the tracker window, set Source to the .r3d file, and click "Track Motion.

5.) The problem comes in at this point, it throws a random tracker, long and horizontal in shape off the the right side of my viewer. When you click it you get the following error code;

"After Effects error: invalid image buffer size (-5280x100). ( 37 :: 102 )​

Usually these buffer size errors have something to do with available ram, disk cache, memory, etc... everything seems to be in the clear on my end however. Anybody have a similar problem trying to motion track within After Effects using the build-in tracker? The other workflow I can think of using would be to create a proxy of some form and track that either through AE or something like Boujou or PFTrack and import the tracking/camera data back into AE.. It's just an extra step that I'd like to avoid all-together if possible.

Thanks!

Also, system specs are roughly as follows;


MacPro5,1
6-Core Intel Xeon
Dual - 2.93 GHz
14 GB RAM

Adobe Production Premium CS5.5 - Everything is up-to-date.
Mac OSX 10.6.8

 

[Tim Hole]

Have you tried rendering a proxy in after effects from Dynamic Linked footage, track that and then copy the tracking data across to your high rez footage?

 

[William Schultz]

I have no doubt I can do that, I was simply curious as to whether or not anybody else has run into this error before. Just an extra step is all, shouldn't really be a big deal. I'll try the same operations on another system when I get a chance and see if I can reproduce the same error. Could very well be a conflict with a certain plug-in for all I know. Thanks!