361 Reply by joan

(5 replies, posted in General)

Just to confirm, there is currently no image stabilization in Kinovea.

If it's for measurement purposes what you can do is track the origin of the coordinate system, this way the other points and lines will be measured with regards to that moving origin.

I made several experiments with regards to stabilization and moving shots over the years and to be honest it's mainly an issue of user interface and integration. I'm not really sure how to "present" this functionality in a well integrated way because it's modifying the video frames themselves and possibly the canvas size necessary to show them. Similarly you will note that there is lens distortion correction but the way it works is that it distorts the coordinate system instead of undistorting the images.

It does feel like a pre-processing step to everything else done in Kinovea and for now it has to be done in a separate app prior to loading.

Go to forum: General

362 Reply by joan

(4 replies, posted in Cameras and hardware)

Yes, please host it somewhere on a google drive or onedrive or similar and send me the link at joan at kinovea dot org.
Thanks.

Go to forum: Cameras and hardware

363 Reply by joan

(2 replies, posted in Cameras and hardware)

Based on the code it should already do 60fps based on the passed value of `iPosition`, which I would assume is just the index in the list of available media types. Can you see the list of stream formats and resolutions in the camera configuration dialog inside Kinovea?

Go to forum: Cameras and hardware

364 Reply by joan

(15 replies, posted in Ideas and feature requests)

Side by side should work but it does feel wasteful that one of the sides is going to be a static image when a simple insert onto the main video would suffice.

My main concern with automating it and the delay is the risk of mixing the wrong bib with the wrong takeoff video, this would be catastrophic.

Go to forum: Ideas and feature requests

365 Reply by joan

(15 replies, posted in Ideas and feature requests)

When using several cameras there are many things that can impact perfs. USB bandwidth, USB power, SSD write speed…

Even if the bib thing itself is a bit niche the general idea of creating picture-in-picture objects from live cameras is interesting. This could be used to provide wider context to a zoomed-in camera, or highlight something from a different angle…

Go to forum: Ideas and feature requests

366 Reply by joan

(15 replies, posted in Ideas and feature requests)

Ah you want to do this at recording time, sorry I didn't quite catch that part.

Go to forum: Ideas and feature requests

367 Reply by joan

(5 replies, posted in Ideas and feature requests)

What about the magnifier? You can also track it.

Go to forum: Ideas and feature requests

368 Reply by joan

(15 replies, posted in Ideas and feature requests)

If it's just one Bib image, and it's not really a video that needs to be properly synchronized, you can right click > Copy image to clipboard and then back in the takeoff video right click > Paste image from clipboard. This will create an image object that you can resize, put in the corner and set to always visible.

This is what replaced the "send image to the other screen".

Go to forum: Ideas and feature requests

369 Reply by joan

(15 replies, posted in Ideas and feature requests)

Hmm, the superposition function is close but not quite… But the data is already there. Maybe with an image tool but then you tell it that the "source" of the image is the synchronized image from the other screen.

Go to forum: Ideas and feature requests

370 Reply by joan

(5 replies, posted in Ideas and feature requests)

It's currently not possible. I'll move this to Ideas & requests to keep track of it.

Go to forum: Ideas and feature requests

371 Reply by joan

(11 replies, posted in Bug reports)

Yes that's correct, it is using the resolution of the images as they are displayed. (this is actually what caused the bug in this topic since that live resolution isn't guaranteed to be supported by the encoder). If I recall correctly it's because it's using the synchronization loop to get the images aligned and painted so it was probably simpler to just grab them from there instead of re-decoding at the original size. I'll make a note to fix this at some point, it's not necessarily as trivial as it sounds. There is also code for vertical stacking in there that's currently unused.

Go to forum: Bug reports

372 Reply by joan

(27 replies, posted in Bug reports)

If it happens with one specific video and not with others it's definitely not the same problem as the OP where the program fails to even start. Please upload an example video on some online storage and share the link at joan at kinovea dot org.

Go to forum: Bug reports

373 Reply by joan

(7 replies, posted in Ideas and feature requests)

Update on this topic.

I added a menu on the keyframes to "Move to current time".

Then I implemented the drag and drop into the timeline (and actually into the whole bottom part since it was not very usable when it only received the drop in the small timeline control).
 
While I was testing this I realized there was a possible issue if you drag and drop from one screen to the other, so in the end I added support for that as well. I think it's relevant to your use-case because now you can just keep the reference annotations in a dedicated video and drag the keyframes from there into the current one. I think it's a good solution to the "template" idea. The video updates itself during the dragging operation so it's relatively easy to get to the right frame. I still need to test it a lot more though.

Go to forum: Ideas and feature requests

374 Reply by joan

(9 replies, posted in Bug reports)

That is very strange.

Let's see… The same functionality exists when clicking on the "Configure" button on the capture screen once the camera is opened. In this dialog you should be able to see both the alias defined in Kinovea (in blue) and the camera internal name (in italics below). The alias is editable directly and the icon is a button. Does editing the alias from there work in your case?

Go to forum: Bug reports

375 Reply by joan

(9 replies, posted in Ideas and feature requests)

I cannot give an estimated time, there are too many other factors.

I started to look into this. One idea I had was to add a function where you right click an existing named keyframe and do "Set as preset X" or something like that. Then I realized that instead of having just the name of the keyframe we could save all the data associated with it and use *that* as a preset maybe. This way you can add a rich keyframe with some pre-made drawings in one click. There is also a feature for keyframe "color" that would fit nicely into this.

So now I'm thinking that instead of saving this as a list of names in the preferences, it might be simpler to have a "preset KVA" that is a normal annotation file but containing many presets for keyframes and drawings. I think this could simplify the logistics for the more advanced automation scenarios. In the preferences you would point to your preset file, it would analyze it and then for each shortcut/action slot you would select the thing to add based on what's in the file.

edit: scratch that, it would be too complicated to setup. I'll stick with simple name+color presets.

Go to forum: Ideas and feature requests