Search options (Page 43 of 131)

Interesting. It might be due to the amount of current the camera is pulling and the extension cables aren't up to spec?   
Some people use Ethernet-to-USB adapters to extend USB over long distances. Maybe an avenue to consider…

Thanks for the follow up. No problem

I just tried it for testing and it worked. (Using 0.8.26).

The app I used is "IP Webcam" from Pavel Khlebovich: https://play.google.com/store/apps/deta … p;hl=en_US

When starting the server on the smartphone, it gives the IP address of the stream in the lower part. It is the IP of the phone with the port configured (8080 by default). When connecting to this address in a browser, the phone serves a web page. I clicked Video renderer > Browser button on that web page and got the live stream inside the page.

Then I did right click on that live stream image and "Copy link location", to get the URL of the actual stream, it was indeed http://<ip>:8080/video.

Copying this address in the configuration dialog in Kinovea made it work. I left the stream format to MJPEG in Kinovea and didn't change any defaults in IP Webcam. I did not choose the MKV option in IP Webcam.

Kinovea still has to be set to Capture > General > Display synchronization > "Camera frame". Not "Forced framerate". I haven't investigated further on this point at the moment.

You need to add a calibration line somewhere in the video and tell its physical length, so the program knows the mapping between pixels and distance. Add a line and then right click and choose calibrate.

This will work only if the camera is standing still on a tripod.

You can also use the more advanced perspective calibration where you calibrate the dimensions of a rectangle.

As mentioned there is no automatic extraction of the average, so you will have to settle on eye-balling it from the curves passing at a point or doing the computation by hand or in a spreadsheet. Min and Max can be read on the plot.

Do you mean when the leg is vertical or when the crank is vertical and the pedal is at the 6 o'clock of the sprokets?

There is a tool for "angle-to-vertical" but unfortunately it is not usable with the angle-angle diagram at the moment.

There might be a simpler way to do this with a custom tool and I'm not an bike fitting expert so please take the following as inspiration only.

If you can show how you normally measure it for a single cycle maybe I can come up with a better solution.

You could add a regular angle tool to act as a reference for when the pedal hits the 6 o'clock mark. Set one of its leg horizontal and the other vertical, with the end of the horizontal leg tracking the pedal or a marker on the foot, aligned with the pedal, and the other two points placed in such a way that the background behind them will not change. This way the angle is always less than 90° when the pedal is up, and 90° when it's at 6 o'clock.

Then add another angle for the knee joint angle.

Something like this:

The blue angle will act as a reference. It will read 90° when the pedal is at 6 o'clock and less than 90° otherwise.

You track these for a while: right click on each angle and do "tracking > start tracking", then progress frame by frame verifying that the auto-tracking is solid and adjust it along the way when necessary, then "tracking > stop tracking" when you are done.

Then go to Tools > angle-angle diagrams, and you should get something like this:

If you look at when the reference angle (X-axis) is at 90°, you can see that the knee angle is around 118 to 120°.

I have not tried this particular camera but if it is UVC compliant in theory it should work out of the box.

If you try please let us know the outcome.

I agree it's annoying, it has happened to me as well. However I think it's important to have a shortcut for the synchronized playback and using the same shortcut as for the single video case makes sense in my opinion.

The problem is that at the moment there is no distinction between opening two videos for synchronization or just for looking at two videos individually. We need to figure out a heuristic to distinguish these use cases. Maybe keep them independent until the user actually clicks on the synchronization button?