Search options (Page 38 of 131)

Hi,
At the moment it is hard coded. And yes the bitrate settings are very aggressive to minimize any loss of information when saving, to best support the archival use-case (e.g: splitting a long session into smaller chunks). It's the first time I hear a player complain because the bitrate is too high though… What player is it?

I've kind of tried to stay away from opening this particular can of worms :-). Codec options can become complex fast, in terms of UI and this complexity will trickle down into the code. Maybe having just two options would work, one for archival and one for web/presentation export? Maybe it can even be selected automatically based on the option to paint the drawings on the images (for archival this should never be done).

Hi,
In addition to the configured framerate and the display framerate, there is also the actual, received framerate. It's possible that Kinovea is not receiving frames at the correct speed for whatever reason (low light, network conditions, camera is lying, etc.). There should be a "Signal" field in the infobar that shows up after a while. This shows the framerate received.

The way recording with delay works has completely changed in the next version, so we'll see if that fixes your particular problem. It will now always save at the camera configured framerate, display framerate is not used anymore.

It's possible the issue is that the stream received is at 30 but Kinovea wasn't able to record it fast enough to disk unless your force it down to 21. Or it's possible the stream received is at 21 in the first place. The "Signal" value should give the answer to that. Another way I use is to pause the stream and navigate in the recent frames with the delay slider to see if the stopwatch matches what the delay says.

Based on your description it looks like the actual received framerate is 21, even before attempting to record to disk. Unless the camera is lying this should be fixable by other ways (most probably adding more light to avoid triggering auto-framerate by way of auto-exposure).

For this case of the camera not sending what it's configured to, currently the best way to fix it is at playback time, by going to menu video > configure timing and fixing the framerate there. In the future I'll also see to add an option to be able to save the "received framerate" in the video, but ideally this option would be per-camera and saved in the preferences per-camera, as the goal is to fix cameras that are lying about their framerate. So as the release of the next version is coming soon, I pushed this to the roadmap for the next one.

Hi,
It could be a bug but I don't reproduce it at the moment. There is a "dual save" button at the bottom right, in the common controls panel, is this what you are using? Which version of Kinovea are you using?

Just in case, you can show both the time and frame number simultaneously using the last menu under Options > Time.

Another time format could be "Normalized" time, where the entire video or zone would be remapped to the 0..1 range. Could be useful for comparisons.

Absolute times would be great for line scan footage, and then a way to calibrate the time span and flow of columns, and a way to show time coordinates by placing special vertical lines or points on the frames...

Hi,
You can also use "Copy image to clipboard" and "Paste image from clipboard". But you're right, it doesn't let you change the opacity at the moment.

As a work around you can have 50% opacity between the two videos by activating the "superposition" option down in the common controls next to the synchronization button.

Hi,
The first number on each log line is the total milliseconds since application startup.
The interface will be visible and fully responsive when you get to about this line:

797 - DEBUG - [Main] - FileBrowserUserInterface - Application is idle in FileBrowserUserInterface.

(So in this case a hot start, 0.797 seconds).

I made a change a few days ago that I think could help with this. I'll send you a message.

As an example, on my machine it takes ~2200 ms to get to this line on a cold start.