Search options (Page 2 of 135)

Yes, it's crucially important! I made a fix and I'm testing it.

The "RenameSelected" command is only for the thumbnail view in the file explorer or camera explorer, to rename files or cameras.

There is not really any shortcut to bring up this properties dialog. The closest thing is to open the annotation pane on the right, on the second tab, and rename the objects from there.

Hmm, it looks like the dual playback shortcuts only work when the joint controls bar at the bottom has the focus. I thought I fixed this a while back, I'll look into it. In the meantime if it's a shortcut that also exist in single screens in the PlayerScreen category you might set it there and it should send the command to both screens.

Which one do you mean by "Object Rename"?

Thanks for the description, I'll do some tests.

When the trigger happens do you see the capture window switching to recording at all with the red bar? Or is it not armed at all and the trigger is completely ignored?

If it's recording but the output file is not updated it's probably because it's already opened in the playback window as you mention using a static filename. Can you try with a dynamic filename just to see if that's the cause of the problem? (Just enabling "auto-numbering" should be enough to test this).

If that's the origin of the problem it might be tricky, maybe we need a different mechanism where it cycles between a few files instead of just one. This could be an extra option next to "auto-numbering" for the max allowed number and when it reaches that number it goes back to 0 and starts again.

I remember now, the issue with immediately killing the tracking as soon as it fails is that it breaks when the object is temporarily occluded, for example an arm or leg passes in front of it. The idea was that when this happens it keeps looking and when the occlusion is over it might recover the tracking by itself if it's still inside the search window.

What I would like to do is add an option somewhere to tell how many frames of failed tracking are allowed before the playback is stopped. 3 or 4 frames should be a good default I think, but if you want you could set it to 1 and get the same behavior as in Tracker.

Or maybe playback should always stop on failure and it's the track that is force-closed after n failures.

It should be possible to make the audio trigger add a key frame. Then we can jump between key frames using a keyboard shortcut or button. The key frames could be on the ball impact or moved back to the start of the swing based on the delay value. The swings would not be neatly separated into their own "clips" though, so playback would just continue into the next swing. I experimented with a multi clips system at some point but didn't go too far.

You can switch between real time and delayed using the third button in the recording toolbar, the blue circle with dots around, next to the "pause" one. It will turn orange when the view is live. This is independent from recording settings, it's just for the preview.

Yes. One difficulty with counters is that if they are global it makes things a bit complicated when using multiple capture screens or instances, and it's hard to know if it should increment after each capture or only after each global trigger, and how to let the user reset it.

You could sort of do it manually right now with a context file with one number per line. You would need to manually click on the next number from the drop down though.

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.