61 Reply by joan

(3 replies, posted in General)

There is no integrated automated way. There is a very manual way where you add a human model drawing object and track it over time but you would have to place joints manually because with full body tracking there is always something occluding some points.

The more automated way is via Sports2D here: https://github.com/davidpagnon/Sports2D

Kinovea can read the files from Sports2D if they are created with the right options, I'm planning on improving this integration more in the future. In the meantime if more people could try Sports2D and report their experience it would be helpful. I think the installation process could be streamlined for non-developers and non-researchers. Right now I think you need to either use google Colab or install python and call it from the command line. Check this tutorial: https://www.youtube.com/watch?v=Er5RpcJ8o1Y

edit: inside Kinovea only the built-in human model has the center of mass, the model used to import Sports2D data files doesn't calculate the center of mass, something to add in the future.

Go to forum: General

62 Reply by joan

(3 replies, posted in General)

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).

Go to forum: General

63 Reply by joan

(18 replies, posted in General)

Ah, I see. In 2026 I plan on updating to a recent version of FFMpeg libraries and add a function to encode exported video with different codecs. Also I could add an output size option on the dual export dialog.

Go to forum: General

64 Reply by joan

(18 replies, posted in General)

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?

Go to forum: General

65 Reply by joan

(18 replies, posted in General)

Release of version 2025.1.1. The original post has been updated.

This is a minor update with mainly translation updates and a couple of fixes. Special shout out to user ntnam that translated the entire thing to Vietnamese in the interval since the original release!

Full changelog:

    Added - Vietnamese locale.
    Improved - Chinese (Simplified), Croatian, German, Indonesian, Japanese, Russian, Slovenian, Thai, Turkish, Ukrainian.
    Fixed - Removed the filtering of The Imaging Source cameras Directshow driver until the GenICam version works correctly.
    Fixed - Updating the tracking search window from the track configuration window was broken.
    Fixed - Camera configuration latest changes could be lost if another camera was updated in another window afterwards.

Go to forum: General

66 Reply by joan

(1 replies, posted in Ideas and feature requests)

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

Go to forum: Ideas and feature requests

67 Reply by joan

(2 replies, posted in Documentation drafts)

Yes the pattern should cover about a quarter of the frame. This is just a rough guideline, it will work even if it's not exactly that. You can have other things visible in the frame.

It should be moved around to cover the sides and corners of the frame, but not go partially outside, all the inner corners between the squares should be visible at all time. It can be tilted / seen in perspective.

The code internally uses OpenCV for this so you might find other guides online searching for OpenCV camera calibration.

Go to forum: Documentation drafts

68 Reply by joan

(3 replies, posted in General)

You can read a bit more about the coordinates filtering in the about page of the Linear kinematics dialog. Usually you want to keep it on because it removes the high frequency noise that is artificially introduced by the digitization process, especially if the points are placed manually.

So it looks like the issue is that the angle value displayed in the viewport is not taking coordinates filtering into account, I will note it down somewhere, thanks.

Go to forum: General

69 Reply by joan

(3 replies, posted in General)

Re: Kinogram mode. Yeah unfortunately at the moment this mode is still bound by the aspect ratio of the original footage. The initial values for the number of rows and columns and the crop rectangles default to the last ones used so it sometimes looks wonky or super small with empty space both at the top/bottom and on the sides. The export will crop out the empty space and can be larger. I tried to auto-rotate the canvas by 90° at some point but it caused other issues.

For now if the original footage is in portrait mode you might find it better to change the grid to something more appropriate, like 3x4 or something. Apart from that it should work the same.

Go to forum: General

70 Reply by joan

(3 replies, posted in General)

Regarding the first point it's not normal, the values should be the same, could you share the kva file with me please?

What do you have as options in Preferences > Drawings > General > "Enable coordinates filtering", and "Enable smoothing of derivatives for high speed footage"?

Do you have other calibrations in place like lens distortion calibration or camera motion estimation?

Assuming it's a tracked angle, are you using version 2024.1 or earlier or are you using version 2025.1? Tracking of objects changed completely.

For the second aspect, I think it's normal that when calibrating with the line tool it doesn't change the angle. It rotates, translates or scale the coordinate system but it's still on a parallel plane as the uncalibrated one so the angle shouldn't change. If you use the grid calibration to calibrate a plane that is not parallel it will change the measure.

Go to forum: General

71 Reply by joan

(4 replies, posted in Ideas and feature requests)

Yes this behavior is intriguing I'm very interested in understanding exactly what is going on. You can send it by email: joan at kinovea dot org.
Thanks.

Go to forum: Ideas and feature requests

72 Reply by joan

(4 replies, posted in Ideas and feature requests)

Loading a KVA created for one video into another video should work, could you share with me one or more files that cause a crash? (joan at kinovea dot org). A crash is always a bug. Even if the videos have different sizes or frame rate there is code that works it out and adapt everything so if it doesn't work in some cases please help me reproduce the context so I can fix it. It may also have generated a number of "Unhandled Exception" files in the application data folder, if you can share those as well it will be helpful, thanks.

Are you loading them manually or via the "default annotations file" option (shouldn't make much difference but will help reproduce)?

Go to forum: Ideas and feature requests

73 Reply by joan

(2 replies, posted in Ideas and feature requests)

I agree, yeah this difference is a long standing issue, but not easy to fix. Attempted the refactoring a few times.

The other aspect where this is limiting is that you can't have drawings go outside the video rectangle in the player, whereas in the capture screen you can, for example a corner of a perspective grid may be out of view.

Go to forum: Ideas and feature requests

74 Reply by joan

(2 replies, posted in Ideas and feature requests)

Thanks. Yes this sounds like a bug. I'll look into it.

Go to forum: Ideas and feature requests

75 Reply by joan

(2 replies, posted in Ideas and feature requests)

Oh I see, you are using a single instance of Kinovea and alternating between a capture screen and a playback screen, correct?

It does save the capture folder, even between sessions, but when you open a new capture screen in the instance it starts from the default state (actually even this should work but I think it's because of opening a player screen in between that it lose the capture screen info).

The new workflow is that you would use a dedicated window for capture, and a different one for replay. Doing this it will remember everything, the camera, the capture folder, the position of the window, etc. It will be ready to go as soon as you start.

Same for the replay, the window will remember the observed folder, the playback speed, etc. Typically if you have two cameras and two replay you would have 3 windows, two capture and one dual replay. It's better to save to different directories otherwise the automatic replay can't tell which file to load. The replay window will also automatically bring itself to the foreground when it loads a new file.

Go to forum: Ideas and feature requests