Search options (Page 58 of 134)

Hello,

The automated tracking performance will depend on the subject, background, markers, light, motion blur, and other factors.
In any cases you should consider that it might be required to manually adjust some points to get the correct trajectory.

One limitation of the current version is that angle tracking (and other tools) does not let you configure the sizes of the tracking windows (search window and object window).

The trajectory tool does not have this limitation and let you alter the tracking windows sizes. You may want to try this one first. Analysis windows with kinematics plots are also only supported for the trajectory tool.

The trajectory tool tracker's default settings are the same as the angle tool ones, but the tracking windows are visible, so you could use this to better understand why the automated tracking fails in the case of the angle. The usual issue is that too much of the background is included in the object window. In this case you would have to somehow make the markers appear bigger (by using bigger ones or moving the camera closer for example). You should use round-shaped markers. It may take a few tries to find the optimum sizes for the combination of markers/background/motion blur in your videos.

You could also use three trajectory tools and compute the angle externally.

When the tracking eventually fails in the trajectory tool, rewind back to the first point of failure and use the right click menu to delete bogus points coming after.

edit: Another thing to note, the current algorithm doesn't fare very well with occlusions. For squat jump scenarios for example, an arm might temporarily occlude a hip marker. In this case it might be required to manually adjust the tracker during the frames where the marker is invisible.

Also review this topic dedicated to markers.

No, unfortunately it's not something that can be easily fixed, as the constant framerate assumption is scattered throughout the code.

Thanks,

Because there are so many different operations one could want to do on the image, color adjustments, rotation, distortion rectification, cropping, etc. the current plan is to not to try to do them in real time at all, but to provide an enriched export dialog with these options. It will be for a later development though.

There is currently no announcement list to subscribe to, the closest thing to it is the twitter feed.

Hi,
There are several possible cause for mis-synchronization.
What Kinovea version are you using ? (While we are at it, what Windows version ?)

Re: real time playback, do you mean that the speed slider decreases by itself or do you mean that at 100% speed the action is played in too slow/fast motion ?
When in dual playback, both speed slider should be locked (unless specified in the preferences).
Would you happen to be comparing a video taken with a high speed camera with a video taken with a normal camera ? If so, what is the capture framerate of the highspeed video ?

1. Add a perspective grid
2. Place its corners on the corners of a rectangular object visible in the scene and on the same plane as the plane that you want to make measurements on.
3. Right click the grid and use "Calibrate", enter the physical dimensions of the rectangle.

You can display the coordinate system with Image > Coordinate system.

Are you working with AVCHD / H.264 videos perhaps ? There are several issues with them that haven't been addressed yet.

Depending on the flavor of the encoder and the parameters used, they are more or less critical. Sometimes the working zone in/out points can't be set properly.