931

(6 replies, posted in General)

badger wrote:

We're looking at purchasing a new one, but have been advised there is little point shelling out for a machine with Windows 8, only to downgrade to .NET framework 3.5. It seems this may pose other issues with regards to functionality within the OS as well. The overal advice was not to go with W8 if we need to use Nf 3.5/Kinovea.

It wouldn't be a downgrade, you'd just install it side by side. http://msdn.microsoft.com/en-us/library/hh506443.aspx

I admit I don't have a Windows 8 machine to try with right now, but I don't quite understand the advice given by the vendor…

932

(6 replies, posted in General)

I'll build a version targetting .NET 4.0 and run some checks and publish it if it's fine. I'd prefer to do this for the experimental version only though (0.8.20, not 0.8.15).
(If I didn't get back with news by sunday please bump this thread).

Bonjour,

Je pense que cela fera l'objet d'une fonctionnalité dédiée dans le futur.

Il doit cependant être possible de faire le graphe de points dès maintenant, avec quelques limitations:

1. Placer la grille, la calibrer par clic droit > « Calibrer » + entrer les dimensions de la table.
2. Positionner un premier « marqueur en croix » sur un point d'impact, et activer l'affichage des coordonnées par clic droit > « Afficher les coordonnées ». Ce point est important car seuls les marqueurs avec coordonnées visibles sont exportés dans les sorties tableur (pas très intuitif j'en conviens…).
3. Positionner les autres points d'impacts avec de nouveaux marqueurs en croix. Ils devraient automatiquement avoir leurs coordonnées visibles.
4. Une fois fini, faire Fichier > Export tableur et exporter.
5. Ouvrir le fichier correspondant dans le tableur. Normalement on a une section pour les coordonnées des points.
6. Créer un diagramme sur les colonnes X,Y, de type nuage de points (nommé « XY (dispersion) » dans LibreOffice par exemple).

Il faudrait ensuite améliorer les axes du graphiques, pour retrouver la forme et la taille de la table.

Important : le point d'origine des coordonnées est par défaut le coin en haut à gauche quand on pose la grille, et les coordonnées progressent vers la droite et le bas. Le nuage de points sera donc inversé de haut en bas.

J'ai réalisé un petit test en quelques minutes sur un échange de tennis:
http://www.kinovea.org/screencaps/0.8.x/tennis-impacts.png

En dehors des proportions on voit aussi que l'axe des X s'arrête à 9 alors que le terrain fait en fait 10,97m. Voir dans les options du graphique comment organiser tout ça. (Si ça se trouve il est même possible d'avoir une image du terrain en fond).

N'hésitez pas si vous avez des remarques ou des questions !

Merci pour la vidéo c'est très intéressant.
Oui je pense qu'une fonction pour exporter les dessins et tracking « vu de haut » serait très intéressante, et pas forcément compliqué à faire maintenant… (À condition que la caméra reste fixe durant toute la séquence dans un premier temps).

Has anyone tried this yet ?

I just stumbled upon this guide on how to use Photoshop in Ubuntu. It mentions tricks to make it look like it's a native application.

936

(2 replies, posted in Cameras and hardware)

The sensor glove is very interesting!
My know-how in electronics is close to zero a the moment but hooking an accelerometer to a small Arduino board has been done. Many applications. And accelerometers are probably quite cheap since they are manufactured by the millions for smartphones. This could probably be used to measure rotation speed of the arm or racket/bat, something impossible to do on 2D video.

I hadn't even thought about capturing EMG data. I can't comment on the science of muscle shortenning as my biomechanical courses are too far away and I have filled my memory with other stuff…

937

(8 replies, posted in Français)

Après réflexion une appli dédiée pour smartphone serait beaucoup plus puissante pour faire office de télécommande.

938

(2 replies, posted in Cameras and hardware)

Hi gang,

With the advent of the Arduino boards, the Raspberry Pi, tiny computers, open hardware, super small Wi-Fi chips, cheap CMOS, other sensors, 3D printing… We are probably going to see many interesting hobbyist projects in the coming years.

Things could be done in the area of capturing data for sport analysis… Video or otherwise.
Streaming over WiFi, high speed raw capture, maybe shutter speed control, interfaces to force plates, wearable sensors sending data in real time… Whatever.

Ideas ? Projects in the works ? Web sites to follow ?

939

(7 replies, posted in Bug reports)

Can you get the logs on a 0.8.20 install ? The first line should state the version number and the log itself should be much more verbose.
Does it crash with tool tracking too ?
Thanks.

940

(7 replies, posted in Bug reports)

This log reports version 0.8.15 but the original dump you posted was for 0.8.20… Do you happen to have the two versions installed side by side ? Does the issue happen with both ?
In 0.8.20 the log should be much more verbose because it's an "experimental" version and the logs are set to "debug" level.

941

(7 replies, posted in Bug reports)

Thanks for the report and sorry for the issue.
Right after this happens can you get the application log (see point 3 here) and attach it to this bug report please.

Do you get the same crash when tracking a tool ? Add an angle for example and right-click > Track.
Thanks.

942

(1 replies, posted in Bug reports)

In the spreadsheet it is the x,y coordinates of each point.
In recent versions, these coordinates are relative to the origin of the coordinate system, as set up from Image > Coordinate system (or set up from a perspective grid system if using 0.8.20).

When using the "Distance" measurement label from the path configuration dialog, the label shows the total distance covered by the path up to the current point.

So the two functions are not meant to display the same values. In a way the data exported in the spreadsheet is lower level. You could recompute the total distance from the coordinates if needed.
Similarly, speed is not exported in the spreadsheet, but could be recomputed from the x,y,t coordinates.

Hope that helps.

943

(0 replies, posted in Français)

Version expérimentale, merci de remonter toutes les regressions éventuelles !

Installeur: lien enlevé. Voir 0.8.21

Le topic annonce sur le forum anglais.

944

(6 replies, posted in General)

The next experimental version(s) should be dedicated to updating/upgrading the capture features.

945

(6 replies, posted in General)

Experimental version feedback needed ! wink
Beware of regressions and report anything suspicious. Do not assume the issue is known.

Installer: link removed. Check 0.8.21

Plane calibration.
The most important addition in this version is the ability to use the perspective grid as a coordinate system.
(To get to the perspective grid you need to do a long click on the regular grid button).

Once the grid corners are in place, right click the grid and choose "Calibrate". This will get you to a dialog where you can specify the actual physical dimensions of the grid.
The grid must map a rectangle on a physical plane (ground, wall, etc.)

Once this calibration is in place, every measure will be in the context of this plane. (distances, angles, speeds.)

http://www.kinovea.org/screencaps/0.8.x/Plane-calibration-th.png

As a bonus, the grid is now also trackable, and the ability to change the number of divisions is back in the configuration dialog.

Plus
- The Russian locale has been integrated, thanks to Andrey Pomerantsev.
- The other minor tweaks and fixes can be found in the raw changelog.