I have uploaded the firmware Waheeden shared with me at the following:

fix_frame_rate.zip

And the original firmware in case things go wrong:

standard_version_not_fix_the_frame_rate.rar

There are instructions inside on how to proceed. I haven't had time to try it myself yet.

587

(7 replies, posted in Bug reports)

Thanks for the sample.
It is one of those files where the first frame of the video has a negative timestamp, this throws off some calculations… Can you share what camera or process has generated the file?
It's probably fixable but needs care to not break other things in the process.

588

(7 replies, posted in Bug reports)

It is the first time I hear of this. Could you share a sample file please?

By going through the frames of the video I can see the timestamps and when the video reaches the last frame I can compute the total number of frames and total time that are actually in the video. So in theory this should be enough to fix this kind of files automatically. I'm not sure what's the best way to go about it though.

It could initially leave things as they are and after the first loop, when it realizes the last frame doesn't match the duration, try to fix it. 

There could be a explicit "Fix duration" button in the Video > Configure timing dialog, that would perform the test and save the actual duration somewhere. This could then become an option in the main preferences to "always try to fix duration", but would be off by default because it will slow down opening the files in the normal case.

Other ideas are welcomed.

590

(4 replies, posted in Bug reports)

The color itself not so much. But it's best if the marker contrasts well against the background. It should also be "rotationally invariant" and if it has contrast itself it's also better. So for example a black disc with a white dot in the middle or vice versa. Otherwise a simple black or white disc should work well enough.

obevz wrote:

great thanks...generally the replay is once and delete...just for feedback to the golfer for practice. Sometimes that golfer is me...to check my swing etc.

If you are sure you won't save the sequence, the simplest way to do instant feedback is to use the delay function. For example you can set the delay to 5 seconds.

obevz wrote:

The lines on the capture screen are not the same when I replay the capture.

I'm trying to reproduce the problem. Could you send a screenshot at joan at kinovea dot org? In particular what is the camera image size, whether the camera view is filling the capture screen, and same for the playback side.

It is now possible to rotate the camera image at capture time in version 0.9.2.

This should work as expected now in version 0.9.2. The drawing will be visible while tracked and fade out afterwards. The custom visibility settings can also be used to deviate from this default.

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.

The problem with special characters preventing some files to be opened should be fixed now in version 0.9.2.

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 should now be fixed in version 0.9.2.

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.

599

(3 replies, posted in Bug reports)

This will be possible in the next version.

600

(4 replies, posted in Bug reports)

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.