I will try to document my efforts to implement chronophotography and other advanced visual effects in this thread.
There is a long road before any of these makes it up in Kinovea, but an important milestone was reached this week-end so I create the thread.

The first step of almost all these effects is to compute the motion of the camera.
This is equivalent to computing how to transform each frame so it looks like as much as the previous frame as possible, and do it for all the frames in the sequence.

The transformation parameters can be combined together, so basically at this point we can map each frame on the first frame of the sequence.
We can visualize the frames boundaries and compute the total size of the background.

http://www.kinovea.org/screencaps/0.8.x/exp-jump-skeleton.jpg
Frame borders transformed and positionned against the virtual background. (high jump sequence same as below)

.
The second step is to compute an image of the panoramic background without the person moving in the foreground.
To do this we compute back all the contributing images to a given location in the final background. This gives a list of pixels each from a different frame of the video, most being of the color of background, some being the person when passing in foreground. The trick is to compute a pixel representative of the background using this group of pixels.

For this experiment, I used the median pixel of the group. It gives good results and it's easy to compute.

Here are some reconstructed backgrounds (with some pictures extracted from the corresponding videos for reference).

http://www.kinovea.org/screencaps/0.8.x/exp-jump800.jpg
High jump sequence. Distorsion accumulates on the left.

http://www.kinovea.org/screencaps/0.8.x/exp-fixie800.jpg
Fixed-gear bicycle sequence.

.
To be continued…
big_smile

This should be fixed in the next release.

Hi,
It's sounds like an interesting use case (and challenging smile)  However I thinks it's important to make sure the capture screen is robust enough and well functioning in its current implementation before attempting other sources.
(Maybe check LongoMatch software, he just added capture too during the summer. He is using a somewhat more versatile library for capture, maybe it already does network sources… And it is more tailored towards team sports too)

1,474

(8 replies, posted in General)

It's not possible yet.
Currently only the lines and angles are exported (in addition to keyframes themselves, stopwatches and path tracks).
I'll try to add the markers in a future version.

1,475

(1 replies, posted in Bug reports)

Hi,
There are two issues in the bug tracker related to issues with .NET 4.0.

If I understood correctly, the .NET 4.0 is only an incremental upgrade of the .NET framework, you can't just have it alone, it still needs the older versions to work.
And when you install the older versions, Kinovea should work properly…

Most especially if you get the message "unable to find a version of the runtime to run this application." it would mean the .NET 2.0 needs to be (re)installed.
(I'm not clear whether the .NET 3.5 can be installed alone and if it can run Kinovea on its own.)

Please report success or failure for the various combinations: .NET 3.5 alone (if possible), .NET 4.0 with older versions, others.

Thanks !

Hi,
Can you confirm that this happens only for lower slow motion values ? (Try with 15~20%, and then with 50%, does it fail in the first case only ?).

edit: created bug 221.

1,477

(6 replies, posted in Bug reports)

litch09 wrote:

Another option that might work is that if the mouse button is held down for a period and dragged out then this would allow the size of the box to be set from the outset.

Hmm, this may interfere with the manual moving of the box ? (when manually adjusting the tracked point)

1,478

(6 replies, posted in Bug reports)

litch09 wrote:

Is there a way of adjusting the bounds that tracking algorithm searches in to prevent this from happening?

Currently this is not possible without changing the source code.
The feature window is computed to be 5% of the image size and the search window is 20%. I agree that the ability to tweak this is desirable.

As often the hard part will be to introduce this possibility without disrupting the general flow of using the default values.
One way might be to have a "hot" lower right corner on the outter search window that would be draggable (maybe with a little hint as for the magnifier window).
(This would increase or decrease both the feature window and the search window though, keeping the ×4 factor between the two. I have tried software where both rectangles can be sized (i.e: Adobe After Effects), and I find it rather hard to manage…)
Or maybe it would make more sense that this dragging would only change the outter window (?)

In any cases, I'm thinking that this possibility should have to be enabled explicitely from the configuration window. This way the default behavior is untouched and the user doesn't risk changing the size of the window when he just want to move it around. (which is very annoying when it happens).

litch09 wrote:

Also, would it be possible to add a feature which calculates the angle between three points. This might be embedded in the angle tool, so that the three points which define the angle can all be tracked at once. Just a thought.

Yes that would be great. It is on the to-do list, but nothing have been done yet.

I just stumbled upon this page:
MoFrames, making movement complexity visible. (Martin Hilpoltsteiner)

If I understood correctly, he is taking the individual images of the person and put them one after the other in a 3D space, then render the view from various angles.

It gives pretty interesting results to grasp volumes used during the action !

Here is a person jumping on a trampoline.
(There are plenty more on the site)

http://www.moframes.net/pictures/moframes_trampoline_02.jpg

daww wrote:

I recieved today a casio exilim fh100 (high speed camera), I haven't been able to use the capture feature with it?
Are you aware of a way to use it? by forcing the directshow?

I don't think these cameras can do direct streaming can they ? Do they have a "webcam" mode ?

If you find a way (any way) to display on the PC screen what the camera is currently imaging, please share program/method used. (I honestly don't know if it's feasible or not).
Thanks

Yes, I agree the magnifier should better integrate with the drawing tools.

I would like to use this thread to gather ideas about what could be done in this area.
If I understand correctly, what you suggest for a start is:
- when drawing on top of the magnifier glass, the drawing should not register to the global image underneath, but should relate to the magnified area.
- the mouse cursor should change to reflect this and to give a more precise pointing tool.

CAR_UARD wrote:

I go to Set original speed and write 29,97 fps.

In this dialog, you should set the frame rate at which the video was captured.
It is common for example that a video is captured at 300fps and the resulting video file plays at 30fps. In this case, you would set "original speed" to 300, and it will say "video is 10x slower than original."

Ah, yes, I get it. This had no effect at some point and has been fixed after the version 0.8.7 was released. So you'll need to use the experimental version.
It was discussed in this thread : Ball velocity calculation with non 29.97 fps video

1,483

(4 replies, posted in Bug reports)

Hmm, I just tried again and it didn't crash this time, a lovely not systematic bug tongue
Anyway, I've added it in the bug tracker (m220).

Please try to save to MP4 or AVI first, make several tests, and report if it makes any difference, thanks.

1,484

(4 replies, posted in Bug reports)

wildrobo wrote:

It then should the correct duration and things played fine. However the back arrow key would not work.  The forward arrow would.  Any thoughts?

That happens with some encoding profiles, I'm interested in knowing more about which output options you used.

1,485

(4 replies, posted in Bug reports)

Oh, are you using the dual export, while the overlay is activated ?

Ah, yes, I got the crash too. I thought I had checked that but apparently I didn't. Thanks for the report.