1,216

(6 replies, posted in General)

This thread is now closed.
Thank you very much to all involved !

big_smile

1,217

(20 replies, posted in General)

- markers = stuff to stick or attach to the person to improve automatic tracking.
- feature window = the smaller rectangle around the point during tracking. This is the actual patch of the image that is looked for in the next frame.
- search window = the large rectangle during tracking, this is the area where the smaller "feature" window will be looked for.

Tracking tennis/baseball balls is most probably out of reach without super high speed camera (can do it manually if needed). But tracking a joint is definitely doable, although it may need some manual adjustments. Using physical markers might lessen or even remove the need for manual adjustement.

Using ping pong balls might be a good idea smile Cheap, round, and come in various colors. But how to attach them ?
Or maybe using balls from these beach racket games with scratch material (or is it called "velcro" I don't know the English term))

1,218

(20 replies, posted in General)

I was asked by mail about markers and the tracking algorithm.

The automatic tracking in Kinovea works by computing the cross correlation coefficient between a candidate window and the feature window of the previous image.
For each possible position in the search window, we get a score, and the best score is the match (unless it is under a specific threshold in which case we assume the target was lost).

So it is a measure of how much the candidate look like the original.
- Contrasting area will make the matching easier. (marker should have a different brightness than its background. Bright on bright is not so good.)
- It is not invariant to rotation, so if rotating the marker changes its look, it will be harder to match. (triangle, rectangle, square: not so good)
- It will look in the immediate surroundings, so having a target that does not resemble any other part of its vicinity is better to avoid mismatches. (background and other parts on the person should be clear of anything that look like the marker).

To sum it up (based on the theory, I haven't done extensive testing in real conditions yet)
- Circular marker.
- Marker that takes about half the feature window.
- A color and brightness contrast with background that is not present in the rest of the search window.

Please post your findings, experiments, which markers work best, etc.
Anyone to do a video showing how various markers perform ?

1,219

(5 replies, posted in Français)

gilles wrote:

Pour finir j'ai la confirmation que le boîtier Intensity Shuttle ne fonctionne pas avec les Express Card USB 3.0. Il faut de l'USB 3.0 en "natif" sur le portable.

Merci pour l'info, c'est bon à savoir !

1,220

(2 replies, posted in Français)

Effectivement la vitesse affichée est la vitesse du segment de trajectoire précédent.

Pour faciliter le calcul de la vitesse moyenne, vous pouvez peut-être utiliser un outil chronomètre synchronisé avec la trajectoire, et configurer la trajectoire sur « distance » au lieu de « vitesse ».
« Distance » va correspondre à la distance totale jusqu'au point concerné, donc si le chrono est démarré au même moment que la trajectoire, il suffit de diviser par le temps pour avoir la vitesse moyenne.

1,221

(6 replies, posted in General)

Thomas wrote:

Hello
I have done 94% in swedish.
Its only the hard ones left, don´t have any good translations of someones.

Fantastic ! big_smile
Please send it by mail (joan at kinovea dot org) so I can integrate the strings, add the menu, update installer, etc.

I don't know if Alexander had started something already for Swedish ?

By the way, for anyone reading this and secretely working on a translation, the ultimate deadline is next friday (May 13th). The official release should be on May 15th or 16th.
After that you can of course still send your translations, but they will be integrated in a later version.
Thanks

Hi,
Thanks for raising these points.

Winkelmandje wrote:

What I'm trying to accomplish is that a video captured at 120fps is synchronized with another video captured at 30 fps.

Hmm, so you have one video in slow motion and the other in regular speed, right ?
Synching videos with different playback frame rate is supported and should be transparent, but I guess your 120fps video is actually played back at 30fps as well.

I wanted to ask you to set the speed sliders at the same value (20% for both for example) but they have been locked together for ease of use in the most common scenario !
(Maybe a future enhancement to think about. Something like ALT + speed change could be specific to the screen it's applied to and not to both screens).

Nevertheless, I will open a bug for this, and think about possible ways to fix this internally. It will most certainly not make it to the next release though (only few days away, and risky change).
Maybe the "normal speed" video should be locked to the slow motion factor corresponding to the other…

Winkelmandje wrote:

When Kinovea is not running and I'm using right mouse click on a file and selecting "open with" > Kinovea, this works just fine.
But when Kinovea is running this option doesn't seem to work. I only see a loading icon for a few seconds and then nothing happens, Kinovea doesn't open the file.

Yes, I have noted this a few days ago. Explorer is probably trying to launch a second instance of Kinovea, which then detects that it is already running and aborts.

edit:
bug 245 - Synchronisation between a high speed clip and a normal one cannot be done
bug 246 - Windows Explorer "Open with" doesn't work if Kinovea is already open

1,223

(6 replies, posted in General)

Well, it is in the pool of new features that will be scheduled for integration during the next series of experimental versions.

1,224

(1 replies, posted in General)

Angle tracking is not currently supported.

Calling for English native speakers big_smile

Currently in the process of updating the help manual for the next release, we could use some proofreading for the new topics !
This is mostly for grammar and spelling, but also anything you want to comment on (it's a first shoot, so general feedback is also much welcome).
Even the smallest typo fix helps !

If you have some time and want to help, the new topics are the following:

Observational References
126 - http://www.kinovea.org/wiki/doku.php/help_en:126

Capture
128 - http://www.kinovea.org/wiki/doku.php/help_en:128
129 - http://www.kinovea.org/wiki/doku.php/help_en:129
130 - http://www.kinovea.org/wiki/doku.php/help_en:130
131 - http://www.kinovea.org/wiki/doku.php/help_en:131

Dual Export
132 - http://www.kinovea.org/wiki/doku.php/help_en:132

You can edit the wiki anonymously or create an account (sorry there's no site wide account management yet…).
Don't be afraid, history of versions is kept so you can't break anything tongue

Thanks !

1,226

(3 replies, posted in Bug reports)

It is probably a version of bug 165 or bug 184. Some files produced by Windows Movie Maker wrongly state they are 1000fps and this was causing problems as we use these informations to set up duration, seeking, etc.

This should be fixed in later versions I think. I'm really interested in knowing if you still have the bug in 0.8.14.

You need to close the running instance of Kinovea before installing the new one, maybe that was the origin of the error message ?

1,227

(4 replies, posted in Français)

Il y a eu plusieurs retours similaires et je pense avoir trouvé l'origine du problème dans la gestion de la reconnexion automatique.
Le gestionnaire de reconnexion automatique à été modifié dans ce sens:
- Désormais le mécanisme de reconnexion ne s'active pas tant qu'on a pas reçu les premières images de la caméra,
- La reconnexion se fera en priorité sur la même caméra, au lieu de basculer vers la première de la liste comme auparavant.

Cela devrait corriger le souci.

I think with the recent changes (not released yet) you should be able to use every camera in turn without problem, even if they are all plugged in.

The problem I have is when I try to open two capture screens and try to simultaneously get 1. the screen camera and 2. the PS3Eye or the other USB webcam. In that case the second camera (PS3Eye or simple USB) stays black for some reason. If I combine the internal webcam with a DV camcorder it works with no issue.

After some more tries, it seems that it is an issue of USB. When I switch USB ports I have different results hmm
(As it's a desktop PC, my screen webcam is plugged to the PC through yet another USB cable)

To me this seem to be fairly specific to the internal webcam hardware/connectivity, so you may or may not experience the same issues…

1,229

(3 replies, posted in Bug reports)

Hi,

- Are you using version 0.8.7 or 0.8.14 ?
- If you are using version 0.8.7 please download the 0.8.14 experimental version and try with it, as the decoding library was updated.
- If it still doesn't work, please send a small sample file (joan at kinovea dot org)
(or create a bug report and attach it there).

Thanks

1,230

(2 replies, posted in General)

JVC Everio GZ-X900
- Records AVCHD,
- To flash memory card.

damien wrote:

Can i live stream it to my laptop ?

Not directly. These camcorders cannot live stream to PC through the USB cable given… I don't think it has a "webcam mode".
You would need to use the HDMI output port and connect to an HDMI capture card in the PC. (However, note that there seems to be anissue with recording in this configuration, which we are working on).


About the playback problems:
Unfortunately, some of the AVCHD files are not well supported in Kinovea, and expose the issues you mention. It's a combination of performance during decoding and display and scrambling during decoding. (The timecodes are somewhat scrambled but the images should be in the right order though)

Currently there is no satisfying solution to the problem.
If possible you can convert the files to another format in AviDemux or Handbrake. This would get rid of the problem entirely.
Also, you can shorten the working zone to trigger the extraction of frames to memory (see settings for "Switch to analysis mode" in Preferences > Playback). This should mitigate the issue.