1

(8 replies, posted in Cameras and hardware)

Download the Basler-Plugin from the Kinovea site:
a folder named "Kinovea" is created in your download folder, containing the BASLER - folder

Open your Kinovea program
click  the menu-topic: help/Open Log folder

this opens a filebrowser having AppData open and looks like this:
... <your kinovea path>\AppData
Double click on Plugins
double click on Camera

open your download-folder in a second filebrowser (open file browser with a right mouse-click)
double click on the folder that has been downloaded and named Kinovea
drag and drop the Basler-folder in it to the Camera-folder of the other filebrowser
and you are done.

Pylon 6.0.1 will work
Kinovea 0.9.5 will work

good luck

2

(10 replies, posted in Cameras and hardware)

If your FO (face on) camera is not fixed to the wall, I would recommend the 6mm lens. Then you can play around with the distance to get it optimized. If you will increase the recording fps, you have to reduce the image height. Then you might go a little bit closer to the object to catch all of the swing. If the camera is fixed to the wall, a more detailed calculation of the geometry is recommended to find the optimal solution. However, there are only 6 and 8mm lenses available, nothing in between. So moving the camera to optimize the FOV is the best you can do.
These both lenses will fit perfectly to the IMX174 sensor camera:

GetCameras LCM-10MP-06MM-F1.8-1.1-ND1
Non-Distortion, Price 398,- Euro

Kowa, LM6HC, 6 mm, 1“, F1.8
Low-Distortion, Price 600,- Euro

I have two of the GetCameras - lenses and they are pretty solid. Didn’t find a better one at that price for the IMX174 sensor camera.

3

(10 replies, posted in Cameras and hardware)

For Golf setup, I recommend a field of view (FOV) of 4500mm width and 2800mm height at the golfer level (not ball).
Using the th IMX174 sensor, your camera should be more than 3500mm away in faceon (FO) position to catch that FOV.
If you select the 2/3" lens, there might be some vignetting at the borders, especially the corners. However, you mostly do not need the full width of 1920 pixels. I use about 1400 pixels and have reduced the height to 1000 pixels, so vignetting should not be a concern. If the 8mm lens will fit (please double check the camera-object distance), I would recommend the C23-0816-2M-S f8mm for 70 Euro. It has an F-value of 1.6 which is pretty good. All other lenses in the recommendation list have a F-value above 2.0 and will more darken the image. The resolution of this lens is 2MB and should just fit your sensor.

4

(8 replies, posted in Cameras and hardware)

David, be aware that the ACA1920-150 has a 1/1.2" sensor (not a 2/3" sensor !). You will get vignetting (borders of the image are darkened) due to that the aperture of the lens is too small for that sensor.
In general, the lens should be adapted to the sensor format. If the lens has a value of 2/3", it will fit on a 1/3" sensor, but not on a 1/1.2" sensor due to the smaller opening diameter of the lens.
The aperture value F determines the maximal opening of the individual lens, determining the amount of light that will go into the camera. Values below F2.0 are OK, F1.4 is very good, F1.2 is perfect. Lower F-values and higher sensor-values are resulting in higher lens prices.
Always check the exact specification of the lens, if it will fit to your individual camera.

It is true that the prices of the lenses for the 1/1.2" sensors are higher. I'm actually using 3 of these cameras from Daheng (have had different 1/2.9" sensor-cameras before) and I think it is worth the price.
If you would like to stay in the medium range, use a 1/2.9" mono sensor-camera (IMX273), and use the S12-lenses that are below 100 Euro, but the light intensity is not as high compared to most the C-mount lenses. You might also look for relatively cheap C-mount lenses in the area of 100 Euro. If your camera-object distance is pretty small, you have to go below 4mm lenses. S12-lenses then are appropriate.

You will also find some other posts in the forum discussing that topic

5

(10 replies, posted in Cameras and hardware)

Looking on light topics, the spectral response and light intensity of each camera is important. It is not the manufacturer of the camera that makes the difference. Comparing the cameras you are mentioned, the cameras with the IMX174 sensor (Basler Aca1920-155um and IDS UI3060CP-M) will give the best results on low lights. The Python1300 sensor (IDS UI3140CP-C) I would not recommend so much. Especially the color version needs much more light. I always recommend the mono versions of each camera due to higher light intensity.
Always keep in mind that the price of the lenses for the 1/1.2" sensor (IMX174) is much higher than for the 1/2.9" sensor (IMX274). An aperture (F-value) below 2 is favorable.

Looking on the spectral responses of all of these sensors, the response at the area of IR-light is rather low. I tested it with some IR-lights and there wasn't a remarkable difference. So I did not went further with the IR-project.

Going below 200 microseconds will be difficult. Then you need a very, very high amount of flicker free light. I use between 300 and 500 microseconds shutter speed, using 2 x 200 Watt flicker free LEDs with an 1-10V dimmer (important to adjust to your need!) from the front (about 45° left and right from the golfers stand, mounted to the wall) and an Aputure Amaran spotlight 40Watt (25°) to lighten the ball directly from the top (mounted on the sealing).

The flicker free LEDs are the following:
AML® SQ-200 D – dimmbar,26.500lm, 200W, 4.000K, regularly used as hall-spots in the industry.

As you are always on the limit of visibility in low shutter speed applications like golf, I' using an automated post processing of the created videos using my scripting tool you may find on the golfsimulator forum.

Do not yet really understand what your measurements will be and for what you need such a high resolution.
I would recommend making a test using the camera of your handy at high speed and reduce the frame size afterwords to see how far you can go down to not loose the information you would like to see. I'm always wondering, of how low resolution will give a lot of information if the image is crisp enough.
Ask the representatives of Daheng regarding the technical details of the Mars camera. I think they can tell you what resolution/fps you may reach with and without a frame grabber.
I have no experience with 10GigE transfer cameras and do not know what the transfer limit will be in real life.
You may estimate the data transfer you need by using the formula: width * height * fps * C/M(factor) / 1000000, resulting in MB/s. For color use factor 3, for mono use factor 1 The limit of USB3.0 is about 350-400 MB/s.

keep in mind that reducing the HEIGHT of the image will increase the fps. Changing the width has no effect.

Blurring is NOT related to fps. Increasing the fps will increase the number of images you will capture in a given distance (in moving objects). The shutter speed alone determines, if each single image shows a blurring. The amount of blurring depends on the speed of the moving object. A shutter speed of 1000 microseconds, for example, means that for each video the camera is recording, the shutter remains 1000 microseconds open during each image is recorded. If the object moves slowly, the amount of blurring is low. If the object moves fast, also 1000 microseconds creates a significant amount of blurring. Of course, blurring is most visible, if the camera is positioned perpendicular to the moving direction.
I suggest, that your intention is to reduce the blurring in your image and a lower fps will be sufficient.

Don't know if Kinovea can recognize a colored marker. In most cases, the marker is more bright but not colored. Mono cameras have a higher light sensitivity (need less light) giving a good image contrast.

This is the webpage of the lens calculator
https://www.baslerweb.com/en/tools/lens-selector/

You have two options. First, enter the camera on the left side. Second, enter the sensor chip and the adapter type on the right side.
If the working distance is small, it might be better to start using the right side. C-mount lenses go down to a focal length of about 3,5 - 4mm.
However, that might not fit your need if the camera is close to the object.
Therefore, start with the sensor chip IMX273 and S-mount adapter.

To get a full FOV (field of view) of a golfswing, a width of 4500mm and height of 2800mm at the golfers body position is needed.

Start the calculation with a width of 4500mm and a working distance of 2000mm in your case (or 2600mm if your measurement was from camera to ball).

The calculation displays a focal length of 2.2mm. The calculated height of the FOV is about 3370mm.
2.2mm is near a fish-eye lens and has a lot of distorsions, that is not recommended.

Do a further calculation, resetting the values, entering a height of 2800mm. In most cases this will be sufficient. Enter your working width of 2000mm.
You will get a focal length of 2.7mm.

I’ve personally used a S-mount lens with a focal length of 2.9mm that works pretty good (the distance camera to object was a little bit higher).
You may check the FOV again resetting the webpage and enter the 2.9mm focal length to see the FOV you can achieve.

You do not necessarily have to buy the S-mount lens from Basler. There are different other companies available that produce good quality S-mount lenses. I bought my from Lensation. However, be aware that the lens will fit to your camera (Focussing and Sensor size). In general, the support of the company should tell you if the lens will fit.

The so called aperture is a value inherent to the lens and does not change the geometry. In general, the lower the aperture is, the higher the price.
In general, the Aperture values of the S-mount lenses are higher than in C-mount lenses. Therefore you need more light.

The lens should be OK, Aperture of 1.6 is a good value. 1/2“ will fit to the 1/2.9“ sensor to prevent vignetting.
I assume it is a C-mount type. If you will buy a further lens, try to go down to a fixed focus lens with an aperture of 1.2 , it increases the brightness of the image a lot and gives you a more crisp image. On the Basler webpage there is a good lens calculator to estimate of what lens you need. Set your distance of the camera to your room dimension and the width of the FOV to about 4,5m to calculate.

30000 lumen is a lot. I have 2x20000 but installed a 1-10V dimmer to better adjust it to the local light situation.

I highly recommend a mono camera due to factors:
In USB-cameras the limit of bandwidth is in the range of 300-400 MB/s data transfer.
Assuming an image of 1000x800 pixels, fps 100, AVI/MKV uncompressed format, in color mode the transfer is about 240 MB/s (1000x800x100x3)
Going up to 1240x1024 pixels, fps 100, the raw data transfer already is 571 MB/s and therefore over the limit.
Same resolution using mono, it is about 190 MB/s (1240x1024x100x1).

You could say, OK, I will use the compressed format MP4. However, then the computer system/Kinovea will have to do the compression and you will see a lot of dropped frames.
To overcome that situation I checked the Baumer camera. They have MJPEG compression build in. But they cost 2500 Euro each.

The second reason I like to use the mono camera is the light intensity that is much better in mono-cameras compared to a color camera, needing less surrounding light.

Anyway, in indoor video analysis you need a lot of light. I actually have switched from an Optoma 1090 HD-projector (3000 lumen) to the Optoma 4K400STx (4000 lumen) and the improvement is impressive. I think it is not only the 4k but more the much brighter image. The screen washout now is minimal also in the situation of sufficient LED light.

I do not think that there is a real difference between the Daheng and Basler camera of the same IMX274 chip. The support of Daheng was fine and needing 2 camers the difference already is 250. The only advantage of the Basler to me was the driver. You can connect and disconnect the camera at any time and it works. However, this advantage only was evident during testing a lot outside Kinovea. If you have Kinovea running, the plug and play doesn’t work anyway and is not needed.

9

(6 replies, posted in Cameras and hardware)

Regarding the lights I highly recommend getting the specification from the manufacturer/vendor. I have spend too many money for led lights that were specified as "flicker free" but they have had a significant flickering if I went down below 1000 microsecond shutter speed. So I recommend first to check, what the lower limit of shutter speed is in your application that satisfies your need.
If your power grid creates 50Hz/60Hz and a framerate of 100/120 fps is sufficient, you may use regular lights and the flickering will not appear. However, if you use higher fps rates, you will see the phenomenon. You can test it with a handy camera.

10

(6 replies, posted in Cameras and hardware)

To answer your question some more information is needed.
What is your intention to use a very high resolution?
It would make things much easier to use a lower resolution around 800x600 or 1000 x 800, having the amount of data to be transferred in mind. Using this resolutions, a much cheaper camera can be used.
If you go up to the resolution of your selected camera (4192X2160), you will have significant problems to use a high frame rate due to the limitation in data transfer. Therefore, Getimage recommends a frame grabber that will create higher costs ( 2x500 Euro). if you select this solution, you have to check if you can use the high frame rate AND the high resolution at the same time. However, the file size of the created video will be huge.

In any case, do not use a rolling shutter camera. You will have a lot of image deformation (bending or extrusion of the objects).

All Daheng cameras that use the Galaxy driver can be used with Kinovea (as far as I know).

All GigE cameras have a lower data transmission limit compared to USB3.0. Maybe using a frame grabber can enhance it, but you should check what the limit is.
The limitation of cable length of USB can be overcome to a given amount. Using high quality cables you might extend the system up to 10m. Using special cable also to a higher distance (see Basler webpage for examples).

Beside frame rate the shutter speed is a very important factor and most often the more critical value. I suggest that you would have to go down to about 500-1000 microseconds to get a crisp image in your video. Otherwise you will have a lot of blurr in it if you look on the video image by image.


Regarding frame rate. In normal gait (about 2-5km/h) I would estimate the speed of the moving leg at about 20km/h. That is 5,5m/second. Using 100fps, you get an image every 5cm of movement, going up to 500 fps every 1,1cm.

Do you use your application indoor? If so, be aware that you may need a lot of light if your shutter speed goes down to 500-1000 microseconds. An absolute flicker free lighting is necessary.

The much cheaper cameras of Daheng already will give you a lot of options to adjust all the necessary parameters.

Two recommendations:
MER2-160-227U3M
1/2.9“ sensor IMX273, resolution 1440x1080, 227 fps, USB3.0

MER2-230-168U3M
1/1.2“ sensor IMX174, resolution 1920x1200, 168 fps, USB3.0

Similar cameras from IDS and Basler are available, but at a higher price.

I recommend a mono camera due to better light intensity and 1/3 of the file size compared to a color camera.
I use 3 of the 168U3M at the same time in video golf recording. The image quality if pretty good. I also have a camera from Basler with the IMX273 that gives pretty good images.

Keep in mind that you can increase the frame rate of both cameras by reducing the image height (not width). Reducing it for example to 1/2 of the specification, the fps rate increases by a factor of 2. This works proportionally.

The 1/1.2“ sensor camera has a better image than the 1/2.9“ and needs less amount of light. However, the lenses for the 1/1.2“ camera are much more expensive.
The camera plus lens cost of the 1/2.9“ camera is around 500 Euro, of the 1/1.2“ camera around 1100 Euro.

Selecting the right lens for your application may be a further topic. But first you should carefully define your geometrical situation of distance to the object and  the field of view you would like to record. On the Basler website you may find a valuable tool to calculate the FOV for a given image sensor/lens combination.

Regarding the workflow you might look on the Golfsimulator-forum. A versatile script, not only applicable for Golf, is available. It can load a complete setup with one click once it is defined and do a lot of post processing to extract videos, single or stacked images, user management etc..
Search for: „Comprehensive programs supporting video golf recording using Kinovea“

Hi Jerome,
see a recent post from today regarding the cameras. I have a similar from Basler and it does a good job. The price/performance relation is very good. A big advantage of the sensor size of 1/2.9" is that you may use relatively cheap lenses for it. Most C-mount lenses cost about 100 Euro, using S-mount lenses (lower quality) will cost about 50 Euro. If S-mount lenses are used, you have to check if the focus of the lens will fit to the camera.
Light requirement depends on your local situation of how much day light you have during recording. If not, you need a light that has a low flicker rate. Going down below 1000 microsecond shutter speed, it has to be absolutely flicker free. Carefully check the specification of the light.
I have had a color camera, but the mono needs significantly less light.
It works fluently with Kinovea

To record before the impact, you have to do the following:

Select options from the menu, then preferences, the preferences dialog appears

Select Capture
select the Recording Tab
activate "Delayed: records delayed frames"

13

(3 replies, posted in General)

Call always waits till the called program is finished

try start instead, that should work:
start "C:\Program Files\Kinovea\..."
start "C:\Program Files\Kinovea\..."

14

(1 replies, posted in General)

I’m using Kinovea on parallels on a Macbook Pro since many years for testing and configuration and it works fluently with all versions.

It also works with the machine vision cameras of Basler, IDS and Daheng if the appropriate driver is installed (Pylon 6.01, IDS 4.95 and Galaxy actual version). All settings of the cameras can be modified.

If OVC-compliant USB2-cameras from ELP or Kayeton are used, it is somehow tricky to set these cameras to the maximal resolution they can deliver. Sometimes they are connected with a maximal framerate of 30 or 60, sometimes with the higher frame rate of 120 fps. To be honest, I could not find a reproducible way to set it to the highest frame rate.

You may start with this post
https://www.kinovea.org/en/forum/viewto … 5244#p5244

If you use high speed recording (>120) up to 3 cameras, I recommend a i9-9900 cpu or equivalent. However, during recording the cpu runs at about 80% load.
If more than 3 cameras are in use, I would recommend an Intel Core i9-13900K or similar in combination with a motherboard having the Z790 chip or similar. On these boards, there are at least 3 USB 3.1 ports available. In case of 4 cameras you may need an additional high speed 2-channel usb 3.0 or 3.1 interface card, connected to a PCI 4.0 x4 (x4 is important, not x1) slot on the board.