Search options (Page 42 of 129)

I agree it's annoying, it has happened to me as well. However I think it's important to have a shortcut for the synchronized playback and using the same shortcut as for the single video case makes sense in my opinion.

The problem is that at the moment there is no distinction between opening two videos for synchronization or just for looking at two videos individually. We need to figure out a heuristic to distinguish these use cases. Maybe keep them independent until the user actually clicks on the synchronization button?

As far as I'm aware the only way is to send the AV or HDMI out of the camera through a capture box or card on the PC. I don't have a lot of experience with that setup so maybe someone with more experience can chime in.

I can reproduce this if I change the reference video framerate in menu Video > Configure video timing dialog. Can you confirm this what you are doing?

For high speed camera you should only change the top part in this dialog: High speed camera > Capture framerate. If you only change this it should work as expected I think.

The bottom part is for when a video has metadata indicating that its nominal framerate is some number but the actual framerate is something else, say 30fps vs 29.97 or something. It does get confusing with high speed camera though. But in your case the camera did intend to create a 30fps file as advertised (or whatever the framerate) and the playback should normally be in slow motion. Maybe these should be two different dialogs because the bottom part is for a rarer scenario, when the video file is broken.

Please retry with just putting your 120fps in capture framerate and leaving the video framerate to its original value and let us know if it works.

To diagnose recording problem you can check the infobar a the top of the capture screen. Look for the bandwidth and drops.

Make sure the camera is configured to MJPEG which should reduce the bandwidth.

Cool! I also think it's one of the most powerful feature in the program, but yeah the documentation is certainly lacking.
I will get around to at least write a page with a raw list of each node and the attributes they support.

If you haven't seen it already, here is an article discussing custom tools: http://www.kinovea.org/en/creating-a-custom-tool/

No, at the moment the text distance is hardcoded. It's a good point though, I'll add that to the backlog for the next version.

Yes. I'll recap how this works for everyone and then add more details on declaring default options.

Each object visibility (objects: segment, handle, ellipse, angle, distance, position, computed point) can be controlled by named "options". These options end up in the context menu of the drawing and can be toggled on/off by the user. Options can also control the enabling of "constraints" placed on handles, such that the handle can be freely moved or constrained based on user desire.

This is controlled by specifying optionGroup="name of option" as an attribute on the object. Multiple objects' visibility or constraints in different objects can be controlled by the same option. There can be multiple options in the drawing.

Option discovery is entirely based on the textual name so be sure to correctly copy & paste the name otherwise they will end up as two different options.

By default all options are "off". To specify default options that are "on", create a "DefaultOptions" node and add the named options under "OptionGroup" subnodes, as following:

<DefaultOptions>
    <OptionGroup>Display ankle angles</OptionGroup>
    <OptionGroup>Display hips angles</OptionGroup>
</DefaultOptions>

Options listed here that are not matched to an option declared elsewhere will be ignored.

Yes you are right. I didn't anticipate that use-case, all the other constraints are mutually exclusive I think, but rotation steps could be combined with others. This is not possible at the moment.

For that specific scenario I think you could use a "LineSlide" constraint, where a handle is only allowed to move along a line defined by two other points. The LineSlide constraint takes "point1", "point2" and "position" attribute. The "position" attribute further determines where the handle can go in relation to the two existing points, and can take the following values: BeforeSegment, BeforeAndOnSegment, OnSegment, AfterAndOnSegment, AfterSegment, Anywhere.  Check the "Archery top view" tool for an example.

So you would first make sure your have two points defining the fixed-angle line in the point list  (without necessary creating a visible segment from them). Then add a third point and a handle referencing it, with a constraint that only allows it to slide along the line defined by the other two, maybe using AfterAndOnSegment. Then you can create a segment object that goes from the angle origin to the sliding point.

I just realized that creating a completely locked point is harder than necessary. You can create a "Point" but it won't be visible until it's either a handle or a computed point. Right now the only way seems to be to create two dummy points and create computed point based on them. Or maybe a collapsed segment. I should probably add a simpler constraint that completely locks a handle in place.

The gist of it is that the "Icon" node contains the Base64 encoded image. In practice:

• create a 16x16 image file of the icon, I would suggest PNG but it should work with JPG and BMP as well.

• Go to https://www.opinionatedgeek.com/codecs/base64encoder load the file and click Encode.

• Copy and paste the resulting text as-is in the Icon node.

You can have a KVA file that is always loaded when you open a camera.

Create the annotations in the playback screen (maybe by reloading a video captured from the camera for alignment) and save them to a KVA file named "capture.kva" (File > Save > Save only the analysis). Then place that file in Kinovea %appdata% directory. The location of this directory depends on whether you are running the installed or zipped version, but you can get to it from menu Help > Open log folder.

The same can be done for the playback screen using "playback.kva". It's an application-wide thing though, there is currently no support for per-camera default KVA.

Oh you are on Windows 7, in that case the program name in the process tab should have a *32 at the end if it's 32 bit.

It could still be this because Kinovea 0.8.24 was only released as a 32 bit app. It's only from 0.8.25 and forward that there is an x64 build. So it would be very consistent with this being the origin of the issue.

Try to load the file in Kinovea 0.8.26 from the download page, it has a lot of updates, including in the loading library.