What is the fastest way to update overlaid graphics in a video?

1 visualización (últimos 30 días)
Suppose you are given a 4D image array (I), where size(I,4) equals the number of frames in the image sequence. You also have a cell array (C) of centroids and radii for detected circles in a given frame. So, for instance, C{i} is an M-by-3 array of M detected circles in the ith frame.
What is the best way to render the detected circles while viewing the video, frame by frame?
I should mention that this will be embedded in an app that I am creating for tracking objects. My current approach is as follows:
  1. I create a patch when the app is instantiated that has no visible faces or vertices.
  2. When the frame changes, I compute the correct faces and vertices for the corresponding cell in C, and then update the patch using:
It works ok, but it is slow if the number of detections is large (1000+ circles in an image). Would it be faster to draw each circle as its own graphics object instead of one patch object? My concern there is that the number of objects will likely change from frame to frame, so the number of graphics objects I will need is variable. Or would it be faster to overwrite the image with the detected objects (i.e. insertShape)?

Respuesta aceptada

Mike Garrity
Mike Garrity el 8 de Mzo. de 2016
Editada: Walter Roberson el 8 de Mzo. de 2016
Actually, it sounds like you're probably up against this case:
But there are a lot of great suggestions in the comment thread on the post that Walter linked to.
I'm basing my guess on the fact that you said that the performance is a function of the number of circles. A graph like the ones I used in this post might be helpful in isolating the cause.
  5 comentarios
Mike Garrity
Mike Garrity el 8 de Mzo. de 2016
In general, modifying the properties of an existing object is going to be faster than creating a new object.
That's a bit of an oversimplification, and you should always profile both approaches if you're in a situation where you're going to be very performance sensitive.
The polygon thing is a bit of a special case. When you change the Vertices property of a patch object, it doesn't know whether it can reuse the old triangulation, so it does it from scratch. If you know that you haven't changed the topology of any of the faces, then you can score a win by using the triangulation.
Another thing to watch out for is the case where you're only changing a tiny part of your object. Imagine you had thousands of polygons, and one of them was moving around. If you stick them all into the same patch object, then MATLAB is going to retriangulate all of the faces and send all of the triangles to the graphics card. In this case, you can do much better by splitting it into two patch objects. Put all of the "static" faces in one, and all of the faces that are changing in the other. That way the big "static" patch will get parked in the memory system of the graphics card, and just the tiny "varying" patch will get pushed across the interconnect each frame.
Matthew Eicholtz
Matthew Eicholtz el 8 de Mzo. de 2016
Thanks for all the help. Big fan of the Graphics blog...looks like I need to add it to my bookmarked pages.

Iniciar sesión para comentar.

Más respuestas (1)

Walter Roberson
Walter Roberson el 4 de Mzo. de 2016


Más información sobre Computer Vision with Simulink en Help Center y File Exchange.

Community Treasure Hunt

Find the treasures in MATLAB Central and discover how the community can help you!

Start Hunting!

Translated by