Search options (Page 70 of 135)

Hi,
First the speed sliders. They are locked together until you change the settings in Preferences > Playback > General > Link speed sliders.

In general you shouldn't have to change this option. The preferred way is to adjust the high speed video settings (Motion > High speed camera) of the slow motion GIF.

In your case it's a bit special because the animated GIF was probably not shot with a high speed camera but rather slowed down programmatically at creation.

You can still fiddle with the high speed camera settings until the info in the bottom part of the dialog "Video is x times slower than original" matches the slow motion factor of the GIF, if you know it.

All this is not strictly necessary, but it's the more correct approach I think. It will display proper times and let you use stopwatches on the slowed down GIF for example. And the normal speed video will be automatically slowed down to match the GIF speed. And you will be able to use the speed sliders.

About the common frame navigator.
There are two different mechanisms, the common play button works by calling play and pause on the individual videos at the right time, to honor synchronization (based on speed settings of each video).

However, the common frame navigator, next button, previous button, etc. and the saving process, all work at the frame level, which causes the problem I think you're having.

Although I used to consider this an unfortunate limitation, I now think it's a bug induced by not using the right approach.

----

Thought a bit about it last night. The following might not make sense without the code, I'm writing it down to remember it

I think it is possible to express synchronization in terms of scaling and translating of two 1-D variables (the videos).
The scaling will map the fps from one video to the other (taking any slo-mo in account), and the translating will express the shift due to the synchronization point.

With this I think we can start with any time coordinate in the first video and find the corresponding time coordinate in the second video.
b = (a-t) * s.
b: time in second video.
a: time in first video.
t: translation = position of sync point in first video.
s: scaling = (fps of second video / fps of first video). (actual playing fps, not necessarily original fps of video).

Hopefully this will someday allow proper frame level synchronization.

I have created a page with interactive documentation for the constraints and impacts.
This subproject is helping build the groundwork for an online viewer/repository of custom tools.

-> Custom tools reference

Most of the custom tools engine is ported. I think in the current state it can render all existing tools except the "Posture" one.

It works for me under Firefox and IE9. It seems that the mini demos are broken under Chrome, and the table of content jumplist isn't working under IE7 and IE8. Browser compatibility is such a pain…

If there are bugs, stuff unclear or other problems, don't hesitate to report.

Effectivement, ça ce n'est pas possible dans l'état actuel des choses. Le suivi des outils fonctionne un peu en mode « tout ou rien » sur l'ensemble de la zone de travail…

Hmm, thanks for the report. I admit I hadn't considered the case where the only camera is a network camera. This will need to be fixed.

I meant that the problem is in Kinovea. The menu is created from names of files found in the folder, using a simple alphabetic sort, which causes this kind of issue. I have recently integrated the more natural sorting algorithm in the main file explorer. It will have to be used there as well.
(If you want to have a look, the problem is in ScreenManager/PlayerScreen/Drawings/GenericPosture/GenericPostureManager.cs, line 71. And an example correct sort in FileBrowser/UserInterface/FileBrowserUserInterface.cs, line 440. The idea would be to first get the list of files from Directory.GetFiles in a variable, then sort it properly before looping on it in the foreach.)

It could also be considered as small plug-ins. I quite like the extension mechanism in Firefox, Wordpress and others where you can browse the available extensions from within the software itself and install them with a few clicks, all without quiting the software. With some added logic, the new tools could even be loaded and added dynamically without restarting.

Hi,
Here is the tutorial : http://www.kinovea.org/en/tutorial-crea … stom-tool/

I realize that what is needed now is a reference doc on the available impacts and constraints. (They can be found by looking at the existing tools or in the sources).