Search options (Page 64 of 133)

Hi,
Great points.

Have you tried the delay slider ? If you don't care about saving each swing it may be enough.

Ideas about capture-replay scenarios have been floating around.
My fear is that a function only available through a keyboard shortcut will be virtually non-existant to 90% of users.

Barring a unique "most popular" replay scenario, what would be needed is to turn this into a mini macro "language" so you can create a macro command by picking actions like "close capture screen", "open playback screen", "launch last captured file", "close playback screen", "open capture on last used camera", etc.
Obviously this is a different beast altogether, if only to make sure the list of commands is coherent.

Implementing trigger by microphone level would be feasible.
Combined with the delay feature and a new function to specify a preset duration for recording, it could be used to record the full swing by hearing when the ball is hit, without touching the computer…

Le besoin existe car les distorsions de la caméra posent des problèmes pour la précision des mesures et donc impactent toutes les fonctions d'analyse quantitative…
Avec la GoPro3 qui filme en 720p à 120fps ça vaudrait le coup de pouvoir rectifier les images.

Un peu sur le même principe, un stabilisateur de vidéos filmées sans trépied est également possible (en tout cas pour les vidéos sans pan ni zoom). Même topo : la fonction peut être implémentée sans trop de difficultés sur une suite d'images données mais pour faire du temps réel c'est plus compliqué.

I concur on what Chas said regarding zoom and shutter speed if your camera support changing these parameters. If you are using a webcam or similar device, place it so that what you want to see fills most of the image.

If you plan on making measurements, another important aspect is the calibration of the space. To make accurate measurements you should either make sure the camera is perfectly perpendicular to the plane on which you make all your measurements, or use the perspective grid to map a physical rectangle and make the measurements on that plane.

I'll try to do a more in depth post to compare the errors that can be expected from both calibration methods.

Yes. The point tool (cross marker) is now using the same tracking system as the other tools. To get back the trajectory tool you need to directly right click the object you want to track and choose "Track path". Do not add the cross marker.

Great !

The sad thing is that there actually was a similar feature in the ancestor of Kinovea back in 2005 (screencap from the help files). You could interactively add/remove positions to the composite.

In all those years I never got around to reimplementing it (Massive limitation : it worked only for perfectly fixed camera views. I want it to work even when there is camera motion, but it's much more involved).

Particularly interesting in the first images you posted is that the composition is selective. You see all the ball's positions, but only a few of the racket's ones. This makes for a much clearer image if all you want to see is the ball trajectory.

Hi,
I just tried and yes, you're right :-)

You need to set the .Owner property of the form to be the main Kinovea form for it to work properly.
If your menu handler is inside Kernel.cs, you can simply do this:

form.Owner = MainWindow;

If it's outside, in another module or elsewhere, you can call a similar function through this :

using Kinovea.Services;

Form form = new Form ();
DelegatesPool dp = DelegatesPool.Instance();
if (dp.MakeTopMost != null)
    dp.MakeTopMost(form);
form.Show();