Some people do it intentionally, setting the replay speed to 50% once and so having it automatically carry over was a feature request, to make a feedback loop that's always in slow motion. I could add an auto-reset option though. But first I want to try to improve the playback perfs.
16 2026-08-12 02:06:49
Re: Working zone never cached in replay observer, playback speed steps dow (3 replies, posted in Bug reports)
17 2026-08-11 21:33:33
Re: Working zone never cached in replay observer, playback speed steps dow (3 replies, posted in Bug reports)
Hi, yes if I remember correctly I deactivated the full caching mode on replay players to make sure it opens the video instantly instead of spending time caching it which can be disruptive if you want instant feedback. In the context of capture/replay loop people usually just replay the video a few times rather than do full analysis so it's a good tradeoff. I think it was also an issue for dual replay synchronization.
Regarding the auto-slow down I'm currently working on updating ffmpeg libraries and reviewing player performance so hopefully I can improve the behavior here. Right now it tries to not drop any frames and it slows down to maintain this goal. But for playback it's probably better to drop frames. I think I have the upgrade figured out at this point and starting to look into performance.
18 2026-07-24 19:29:20
Re: Kinovea vs SiliconCoach (5 replies, posted in General)
1. Lag: there are a few axes. Using an SSD, saving the recordings to a different drive than the Windows drive, changing the recording mode in the preferences.
2. Side by side comparisons are possible yes. For example, menu View > Two playback screens.
3. Currently the capture of video is not optimized for sharing. I'm working on this for the next version, among other things. Capture images should be fine, you can save as jpeg or png and share that. If you meant capturing the whole interface like a screencast then no, you would have to use something else on top.
For multiple cameras setup there is a possible workflow where you have one instance of Kinovea for recording and another instance of Kinovea for reviewing. This can better utilize the CPU cores. Even for just one camera and one instant replay that might be another way to improve responsiveness.
Sorry I don't have more time to expand these points in too much details right now but should have more time later in the summer. Unfortunately I didn't get around to fully update the manual lately, so it's half way done in a draft version, I'll get around that at some point as well.
19 2026-07-24 19:05:10
Re: Larger / adjustable Font size (1 replies, posted in Ideas and feature requests)
I'm not entirely sure what you mean. Ideally if you can create a bug report in github and attach a screenshot that would help me understand and can be used to track progress.
20 2026-07-24 19:02:48
Re: Video timeline cuts off/skips final frames during playback (Decoder mi (2 replies, posted in Bug reports)
Hi, I have started the work to update to the latest FFMpeg version. (It's likely not a problem in the library itself but in how Kinovea uses it, but the refactoring to adapt to the latest version should help fix these issues.)
If you could send me a private link to the file as an example it would help my tests (joan at kinovea dot org).
edit: oops, I just realized you already sent me the video! Thanks.
21 2026-07-05 14:28:47
Re: Unhandled crash after adding tracking to perspective grid (2 replies, posted in Bug reports)
I reproduced it quite easily and testing a fix. It's a regression related to the tracking now running in parallel.
There are a few more things to fix. In terms of user interaction, we can't easily "stop tracking" on the grid itself. And the idea for making measurements with a moving camera was to go through the "Camera motion estimation" procedure instead, then the grid will automatically stick to the object throughout the video, but right now this doesn't play nicely with the coordinate system and measurements.
22 2026-07-04 15:26:28
Re: Unhandled crash after adding tracking to perspective grid (2 replies, posted in Bug reports)
Thanks. I will try to reproduce it.
23 2026-07-02 12:10:38
Re: error save picture (1 replies, posted in Bug reports)
It looks like the file path has characters invalid for file names (something like <, >, :, ", /, \, |, ?, *). it should be caught before saving and show a dialog but it must be missing it.
24 2026-06-20 17:37:07
Re: version 0.9.6 (1 replies, posted in General)
I'm curious where that information is coming from. Kinovea has never supported RTSP, only MJPEG.
25 2026-06-19 23:44:52
Re: Kinovea 2025.2 (2026-03-21) (4 replies, posted in General)
The distortion grid has been replaced with the Lens calibration menus under Tools. Especially the Lens calibration mode has a more complete calibration workflow now. It needs to be run on a short checkerboard calibration video. Check here.
The color profile button has been removed because of some changes in the way the drawings properties work. Now when we change properties like color on a drawing they are immediately saved as the new default, and the next drawing of this type will use these properties. This is more natural than having to manually save it every time. If you have a specific workflow that is broken by this change let me know so we can see if it's something that can be worked around or taken into account.
26 2026-06-18 12:32:47
Re: v 2025.2 does ot open all my video files (3 replies, posted in Bug reports)
Could you share one of these videos that cause the problem please? If it's small you can send it at the following: joan at kinovea dot org. If it's more than 5 MB please send it via a file transfer website like swisstransfer or put it on google drive or similar and share the link by email.
27 2026-06-14 11:59:30
Re: v 2025.2 does ot open all my video files (3 replies, posted in Bug reports)
That is very strange.
What do you mean by "a continuous blue line next to the red indicator", what red indicator?
28 2026-06-02 15:18:29
Re: Video playback speed (1 replies, posted in General)
For now I would say just set the playback speed to 50% (use up/down arrow keys to land on exact percentages), if it's possible for your use case. And if you are sure the videos were captured at 30 fps you can set that in the time calibration dialog so the timestamps, time intervals, speed measurements, etc. take it into account. Time calibration doesn't touch the internal video frame rate used for playback.
Sometimes the file format container and the video codec disagree maybe it's one of those cases. Unless the video is interlaced in that case you would see artifacts and you would need to do Image > Deinterlace.
Not familiar with continuous x-ray images, is it imaging someone/something in motion or is it the tool that is moving and scanning at different depths/locations? Where is the 30 fps information coming from? Is it 30 or 29.97?
29 2026-05-05 15:05:10
Re: Error using marker (1 replies, posted in General)
rodrigoncalves_ wrote:
the application closes automatically.
Hi,
First of all sorry for this, it sounds like a bad bug. Do you have any exception logs in the log folder, these are files starting with "Unhandled Crash" in the file name. If so please send them to me at joan at kinovea dot org. Thank you.
30 2026-05-04 10:27:37
Re: Positioning Multiple Zoom Tools (1 replies, posted in Ideas and feature requests)
It's not necessarily a simple feature to implement because the magnifier tool is unlike any other tool due to how it behaves and also functionally the magnified area can take up a lot of space in the viewport so it would make it difficult to use (at least until the magnified area can be moved outside the original image area).
Maybe a different approach would be something like the Kinogram mode where the viewport is split in multiple tiles and you can manually pan around inside each tile, and there is a zoom level for all the tiles.