You are not logged in. Please login or register.
Kinovea - Forums → Posts by joan
There is no "limb tacking" in any version, only pattern tracking. For an angle it will track the three points independently.
This should be there in 0.8.27. The sizes of the pattern window and search window are taken from the default tracking configuration set in preferences. It works much better with markers and typically it still requires some manual adjustment. The tracking performance and UX is not so good even in latest versions, I'm investigating various ideas to improve it.
Yes, this has been a problem for a long time and I want to address it.
There are two directions: 1. improving tracked drawings interface to have the same utilities as the trajectory, and 2. being able to convert multiple trajectories into a single drawing. The second one is interesting but feels much more complex in terms of logistics. The first one is important to have anyway, so I think it will start in this direction.
One of the next things I intend to do is move the drawings' configuration dialog to the new right-hand side panel and it looks like the tracking configuration for drawings and trajectories could be moved in a tab there as well.
It will probably always be necessary to correct multiple points at the same time since the tracking might fail only for one tracked point of the drawing.
Yeah I've seen this, it's interesting, but it's mainly used along with proper player tracking no?
It would be static in Kinovea because tracking for team sports requires a different approach than the currently implemented tracking algorithm and that's a big pandora's box.
For the ellipse itself, it may look simple but in order to properly hide the part of the drawing behind the legs of the player it needs to know what's the background and what's the player. At the moment the drawing tools in Kinovea don't have ways to do that. (Maybe it could be done simply with chroma-keying on the grass color, not sure)
I do want to improve the tools to highlight things though. At the very least have a simple free-hand highlighter.
Note that in the (unlikely) case that you already have the whole field calibrated with a perspective grid you could directly use the circle tool to do this. Keeping in mind that it won't properly hide the back part behind the legs of the player.
*Edit
My Chromebook runs on 32 bit... Is that a dealbreaker? (I fear it is)
The last 32-bit version is 0.8.27, you can get it in the download page.
Hi,
Do you really need a date-time format or just something numerical to do arithmetic on?
What version of Kinovea are you using? Recent versions will always export the time column in numerical format which R should be happy with (although I'm not familiar with it let me know if it really requires a date-time). If your time units inside Kinovea is set to time code or time code + frame number it will be automatically converted to seconds for spreadsheet export.
If it's on the text tool you can increase the font size. I'm assuming the 4K video is getting downsized and it hits the part of the code that prevents the labels to become very small in the user interface. So they appear larger than what they really are only in the player window. The export is at the original image size so it respects the font size from the tool configuration.
If changing the size just by one or two steps doesn't appear to make a difference it's definitely this. Increase the size from the tool configuration until you can see the text actually getting larger again, then at that point it should match the export.
Post history
2024-08-25: First release of 2024.1
2025-08-24: Updated with links to 2024.1.1
-----
Hi everyone!
Links
Kinovea-2024.1.1.exe (installer)
Kinovea-2024.1.1.zip (self contained archive)
Changelog
Here are the main changes from 2023.1 in each domain
Qualitative analysis
Camera motion estimation
Kinogram: time shifting & label font size (time shift with ALT+Mouse scroll)
Custom pointers for presentation purposes (see note under "hand tool")
Annotations
Background layer with color and opacity, sitting between the video and the drawings
Grid tool: separate number of rows and columns, option to display distance lines
Text tool: option for transparent background
Visibility: longer maximum for fading and opaque duration
Rectangle & circle: fill option
Measurement
Revamped lens calibration workflow (dedicated mode, new menus)
Calibration validation window with 3D camera position and control points
Plane calibration improvements: coordinates offset, rotating/flipping axes, decimal places
Import/Export
Export comments in JSON export
Capture
No significant updates but working on a universal GenICam plugin for machine vision cameras.
Cheers!
Soon™ :-) I'm updating the translation files for the new strings added since the last version, which is one of the last steps. New version should be out before the end of the month.
OK. I can set it down to about 545 px wide. After that there is always overlap in the controls which is undesirable.
Yes you're right it's currently a limitation of this that it works in screen space and not parallel to the coordinate system axes. I'll add this to the bug tracker to remember it.
If you want to measure the hand position or travel distance you will need to have some sort of reference length in the frame on the same plane that the hand is moving. Maybe something directly on the ukulele and setting things up so that the perspective error is minimized (because the hand will be moving on a plane slightly in front of the ukulele). You can check this page: https://www.kinovea.org/help/en/measure … lines.html
I hope this happens it would be great.
I tested one capture card today. The card is recognized and exposes MJPEG 1920x1080@60fps. Streaming from the GoPro works, HOWEVER, the resulting video is a false 60 fps, it's really 30 fps with every other frame duplicated.
I investigated a little and it looks like it's actually the GoPro that is producing this fake 60 fps stream over HDMI. Other people have had the same problem. It's not related to the capture card.
According to this video, there is a way to get a proper 60 fps output by simultaneously recording on the device. This apparently only works for GoPro 8 and newer models, mine is a GoPro 7 so I can't test this.
I haven't tried this in a while, I'll grab a couple of the new USB 3.0 ones to see if they work as expected. I have an old USB 2.0 one, it can stream the gopro at 1280x720@30fps.
Non ce n'est pas que chez vous, il y a plusieurs personnes qui ont ce problème, il y a au moins 3 fils sur le forum en Anglais et un bug rapporté sur github, mais je n'ai jamais réussi à le reproduire chez moi donc impossible à debugger. Mais ça m'intéresse beaucoup de pouvoir comprendre ce qui se passe.
Ils sont gros ces fichiers .dmp? Vous pourriez me les envoyer à joan at kinovea.org ? S'ils font plus de 5Mo au total plutôt via google drive ou un truc dans le genre car la boîte mail n'a pas beaucoup d'espace. Merci.
Kinovea - Forums → Posts by joan