721 Reply by joan

(8 replies, posted in Bug reports)

Hi,

I have addressed the following points for the next release:

1. Position of the text for angles

There is now a "textDistance" attribute on the angle node.

<Angle origin="1" leg1="2" leg2="3" signed="true" ccw="true" supplementary="false" radius="0" textDistance="40" tenth="true"/>

2. Double constraint fixed length + rotation steps.

The rotation steps constraint now has an attribute "keepDistance" that will force the point to stay at the same distance from the origin. I think it still didn't make sense to have a full multi-constraints system, as this was the only meaningful combination of two constraints.

<Constraint type="RotationSteps">
        <RotationSteps origin="1" leg1="0" step="5" keepDistance="true" />
</Constraint>

Note that the existing "DistanceToPoint" constraint supports the SHIFT modifier that forces segments to lock onto 45° steps. This is supported out of the box and doesn't need any specifics in the tool file.

3. Completely locked points.

There is now a "LockedInPlace" constraint that will simply ignore the applied motion. 

<Constraint type="LockedInPlace" />

In addition to that, there is now a debug mode for the custom tools. It will be available from menu Options > Preferences > Drawings > General, check box "Custom tools debug mode". It will show the points ids, the segments ids and names, and angles ids and parameters. Counting starts at 0.

http://www.kinovea.org/screencaps/0.8.27/customtooldebug3.png

Go to forum: Bug reports

722 Reply by joan

(16 replies, posted in Cameras and hardware)

Does it still crash if you set the following: Preferences > Capture > General > Display synchronization, set to Forced framerate and value to 25 or 30.

Go to forum: Cameras and hardware

723 Reply by joan

(7 replies, posted in Cameras and hardware)

govert.vandevijver wrote:

But at the top of the image I see @17fps although the camera is setup in the "uEye cockpit" to have 60fps. Also, altough I configure the camera in the "uEye cockpit" to a monochrone image, the image in Kinovea will be in full colour. I looks like the camera parameters are ignored.

To clarify a point, the way the IDS cameras work, at least in regards to the IDS SDK used in Kinovea, is that each application is responsible for managing its own set of parameters for the camera.

When the program connects to the camera for the first time it will always receive a default parameter set. Then they have helper functions to save and load the parameter set as it gets customized for the application.

You can see the file where these parameters are saved for Kinovea by going to menu Help > Open log folder, and then go to the sub folder "CameraProfiles\IDS". There you should see a .INI file for your camera. There will be entries like image width, height, framerate, exposure, etc.

The parameters you set in IDS uEye Cockpit are only used by the Cockpit application.

This works differently than, say, Basler cameras, where they have a "global" parameters manager/API and all applications will read/write the same values.

In uEye Cockpit you can also see this concept by the menu File > Load parameters and File > Save parameters. This will save an .INI file that has the same format as the one you can find in the sub directory of Kinovea preference files above.

I imagine that if you had a specific parameter that you wanted changed that is not exposed in Kinovea you could try to save the .INI file from uEye Cockpit and then merge it with the file used by Kinovea. Although I would like to hear about these specific parameters to see if it would be relevant to have them supported natively in Kinovea.

Go to forum: Cameras and hardware

724 Reply by joan

(14 replies, posted in General)

I answered in the other topic here.

Go to forum: General

725 Reply by joan

(7 replies, posted in Cameras and hardware)

Hi,
Kinovea has its own configuration for some of the parameters and should leave the others untouched.

What do you have when you go to the camera parameters in Kinovea? (You can click on the info line at the top or use the configuration button in the lower left).

You should be able to set the stream format to MONO 8 here for monochrome and change the image size, framerate, exposure and gain.
The framerate configured can only be reached if the exposure duration value is low enough though, as exposure has priority over framerate. For your 60 fps target, make sure the exposure duration is less than 16 666 microseconds.

This is for 0.8.26 by the way.

Go to forum: Cameras and hardware

726 Reply by joan

(16 replies, posted in Cameras and hardware)

Could you send me the crash log (Unhandled Crash ***.txt ) and the log files from right after the crash?

Go to forum: Cameras and hardware

727 Reply by joan

(16 replies, posted in Cameras and hardware)

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…

Go to forum: Cameras and hardware

728 Reply by joan

(11 replies, posted in Cameras and hardware)

Interesting setup using the phone as WiFi hotspot. Although I imagine the combo hotspot + camera + streaming must drain the battery very quickly.

Go to forum: Cameras and hardware

729 Reply by joan

(16 replies, posted in Cameras and hardware)

Thanks for the follow up. No problem smile

Go to forum: Cameras and hardware

730 Reply by joan

(16 replies, posted in Cameras and hardware)

Hi,

@purk_7 stated in another thread that the camera settings were reset after every reboot. Does anyone else have the same issue?

This is not expected. The settings should be saved on Kinovea side and re-injected in the camera when reconnecting, but there might be something special with this model and the settings can't be pushed back.

Go to forum: Cameras and hardware

731 Reply by joan

(11 replies, posted in Cameras and hardware)

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.

Go to forum: Cameras and hardware

732 Reply by joan

(10 replies, posted in Cameras and hardware)

The C922 is among the best you can get.

Make sure you are using the most recent Kinovea version even if it's marked experimental, it has many improvements on the capture side.

The framerate and resolution are largely independent but together they define the total bandwidth that the camera has to process and then send over to the computer. The hardware itself is limited by the amount of data it can capture and then the USB link also has a limit to what can be transferred. USB cameras define a set of framerate and resolution combinations that can be selected.

When you go to the camera parameters dialog in Kinovea you will be able to select the stream format, the resolution and framerate. Resolution and framerate option availability depends on the stream format. Set the format to "MJPEG", this way the video will be compressed directly on the camera and the bandwidth to the computer will be much reduced, allowing to choose the top resolution/framerate combo without frame drops.

The PS3Eye has a really low resolution, I wouldn't recommend it in 2018. Some of the Chinese cameras can be interesting but I don't think they have anything above the flagship Logitech if you are looking for top resolution/framerate.

Go to forum: Cameras and hardware

733 Reply by joan

(1 replies, posted in Bug reports)

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.

Go to forum: Bug reports

734 Reply by joan

(16 replies, posted in Cameras and hardware)

Thanks for testing!

The recording should happen at 120 fps in the sense that all the 120 frames are put into the file per second, however the final video file is marked as 30 fps for replayability purpose. So the final file should look slowed down four times if you play it at 1x speed. This is triggered for any camera feed above 100fps.

There is no setting to change this at the moment. Although you could force it back to 120fps upon reopening by going to Video > Configure video timing > Video framerate.

Go to forum: Cameras and hardware

735 Reply by joan

(3 replies, posted in General)

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.

I need the angle value when the leg is in 6 oclock

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:
http://www.kinovea.org/screencaps/0.8.x/cyclist-tracking.jpg

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:

http://www.kinovea.org/screencaps/0.8.x/cyclist-angle-angle-diagram-500.png

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°.

Go to forum: General