You are not logged in. Please login or register.
Kinovea - Forums → Posts by joan
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?
Very cool. Reading your original post I thought this was like a contact microphone but in your case it can just hang on a net and get triggered by distant movement, quite interesting.
How sensitive is it? If we put it on a high jump mat for example, would it trigger from the jumper falling on the other side of the mat? Or if it is attached to a net like in your picture and someone else passes by quickly, does it trigger from the small wind?
Maybe it could also be used to detect water surface breaking in diving.
Actually this makes me think there could be a function where the trigger is used to increment a counter instead of starting capture.
This sounds great! The link doesn't work maybe the repository is on private?
If you are not using the center of gravity point then it doesn't really matter, you can place the joint points exactly where you need them to be according to your needs. The CoG placement is based on segment weights coming from old anthropometric tables. You can build an alternate human model by modifying the existing one if you need more customization.
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.
It appears the issue with FLIR cameras is that when you have two of them of the same model connected at the same time, the identifier we use doesn't differentiate between them and this causes a crash. Single camera should work.
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?
That's great to hear!
Yes the Spinnaker SDK has the "FLIR_GenTL_v140.cti" file which is a bridge between the actual device driver and the GenICam libraries. (In the case of user aroe79 above they already had that installed based on the log so that wasn't the issue).
I'll add a little paragraph to the first post to clarify.
En el menu Herramientas > Calibración del tiempo (puede que sea otro nombre según la version de Kinovea). En este dialogo se puede cambiar el eje del tiempo. Si quieres que el video se reproduzca a 120 fps, ignorando el valor escrito en el archivo, puedes cambiar en la parte inferior.
No, at the moment you cannot do any tracking in the capture screen on a live camera feed.
Check via Tools > Scatter diagram. It shows the positions of all the markers and has a "Copy to clipboard" function that copy the data as CSV.
The compatibility table at the moment is the following:
- Kinovea 2024.1 + plugin Kinovea.GenICam-1.1.0 = Basler Pylon any version.
- Kinovea 2023.1 + plugin Kinovea.Basler-1.3.0 = Basler Pylon 6.1
- Kinovea 0.9.4 and 0.9.5 + plugin Kinovea.Basler-1.2.0 = Basler Pylon 6.0
Kinovea 2024.1: https://www.kinovea.org/en/forum/viewtopic.php?id=1959
Kinovea.GenICam-1.1.0: https://www.kinovea.org/en/forum/viewtopic.php?id=2005
So far I have received feedback from 3 persons with Teledyne FLIR cameras. It worked for two of them and didn't work for the third one, but I'm not sure what the problem is. So any additional feedback helps.
Certain machine vision cameras go in this direction of the trade off since for industrial inspection they also often need more resolution and don't care that much about frame rate. I see devices listed with 5496×3672 at around 5 fps for example or even 5320×4600 at 15 fps. But they can be quite pricey.
I wonder if at a certain point, maybe 0.5 or 0.1 fps, the best approach would be to have something that takes regular photos and save them to a folder, and then something else is taking these images and produces an MJPEG stream out of it.
If the images are saved directly to the computer it could even bypass the stream/capture step entirely. Kinovea can open a folder of images with sequential names and load it as a video. I have not tested this with very large images, the explorer will be quite slow to create the thumbnails which isn't necessary for this. I think for 8K images at 0.5 fps or less this might be an interesting option.
There is also latency and lens quality to think about.
For versions before 2023.1 (including 0.9.5) the export size depended on the current view port size so it will change depending on your screen resolution. For 2023.1 and newer it only depends on the original size so saving dual FHD videos should result in 3840x1080 or 1920x2160 if saved vertically.
Kinovea - Forums → Posts by joan