Search options (Page 11 of 131)

Ah OK, ce doit être une de ces vidéos avec des pixels rectangulaires au lieu de carrés.

C'est ça qui dit aux lecteurs que la vidéo dont les images sont stockées en 480x480 doit en fait être dessinée comme 480x640. (480/0.75 = 640)

ll doit y avoir un bug quelque part de mon côté qui fait qu'à l'export ce ratio d'aspect est à nouveau ré-appliqué: 640/0.75 = 853. Probablement la vidéo est exportée en 480x640 avec la valeur d'aspect qui est restée à 0.75 au lieu d'être remise à 1.0.

You can't disable it at the moment. It should never get down to 0% though. The player is constantly monitoring how long it takes to display the video and drops frames when it can't keep up, and this is triggered when too many frames are dropped. I'll consider adding a different option where it just keeps dropping the frames so instead of a slow down you will see jump cuts.

Can you tell more about the resolution and frame rate of the video?

It is not a known issue. I will try to reproduce it. What version are you using?

Hopefully someone with more hands on experience can come along.

A smartphone setup is different. To capture high speed footage with a smartphone you must use the smartphone itself for capture. When the smartphone does high speed it records to its onboard memory and then transfer it to its own storage. Then you have to transfer from that storage to a file on your PC. If you can somehow have access to the phone storage from the PC then it can be a time effective option. Capturing a smartphone camera feed from Kinovea capture module is not going to deliver the same performance as machine vision cameras.

Maybe someone else has a different take on this but in my opinion rolling shutter in human activities is mainly a concern for the objects we use, implements, balls, etc. because they can move much faster than the human body itself. Body segment movement under the athlete own force isn't very fast in the grand scheme of things. This is also true for frame rate in my opinion, you don't really get more information from a 2000 fps than a 1000 fps one when looking at body segments, we can't produce the kind of acceleration that would make a difference. (Not true for the objects we throw or the tip of things we hold though). Rolling shutter is directional, if you know the maximum extent of motion expected you can orient the camera to minimize it.

It's mostly machine vision cameras that are specified like this, they give the frame rate for the max resolution of the sensor but if you lower the number of lines it can actually go faster. When you do this the frame rate slider in the camera settings in Kinovea should have a wider range. For some camera types you have to click a button to refresh the slider range.

Salut,
Le code qui implémente ça est ici: Butterworth.cs

Et le truc qui appelle cette classe est ici: FilteredTrajectory.cs#L134

En espérant que ça aide

If you want to record yourself while you are doing the analysis, it is not possible within Kinovea, you will have to use an external screen casting software like OBS and record the window.