Search options (Page 21 of 133)

You can restrict the working zone around your set point in the timeline, this should trigger the caching, (if enough memory is allocated in the preferences).

Other than this mechanism, there is already a small cache constantly updated around the current spot, about 16 frames. Maybe there should be a visual indicator of this to give feedback about where it stops, and allow more control over its size.

(Sorry your message didn't appear initially, all first-time messages containing links go to a hidden forum for spam triage)

Do you click from the list in the explorer panel on the left or from the thumbnail panel? Do you see the thumbnail at all? If you do F5 does it refresh the thumbnail?

Have you installed another camera plugin since? There seems to be an incompatibility with the Baumer one where one of the plugin takes hold of some shared resource. Can you share the log of a startup, the camera initialization is logged, there should be some info there as to what's going on.

Hmmm, the original capture history panel was a tree with each day its own entry and the list of captured videos from that day below it. http://www.kinovea.org/screencaps/0.8.x … istory.png
But that was too complex to maintan. And you had to periodically clean it up, and always the problem of stale links when a video is deleted.

In what consist a "session" in your workflow? A day of recordings or just one event, so possibly multiple sessions per day? In that case it would need a concept of starting and ending a session, and the videos would be grouped under that session. More complex.

Another mechanism would be to use the Post recording command from automation panel, and point it to a script that collects all files in the current folder and consolidates them to a text file. The advantage of this is that once it's set up you can't forget to export the list. And you get the concept of session for free by just changing folder.

Just to confirm, there is currently no image stabilization in Kinovea.

If it's for measurement purposes what you can do is track the origin of the coordinate system, this way the other points and lines will be measured with regards to that moving origin.

I made several experiments with regards to stabilization and moving shots over the years and to be honest it's mainly an issue of user interface and integration. I'm not really sure how to "present" this functionality in a well integrated way because it's modifying the video frames themselves and possibly the canvas size necessary to show them. Similarly you will note that there is lens distortion correction but the way it works is that it distorts the coordinate system instead of undistorting the images.

It does feel like a pre-processing step to everything else done in Kinovea and for now it has to be done in a separate app prior to loading.

Based on the code it should already do 60fps based on the passed value of `iPosition`, which I would assume is just the index in the list of available media types. Can you see the list of stream formats and resolutions in the camera configuration dialog inside Kinovea?