Motion tracking - poor system performance when selecting keyframe matching on large video #51850

New Issue

Evert Vorster · 2017-06-20T08:37:34+02:00

Evert Vorster commented

2017-06-20 08:37:34 +02:00

System Information
Intel i7 with 35Gb of RAM.
Windows 7 Professional.
Also:
Arch linux in a virtual box and on bare metal on the same machine, but booted off a USB disk

Graphics : nVidia Quadro K3100M

Blender Version
Broken: 2.78c

Short description of error
Doing motion tracking in equirectangular 4K video, thousands of frames.
When selecting keyframe as reference, a couple of frames are done quick, and then Blender slows down to a crawl, with maybe doing one frame every few seconds.
When selecting previous frame as reference the performance issue disappears.

It's almost like the reference picture is read from the frame where it was specified every single time a comparison is made, causing Blender to seek back and forth through the video. With large seeking times in the video the whole performance suffers.

Exact steps for others to reproduce the error
Load large video
Select motion tracking workspace
Add motion tracking point, using default settings
Track forward (it works fine for a couple of frames, and then slows down dramatically)

The workaround I found was to select fast motion preset for the tracking parameters, and then there is no slowdown.
Based on a (as simple as possible) attached .blend file with minimum amount of steps

**System Information** Intel i7 with 35Gb of RAM. Windows 7 Professional. Also: Arch linux in a virtual box and on bare metal on the same machine, but booted off a USB disk Graphics : nVidia Quadro K3100M **Blender Version** Broken: 2.78c **Short description of error** Doing motion tracking in equirectangular 4K video, thousands of frames. When selecting keyframe as reference, a couple of frames are done quick, and then Blender slows down to a crawl, with maybe doing one frame every few seconds. When selecting previous frame as reference the performance issue disappears. It's almost like the reference picture is read from the frame where it was specified every single time a comparison is made, causing Blender to seek back and forth through the video. With large seeking times in the video the whole performance suffers. **Exact steps for others to reproduce the error** Load large video Select motion tracking workspace Add motion tracking point, using default settings Track forward (it works fine for a couple of frames, and then slows down dramatically) The workaround I found was to select fast motion preset for the tracking parameters, and then there is no slowdown. Based on a (as simple as possible) attached .blend file with minimum amount of steps

Evert Vorster commented

2017-06-20 08:37:34 +02:00

Changed status to: 'Open'

Evert Vorster commented

2017-06-20 08:37:34 +02:00

Added subscriber: @evorster

blender-admin commented

2017-06-20 08:37:34 +02:00

#53344 was marked as duplicate of this issue

Bastien Montagne commented

2017-06-21 12:21:09 +02:00

Added subscribers: @Sergey, @mont29

Sergey Sharybin was assigned by Bastien Montagne

2017-06-21 12:21:09 +02:00

Bastien Montagne commented

2017-06-21 12:21:09 +02:00

Not sure we can do much here, @Sergey would know.

Also, did you try to change your Memory Cache Limit setting in System tab of UserPreferences?

Not sure we can do much here, @Sergey would know. Also, did you try to change your Memory Cache Limit setting in System tab of UserPreferences?

Sergey Sharybin commented

2017-06-21 12:58:10 +02:00

What is the type of medium you use (video, image sequence)? Does it happen with latest build from builder.blender.org? Try monitoring blender's memory consumption, see if it stays at some constant value after few frames reached or keeps raising up?

@mont29, there shouldn't be measurable difference between 'previous frame's and 'previous keyframe' reference option.

What is the type of medium you use (video, image sequence)? Does it happen with latest build from builder.blender.org? Try monitoring blender's memory consumption, see if it stays at some constant value after few frames reached or keeps raising up? @mont29, there shouldn't be measurable difference between 'previous frame's and 'previous keyframe' reference option.

Evert Vorster commented

2017-06-21 14:16:12 +02:00

The medium type is x265 compressed video clip. It has exceedingly bad non-linear seeking performance.

Memory usage is a constant 1Gb, no creep. The system itself has about 35GB available.

I will try to set a higher memory limit and try again, but just adding more memory for the problem "feels" wrong, as there is no slowdown with using previous frame as a reference instead of keyframe. I can also provide a screen capture of the problem in action, if you want.

The medium type is x265 compressed video clip. It has exceedingly bad non-linear seeking performance. Memory usage is a constant 1Gb, no creep. The system itself has about 35GB available. I will try to set a higher memory limit and try again, but just adding more memory for the problem "feels" wrong, as there is no slowdown with using previous frame as a reference instead of keyframe. I can also provide a screen capture of the problem in action, if you want.

Evert Vorster commented

2017-06-21 14:24:16 +02:00

Just tried again with the same version of blender, on Windows 7.

I upped the memory limit to 10Gb, and when using keyframe for reference it eats my memory pretty quickly, ie: it uses more and more memory until all the 10Gb is used up, and then it slows down again.

Just tried again with the same version of blender, on Windows 7. I upped the memory limit to 10Gb, and when using keyframe for reference it eats my memory pretty quickly, ie: it uses more and more memory until all the 10Gb is used up, and then it slows down again.

Sergey Sharybin commented

2017-07-05 16:16:36 +02:00

I can not reproduce the issue with my video files on my workstation.

Please share some of the videos which shows the error, together with .blend file with the motion tracking prepared for the error to happen (so it's enough to press Ctrl-T to start tracking).

I can not reproduce the issue with my video files on my workstation. Please share some of the videos which shows the error, together with .blend file with the motion tracking prepared for the error to happen (so it's enough to press Ctrl-T to start tracking).

Evert Vorster commented

2017-07-05 16:31:28 +02:00

Hi there, Sergey.
Providing you with a video might be difficult. They are all over 1Gb of HEVC compressed 4k equirectangular video.
Even if I had the bandwidth to upload such a video, would this website accept it?

As a bit of side information I have the panoramatools plugin installed. Not sure if it matters much.

Kind regards,
Evert Vorster

Hi there, Sergey. Providing you with a video might be difficult. They are all over 1Gb of HEVC compressed 4k equirectangular video. Even if I had the bandwidth to upload such a video, would this website accept it? As a bit of side information I have the panoramatools plugin installed. Not sure if it matters much. Kind regards, Evert Vorster

Sergey Sharybin commented

2017-07-05 16:42:13 +02:00

It might matter. So test whether using factory startup blender affects the issue.

Bastien Montagne commented

2017-07-17 12:59:31 +02:00

Changed status from 'Open' to: 'Archived'

Bastien Montagne closed this issue

2017-07-17 12:59:31 +02:00

Bastien Montagne commented

2017-07-17 12:59:31 +02:00

More than a week without reply. Due to the policy of the tracker archiving for until required info/data are provided.

Lars Soderlind commented

2017-08-13 00:40:46 +02:00

Added subscriber: @soderlind

Lars Soderlind commented

2017-08-13 00:40:46 +02:00

I'm seeing the same thing also on Windows 7 and Linux Mint on another computer. Blender 2.79 RC1 and earlier.

It only happens when the clip doesn't fit the memory cache.

As soon as the memory cache is filled up while tracking with keyframe as reference, it slows down dramatically. Using previous frame as reference instead makes it go through the whole video with no slowdown.

It seems to be worse on higher resolution videos, or maybe videos with slower seek. I'm not sure.

Image-sequences show almost no slowdown, but if you pay attention it looks like it might behave the same, just too little to notice really.

I made a blend file with a random video that has this slowdown. I downloaded the video from: https://pixabay.com/en/videos/ski-winter-snow-mountains-8558/

Just open blend and press Ctrl-T.

Make sure Memory Cache Limit is low enough in the settings. (At 1024 MB the slowdown happens at around frame 130 for this video.)bugtest.blend

Ski - 8558.mp4

I'm seeing the same thing also on Windows 7 and Linux Mint on another computer. Blender 2.79 RC1 and earlier. It only happens when the clip doesn't fit the memory cache. As soon as the memory cache is filled up while tracking with keyframe as reference, it slows down dramatically. Using previous frame as reference instead makes it go through the whole video with no slowdown. It seems to be worse on higher resolution videos, or maybe videos with slower seek. I'm not sure. Image-sequences show almost no slowdown, but if you pay attention it looks like it might behave the same, just too little to notice really. I made a blend file with a random video that has this slowdown. I downloaded the video from: https://pixabay.com/en/videos/ski-winter-snow-mountains-8558/ Just open blend and press Ctrl-T. Make sure Memory Cache Limit is low enough in the settings. (At 1024 MB the slowdown happens at around frame 130 for this video.)[bugtest.blend](https://archive.blender.org/developer/F708584/bugtest.blend) [Ski - 8558.mp4](https://archive.blender.org/developer/F708585/Ski_-_8558.mp4)

Lars Soderlind commented

2017-08-13 02:15:27 +02:00

Looks like the video filename changed when it got uploaded. (To underscores instead of space.)
If you use my blend file you probably need to rename the video to this: Ski - 8558.mp4

Looks like the video filename changed when it got uploaded. (To underscores instead of space.) If you use my blend file you probably need to rename the video to this: Ski - 8558.mp4

Bastien Montagne commented

2017-08-13 10:43:23 +02:00

Changed status from 'Archived' to: 'Open'

Bastien Montagne reopened this issue

2017-08-13 10:43:23 +02:00

Bastien Montagne commented

2017-08-13 10:43:23 +02:00

Yeah… as if it has to reload the keyframe every time…

Sergey Sharybin commented

2017-08-13 10:48:18 +02:00

The pattern area we're comparing against (the one which is denoted by keyframe match) is supposed to be cached inside of the tracking context which is not covered by memocy cache limit at all.

Will do some troubleshooting on Monday.

One thing you might want to try at the meantime (and this is actually something recommended when tracking video files): try generating timecode (Built Proxy/Timecode in the Proxy panel) and set tmecode to something like Record Run. See if that has any affect on performance.

The pattern area we're comparing against (the one which is denoted by keyframe match) is supposed to be cached inside of the tracking context which is not covered by memocy cache limit at all. Will do some troubleshooting on Monday. One thing you might want to try at the meantime (and this is actually something recommended when tracking video files): try generating timecode (Built Proxy/Timecode in the Proxy panel) and set tmecode to something like Record Run. See if that has any affect on performance.

Bastien Montagne commented

2017-08-13 10:50:52 +02:00

@Sergey I just tried generating TC on his file, and saw no difference at all here…

blender-admin commented

2017-08-14 11:41:12 +02:00

This issue was referenced by a850235a44

This issue was referenced by a850235a44207d856644cab38a1155a85d90337a

Sergey Sharybin commented

2017-08-14 11:44:02 +02:00

Changed status from 'Open' to: 'Resolved'

Sergey Sharybin closed this issue

2017-08-14 11:44:02 +02:00

Lars Soderlind commented

2017-08-15 20:47:31 +02:00

Tried latest buildbot build 66c1b23 and tracking is not working at all anymore. It gets stuck at 0% and if I try to quit blender it will stop responding.

Tried latest buildbot build 66c1b23 and tracking is not working at all anymore. It gets stuck at 0% and if I try to quit blender it will stop responding.

Sergey Sharybin commented

2017-11-21 16:48:46 +01:00

Added subscriber: @PauloJoseOliveiraAmaro

Sign in to join this conversation.

No Label

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Motion tracking - poor system performance when selecting keyframe matching on large video #51850