Search options (Page 5 of 6)

Hi,
using the Basler lens selector you can choose your camera and lens and the distance camera-to-object to see the dimension of the frame the camera can record. Your pixel size of the sensor is 6,9 micrometer, so 5MB resolution should be enough. Open the aperture fully to 1,8.
If the recording-window is too small in dimension, you would have to go below 4mm focal length. However, most C-mount lenses do not go below 3,5mm. To go further down to about 2,8-2,9mm (I use it for down-the-line recording from a distance of 1,9m) you would have to use S-mount lenses.
However, the internal color-adapter of the camera might have to be removed to bring the lens close enough to the sensor. You should check with Basler to get it work it necessary.
To my (painful) experience, selecting the right lens is not as easy as I thought at the beginning. So it would be good to be sure to get it returned if it doesn't work as expected.
Regarding light, 250W LED should work. Start at 100fps framerate and 1000microsecond shutter speed. To get the image (the club) completely freezed you would have to go down to 200microseconds (not milliseconds!). However, going below 1000microseconds and over 100fps, the lightning source should have a near zero flicker index, otherwise the video flickers tremendously.

most of the handy-cameras recorded videos did NOT use a constant framerate. Therefore, it may be favorable
to convert the video to a constant framerate. Furthermore it may help to convert the video to "mjpeg" to store a full frame to every frame. MP4 is the container but does not control the content of the video. Be aware of creating a hugh file using the mjpeg-options.

using FFmpeg the option -c:v mjpeg creates a video that contains a full frame for EVERY frame, not only the difference from one frame to the other. This type of video can be read in Kinovea and it is possible to scroll back and forth from one frame to the other. Furthermore, you could experiment of using a constant framerate for the output-video using the -r option. The quality is controlled by -q:v 2 (highest quality, 23 lowest).

Example
ffmpeg -i input.mov -c:v mjpeg -q:v 3 -r 30 output.mp4

Hi,
I'm glad to see that others are also using Basler-cameras. So far, my experience is very well with them. In general, the interface is very stable.

The problem definitively is the bandwidth, it is too high and over the limit. I would suggest, that using your resolution in color, about 40fps would be the maximum any system can transfer.

My camera is a MONO 1,4MB (1440x1080 pixel, 220fps, Basler ace acA1440-220uc). Trying to use the maximal setting with this camera, the limit already is reached.

Recommondation:
- First check your hardware configuration using the BANDWIDTH-Manager in the pylon interface (under Tools). Look on the maximal bandwidth your system can deliver.
Play with the parameters of the camera and check out, what will be the maximal setting you could use on YOUR actual system. Then, go down a little bit to take the conversion inside Kinovea into account.

- Start using MONO8, Resolution 800x600, 100fps. The bandwidth will be about 100MB/s and should run smoothly.
Then go up with the resolution and the fps and see, what the Pylon-program will show. To my experience, the bandwidth should be below 300MB/s to work stable (having a dedicated USB3.0 interface).
If you use color (PixelFormat RGB8) acquisition, the transfer-rate will increase by the factor of 3 !

- Try out BINNING, if available in the color version. It reduces the resolution by 2 and gives you a much brighter image at the same lighting.

- regarding hardware: it is important to have at least one dedicated USB3.0 port available where no other devices are connected. I'm using a separate PCI-card with 2 INDEPENDENT USB 3.1 V2  ports and the USB 3.1 -port of the motherboard.

- If you have only 1 camera connected, your hardware should be sufficient. Check it out looking at the CPU-Load. Open Task-Manager, click on "more details" and you can see the amount of CPU-load of all your tasks.

Hi Inorkuo,
I already did a lot of performance analysis of the new version. Depending on the CPU-type the load is different. More Cores and threads decrease the loading a lot. I just work on an load/Bandwidth overview of different processors/camera settings and will publish it the next time. In short CPU/Load (delayed mode) for 1 Camera/1Kinovea:
Pentium Core2: 45%, i5-9600k: 25-35%, i9-9900: 12%

If Kinovea is in delayed mode (for us golfers a must have), it is quasi under full load. If record is pressed, the load will NOT increase any more, it stays at the same level. If in camera mode, the load goes down to below 5%, but if record is pressed, it goes up to the same level as in the delayed mode. Therefore, it doesn't matter if delayed mode is used anyway.

Hi Joan,
I actually tested a BASLER Camera that can speed up to 200fps.
I used a special USB 3.0 adapter card that has 3 controllers, so there will be no bottleneck. Speed is about 380MB/s using the Porttest of the BASLER software.

Actually, I use a KAYETON that uses 100fps and the BASLER Camera at 200fps.
The actual test show that also in DELAY-Mode using 1,5 seconds, KINOVEA is capable to capture the video at that high rate of 200fps.

It may be interesting to other users that would like to capture videos at higher speed.

Here you can find the link to screenshots of the settings used for the BASLER-Camera:

https://hente-my.sharepoint.com/:f:/g/p … A?e=lHeWgJ

Hi,
if Kinovea is in replay mode, and the left window is loaded once with a video, I could not find any solution to "reload" it with another video. I can only address the right window using ctrl-o or Open/File to load another video. I don't want to use Drap and Drop (AutoIt-script).

Is there any solution or maybe a hidden hotkey?
Thanks