Search options (Page 4 of 136)

If you can share the video privately it would be great to see where it falls short to improve the algorithm or the experience.

The core tracking algorithm in Tracker and Kinovea are fairly similar. They are both based on tracking a template inside a search area and update the template based on some heuristics.

Depending on the failure case you might try different values for the match and update thresholds. This is how Kinovea controls template update (Tracker uses different mechanics with "evolve" and "tether").

For example if it gets the wrong marker too often you can increase the "match threshold". When it fails and you replace it manually it will reset the template.

I see now that it doesn't actually stop the playback when it looses tracking, I agree it probably should, I think this behavior was changed at some point. I'll fix that or at least make it an option you can toggle on/off.

You can also increase the update threshold to 0.85 or 0.90, if the tracked object visually changes a lot this will update the template more often and can improve things.

One of the most important thing is that the object window, which defines the template, should be as tight as possible around the physical marker to avoid picking too much background (but still have some details in it). The search window should be large enough to cover marker motion but not too large that it might get confused with another marker.

A round shaped marker will work better (in both software) because an "X" shape will vary under rotation. (we don't look for the rotated template, only slide the template inside the search area and compute a score based on pixel correspondences).

If you can share the video with me I would love to test it.

A big change related to tracking is that when you turn on tracking on an angle it now creates 3 individual track objects. The angle object is "attached" to the tracks but apart from that the tracks are relatively independent from it. For example if you delete the angle the individual tracks are not deleted.

If you double click on the search rectangle of one of the track it will open the right-hand side pane on the Tracking tab. There at the top it will say something like "Angle 1.a" or "Angle 1.b", that's the name of the track. You can click on another track and it should switch to it. From this panel you can change the search window and object window sizes individually for each track (this wasn't possible before).

Previously the tracking of angles and other objects like line, human model, etc. was using its own code and was less accurate and less configurable than bare tracks. Many people used multiple track objects to emulate this (from right-click > Track path). Now the two systems have been unified. Tracking on objects is now basically a shortcut to manipulate the attached tracks at once. This means you will also see the "trace" of each point because it's drawn by the tracks.

There are probably more options that should operate on all tracks at once. The tracking menus when you right click a track are for that track alone. The tracking menus when you right click the angle are for all the attached tracks (start/stop, delete end of tracks, and delete tracks).

I am not sure what you mean by "It picks one, and that's the only marker I can alter.". If your experience is not as above please link to a screenshot or describe the unexpected behavior.

Normally you shouldn't need to copy the .cti files into the GenICam folder of Kinovea. When you install the GenTL provider of a given vendor like FLIR it will add itself to the environment variable GENICAM_GENTL64_PATH. You can check in the system environment variables if it correctly added its path there.

This setting has moved to be directly in the capture screen, to the right of the delay slider. The one with the little STOP icon next to it. I'm still in the process of updating the user manual, hoping to finish somewhere in January.

I'm not sure but it might be related to a change in how the videos are loaded specifically in the case of instant replay / observer. Because in this case the goal is normally to load the videos as fast as possible for instant feedback it no longer tries to load the individual frames in memory, as this could cause a big delay. The observer mode tries to stay as lightweight as possible during loading.

See if clicking once on the "reset working zone" button triggers a reload of the working zone into memory. (The blue leftward arrow).

That's quite strange, it should be completely uncorrelated as the frames are generated one by one and the frame rate is stored as metadata. Does it do it with all image sizes? Is the resulting file playing slowly compared to its nominal frame rate or the stored frame rate itself is slower than expected? Like if you open the file in another player what does it say the frame rate is?

Yes there is a way but not directly inside the program, in order to capture key presses when it doesn't have focus it needs to be something else.

You can use AutoHotkey (AHK) to capture the key presses, then a command to find the right Kinovea window and send it a Windows Message. People have posted the code in the forum I think, sorry I can't be of much help right now I'll come back later with more info if no one else has done so. The documentation is light but might get you started: https://www.kinovea.org/help/en/misc/copydata.html