simple [panel] question

Aug 10, 2009 at 3:32am

simple [panel] question

hi all,

something I’ve been wondering for a while.
In regards to using the [panel] to facilitate UIs,

How much is too much before the behavior is affected.
The scheduler has to redraw each [panel] everytime. So basically behavior accuracy decreases. right.

Over time I have gotten into the habit of using UI objects a least as possible. < -I have seen obvious differences in behavior and even less crashes too.

Again, when I get into really big patches I want to save on CPU scheduler etc… as much as possible . So how demanding is the [panel] object.

Should I try avoiding them as I have w. other UI.

thanks a lot

phil

#45058
Aug 10, 2009 at 4:37pm

you are not saying what you are doing, i assume you change the
color of [panel] and/or resize it.

the main CPU hog here is probably not only the panel drawing
itself, but the other parts of your patches – for example the
use of messageboxes (bad!) or numberboxes (bad!) to store
values for you panel.

i dont know offhand if [lcd] or a pictureslider would be more
efficient as i dont know your patch.

#162363
Aug 10, 2009 at 5:43pm

hi Roman , thanks for the reply.

>>you are not saying what you are doing, i assume you change the
color of [panel] and/or resize it.

It is not for a specific patch, just every patch in general.

In my patches, I use it as a light square colored shade behind patch module that have a specific function. < - it facilitates the eye when performing.

But as you said, UIs take away the juice and since my patches do quite a lot I want to use as little UI objects as possible.

So yesterday while building a patch , I was wondering how heavy panels were. < - Again , they are practical for the eye.

Does color change anything on CPU? I mean for the computer it’s just values. White 1. 1. 1. Black 0. 0. 0.

But the fact that it has something more to draw every cycle,< - well how expensive is it. I mean it's not a [number] <- that is moving <- or does (changing values change anything) or as you said a [message] to store stuff.

thanks for the info.

phil

#162364
Aug 10, 2009 at 8:15pm

Thanks Rabid,

That’s all I wanted to know and thanks for the link

phil

#162366
Aug 10, 2009 at 8:35pm
phil hughes wrote on Mon, 10 August 2009 19:43
Does color change anything on CPU? I mean for the computer it’s just values. White 1. 1. 1. Black 0. 0. 0.

thats true, but in max many things – [panel] for example –
have to be calculated by the CPU, an not by the graphics
card, like in some jitteer objects or your favorite ego shooter.

so in fact the computer has to handle “1. 1. 1.” for every pixel,
in a panel of 1000*1000 pixels that makes a million times
“1. 1. 1.” – around 10 mb of data have to be written to a
register and then read again in order to send them to the
video card.

in some situations things only have to be calculated when
they are “seen”, in some situations things run completely
on the graphics card. but for [panel] you can be sure your
PC have to handle each byte of it.
and while it is busy with sending “1.” to panel via numberbox
and messagebox no other process (like playing a note in max,
but also like displaying html in safari) can be done.

-110

.

#162367
Aug 10, 2009 at 9:38pm

Thanks Roman,

If I understand what your saying correctly, then there is no difference between black and white. The computer has to write value. < - So more more precisely , no matter what color, the computer has to write it. I mean it's not more work depending on the color.

Again, i only use these for background purposes.

thanks for the info.

phil

#162368
Aug 11, 2009 at 1:34pm

Hi Phil.
As stated before, I wouldn’t worry too much with static panels, really (even though I would instead use [bgcolor] for that matter).

Cheers,
_y

#162369

You must be logged in to reply to this topic.