Interesting… The timestamp part might be covered by the existing naming scheme feature. Have you tried that ? From the capture tab in the main preferences you can have the snapshots named automatically with a timestamp. If it needs to have more precision it would probably be simple to integrate.

Then the second part would be to collect the list of files/timestamps in a text log, csv or spreadsheet file.
This could be done entirely in an external program I guess, monitoring the output directory and collecting info on the fly. Or it could be added as an internal feature, but it sort of feel a bit specific…

Another way that might be interesting would be to be able to define an external command to be executed after each snapshot is saved. That would leave the possibilities open and allow for many other uses. The external program would be fed the file name, time stamp and other variables as parameters.

It's more advanced on the user side and would need a bit of programming to get it working but we can probably create scripts for common scenarios as the requests come.

Indeed this thread is initially about instrumenting playback with actions. I moved your message here.

Giving this its own topic.

Alexander wrote:

I am not quite sure if this idea fits in here, but I would very much like to "time stamp" and save images from a streaming video.
Example: I am streaming a finish line of a crosscountry race. When competitors cross the line, I click and save an image with a running clock timestamp. All the timestamps are recorded in a file and can be opened later with Excel/OpenOffice etc. to match with corresponding images.
In this way I have a backup and documentation of the runners.

964

(1 replies, posted in Bug reports)

Indeed the high speed camera setting has no effect on playback speed, it just changes the time base used to compute time values.

The resulting maximum reacheable framerate will depend on the bandwidth of the video (size of images and frames per second) and on the encoding format. The encoding has a great impact on the decoding time. If decoding + display cannot be done in less than the frame interval, frames are skipped. If this repeats constantly, the speed slider is automatically brought down.

In recent versions, the decoder tries to use the display size so that the image can be rendered without interpolation as fast as possible. Try to decrease the size of the image with the corner handles to see if it mitigates the problem.

Welcome smile

Yes, you're correct. You can only save the piece of video that you created, not the process of creation itself.
That would be an interesting one though, but you can also do that with a screen grabbing application like camstudio.

Grouping would be definitely interesting. It'd also be interesting in the context of creating a custom tool out of existing ones. However at the moment it's still not planned for short term.
One question will be: how do you know if the user is dragging the mouse to create a selection or just trying to move the image around.

Regarding pencil tool, merging the pieces of the drawing would be easier to implement as a short term mitigation of the problem.

Regarding temporarily hiding a drawing or a group of drawings, how would you "unhide" it ?

@wumastah: Apparently there was an issue related to TV Capture cards recently fixed in the AForge library (that Kinovea uses to support DirectShow cameras). I'll try to integrate this for the next version.

@SteelAl: if you use the experimental version, try to get the log and send it by mail.
I do most of DirectShow testing with a Sony DCR-HC47 so it should definitely work.

968

(23 replies, posted in General)

The way it works for now is that each time you manually moves a point, it will reset the series of saved positions for this point. From that moment, it will start tracking the new point.

969

(23 replies, posted in General)

niklas.quetri wrote:

i can't find it.....if you time and will can you please take a look at you computer and tell me? thanks

Hi,
First of all, you need the experimental version if it's not the case already.
Then check this topic : Experimental version - 0.8.18 for a visual description of the new toolbar.

You make a very good point about the pencil tool. At the moment there is no secret function to fix the problem.

Holding down a key would be a solution but I'm not sure if it would be very convenient while drawing.

Another idea would be to automatically group the new pieces of the drawing with the existing pencil pieces of the same color on that image. So until you change color, or change key image, the pencil would be adding to the existing group. On a given image, all pencil pieces of a given color would actually be a single drawing.

Or be in this additive mode only until you switch to another tool. This would allow to have several groups of the same color.

971

(6 replies, posted in General)

I just posted a more in depth article about measuring angles on the perspective grid.

jankoc wrote:

However, loading the kva-file is very slow when I have 10 minutes of video with one information point every second (which gives 600 keyframes). Loading the video now takes several minutes (during which Kinovea hangs). So I guess there is a need for a more dedicated function.

Thanks for the sample files, it is helpful.
The slowdown/freeze is coming from the fact that upon loading the kva, the file is seeked to create the key images thumbnails on the fly. It will inevitably slow down the loading. Worse, on some formats seeking itself is problematic and can take even more time for each seek.
The final feature shouldn't necessarily create key images, just overaly the data in real time.

When using the perspective grid, it would also be interesting to be able to treat KVA files themselves as input for an overlay, to provide the view of data as seen from above.

Don't really have time to dive into this right now, but it solves several recurring needs so it's definitely climbing the todo list.

973

(2 replies, posted in Bug reports)

Currently there is no workaround for this issue. Besides, I don't really know how it should be adressed. Maybe one day if we have finer settings for persistence that would allow specifying named key images as cue points.

Hi,
Thanks for working on this.
Could you send me some sample files so I can later look where the slowing down is coming from ? If you send the .kva I guess I can load it on my own 10min video and see what happens. Having the gpx would be interesting too.

There is certainly a lot of interesting things to do in this area. Overlaying raw data, graphs, cloud of points, or maybe even maps would be super cool.

The spec for .KVA files can be found in the source under Tools/XML/Schema. (online here).
I admit it wasn't really thought out to scale to 500+ key images…

You can also disable fading entirely, the drawing should only be visible on the exact key image it is attached to.
<InfosFading>
            <Enabled>false</Enabled>

djpronk wrote:

BTW I think your mailbox is full...

Should be fixed now !