Search options (Page 38 of 129)

Things to test: right click on the camera thumbnail and do "Forget custom settings".
If that doesn't work, go to Help > Open log folder then go in CameraProfiles and IDS and delete the file there.
Did you plug them back in the same USB ports? It's best to use ports that are on different USB root controllers so each can have the full bandwidth and power.

No it's probably a regression.

Please provide as many details for reproduction: what is the size of the original video, does it fit freely in the screen before the bug or is it forced to fit? Is it forced under its original size? Are you applying rotation manually? Is Kinovea applying rotation automatically? (check the image rotation menu), Do you get the problem with other videos, if not what is different?

Thanks

When you click the "Manual connection" button the dialog window has fields for user and password.

In the end these get added to the URL like this: http://<user>:<password>@<ipaddress>:<port>/<resourcelocation>

Thanks for the extensive feedback! To address some questions (the easy ones ):

Bandwidth here is the bandwidth between the camera and Kinovea. It depends on the image size, framerate and stream format. If the camera is configured to stream MJPEG directly, it will have much lower bandwidth. Maybe the ELP camera was configured to send uncompressed frames?

It should not take 10 seconds. Thanks for reporting this (people might not know what to expect so these types of issues are under-reported).

The first cold start takes about 3 seconds on my machine and the second start about 1.5s. The difference is the .NET framework being already loaded the second time around.

If you open the log, you will see each line starts with a number, it's the time in milliseconds since the start of the program. Can you send me the log or identify if there is a big jump in time and paste the surrounding lines? You have to scroll to find a start point. The first line says "xxx - DEBUG - [Main] - PreferencesManager - Importing preferences." and the first timestamp should be under 500ms.

I am not sure if that's what you are looking for but if you double click the image it will try to fit to the display area.

I'm not sure to understand what you mean. Can you elaborate?

Yes this depends on the camera. It should be shown as "exposure". It should be available on the ELP and the other one, as well as Basler and IDS cameras. Depending on the camera API the number will be in milliseconds (time the shutter stays open) or an arbitrary number.

I plan on looking into rotation of the camera stream shortly. I think 180° should be trivial because it doesn't change the aspect ratio. We'll see about the implications of the sideways rotations. (rotating the image is simple but then it breaks features that assume the image size is the same as the source…)

And just today they released Pylon 5.2.0. Release notes: https://www.baslerweb.com/fp-1551786538 … otes~1.txt

It's not binary compatible with previous builds so Kinovea users should not update yet.

I'll double check with the newest Pylon to see if that could be the issue. I had initially tested 0.8.27 with a Basler camera and knows at least one other person for whom it worked. So it might be context specific. (Version I currently have on my machine is 5.1.0.12681).

Can you double check that you have the Basler runtime in your Path variable?
During installation make sure the option pylon C .NET Runtime is checked, under pylon Runtime option group. You may have to use the "Custom" install profile to be able to select that option.

edit: I realized you are using Pylon 5.0.x. Kinovea has to be built against a specific version of Pylon as they change their API. So please install Pylon 5.1.x if possible, and see if it works with 0.8.27.