46 Reply by joan

(17 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?

Go to forum: General

47 Reply by joan

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

Go to forum: General

48 Reply by joan

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

Go to forum: General

49 Reply by joan

(17 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.

Go to forum: General

50 Reply by joan

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

Go to forum: General

51 Reply by joan

(1 replies, posted in General)

The multi-window system is new in 2025.1.

Go to forum: General

52 Topic by joan

(17 replies, posted in General)

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.

Go to forum: General

53 Reply by joan

(2 replies, posted in Ideas and feature requests)

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

Go to forum: Ideas and feature requests

54 Reply by joan

(5 replies, posted in General)

I added a `-video2` parameter. For the synchronization mark it's more complicated because it's not a property of the screen but an annotation on the video so it's handled differently.

Since you are processing the videos with ffmpeg and looking for black frames I wonder if you could trim the beginning of the video directly with ffmpeg without re-encoding. https://superuser.com/questions/258032/ … of-a-video

Go to forum: General

55 Reply by joan

(5 replies, posted in General)

Thanks, very interesting. It shows me something I haven't really taken into account in the new system I think.

The new system uses a concept of "windows", that is conceptually similar to the old workspace, they contain the 1 or 2 screens with the content in it. But the XML for these is stored in the application data folder and managed by the program. So now the way to start on a specific screen configuration from the command line is to pass the window id or name, instead of the path to an external file. All the existing windows are listed in the UI so it's easy to reload old ones but creating new ones is also done from the UI.

This means something appears to be missing compared to what you want to do, you would have to create/modify the window xml stored in app data which is doable but not ideal. It would be much simpler if you could pass the paths to the two videos on the command line no?

For a single video you can directly pass the path to the command line or use the -video parameter, no need to create a window or workspace file. Maybe there should be a -video2 parameter that let you start in compare mode directly.

Go to forum: General

56 Reply by joan

(2 replies, posted in Cameras and hardware)

Assuming you have reduced exposure duration to remove the motion blur and then increased gain to try to compensate the darkness of the image, and that caused a lot of noise/grain. There is no easy solution you must add external lights if you are indoor in a low light room. Then you can use a lower gain and not have so much noise.

Go to forum: Cameras and hardware

57 Reply by joan

(5 replies, posted in General)

Hi,
Synchronization works via the "time origin" annotation and is saved in KVA files. So the way to do this would be to have a KVA file for each video with a time origin set a the timestamp of the sync point.

Please note that this workspace file format will be obsolete in the next version as the multi-window system has been rewritten and better integrated in the program, and furthermore "workspace" means a different thing now.

Are you generating these files from code or are you editing manually? The timestamps are not in seconds or frames they are in a unit that depends on the video file so it's a bit more complicated.

Go to forum: General

58 Reply by joan

(4 replies, posted in Bug reports)

This will be fixed in the next release.
See: https://github.com/Kinovea/Kinovea/issues/180

Go to forum: Bug reports

59 Reply by joan

(1 replies, posted in Bug reports)

Thanks.

It's related to the function of auto-numbering file names. I can reproduce if I set the file name to contain a very large number like "test1234567890123". When it tries to automatically increment the number it fails because it's too large.

It will be fixed in the next release.

Go to forum: Bug reports

60 Reply by joan

(1 replies, posted in Bug reports)

Is it a very long video? I don't think I've had the issue you are mentioning where you click on the cursor and it jumps to a different frame.

You can also try the "time grab": ALT + mouse left drag in the video viewport. When you click down (anywhere) it will be registered to the current frame and when you drag left or right it will move relatively to that so I think it's what you are after. 

edit: actually I see what you mean on certain videos, it might be a bug in the mapping between pixels and timestamps I'll have to double check.

Go to forum: Bug reports