Kinovea 2023.1 (updated 2024-05-18) (Page 1 of 2)

Here is a list of the limitations and things I'm most likely to look at next

- In Kinogram mode, being able to change the time of each individual image, and change the font size of the labels.
- Counter and cadence tool.
- Camera motion compensation and related features.
- A way to export videos with more reasonable encoding parameters, for social media and whatnot.
- A number of videos people have shared end up cut short at the end for some reason.

Some of the machine vision camera plugins may not work with this version, I'll go over them as soon as I can.

Note: the translation coverage fell behind when I integrated the strings for the new features, you can help here:

https://hosted.weblate.org/projects/kinovea/#languages

Here is what I intend to do with releases going forward. After this initial release I will make several branches. We will consolidate bug fixes and translation updates into 2023.1 (calling it 2023.1.1, 2023.1.2, etc.), while new features and improvements go in the next version as normal. Basically the main change compared to before is that we will keep this version alive and it will receive bug fixes and language updates for a while.

Thanks.

There are two ways to export the stopwatch data now. The traditional way using Calc or Excel as a target and the dedicated Chronometer CSV export.

The traditional way should export the data as in your suggested format. Each stopwatch will have its own separate small table with the split times and cumulative times, and also start and stop.

Now the second way is more advanced, and the reason it's organized like this is because it will try to match different time sections from multiple stopwatches, by their names (I have a video coming up explaining the new options more in detail).

This is interesting when you have several of these multi-time stopwatches overlapping. To give an idea, the first use-case this was developed for is a hurdle race where you are timing both the time intervals between the hurdles and the jump time above the hurdles, and then you want to export a table where you collate all the data for each interval. So you have a column for say the 4th interval and then you have rows for all the things you have timed during this interval.

I guess it could still be transposed, but I know at least one user that is really interested in having it in this shape, so it would have to be an option like a checkbox on a dialog before the final export.

A third way to export is through the JSON export, in this case the data is a bit more structured and it could be shaped differently, this is intended for consumption by another programming language.

Right now the way to prevent the shortcuts to be applied to a particular stopwatch is to use the menu Options > Locked on that stopwatch. It's the only thing this menu does (you can still start/stop/split manually). I admit it's still not perfect though, it has already happened to me a few times to forget to set it and mess up the times. If you show the label above the stopwatch, it also has a little square icon which represent the "locked" state.

edit: Maybe another idea would be to check if the stopwatch already has data points in the future and in that case ignore the shortcuts. I think in most cases it should be the right thing to do. If we really want to accept shortcuts in the middle of the existing times maybe *this* can be the explicit option to activate. The only issue with this approach is that it will still potentially add unwanted time points at the end.

I like this idea. And there is a related UX issue with trajectories, when there are several of them crossing paths it can be difficult to manipulate one without inadvertently grabbing a point from another, and this could use a similar approach of "disable all the others and make this one special". 

I wish to make the menu phrasing more explicit though, maybe something like "Disable shortcuts for other stopwatches" or something along these lines.

Hey Joan, 10000 thank yous for the update. Lots of much needed features added and seems to be a slicker package already minus a few small issues.

One bigger issue I have been having is extremely slow video exporting. Especially composite videos. What used to take 30 secs, is now sometimes taking 10 minutes +.

Please let me know if this is an issue you have come across with others or if it is maybe my poor hardware?

I've done some further investigation. Seems that all my videos are very slow to export, regardless of base file size/resolution etc... I also now seem to have the issue of the comparison videos exporting "zoomed in" and then not playing, regardless of format (AVI, MP4). Screenshots attahced for reference.

I'll try a re-install of 2023.1. Should I also uninstall 0.9.5? As I have both on my computer at the moment?

Thanks as always for the help