Colour Screen Out Of Resources

[geeland]

Hi,

I am having some issues with my screen. I am constantly recieving error messages and the screen freezes and re-boot. The messages are below.

Exception 'EOutOfResources' in module Homegate.exe at 00030A58 Out of System resources.
Module: Graphics, Source:Graphic.pas, Line 2522
Procedure: Out of Resources

and

Application Error
The exception unknown software exception(0x0eedfade) occured in the application at location 0x7c81eb33

My log file states I have 18M of free memory.

Does anyone know whats going on.

Regards,
Grant Franklin

[Darren]

This is a problem which occurred with the early Colour C-Touch software. An update was done years ago which mostly fixed this. When HomeGate starts up, please check that you have Windows NT 5.1.2600 Service Pack 2. If not, you will need to get an update card from Clipsal.

The other likely possible causes are:
1. Problems with an HTML component displaying a web cam or web page
2. Lots of images

Are you using HTML components or lots of images?

How long does it take for the Colour C-Touch to stop operating?

[[IL]NewGen]

i've also found that image sizes & image formats play a role with mem usage too so try and resize and format to jpeg wen ever you can.

This is also a problem with CCTV feeds from Network output boxes, too many and outputs displayed or not rescaled will rack up resources too:p

[geeland]

Thanks guys,

I assumed this would be the issue. I have 30 photos as screen savers and various wheather displays and music displays. Can you get larger memory capacity flash cards for the screens.

Regards,
Grant Franklin

[ashleigh]

Something commonly done with images is to load em in and let the CTC re-scale them to fit the screen size.

eg - image from digital camera at 2000x1500 pixels.

This works but it is a massive resource pig. Even though the file might be JPEG and compressed and only a Mbyte or so - the picture DOES have to be uncompressed before display.

So using that example above, the picture will consume 2000 x 1500 x 4 bytes of memory (the x 4 is because pictures use 24 bit = 3 byte colour, but this should be rounded up to the machine word size (4 bytes)). So that picture uses 12 MILLION bytes of ram.

Then it has to be rescaled to suit the display - down to 640 x 480 pixels (again 4 bytes per pixel) - this time its 1.23 million bytes. But both copies are floating around in RAM for a while.

So rescaling that picture will consume around 13 to 14 Mbytes of available RAM when it is done dynamically (and it will be slow).

If you use something like PICASA from Google (which is free) to resize the pictures (irrespective of how they are loaded / displayed / served / whatever) then no resize is needed. Performance is faster, and the amount of processing resource consumed to make it appear is dramatically less.

[Darren]

If you use something like PICASA from Google (which is free) to resize the pictures (irrespective of how they are loaded / displayed / served / whatever) then no resize is needed. Performance is faster, and the amount of processing resource consumed to make it appear is dramatically less.

You can do it from within PICED by selecting the Tools | Images | Rescale All Images menu item.