I agree it's not ideal, a tool-specific toolbar would be nice to have somewhere. You don't have to open the color profile and search for the tool though, if you right click in the video background while the tool is active it will directly bring you to the color profile at the right page.

422

(1 replies, posted in General)

You can tell it to stay visible for a number of frames.
Right click > Visibility > Custom fading, and then in "Configure custom fading" change the "Opaque duration (frames)" counter.

423

(42 replies, posted in General)

No it hasn't changed. Set the working zone then use either menu "File > Save" or the "Save video" button in the lower right corner of the playback screen and then "Save video with annotations permanently applied" to export a new video.

What is the result you are getting? The output contains the whole video?

424

(6 replies, posted in Cameras and hardware)

I don't know about that camera but I'm confident it doesn't stream 1080p@120 fps to the outside, that spec is what goes to the SD card.

You can record with a smartphone, you need to install an "IP camera" application that outputs an MJPEG stream, like "IP Webcam" for Android. This won't get you to 1080p@120 though.

Another option is industrial "machine vision" cameras, like Daheng Imaging, Basler, IDS. These have much better perfs but are more expensive and you have to buy a lens in addition to the camera, but quality-wise they are the best.

The way the dual recording works makes this complicated, it's pulling frame by frame as if you were manually moving the slider from the joint controls, this uses a common time axis for synchronization and is oblivious to the local slow motion of the videos. That is, a given position in the bottom slider corresponds to a specific time, in a common reference frame where both time origins are aligned, slow motion has no impact on that.

Probably a work around for now would be to redefine one of the video nominal speed by going to menu Video > Configure video timing and forcing a different framerate in the bottom part of the window. There is a bug related to time display with this function that is only fixed in the development version but this should hopefully not prevent the work around from working.

To clarify, maybe, in the current synchronization approach, the output at 1.0 seconds should always show what happened at 1.0 seconds in each source video.

I understand there is a need to compare events with different durations "as if they had lasted the same duration", essentially normalizing on the duration of one to be able to compare the forms only. I'm still unsure what's the best approach for this. It has come up a few times but it would help to have a good pair of videos with the corresponding objective.

426

(6 replies, posted in Cameras and hardware)

Re: replay folder observer,

Go to menu "File > Open replay folder observer" and point it to the folder where your files are saved. That is, the same path you set in capture preferences. What this does is create a playback screen that is constantly monitoring this particular folder for new files. When you capture a file it will open and read it.

427

(1 replies, posted in General)

Thanks!

428

(6 replies, posted in Cameras and hardware)

You can now set it to automatically stop recording after a few seconds and then automatically open the file as instant replay in a loop, see "replay folder observer". The kind of programmable scenario as you quoted is still not possible.

Note that the webcam mode in the new GoPro Hero 7 & 8 is not currently supported in Kinovea so you won't be able to use these cameras for direct streaming into the program.

Another possibility could be the Daheng Imaging cameras which are supported since version 0.9.2. For example the MER-160-227U3C is based on the same sensor as the Blackfly you listed above (IMX273, 1440x1080, 227fps) and their MER-131-210U3C is based on the same sensor as the IDS (Python 1300, 1280x1024, 210fps).

430

(2 replies, posted in Bug reports)

Go to Options > Preferences > Capture > Memory, and increase the memory allocated for delay buffers.

No, cameras from FLIR / Point Grey Research are not supported at this time.

Yes, this was fixed in version 0.9.1.

No it wasn't removed, image objects (either from built-in SVG files, importing images, or from pasting an image from the clipboard) should have a "Visibility" menu in their context menu, like this:

https://www.kinovea.org/screencaps/0.9.2/092-configurefading2.png

434

(42 replies, posted in General)

Where did you get the driver from? I didn't do anything. Or is it a Kayeton camera?

435

(42 replies, posted in General)

Also double check the framerate received by Kinovea is the one you expect. You can see this in the infobar above the capture screen. The "Signal" value should be near the framerate you expect. If it's around half what you expect you will get a sped up video as you describe. If you are in low light conditions for example the camera can decide to increase exposure time and lower the framerate automatically, disregarding the configuration.