16

(3 replies, posted in General)

Some spambot posted an answer to this which made me realize I hadn't responsed. Is it still a problem in 2025.1? If yes can you identify which version is working and which version is not working? Which output format are you using?

17

(1 replies, posted in Bug reports)

By flickering do you mean that the frames are rendered out of order? there are black frames? something else?
If you re-open the exported video in Kinovea does it also do this or only the other media player?
Does it do it in VLC media player? What is the other player?

Unfortunately this option was lost at some point during a refactoring. I will try to bring it back. Essentially you have long-running trajectories and you only want to see it focused on a few frames around the current frame and hide the rest, correct?

You should be able to change the color and re-export.

You save the analysis itself to a KVA file which is text based and has the style information. If you reload this file onto the original video (File > Load annotations…) you can continue the analysis, change the existing positions, color, name of the trajectories or any other object. Normally the KVA file is saved with the same name as the original video, only the extension change, in that case it will be loaded automatically when you open the video.

The images and videos exported have the drawings baked in so they can't be modified afterwards. But if you still have the annotation file (.kva) and the original video, you should be able to make some changes and redo the export.

20

(2 replies, posted in General)

We've set the signed clockwise angles because it's more familiar for us.

That is pretty much the reason why the different options exist. When you first place the angle object you may find that its default configuration is not measuring what you expect, because of the ambiguity around which leg is the base leg and in which direction the angle is measured. So these options let you tell the program how the angle should be measured.

The dashed leg is always the base leg from which the angle is measured, in other words the angle is the one that spans from the dashed leg to the other one. In the latest version I added a small arrow to make this clearer.

The default direction is counter-clockwise as in trigonometry, but depending on whether the person is facing left or right you will need to change this. It's just a default.

Since we rarely measure angles above 180° when measuring human range of motion the default is "signed" which means any angle between 180 and 360° is converted to be in the 0 to -180° range instead. So let's say your anatomical reference position has 0° as the full extension, but that person has hyper extension and can actually go further, bending the joint backwards, then it would measure as negative, maybe -5°, instead of measuring 355° which wouldn't really make sense in this context. But it's an option for when it might make sense.

For measuring joints range of motion it's probably better to use the goniometer and set the reference axis.

The first measurements you need to figure what configuration corresponds to what makes sense compared to what you know the value should look like when you progress from flexion to extension or vice versa. This is similar to what you would do with a physical goniometer, you place it as you know it should be placed but then you check that the measured value makes sense because it's easy to mix things up. There is no way the program can know in advance in which direction the motion goes or how you want to measure it.

Hmm, I don't think it's in the scope of the project to tell you where to place the markers, it really depends on what you want to study. This should normally be based on the specific domain's literature.

Placing markers in one place or another doesn't really change how they are tracked inside the software, the only caveat is to be aware that cloth or even the skin can "swim" a bit above the actual point you want to track, and that occlusions are not well handled so you may have to manually correct the track position during the frames they are occluded.

There is no built-in function for this at the moment.

Maybe you could have a post-recording command that goes in the target directory and removes the X oldest files or any file that's older than the current date or something like that.

edit: well it turns out the message above was posted by a spam bot, they are becoming impossible to detect manually… I'll leave the topic up anyway.

23

(11 replies, posted in General)

It sounds like a bug but I haven't experienced it so it might happen in a context I haven't tested. This behavior of decreasing the playback speed automatically happens when the player starts the playback loop but can't keep up the pace, typically because it doesn't have enough resources. First it skips frames, then skips multiple frames at once, if skipping frames is not enough it starts lowering the frame rate.

Normally it settles down to whatever it can manage. Since you say that manually changing the speed works, it seems there is something that makes the system busy specifically when the file is opened for some reason.

What is your window/screen setup? Try with one window for the capture and a separate window for replay, this should better spread the load over different CPU cores. If you have two cameras and a dual replay, make sure the files don't go to the same folder.

Do you have a default annotation file that is being loaded in the player?

Another idea, are the files saved to a folder that is synchronized to cloud storage, like OneDrive or Google Drive?

24

(1 replies, posted in General)

For golf and other activities where the subject doesn't move it's typical to change the default by going to Options > Preferences > Drawings > Opacity > and check "Visible for the entire video".

In general people create different drawings at different times so the default is that the drawings fade away so they don't overlap each other.

You can also customize this behavior for each drawing by doing right click > Visibility.

25

(11 replies, posted in General)

Thanks, I see what's going on. I made a fix but I was actually considering removing these settings from that window and only leave the style options like for other drawings. The annotation panel should be the main way to interact with it and it has all the options now (match and update thresholds).

26

(11 replies, posted in General)

I just found the following problem related to languages: if you use the installer and install on top of a previous version it will use the old resources for the languages and will display untranslated elements in the user interface.

In general I suggest uninstalling the previous version before installing this one.

27

(2 replies, posted in General)

Yes unfortunately this is always an issue with new releases. I believe the only work around during the initial period is to click "More Info" and then "Run anyway".

It is a reputation based system handled by Microsoft, once enough people do this the warning goes away. They have a business model where the software publishers buy a code-signing certificate to make it go away faster. I will review the options again as I haven't looked into it in a while.

28

(1 replies, posted in General)

The multi-window system is new in 2025.1.

Post history

  • 2025-11-05: First release of 2025.1

  • 2025-12-07: Updated with links to 2025.1.1

-----
Hi everyone!

I'm happy to finally publish Kinovea 2025.1. This is a major release.

Links
   
    Kinovea-2025.1.1.exe (installer)
    Kinovea-2025.1.1.zip (self contained "portable" archive)

The change log got so long and hard to read that I decided it was time to improve the presentation, you will find a list of the changes here: What's new in Kinovea 2025.1

Big thank you to every one that helped test the new features during the past few months!

I started to update the manual to reflect the changes, I will continue to update it in the coming weeks.

Translation coverage also took a hit with all the changes, you can help the translation effort on weblate. There will be minor releases periodically with translation and bug fixes.

Let us know as soon as possible if you find any issue.

There will be a button for this in the next version. In the meantime you can use the keyboard shortcut Alt + Home. (You can re-bind this in the preferences look for CaptureScreen > ToggleDelayedDisplay command).