nice solution, have never seen this function. Thanks


(3 replies, posted in Español)

I gave up that project. Got a nice M1 Mac on last christmas, installed Windows 11 for Arm -64bit from the MS-Developer side (including last version with X64-emulation) on Parallels 17.x and tried to install a bunch of different .NET frameworks but couldn't get Kinovea to run. I also found other simple video-programs did not fully support the Mac-Camera. Actually, the main problem seems to be any USB-driver that is not adapted to the ARM-processor.

Asking the camera manufacturer BASLER if there will be support of the their USB-driver in the near future. They told me, that they will not support ARM-processors and they do not even know other camera-manufacturers planning to support it.

You could also read in the internet (youtube-channels et al) that there is no guarantee that windows programs not specifically compiled for ARM-processors are running on windows at the present time.
I therefore gave back the M1 and switched to the last i9-MAC.
Too sad.

sorry for the number of questions-marks (Don't know where they come from). They should be replace by a space.

In the meantime you could use the ability of Kinovea to call an external program after each recording, which is a great and versatile feature of Kinovea.

It can be found under: Options/Automation/post recording command

To extract an image frame from the video at a selected time position, ffmpeg.exe may be used in conjunction with a „batch“-file (windows files having the extension „bat“, serving as a simple command processor).

See below the content of a batch-file named EFsecond.bat (ExtractFrame using seconds)
The batch-file contains a final command using ffmpeg to extract an image frame out of a video.

To use this batch file you might:
- download FFMpeg and install to a directory (in the example: d:\ffmpeg\bin\ffmpeg.exe)?Go to and search for „Get packages & executable files“ to download an actual version compiled for windows. FFmpeg is free of charge.?if a different installation-directory is used, modify the line „set ffmpegexe=…“ in the batch-file according to the full path of your ffmpeg.exe - location
- Create a directory to contain the batch-file (in the example: d:\batch)
- Create a file that is named EFsecond.bat and copy the lines below to it.?Create a directory (your directory) the extracted images should be saved (in the example: c:\images)?set this value to the line: set targetdir=„your directory“?(do not use quotation marks or spaces after the „=„ and be sure the directory exists?Save the file. Be sure that the extension of the file is „bat“
- Open your Kinovea instance and go to the inputfield „post recording command“ in options
- Type in: d:\batch\EFsecond.bat %directory %filename means: second.milliseconds, i.e. 1.5 to extract the frame at the position 1.5 seconds. Use a DOT, not a Comma as decimal separator)

Now, after each recording, an image frame is extracted from the video and store in the image directory. Naming of the image is: SourceVideo.ext.JPG.
The batch-file may be modified to further needs.


Some hints on Framerate in relation to the target frame to extract:
To extract a specific frame, you could calculate the seconds from the target frame.
Example: The resulting video has a frame rate of 120. So each frame „consumes“ a time of 1/120 seconds = 0.00833 seconds. To extract the 255. frame of the video, the time-value has to be 255*0.00833 = 2.124 seconds.

If you use a higher frame rate take into account the framerate-replacement feature of Kinovea. It is defined in the settings (Options/Capture/Recording):
Example: A Video is recorded using 200 fps for 2 seconds. FPS-replacement is set to 30 fps. FFmpeg will see the resulting video as a video having 30fps with a duration of (200/30 * 2.0) 13.3333 seconds. To catch a frame at the „real“ position of 1.5 seconds, a value of 1.5 * 200/30 has to be used: 10 seconds.
Dropped frames are not taken into account here. Furthermore, the exact target frame may not always be at the same location inside the movement due to some microseconds delay to the sound trigger.

Content of EFsecond.bat:

@echo off
REM ===== Extract an image frame out of a video at a specified time location (seconds.milliseconds)
REM ===== Example used in Kinovea/Options/Automation/post recording command:
REM =====    d:\Batch\EFSecond.bat %directory %filename 1.0
REM ===== Parameters in use
REM %1 contains directory, Kinovea: %directory
REM %2 contains filename, Kinovea: %filename
REM %3 timeposition to extract frame, if omitted uses 0.0 (first frame)
REM ===== Modify these parameter-values according to your setup
set ffmpegexe=d:\ffmpeg\bin\ffmpeg.exe
set targetdir=C:\images
set timepos=0.0
IF "%3"=="" GOTO Final
set timepos=%3
%ffmpegexe% -y -ss %timepos% -i %1\%2 -frames:v 1 %targetdir%\%2.jpg

One more point is to download the Basler Plugins from the Kinovea homepage and copy them to the appropriate subfolder:

there have to be two files:

Hi Oscar, congratulation to the new PC smile

I've had the same issue when installing Windows 11 and Kinovea on a new setup.
First of all for Kinovea up to 0.9.5 you have to use the Pylon 6.0x - Version, NOT 6.1 and up.
So if you have installed higher than 6.0x deinstall this version first.
Download 6.0x from the Basler homepage. You have to actively seek them.

During installation select CUSTOM settings and active Pylon Runtime to install (on a submenu). By default, the installation program does not install the necessary runtime files.
Hope that will help.

would try to use a SEPARATE instance of Kinovea for each camera. Found unclear behavior if using 2 cams in 1 Kinovea. Interestingly, the cpu power usage is lower if 2 pairs of camera-kinovea relation is used compared to using 2 cams in 1 Kinovea.

Using a relation of 1 camera in 1 Kinovea even works with 3 cams without problem (6 Kinovea open).
To prevent file naming conflicts, it might be necessary to use a separate directory for each cam and set the observerdir to this directories.

This is what the log.txt shows.
What exactly does the time format mean. second*1000 + ms (3digit) ?

There are 1 USB2.0 and 2 IDS 3140 cams installed.

the first IDS seems to be fast, but the USB2-cam takes a long time.

543 - DEBUG - [Main] - FileBrowserUserInterface - Application is idle in FileBrowserUserInterface.
1481 - DEBUG - [Main] - CameraManagerDirectShow - DirectShow device enumeration: RYS HFR USB2.0 Camera (moniker:@device:pnp:\\?\usb#vid_15aa&pid_1555&mi_00#6&f5b74ed&0&0000#{65e8773d-8f56-11d0-a3b9-00a0c9223196}\global).
1512 - DEBUG - [RYS HFR USB2.0 Camera thumbnailer] - SnapshotRetriever - Starting RYS HFR USB2.0 Camera for thumbnail.
2151 - DEBUG - [UI314xCP-C thumbnailer] - SnapshotRetriever - Starting UI314xCP-C for thumbnail.
2226 - DEBUG - [UI314xCP-C thumbnailer] - SnapshotRetriever - Camera UI314xCP-C closed after thumbnail capture.
6249 - DEBUG - [UI314xCP-C thumbnailer] - SnapshotRetriever - Starting UI314xCP-C for thumbnail.
6249 - DEBUG - [Main] - CameraManagerDirectShow - Received thumbnail for RYS HFR USB2.0 Camera.
6296 - DEBUG - [UI314xCP-C thumbnailer] - SnapshotRetriever - Camera UI314xCP-C closed after thumbnail capture.
16063 - DEBUG - [Main] - RootKernel - Root is closing. Call close on all sub modules.

Hi Joan,
using 2 IDS UI3140CP at the same time, the camera entries appear in the list after about 1-2 seconds, further 2 seconds until the camera-pictograms are shown. It is reproducible closing and starting Kinovea multiple times.

There is about no delay between the first and the second IDS-camera, they appear just one after the other.

Log-file did not show any problems.
System: i9-9900, every camera has a separate dedicated USB-port (2 channel extension-card). It seems to be driver-related.


(5 replies, posted in Cameras and hardware)

Some comment on Transfer-rate of USB. The maximum transfer speed of USB 3.0 (USB 3.1 Gen1; USB 3.2 Gen1) is 625Mb/s (5GBit/s). This is the absolut maximum. If you use MP4, conversion to MP4 (Basler uses AVI) has to be done by the system. So dropping of frames often will occur. So use uncompressed Video to get the maximum out of your system. To my experience, also an i9/9900 is not fast enough to compress the video without dropping frames.

If you use the full resolution of your camera, you might be over the limit due to some overhead that is needed by the system. Selecting Mono will reduce the transferrate to 1/3 and may help.
Below some examples of the relation of resolution/fps and resulting transfer rate. To my experience it is save if you remain  significantly below 450-500 Mb/s

Width    Height    FPS    Mono Color
1024    1024    100    105    315
1024    1024    200    210    629
1024    1024    300    315    944
1920    1024    100    197    590
1920    1024    150    295    885
1440    1024    100    147    442
1440    1024    200    295    885


(11 replies, posted in General information)

Maybe I misunderstand the problem. But the easiest was is to load 2 Kinovea side by side on the desktop.
The first Kinovea deliveres the "Life" Video and the second Kinovea uses observermode to replay.

That doesn't sound good. However, I have version 0.9.3 running since release and never have had a crash. My default setup is having 6 Kinovea open at the same time without any problem.

To narrow the problem some infos would be interesting:

Are any other programs also crashing
Do the camera-drivers, if are installed, have the right version that is compatible with Kinovea 0.9.3. There are a lot of error messages related to the IDS-camera. IDS-software suite Version 4.93 will work. If you have the Basler pylon software installed, be sure to have 6.0 (not 6.1 !)

Try to deactivate all virus programs. To be save, you could disconnect the internet during testing.

However, what I have personally seen is, that once this type of error occurs, it definitively is time to reinstall Windows from scratch. Expecially if the windows version is updated from an older version (i.e. Windows 8), I have found similar problems. Another reason I have seen are some "tools" - installation (these nice small programs we all like smile ) that replace important Windows-DLLs.
Since longer time, I always reinstall the system on a clean partition if windows shows a strange behavior.

Futhermore, if the computer is running for some years, remove and reassemble the memory-chips after running a memory-checking program to secure that the chips are in good conditions. Also disconnect and reconnect the graphics card to the motherboard slot.
Good luck

Yes, the price for Europe is about 205 Euro. However, be aware of a handling fee of about 50 Euro.
Furthermore, this price is EXCLUSIVE VAT.

You will get a camera at a similar price in Europe, i.e. from Basler:
224fps, 1/3" sensor
Monochrome: … 440-220um/
Color: … 440-220uc/


(39 replies, posted in General information)

skabsurd wrote:


I love Kinovea, such a great piece of software. I use it especially for delayed video playback and recording for instant video feedback in martial arts tricking.
So far the newest beta version ist stable in my use case. Sometimes when I set the video to 5sec delay, its rather the double of it and sometimes its 5sec. I'm looking for more testing on my side.

A simple bug in this version (hopefully not only for me) is, that when I open a video in the playback screen and double klick on the video so that it fits the screen, the playback stutters too much. Then it seems like a 10fps video. When I double click on the video again, its nicely smooth (1080p 60fps). It stutters on 720p 25fps video too.
My machine is a surface pro 7 with i7 processor and 16gb of ram. In the options the memory is set to approx 5gb each for video playback an recording. Display framerate is set to 60.

I hope I could help you for some bug reporting and hope you could solve this issue in the next version.
Thank you

it sounds like a performance topic.
Did you set the display framerate to 60 in windows or Kinovea? If in Kinovea, I would reduce it to 25 or 30. Your eyes will not recognize a higher framerate.
Your graphic card is integrated into your cpu. So everything is shared and may interfere. If there is too less memory available, the system has to store the memory on a file that may things slow down significantly.
You don't need 5GB for each video. If you look on the size of your created video, you can estimate how much GB you need. I is related to the length of recording, not the delay.
If you acquire your video in color, try to reduce it to mono. It will reduce all loads to 1/3.
Start the task-manager and observe cpu-load and especially the amount of reserved memory to be over 100%. Click on "resource monitor" to find the individual values of cpu and memory.

You may use a "standard", cheap microphone. Use an extension cable to position the microphone near your impact area.
If it is as close as possible to the golf ball, you can lower the trigger threshold to exclude undesirable trigger actions due to background noise. I have it clipped to my launch monitor, about 25cm from impact area.