I'm attempting to track a slightly longish shot, and I don't want to fill up all my ram.

I can play the animation with ⎇ AltA and blender caches and displays uncached frames in near real-time (~35 fps with 60fps footage). Blender will track cached frames faster than real-time.

Yet when trying track uncached frames, blender takes longer than 10 seconds per frame! Often as long as 15 seconds.

What is going on here? Why does tracking uncached frames take far longer than the time needed to both cache and track separately?

  • $\begingroup$ A lot of it depends on the video codec you are using and how fast the CPU interprets them. If you create proxies as a JPEG sequence (very low CPU overhead) you'll see better performance... $\endgroup$ – user1853 Mar 28 '15 at 1:45
  • 1
    $\begingroup$ Speed might also be impacted by the size of the frame and the speed of your drives...Also, using a smaller search area for the tracker helps tremendously. $\endgroup$ – user1853 Mar 28 '15 at 1:48
  • $\begingroup$ What codec is the video encoded in? $\endgroup$ – user1853 Mar 28 '15 at 1:56
  • $\begingroup$ @cegaton h264 I believe. I can understand it going a little slower when caching as it's tracking (cache time + track time + a little overhead would be perfectly acceptable). But it's going far slower.. $\endgroup$ – gandalf3 Mar 28 '15 at 2:56
  • $\begingroup$ In other words: It's tracking very fast (the trackers are quite small). It's caching very fast (30 fps). However when doing both at once it goes many many times slower (>10spf). $\endgroup$ – gandalf3 Mar 28 '15 at 3:00

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.