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

35

(18 replies, posted in Cameras and hardware)

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.

37

(1 replies, posted in General)

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.

38

(3 replies, posted in General)

For others: you can change it on a per-drawing basis but if you would prefer the default for all drawings to always be visible you can change the default visibility in Options > Preferences > Drawings > Opacity, and check Visible for the entire video.

It's a bug I'm also seeing it in various videos but haven't had time to investigate more deeply yet.

40

(18 replies, posted in Cameras and hardware)

Thanks for testing and sorry it's not yet working correctly. Thanks for the log by mail. I don't think SwingCatalyst is interfering. I'll investigate.

41

(1 replies, posted in General)

Typically when the resulting video appears sped up it means the frame rate received and recorded is lower than the one configured. Either because of frame drops or some other issue.

How do your record the video from the camera? Via an MJPEG server or some other means? I'm not familiar with Droidapp and search doesn't really yield any relevant info.

42

(18 replies, posted in Cameras and hardware)

Hi everyone,

Here is a link to the first public version of the GenICam plugin.

Kinovea.GenICam-1.1.0.zip

Compatibility: this plugin is only compatible with Kinovea 2024.1

Thanks to every one that helped test this plugin so far!

How to use:
- Unzip the archive somewhere and copy the "GenICam" folder into Kinovea application data folder under the Plugins\Camera directory (you can find the application data folder via Kinovea menu Help > Open log folder).
- You must still install the drivers and software from your camera vendor separately. If the installer for the vendor runtime or SDK has various options make sure to check the options mentioning "GenICam" or "GenTL".
- Restart Kinovea.

Currently reported to work with cameras from the following vendors:
- Allied Vision
- Basler
- Baumer
- Daheng imaging
- IDS
- Teledyne FLIR
- Vision Datum

Known issues:
- With IDS cameras, reducing the image resolution results in a black image. (Not clear if this is only for the UI-xxx cameras or also the newer U3-xxx, if any one has one of these please report).
- 1 report that Daheng cameras using GigE interface don't work (USB 3 cameras do work).
- When using two Teledyne FLIR cameras of the same model at the same time it can crash. One camera should work.

Please report your experience and what camera type you test it with.

Thanks,
Joan

Do I understand correctly that you are *producing* new kva files out of excel, not the other way around?

The mapping from timestamps to frames changes with each video, it's decided by the encoder. But there is some logic in the kva importer to adapt files created from one video when loaded into another with different frame rate. Can you clarify your process a bit more, how is the excel sheet created, is it referencing times or frames, do you do any annotations in Kinovea or is it another program that creates this excel sheet that you want to import, etc.

Apart from here there are some occasional discussions on the Golf Simulator forum, especially the Computer Systems sub-forum.

Maybe of interest also the Aravis discussion board, Aravis is an open source library to work with GenICam machine vision cameras. The forum is of course focused on the use of the library but you might find some interesting info there. (note: this library requires changing the driver of the cameras to the generic libusb one which typically makes them not compatible with the manufacturers software).

For instance when just looking at the information I can find on for instance the IMX287 I can't see any indication that I can get more fps at lower resolution but things I have read indicates that it should be possible.

Yeah I think that's because it's not a feature of the sensor itself but of the firmware. Most likely all sensors are capable of this, even those in webcams, action cams or phones, but the on board chip and its firmware driving the sensor are exposing different functionalities.

Many vendors have an area on their website with "white papers" or a "knowledge base" or "application notes", with interesting info at the level you might be interested in, not necessarily specific to one particular camera.

Some links:

- https://www.baslerweb.com/en/downloads/documents/
- https://www.baslerweb.com/en/learning/
- https://en.ids-imaging.com/knowledge-base.html
- https://www.baumer.com/us/en/service-su … w-Overview
- https://www.teledynevisionsolutions.com … edge-base/

How are the files created? What video player can read them? Could you share a small sample file in a new issue in github (click Bugs at the bottom of this page) or by email joan at kinovea dot org. Thanks.