1

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

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.