31

(1 replies, posted in Bug reports)

rather sounds like a hardware or connection problem. Would change the microphone including the cable and try again.

32

(27 replies, posted in Bug reports)

@niraj_k
To better understand
- Kinovea starts up without any crash?
- It crashes after trying to load the file:
  08.Modeling Introduction - Blender 2.80 Fundamentals.mp4   ?

Can this video be loaded using another program like VLC ?
You could try to save the video, using VLC for example, to another format and then try to load the converted video to Kinovea to see if it works.

33

(27 replies, posted in Bug reports)

@niraj_k
To better understand
- Kinovea starts up without any crash?
- It crashes after trying to load the file:
  08.Modeling Introduction - Blender 2.80 Fundamentals.mp4   ?

Can this video be loaded using another program like VLC ?
You could try to save the video, using VLC for example, to another format and then try to load the converted video to Kinovea to see if it works.

34

(27 replies, posted in Bug reports)

Regarding the .NET - Version the information inside the Kinovea log file is misleading. It is the FRAMEWORK - version, not the DOTNET-version (thanks to Microsoft smile )
To get the .NET versions that are installed, try this tool from Github:
https://github.com/jmalarcon/DotNetVersions/releases
It shows up all versions that are installed

35

(27 replies, posted in Bug reports)

@Martin
- try to install uEye Version 4.94 if not already done. You could check the installed version number in "IDS CameraManager".
  This version will work for sure. I use it on different machines.
- do not forget first to first de-install the actual uEye - version on your system.
- always disconnect all camera during (de-)installation. And restart windows before the next step.

@niraj_k
It might be the MTS-file Kinovea is loading at startup (00005.MTS). You are obviously using a "video observer root" activated.
Try to delete preferences.xml from your Kinovea\Appdata - subdirectory and restart Kinovea from scratch to see if it runs.
There might be an error in the video-file.

Hope that helps

This is what I'm using, works perfect for me. Pretty standard equipment

Microphone:
https://www.amazon.de/gp/product/B06XX7 … &psc=1

Audio Extension cable:
https://www.amazon.de/gp/product/B01CNA … &psc=1

A concern against using the iPhone might be that the camera is a rolling shutter camera, not a global shutter.
A rolling shutter camera records one pixel line after the other from top to down until the full image is recorded, a global shutter records the full image at the same time.

Depending on the speed of movement there may be a significant distortion of the recorded frame image. The distortion does not reflect the real geometry and  may lead to wrong measurements between two points. Unfortunately, you may not correct the distortion by any equation due to the unknown movements in different directions.

For testing your approach it might be good enough but to use it in a thesis it will be difficult to explain the error in the method section.

nice solution, have never seen this function. Thanks

39

(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 ffmpeg.org 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 s.ms?(s.ms 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.

Reiner


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
:Final
%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:

<drive>:\<Kinoveadirectory>\AppData\Plugins\Camera\Basler
there have to be two files:
Kinovea.Camera.Basler.dll
manifest.xml

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.

44

(3 replies, posted in General)

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.