Oh, I forgot to update the little file that tells what's the latest version. It should be fixed now, you can try again.

Or you can get it from here: https://kinovea.org/download/

Is it a normal angle object or is it an "angle-to-vertical" or "angle-to-horizontal" object?
There was a bug with the latter that was fixed in 2025.2.

3

(2 replies, posted in General)

Is the file in the OneDrive folder by any chance? I'm getting more and more reports of people trying to open files that are synchronized to OneDrive and these files aren't really there even if Windows shows them as if they were local. I have to check how to handle this case gracefully but if that's your case you could temporarily copy the files to another folder and try again. This will force Windows to actually download the files.

Another known issue like this is specifically for the Korean locale when the file name has Hangul characters in it.

I think the discrepancy is because the ones on the video viewport don't take the smoothing filter into account for performance reason. If you disable all the smoothing in the preferences they should match again. But the smoothing is important for accuracy, to remove digitization noise. The main thing I want to avoid is recalculating the whole series on every frame during tracking and point manipulation, maybe it could update whenever the track exits editing mode.

What is the original camera frame rate?
To work around the limitation you could set the threshold to something very high, above the camera frame rate, this way it will never trigger and the final video will have the same frame rate as the capture (no replacement). I think the threshold also maxes out at 1000 fps though.

Ces fonctions ont besoin de plus de mémoire, vous pouvez aller dans Options > Préférences > Lecture > Mémoire et augmenter la mémoire allouée. Et réduire la zone de travail au plus près possible autour de l'action.

7

(1 replies, posted in Bug reports)

Did you try in version 2025.2 released last Saturday? There was a bug that was fixed in there.

8

(1 replies, posted in General)

Hi,
Just to confirm that the timestamps in the file are not hardware timestamps. This is a topic of interest but so far I haven't looked too much into how to get the timestamps when available.

On a related note I'm also interested in trying to measure the accuracy and stability of the frame rate of arbitrary cameras by independent means (like filming an array of LEDs flashing at known frequency to create a binary clock). With the goal of controlling the assumption that the frame rate is stable and that time fluctuations are extremely small or at least much smaller than other sources of error.

Aside from small frame rate fluctuations a possible source of error is when a frame is completely dropped from the output. There should be a drop counter in the info bar of the capture screen. A single frame drop will throw inter-frame arithmetic out of wack. Using recording mode "retroactive" should help if the duration of the recording fits in memory.

9

(0 replies, posted in General)

Hi everyone!

I just published Kinovea 2025.2. This is a minor release with several improvements, translation updates, bug fixes, but no new major features.

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

List of changes here: What's new in Kinovea 2025.2

Please report as soon as possible if you find any problem.

Cheers,
Joan

10

(1 replies, posted in Bug reports)

Thanks for the report. I think it's a combined problem in the file explorer tree view component accessing the network drives and trying to cache the little file icons in the background. Incidentally I also noticed a slowdown on the Favorites tab when a sub-folder has a large amount of files, like 150 files or so.

I think there is utility in accessing network drives for some users though so it should be an option.

The file explorer component is also causing issues on some Windows versions and on Wine. It is hooking into very old and low level Windows API. I will try to address it asap but it's not a quick fix. Although maybe a temporary measure would be to make a build without the explorer tree view component at all.

11

(18 replies, posted in General)

Tam wrote:

I am using Kinovea 2025.1.1, which has been updated to include Vietnamese.

However, when I select Vietnamese, the interface still displays in English.
How can I fix this?

Sorry about this, the build system was not adding the Vietnamese resources to the final package. It's fixed now and a version with the fix should be released shortly.

If you want to return to default settings you should also delete the content of the "Windows" directory in the preferences as that's where the delay is stored. (and in that case probably delete the "Workspaces" content since workspaces are pointing to windows).

For it to work correctly there must be at least 10 seconds (or whatever is the delay value) worth of images already in the buffer when recording starts so recording shouldn't be triggered before that. Could it be that? This should show in the displayed image as black with a negative timer until it's available. (if configured to show the delayed image).

It also depends on the Recording mode configured in the preferences. Preferences > Capture > Recording > Recording mode and delay > Delayed or Retroactive.

This should be fixed in the next release.

14

(4 replies, posted in Bug reports)

Sorry I missed these posts. The translations are integrated into the codebase at irregular intervals and they end up in the next software release, these happen a few times a year. I'm in the process of setting up continuous builds though, so people can test the latest changes faster, including translations.

15

(1 replies, posted in General)

The intended mechanism is that the setting in the global preferences is used when you create a new capture screen in a new Kinovea window. But after that the capture screen itself stores its own configuration, to allow for different names in different capture screens. And within a given Kinovea window it will remember the last capture screen you opened and what name was used there. So when you close and re-open a capture screen it will reuse the name that was used in that capture screen, independent of what's in the global preferences.

So in your case I think if you change the name inside that capture screen, it should retain it from now on, even if you close and re-open that capture screen. And if you create a new window and add a capture screen there, or create a second capture screen in the same window, it should use the name from the global preferences.

Hopefully that made sense, I'm still in the process of updating the documentation.

The main change is that essentially anything you can configure on the capture screen user interface (delay, max duration, capture folder, file name), is not coming from the global preferences but from the preferences of that particular window. The window can either be in "continue where I left off" mode or use a specific configuration, this is changed in Window > Window properties menu.