You are not logged in. Please login or register.
Kinovea - Forums → Posts by joan
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.
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…
Ah you want to do this at recording time, sorry I didn't quite catch that part.
What about the magnifier? You can also track it.
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".
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.
It's currently not possible. I'll move this to Ideas & requests to keep track of it.
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.
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.
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.
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?
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.
Hi, thanks for the follow up and the details.
Regarding the menu, you may be using an older version or there is a problem. The context menu is generic and should look like this:
You can also change the camera icon from there to identify it better.
Hello there, Im using the latest version of Kinovea, Im working on finding angles however after saving annotations as .kva file, it always gives me this error whenever I open the file ''Failure: unable to open file: file not found or empty''
Sorry, the error message is not very helpful. I think what's happening is you are trying to open the KVA file as a if it were a video. The KVA file only contains the annotations. Open the original video normally and load the KVA file into it using File > Load annotations… If you have saved the KVA file next to the original video and with the same file name, it will load it automatically.
They work fine w/ Kinovea, I just wish the camera list distinguished them.
Right click the camera then "Rename" menu and set the "Alias". Does this work?
Kinovea - Forums → Posts by joan