maximum dirty region count

Question

See generated codes for RGBA8888 package, number of dirty regions between frames is limited to 4.

Is that somehow configurable?

We got a OSD full of small widgets scattered all around which update at quite high freq, it would be great help if we could increase this number a bit.

Answer 1

Hello,

the management of several update regions was introduced to reduce the necessary update areas to a minimum. However, in order to reduce the overhead that is caused by comparing several areas and by building unions - the number of update areas have to be limited.

The number of update areas was choosen as a kind of trade-off or best compromise and it is not configurable.

If you have many different widgets that will change their content, it is no problem to update them with the current setting - at the end the entire screen update will be synchronized by the display sync.

Best regards,

Manfred.

Comments

Hello,

I agree that the result will be correct. However the performance denpends on the scenario.

We got a big resolution screen, displaying OSD containing many small constantly updating widgets. Will that probably result in unexpected union of 2 rects far from each other if the maximum number of dirty rect is small?

Unfortunately, we got a low end CPU running GUI, on which we may want run GUI in full fps in case update areas are small enough.

Is there any way to overcome that?

---

Hello,

each rectangular area that requests an update is compared with the current dirty rectangles in order to build small areas. Of course, it is the goal to build minimal areas. This is the reason why the number of areas is limited - to avoid that building the smallest areas takes too much time.

Can you provide some information about your system and share some screenshots of your GUI? Maybe there are some ideas for optimization.

Best regards,

Manfred.