1 Topic by ChristianK

  • ChristianK
  • -
  • Offline

Hey there experts!

I used Kinovea for the first time during some of my biomechanics units in undergrad, now I've a sports podiatrist I'm looking at using it at my current clinic to replace SiliconCoach which is 1. Expensive and 2. doesn't like to work very often.

I've tested Kinovea at the clinic and it works well with the occassional lag spike and non-responsiveness when trying to play back a just recorded video. For some of my less technologically-savvy colleagues it can be a bit daunting so my boss has got a few questions below:
1. How can I reduce the chance of lag when with patients?
2. Is it possible to do side-by-side video comparisons to look at shod vs unshod or compare different footwear and orthotics?
3. Are there any integrated capture tools for both image stills and videos that we could email off to sports teams or other practitioners effectively?

I'm fairly certain I know the answer to these questions but I'm hoping you guys could also give me some clearer explanations so I can be sure I don't miss anything.

At the moment we have a 4 camera setup and switch between the cameras to record patient's and that works really well with Kinovea though I'm not sure if the camera quality is as high.

Would it be possible to please treat me as a complete newbie and give me a bit of a rundown on how much more I can use it for and how to optimise it for a clinical setting? I'm reading through the manual as well but thought I'd post this here in case there is anyone who would also let me ask them some questions if I get stuck.

Thanks!

2 Reply by joan

  • joan
  • joan
  • Admin
  • Offline

1. Lag: there are a few axes. Using an SSD, saving the recordings to a different drive than the Windows drive, changing the recording mode in the preferences.
2. Side by side comparisons are possible yes. For example, menu View > Two playback screens.
3. Currently the capture of video is not optimized for sharing. I'm working on this for the next version, among other things. Capture images should be fine, you can save as jpeg or png and share that. If you meant capturing the whole interface like a screencast then no, you would have to use something else on top.

For multiple cameras setup there is a possible workflow where you have one instance of Kinovea for recording and another instance of Kinovea for reviewing. This can better utilize the CPU cores. Even for just one camera and one instant replay that might be another way to improve responsiveness.

Sorry I don't have more time to expand these points in too much details right now but should have more time later in the summer. Unfortunately I didn't get around to fully update the manual lately, so it's half way done in a draft version, I'll get around that at some point as well.

3 Reply by ChristianK

  • ChristianK
  • -
  • Offline

Hi Joan,

Apologies for the delay in replying!

Good to know, I'll keep in mind SSD (keep separate to Windows drive), use two playback screens (and is it possible to have two instances of Kinovea running to show 4 views at once? I have more I'll ask a bit later on), capture images is fine, we can work with that.

Your reply has been very helpful and I was wondering if you've got any more time to expand on it if you might be able to help me out with the hardware side too or point me in the right direction for where to look.

We have been using Kinovea in our clinic for a while and it's great because it doesn't crash (though my older colleagues still don't like change and are taking some time to get used to it). I would love to know if it's possible to get Kinovea working in this way:
- Have an automated folder routing and dual-instance capture before the patient steps onto the treadmill so we have two Kinovea instances running side-by-side (E.g. one for Anterior + posterior ankle, one for sagittal + posterior global)
- Automated naming and target folders to auto-save to a dedicated local NVMe. Having a replay folder observer that can be configured so the playback screens populate automatically once a recording is finished.

Ideally it would run like this:
1. Trigger recording with hotkey or pressing the red button.
2. Capture 5-20 seconds at around 60-120 fps
3. Hitting stop immediately saves the stream and the replay folder instantly renders the files into the side-by-side playback workspaces

I would love to know also what the best cameras would be to hook up to the system as we use HDMI at the moment but I understand USB would likely be better?

Any help would be massively appreciated and you've already helped tonnes, thanks!

4 Reply by joan

  • joan
  • joan
  • Admin
  • Offline

is it possible to have two instances of Kinovea running to show 4 views at once?

Yes you can open multiple instances to have more players and cameras.

You can give names to the instances and recall them later (menu Window > Window properties…, Reopen window, Manage windows…). The general preferences are shared and synchronized between the windows, there is no "master" you can access the window manager or change the list of capture folders from any window. The concept of "workspace" is one level above that, it's for saving a whole set of windows and creating a shortcut to restart them all at once.

Ideally it would run like this:
1. Trigger recording with hotkey or pressing the red button.
2. Capture 5-20 seconds at around 60-120 fps
3. Hitting stop immediately saves the stream and the replay folder instantly renders the files into the side-by-side playback workspaces

Yes that should work. The hotkey or record button is in each window though, so if you want to start recording simultaneously in all windows it needs a different approach, easiest is via microphone trigger but there are other means.
Same for stopping the recording. The easiest is to set a predefined duration so you can't forget it and you will see a red bar reducing towards the left as a countdown.

20 second recordings is going to make large files, for your context where you'll likely have hundreds of videos it will be a concern and the NVMe will fill up. Next version will have a way to define more sensible compression settings (and improved performances to avoid frame drops). If you use USB webcam types they often have a stream that's already MJPEG encoded, this could work well for this.

The replay starts when a file is finalized in the observed folder. You have to tell it which folder to look at, it doesn't directly know about the capture windows. The linking is via the capture folder.

So in your case the first thing you want to do is define your capture folders. Then in the camera screens you tell each camera where it will save its files (using the drop down at the bottom). And for the replay screens you point them at the corresponding capture folder. Any time the capture side finalizes a recording it should be automatically loaded and played in the replay window.

Here is a tutorial that should be relevant, it was for golf but the setup is similar I think. Tutorial for golf swing automatic capture and replay.pdf

Or you could have each pair of camera + replay in its own window, if it's simpler.

For your use case there is maybe an extra layer of automation to investigate. You could have all the patients names in a CSV file, maybe exported from the main software that handles patient records. Then you import that into the "Context" (Options > Context > Import). In the capture screens you'll then get a drop down with all patient names and can specify who is being recorded. The capture folders and file name patterns can use that as variables to automatically put the files in a folder named according to the patient.