Forums > MaxMSP

lcd object and performance

March 7, 2010 | 7:22 am

I am drawing a 3D cube using the lcd object (projected to 2D of course). The orientation is updated by polling the serial object at regular time intervals. Since each update includes many ‘moveto’ and ‘lineto’ commands, the cpu usage gets close to 50% occasionally. In addition the size of the lcd object also matters – the cpu load gets higher as the lcd object is being set larger.

I thought that using qmetro instead of metro (for polling the serial object – that’s the only metro in the patch) will help reduce the cpu load, but it doesn’t. Two quations:

1. Why the qmetro dosn’t seem to make any difference?
2. Is there another solution to reduce the cpu load (besides the obvious of using larger time intervals between polling events)?



March 7, 2010 | 7:22 am

March 7, 2010 | 9:32 am

You have most likely a graphics card capable of OpenGl.
There are two ways to use it in Max. The first is Jitter, the second is a jsui. Doing it by hand with drawing into a LCD is just overkill, let the graphics processor do the main work…


March 7, 2010 | 9:39 am

I’ll give it a try… Thanks!

March 7, 2010 | 11:48 pm

if you are using a lot of uzi to draw, [defer] might make a difference.
there is also a lighter version of uzi, which i just can’t recall the name…

March 8, 2010 | 12:38 am

unless i’m gravely mistaken, jsui can do openGL, but will only do it in software. is this wrong?

March 8, 2010 | 2:32 pm

That’s correct. Although you can use js to program your jitter patches.

Viewing 7 posts - 1 through 7 (of 7 total)

Forums > MaxMSP