Search options (Page 2 of 129)

That's very odd and the first time I hear about something like this, I'm not sure what could cause the issue.

If you go to the log folder there might be a number of crash files with names starting with "Unhandled Crash", could you please send me the log.txt and log.txt.1 and any of those Unhandled crash files at joan at kinovea dot org please?

Are you working with two instances of Kinovea or dual screen inside one instance?
Do you have the same issue when working with just one video? Is it specific to when you work with two videos?

Normally when it crashes the next time you open it should propose to load the last session, including any unsaved changes, if you don't see that there might be a second problem.

Hi, these instructions are for an older version, there is an additional "arming" mechanism now that's preventing unwanted recordings, and it's disarmed by default (this may change in the future but for now it's like this). In the toolbar at the bottom of the screen there is a speaker icon that you need to toggle. Once you toggle it to "armed" it should work. You need to do this once at the beginning of the session.

I didn't quite get the relation between triple playback and HD framing.

It should be possible to add spacing between the two videos, or maybe a margin at the bottom, I'll write it down for later.

It is unlikely to happen in the near future. Other things you can do is launch two instances of Kinovea, but you won't have synchronization, or maybe synchronize two videos first, export that and then load the combo with the third.

May I ask if this is for synchronizing 3 different persons or 3 different views of the same person, or something else?

This sounds great! The link doesn't work maybe the repository is on private?

Hi, there should be one or more files in the log folder with names that start with "Unhandled exception", could you paste the content of the most recent one here as well? This will contain more precise information for debugging.

But more importantly this is from an old version published in 2011, could you try and see if you reproduce the problem in the latest version? A lot has changed in the comparison/synchronization system.

Hi,
What version of Kinovea are you using? There were some important changes in 2024.1, it's possible there is a regression I haven't noticed in my testing.
Is the camera static? Are you using camera motion estimation? When you say a digitized point do you mean a new static marker or a new point along a trajectory?
Indeed a given point on a given frame shouldn't change coordinates unless the coordinate system is tracked or the calibration object is tracked, is it your case?