Search options (Page 26 of 131)

Can you go into the Configure camera dialog from and show what's in there?

Some possible causes:
- The camera is sending a stream format that Kinovea doesn't support. Try changing the stream format from the Configure dialog.
- The exposure duration is too low, everything is so dark it appears black. Increase exposure.
- The camera doesn't have enough electrical current available through the USB port.
- The camera doesn't have enough data bandwidth available through the USB port.

For the last two, especially if you are on a laptop, try changing USB ports or using a powered Hub. Especially if you have other devices connected on the same USB root (it's hard to know which ports go to the same root USB controller but try disconnecting other devices to see if it makes a difference). Also try a smaller resolution from the configuration dialog.

Hi,
It's working for me here, one thing though is that the size is clamped down at some point to avoid it going too small. If your video is constricted by the viewport it's possible that there is a range of font size configurations that all result in the same final apparent font size. Try to put it to size 96 to see if it does anything at all. You can also pull down the label by the bottom-right corner with the mouse. Also try with a low-resolution video to see if you get the same issue.
Thanks

I see what the problem is in the code but this seems to be an old bug and I have the same problem in 0.9.3 so I would like to understand whether we are talking about the same bug or if it's two different ones.

The problem is that it is writing the value with the comma as decimal separator in the XML. The spreadsheet expects it with a dot. This issue is specific to the angle tool.

One confounding factor is that in 0.9.3 and prior versions the angle tool doesn't show decimals in the user interface.
I only have LibreOffice Calc on this machine and I import the MS-Excel file into it so this may be a factor as well. I get the same results when exporting to ODF anyway.

For reference:
Windows settings: Control panel > Region > Formats > Additional settings > "Decimal symbol".
LibreOffice settings: Tools > Options > Language settings > Languages > "Locale setting" and "Decimal separator key".

Experiment 1:
- Windows regional settings: ,
- LibreOffice settings: Locale=French (France), Decimal separator: Same as locale setting (,).
- Kinovea 0.9.3.
- Export to MS-XML.
- Opened in LibreOffice: BUG. The data is stored with a comma which is interpreted as thousand separator by the spreadsheet.

Experiment 2:
- Windows regional settings: .
- LibreOffice settings: Locale=French (France), Decimal separator: Same as locale setting (,).
- Kinovea 0.9.3.
- Export to MS-XML.
- Opened in LibreOffice: GOOD. The data is stored with a dot. The spreadsheet then display it with commas.

In summary:
- The bug is triggered when using comma as decimal separator in Windows (I will fix this).
- Using dot as decimal separator in Windows works around the bug.
- Changing the spreadsheet option only impacts the spreadsheet display and doesn't trigger the bug.

I get the same problem using 0.8.27, 0.9.3, 0.9.5.

Can you describe your configuration where it was working in 0.9.3?
Thanks

This part I didn't quite get. If I understand correctly you would have a prepared file with 11 keyframes in it, and you want to redistribute these keyframes in time to match the tempo of the current video. Is this correct?

You can change the name/title of the keyframe by editing it directly under the thumbnail or going into the keyframe edition and changing it there.

At the moment you can't change a keyframe time coordinate. I agree this is an unfortunate limitation. I'm not sure how it could be exposed. Maybe a new context menu to "move keyframe here" or drag and dropping the thumbnail on the timeline… Or maybe just changing the time manually from the keyframe dialog. This last option would probably be the easiest to code but maybe not very user friendly.

These cameras are not supported at the moment.
I really need to find a way to add generic support for USB3 vision cameras. Implementing each vendor SDK is not sustainable.

The problem appears to be a vertical flip. The rotation makes it look like horizontal mirroring.
I can reproduce the issue when I switch to "Raw" stream mode instead of "RGB". The problem seems to be with any monochrome stream.
And do you also have the issue on the thumbnail?
Thanks

What type of metrics are you interested in in the kinematics plots?
At the moment there is no kinetics measurements as there is currently no way to assign weights to points.