Search options (Page 20 of 137)

Yes it should be possible and useful. Probably to be grouped with the "go to key image" menu. Somewhat related to this I recently fixed a bug where copy-pasting objects to a different time wasn't working. Now it will create a new key image and paste the drawing into it. "move to current time" would be equivalent to cut and paste.

Another thing I looked into a while back is the stacking of objects. It would be nice to be able to say "send to the back" / "move to the front", etc. when drawings are overlapping. This is easy with just one image but on video with objects belonging to different frames it's not as trivial.

(By the way I'm currently super busy at work, I won't be making progress on any of this for a bit. But this feedback is very appreciated.).

Something that might happen is that a Windows update somehow changes the driver to a newer version from Microsoft and breaks some features. I have had that happen with other cameras. Check in the device manager if the button to restore the previous driver version is enabled.

It sounds more like a software bug. I'll look into it.

I haven't come across this issue. The video export was rewritten and maybe this is what introduced it. One major change is that the video is now exported at the original image size, where it was exported at the display size before. So for large image size this may make the export longer.

I still want to have a system to choose different export formats for web vs archiving as soon as possible but it's a bit of a big undertaking.

I've never formally tested the max throughput of the IP camera module. The low level code for this is coming from an external library, there might be a couple of extra buffer copies that could be factored out by rewriting it. I don't know if that's the culprit though.

Once the buffers are captured they go through a pipeline that is shared with the other camera types and this is known to support this kind of speed so the issue is probably somewhere before that.

If you film a high precision stopwatch, can you figure if the lost frames are happening at random intervals or if they are bunched together, like a whole chunk missing at once?

As an experiment you could have the server on the same machine and capture through the loopback, see if you still get the limit.

Another feature of the Distance grid tool is that it lets you reverse the X axis direction and anchor the origin at the bottom-right. This can be useful for measuring things going right-to-left. I'll try to get all of this in the normal grid.

edit: actually this can be done by manually flipping the grid.

Another way is to have a second way of entering the calibration grid dimensions, instead of entering the sizes of the sides, to enter the coordinates of the bottom-left and the top-right corners. If the user chooses this way we calculate the sides and the offset from the entered values. (In theory this could be an aribitrary quad but it makes things simpler to force a rectangle).

That was kind of the direction the Distance grid tool experiment was going. But now I think this tool won't be necessary anymore, if the offset can be set up on the normal grid. Then the distance line can become a display option (and it can have a vertical distance as well).

The link to meta ai tracking project is super interesting. When the basic camera motion integration is done I want to look into connecting machine learning algorithms more easily. There is so much to leverage, super-slow-motion, pose estimation, background/foreground segmentation, image stabilization…