Search options (Page 76 of 133)

Great! Thanks for the investigation.

@edwin, It seems you are referring to two different concepts.
Going from 25 to 50 fps is generally done in the context of deinterlacing. Many videos are actually 50 fields per second, a field being a half image with only the odd or the even lines. There are several ways to rebuild a full image from the two fields. Kinovea use a somewhat basic technique that for this example would yield 25 full frames per second. Some other software may use reconstruction algorithms that gives 50 full frames. This can be advertised as slow motion, but it can only works on video that are interlaced to begin with and only to x2.

The link you gave, is a much much more advanced technology. As far as I know, only two products can do that, both commercial: MotionPerfect from GooderVideo/DynaPel and Re:Vision Twixtor family of plugins (for Premiere, After Effects and the like).

The alternative is to use a camera capable of high speed shooting. For very fast motion you'll want as many frames in the source as possible. As HDAV points, frames reconstructed by algorithms will never be as good as frames actually captured by the device.
For fast motion, if you can control the capture process I would definitely consider a camera capable of shooting at +100fps (Don't need 1 trillion fps ). Software reconstruction would only be interesting for video got from external sources.

It could be. The speed slider is decreasing by itself when the time to decode and display an image is constantly higher than the time interval between frames. In this case we can't possibly keep up the rate, the automatic decrease is to avoid freezing up the computer.

Ha! This.
I think I know where it's coming from. I had made some experiment to make the controls render faster, especially when changing the main window size, to improve the experience when going in or out of full screen mode. (Otherwise you can see each control outline before it's actually rendered, not very nice). After more use, I also noticed that there seems to be a conflict between this modification and the splitter control, especially the one between the list of files and the playback screen. It doesn't happen everytime, but when it does it's horrible.

When this flickering happen (and consumes 100% CPU), try to nudge the splitter left or right to expand or reduce the file explorer panel. In my experience this cause things to fall in place.
I have removed that modification for future versions.

There is some technical/developer documentation I wrote a few weeks ago:
http://www.kinovea.org/wiki/doku.php/trackingalgorithm

Thanks for the feedback.
What is meant with recorded video not smooth ? Video recorded from the capture screen then played back ? Can you determine if the issue seems to be in the recording step or in the playing step ?

It is not currently possible.
It may become the default in a future version though, as it seems more practical for data post processing.