Search options (Page 34 of 131)

This issue of corrupted alignment in dual save is fixed as of version 0.9.1. It was related to the total size of the composite video adding up to something not a multiple of 4 pixels, this is not always supported by the output format.

This scenario is supported now in version 0.9.2.
After copying and then pasting the image in the second screen, right click and Visibility > Custom fading, then lower the "Maximum opacity (%)" field to make it more transparent.

This was addressed in version 0.9.2. The drawings are now opaque whenever they are tracked and they fade in/out around the tracked section(s). You can use the custom visibility options to change the maximum amount of opacity and the fading ramp.

There are adjustments but they are a bit hidden, you need to go to Options > Preferences > Drawings > Tracking. There you will find the default options for the size of the object window and the search window.

The object window should be as small as possible around the marker to avoid picking up the background. The search window should be large enough to encompass the marker's motion from one frame to the other, but not too large that it may pick up another marker.

One way to find the best settings for these values is to start with a normal trajectory tool (right click > Track path), and then go to its configuration window and adjust the values visually from there and do some trial and error to see what works best. Then you can copy the settings over to the main preference window.

It's probable that you will still have to adjust the position manually once in a while.

(The following is for version 0.9.2)

When you add a line or other object you can right click it and select the menu Visibility > Always visible. This way it will stop fading out after a few frames.

If you are only interested in having lines that are always visible, you can go to Options > Preferences > Drawings > Opacity > Default opacity of new drawings and check the box saying "Visible for the entire video". Now new drawings will be always visible by default, although you can still customize the fading option on a per-drawing basis by going to each drawing visibility menu.

If you are interested in having a specific set of lines to appear every time you open a video, you could create these lines, save them in a KVA file through File > Save > Save only the annotations, and then save this file as "playback.kva" and copy it in the application data directory. This directory can be found from menu Help > Open log folder. This way every video will load the KVA annotation file upon opening.

edit: I forgot to mention, and this is new in version 0.9.2, if you add the line directly in the capture screen, a KVA file should be saved automatically when you capture the sequence, and will be reloaded when you replay it. In this case the objects added at capture time should already be in "Always visible" mode.

Also if you are interested in these capture-replay scenarios there is also a way to automate the capture/playback loop so you don't have to attend the computer each time. This is done using File > Open replay folder observer and point it to your capture target folder.

Hi,
When you can see each camera independently but not at the same time it's usually an issue of bandwidth or current at the USB level. Both cameras are ending up on the same USB root hub and have to share the bus bandwidth. If your laptop has other USB ports try switching around to find ports that are on different USB root hubs. The device manager might be of help to know if you have several root hubs or a single one serving all the ports. Put them on USB 3 ports if you have any.

Thanks for the sample.
Unfortunately it does look like the problem is in the files themselves.
I get similar duration with other tools, the main metadata are wrong:

Duration: 26:29:35.34, start: 13378.435000, bitrate: 0 kb/s

I'm not sure what could cause this aside from a bug in the encoder in the camera. Does this camera work in "loop recording" mode like a dashcam, where it's constantly overwriting the same small file and it's only when it detects motion or you raise a special command that it splits the file to an indepedent one? I wonder if the duration could be the entire duration since the start of the loop recording process. Does it increase progressively after you restart the camera?