Search options (Page 5 of 136)

Yes the pattern should cover about a quarter of the frame. This is just a rough guideline, it will work even if it's not exactly that. You can have other things visible in the frame.

It should be moved around to cover the sides and corners of the frame, but not go partially outside, all the inner corners between the squares should be visible at all time. It can be tilted / seen in perspective.

The code internally uses OpenCV for this so you might find other guides online searching for OpenCV camera calibration.

Re: Kinogram mode. Yeah unfortunately at the moment this mode is still bound by the aspect ratio of the original footage. The initial values for the number of rows and columns and the crop rectangles default to the last ones used so it sometimes looks wonky or super small with empty space both at the top/bottom and on the sides. The export will crop out the empty space and can be larger. I tried to auto-rotate the canvas by 90° at some point but it caused other issues.

For now if the original footage is in portrait mode you might find it better to change the grid to something more appropriate, like 3x4 or something. Apart from that it should work the same.

Yes this behavior is intriguing I'm very interested in understanding exactly what is going on. You can send it by email: joan at kinovea dot org.
Thanks.

I agree, yeah this difference is a long standing issue, but not easy to fix. Attempted the refactoring a few times.

The other aspect where this is limiting is that you can't have drawings go outside the video rectangle in the player, whereas in the capture screen you can, for example a corner of a perspective grid may be out of view.

Oh I see, you are using a single instance of Kinovea and alternating between a capture screen and a playback screen, correct?

It does save the capture folder, even between sessions, but when you open a new capture screen in the instance it starts from the default state (actually even this should work but I think it's because of opening a player screen in between that it lose the capture screen info).

The new workflow is that you would use a dedicated window for capture, and a different one for replay. Doing this it will remember everything, the camera, the capture folder, the position of the window, etc. It will be ready to go as soon as you start.

Same for the replay, the window will remember the observed folder, the playback speed, etc. Typically if you have two cameras and two replay you would have 3 windows, two capture and one dual replay. It's better to save to different directories otherwise the automatic replay can't tell which file to load. The replay window will also automatically bring itself to the foreground when it loads a new file.

If you are using version 2025.1 you now need to manually enable the debug logs from the help menu in order for it to produce all the logs.

Apart from that I don't know. The fact that it can get the thumbnail sounds encouraging, it means it managed to connect to the camera and grab a frame. When it opens the capture screen it does more stuff to get the current values of the properties like stream format, image size, etc. maybe something happens there that causes the failure, but that should be caught by exception handlers. 

One issue I have seen with GigE cameras is when a VPN is installed on the computer, sometimes that trips the driver when it enumerates the interfaces.