Search options (Page 27 of 135)

For this application I think it's paramount that the board be vertically aligned perfectly with the edges of the image, pixel wise. Otherwise if it's not filmed straight down it could be misleading and impossible to really say whether the shoe actually crossed the board before take off or not. I want to add more options to the "Camera test grid" object for this kind of scenarios. Maybe a simple vertical line for starters.

Hmm, yeah there are a few places where one millisecond is used as a time base, I guess this is one of them. It will break for this kind of framerate. I'll see to fix this.

You can have the two instances of Kinovea running at the same time so you would see the two capture and the two players simultaneously. I don't know if this was clear from what I wrote.

Yeah I followed this change, I find it a bit weird to be honest.
Is this change being implemented at all levels of competition?

I think it may be possible to do in Kinovea but probably there is a validation process by the federations.
Do we know what hardware and specs is used in the existing systems? I imagine this must be documented so federations and systems providers can comply.

There is also an undocumented "finish line" feature in the program that could help. It triggers for some machine vision cameras when configured for very few lines. This mode records the lines at high frequency and stack them to create "photo-finish" images and videos.

Hi,
You can start a second instance of Kinovea and have one or two players there.
With the help of replay folder observers you can have these players automatically load the captured videos as they are created. For the case of two capture/two playback you will need to set each capture to save in its own folder, so the corresponding player can monitor that folder without loading the videos from the other.
Let me know if this matches what you were trying to do.

Hola, quieres decir iPad?
No sé pero mejor escribe en el foro en español en un nuevo hilo.

Hi,
Thanks for reporting about this.

The distortion model is the one from OpenCV.
http://docs.opencv.org/doc/tutorials/ca … ation.html

Kinovea solves for the three coefficients k1, k2, k3 (radial distortion). And the others (p1, p2, tangential distortion, and fx, fy, cx, cy intrinsic parameters).

When you run the calibration the coefficients found will be written in the log and should be available in the camera calibration dialog.

I imagine there are two places where this process could fail, either in the initial calibration, or when applying it.

You may be right that only one view is sufficient. I think the idea with multiple views was to have data in all parts of the image, as if you have only one view there might be corners with no data if the pattern filmed is at an angle. I'm not sure why it would fail with multiple views though, it worked in the past. I'll have to retry it.

It should also be possible to automatically find the corners in the image and avoid the whole process of manually placing them.

You can also tweak the coefficients manually to find a good fit. In this case usually only k1 and k2 are used.