You are not logged in. Please login or register.
Kinovea - Forums → Posts by joan
I like these suggestions.
For the first one though I think this option would have to go in the general preferences, there is already a lot of stuff going on in the screen UI.
For the last one I don't think I can do anything, the range is a mapping of what the microphone API is providing, so I'm already getting a number between 0..1 that is (log) mapped to the range seen in the user interface. So there is nothing "above" the max number, it's where the mic is clipping.
You can change the keyboard shortcut under Preferences > Keyboard > CaptureScreen > ToggleRecording.
So you could have a wireless keyboard or numpad and use that maybe.
More advanced ways: using a virtual audio cable (like Voicemeeter Aux Input/Output or Voicemeeter Banana). Then you can have an application trigger this somehow. There is also a Windows Message option that can be triggered using any program that can send Windows messages, like AutoHotKey, but that is not really documented yet, or rather we don't have a neat little example of a program calling this.
Edit: maybe it's also possible to use a contact/piezo microphone with a long wire, it should be possible to make it trigger only when actually touched, not from ambient noise.
If the app that makes the iPhone act as an IP camera is serving the stream as MJPEG, then Kinovea can be the client. Go to manual connection, IP camera and fill the details.
For HDMI to USB it must go to USB3 to get enough bandwidth.
Just to say that I reproduce the crash. It's rather low level and I don't have an easy fix for now but I am investigating. Unfortunately it crashes even when the Reincubate Camo application is not launched, since it's the virtual camera driver that is causing the issue in Kinovea. Kinovea tries to contact the camera in the background to prepare the thumbnail, it fails to open it, and upon cleaning the resources there is a low level crash.
Looks to be related to Reincubate Camo, I see this is a webcam application to stream mobile phones, I'll install and try to see what's going on.
The driver from CodeLaboratories only works for Windows 32 bit.
Try with this one instead: https://github.com/jkevin/PS3EyeDirectShow/releases
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.
Can you go to the log file and see if there are any errors? If you use the .zip version the log file is under the AppData sub directory.
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
Hi,
"Select Source" is referring to an older version. There is a Camera tab in the explorer panel on the left, you should see your camera from there.
See here: https://www.kinovea.org/help/en/capture/listing.html
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
Thanks, I can reproduce the problem.
No there is no easy way to export the angle to vertical at the moment.
I'm imagining clicking on a keyframe, being able to type in the exact time of occurrence for that keyframe (i.e., "Contact" for when the bat connects with the ball), and the marker would jump to that point.
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.
Hi,
I don't reproduce the problem at the moment, please let me know of the following:
- What column has the problem, the data column or the time column?
- If it's the time column, make sure you are using a numerical time format, the default time format is a time code, not a number, if there were minutes it could look like this for example "3:10.54". If you only have seconds and hundredths it can look like a number separated by a dot but it's not a number, it's text. You can use the Total milliseconds format instead to make sure the time column is numerical.
- If it's not that, let me know what you have set in Windows under Control panel > Region > Additional settings > Numbers > Decimal symbol. This is the character that should be used.
- If it still doesn't work, let me know what kind of object is exported with the wrong format, maybe it's specific to the tool.
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.
Kinovea - Forums → Posts by joan