Search options (Page 3 of 134)

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

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

This seems very difficult. If it's around the world vertical axis you might attach a camera to the ceiling, if it's the player vertical axis, aka the longitudinal axis then I don't really see how you can measure this from 2D video, the camera would need to be somewhere along this axis.

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?

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?

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.

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.