Hello everyone,

There seems to be an issue with some (all?) IDS camera and slow startup time. Looking for more data about this.

When opening the program on the camera tab, how long does it take for your IDS cameras to fully show up?

I have a small USB 2.0 "UI1220LE" and based on the logs it already takes about 300ms. But I have received logs of people where the high-end cameras are taking multiple seconds.

Data I've gathered so far:
- UI1220LE: 0.3 s.
- UI3240LE: 1 s.
- UI3140CP: 4 to 5 s.
- UI3160CP: 5 s.

I don't reproduce this with other machine vision cameras so I'm wondering where the problem might be coming from and if it could be mitigated. We've already ruled out the "USB selective suspend" option in Windows power settings, we still get the same lengthy initialization with the option disabled.

Do you have similar slow startup times with high-end IDS cameras (multiple seconds)? Is it the same in uEye Cockpit?
Thanks

Great! What was the name of the software? Maybe I can reproduce the crash and see if anything can be done about it.

528

(11 replies, posted in General)

The requirement here if I understood correctly is to have a single instance of Kinovea with a single screen inside, and to switch between capture and playback, to minimize resources consumption.

529

(11 replies, posted in General)

Yeah, at the moment I don't have a good idea on how we could do this nicely.

One idea maybe would be to have a command that starts a playback screen on whatever is the most recent entry in the capture history. Then you could close the capture screen and use this command. To reload the camera afterwards would require the workspace function to work at any point in the life cycle of the application instead of just the startup.

530

(11 replies, posted in General)

No, it is not expandable unless the source code is modified. The underlying mechanism is "commands" and the shortcuts are bound to commands.  The preferences.xml file defines the mapping between commands and shortcuts. In order to add a new shortcut there first need to be a existing command. A command does not necessarily have a corresponding shortcut bound to it.

What is the action you wanted to do via a keyboard shortcut?

Yes. This should be fixed in the next version.

Allow me to clarify what is happening. In previous versions the direction of the calibration line was completely ignored, and the coordinate system was always aligned with the image axes. This was a bit restrictive, if the camera was rotated a bit you couldn't really get vertical or horizontal coordinates in world space, they were always aligned with the rotated camera. We had to use the plane calibration to work around this limitation.

In 0.9.3 the line direction is used as the horizontal axis. This way we can have a rotated camera and still get coherent coordinates. But as you noted this is not always desirable.

In the next version when you define the scale of the line you also tell if this line is along the horizontal axis, the vertical axis, or if its direction should be ignored and the coordinate system should use the image axes.

532

(5 replies, posted in Cameras and hardware)

Try version 0.9.3 if possible, there is a new recording mode and more improvements.

When you press the red record button it records the video using the mode set in Preferences > Capture > Recording. This defines if delay is taken into account or not and whether the recording is done on the fly or not.

It decides to compress the video or not based on Preferences > Capture > General. Depending on the speed of the storage medium and the CPU one option might be better than the other. If you have an SSD with room to spare you can try recording without compression.

If the length of the recordings fit in the delay cache you can try the Retroactive recording mode. In this mode it stores the frames in memory until the the recording operation is over and then compress/save all at once, this avoids dropped frames.  You can change the size of this cache in Preferences > Capture > Memory.

533

(5 replies, posted in Cameras and hardware)

Hi,
Please add more details:
- Which version of Kinovea?
- What camera settings ? (stream format, image size, framerate)
- Which recording mode are you using?
- Are you saving compressed or not compressed?
- What is the storage medium SSD, HDD, is it the location as Windows system?
- What value do you see for "Load" in the infobar? Does it go over 100%, what about the drop counter?

Ouch, these exceptions are happening in very deep and low level parts of the code… What kind of computer is it?
I'll leave the capture running overnight to see if I can reproduce any spurious crash.

No it's all the logging there is… What kind of camera is it?

536

(1 replies, posted in Cameras and hardware)

Double check the exposure time in the camera configuration dialog, maybe it is so low that everything is dark and you can't see anything. If it's not that it's probably a bandwidth or current bottleneck. Do you get an image in Zoom/Skype or other software using the camera?

Hi, I don't think the MER-160 exists in GigE / Ethernet variant, only USB3.

Usually when cameras works independently but not simultaneously it's a USB issue. They either want to draw more current than possible or want more bandwidth than available.

It's not that easy to diagnose, sometimes all the ports on a laptop end up in a single USB root hub. There is a tool called USB tree view or that let you see the USB hierarchy and which ports ultimately end up in the same root hub and have to share resources. https://www.uwe-sieber.de/usbtreeview_e.html

539

(2 replies, posted in Bug reports)

Hi,
Yes this is the way it currently works in 0.9.3.
The "saving last configuration" you read was probably about the fact that the camera options themselves, like exposure time, framerate, etc. should be restored when you reopen that particular camera.

For the next version there is a concept of "workspace" that will contain the screen arrangement and content. Each instance can have its own workspace and will start up on this arrangement. Maybe later there will be a different or related function to save and restore the state every time but first I will want to get some feedback on that workspace feature.

No worries. This particular UI change has confused a lot of people. I'll try to add back a way to select the camera from the configuration dialog when the screen is empty or at least put a message box explaining the new way to open cameras.