You are not logged in. Please login or register.
Kinovea - Forums → Posts by joan
@Martin, your problem is different. Based on the log it's possible the newest runtime from IDS is no longer compatible with the SDK I used to make the plugin.
For the problem of the crash with no error message in the log I'm not sure where to start and I don't know how to reproduce the problem to investigate it.
Hi,
This is not implemented and at the moment it's not on the roadmap.
You can use a dedicated software to capture the screen. OBS is free and open source.
Yes that's correct. You should get all the frames, they are just spread out more in time.
If I recall correctly this is written in the log at some point during recording. Otherwise it is saved in the .KVA file produced along the captured video, but if you opened it, modified the value and saved back it was most probably overwritten. However if you recorded multiple videos the same day one of the KVA file might still have it.
There are two log files and they roll over based on file size so there should be history for a few recording sessions in there.
Hi,
This aspect is often confusing because there are many different framerates when recording high speed footage.
Normally it should be automatic and work like that: the camera sends frames at 260 fps, Kinovea records 260 frames per second in the file, and at the end, in the metadata of the video file, writes "30 fps". This is to avoid media players trying to replay at 260 fps (or higher) which they can't do. It's similar to the high speed function on a phone or a camera. That's why high speed footage looks slowed down when replayed.
On the playback side there are two things to consider, the playback speed and the times displayed. The typical way to do things is to let the footage be slowed down but "fix" the time display so you can still make time measurements or compute the speed of an object. This is controlled under Video > Configure video timing. If you recorded the video with Kinovea it should be set automatically.
If you really want to have the final video marked as 260 fps (it will probably not playback at that speed), you can change the behavior under Options > Preferences > Recording > High speed cameras. Check this paragraph of the help: https://www.kinovea.org/help/en/userint … ed-cameras
Right click the video image itself, without adding any marker. In the "background" of the video frame so to speak. There is a separate context menu when you aren't on any drawing. It's in this menu. This means you can directly right click the area of the video you want to track, don't add a marker.
Is it an IDS camera? I remember there was a similar slow down with these cameras.
Could you show the beginning of the log when this slowdown happens?
Yes, that's a good change. Please send a pull request.
For the XML files it depends on the tools, some of them are explicitly described and others are just referencing an internal class and use the XML only to describe styling options. What kind of options do you want to add?
This will only give the time. For the crossing speed it's more complicated. Maybe an alternate metric that gives the ratio between the two parts, so you can do the computation later after export if needed.
If I understand correctly, this would be under the assumption that the movement is linear between the two frames. In reality the subject is most likely accelerating/decelerating but it could be a good enough approximation in many cases, better than nothing anyway.
Maybe this could be integrated into a line tool. You trace a line between two points that are supposed to be in two consecutive frames, and the line would have graduations corresponding to subdivisions of the frame interval, and show the corresponding time at each graduation.
Or a line with one sliding point in the middle, with a mini label attached, and you slide the point to where you are interested in reading the time.
Maybe called "time segment" tool, a segment of a timeline.
How do I insert an image in this forum post ? That will show the problem.
You need to host it elsewhere like on imgur.com and then use the URL in an img tag or just post the URL.
Is the 0.7 s very consistent, like exactly the same number of frames each time, or is it erratic?
The log should have more info about the recording process, including stop reason, duration and number of frames.
La velocidad media bajo toda la trayectoria? No, tendras que exportar los datos y calcularla fuera, en Excel o algo similar.
The onething I have been asked over and over again is about a single button capture start, rather than having to position the mouse over the Record button then click it. Are there any plans for this to be available or being able to create a HotKey for this. The second option would be really good as we could then attach and external button and programme this to the same hotkey.
Hot key for toggling recording on/off is CTRL+Enter by default, you can change that in Preferences > Keyboard.
There is also a listener of Windows Messages that will listen to named commands so you can trigger it from external software.
You can also trigger by sound threshold from the microphone input (See Preferences > Capture > Automation). I think from this last one you could also build a hardware trigger by hooking an Arduino or something directly to the Line In (I haven't tried).
If you have delay it needs a memory buffer to store the frames, if the two cameras have very different image size/framerate it might do this I think, although the difference is extreme. Can you tell more about the recording parameters: Options > Capture > Recording : what recording mode do you use here? What delay, size and framerate of cameras, size of memory buffer, stream format.
Kinovea - Forums → Posts by joan