🚀 go-pugleaf

> Could you do a test to see what the impact on performance is by statement
>
>   int iGrey = b*0.11 + g*0.59 + r*0.30;
>
> Just make it int iGrey = 111; // value does not matter.
>
It maked maybe a single frame extra (faster) per second.


> Think that those three multiplications are a performance break.
>
> If so than there are possibilities.
>
Maybe its folish of me to first convert the JPEG stream to RGB24 with the 
TJPEGImage component and then greyscale convert it to 8 bit. Two complex 
algoritms that should be taken care of after the capture and not in the 
callback routine.
Unfortenly my boss incists in the realtime conversion.

>> Is it for example possible to set the bit depht and greyscale directly in 
>> the JPEGImage component and would it be faster?
>
> Don't know that much about that. You better start a new thread in
> borland.public.cppbuilder.graphics where you post your problem.
I'l try to post a question there, thanks Hans.

>
> Please do the test. Could you spend an extra 16MB for a table ?
>
Memory is not an issue here
I already using:
struct CAPIMAGE
{
  DWORD dwTime;
  BYTE Data[CAMRESX*CAMRESY];     //640x480
};

pImages  = new CAPIMAGE[MAXIMAGES];    //MAXIMAGES=50

BYTE* pData8Out = pImages[iIndex].Data;

This is my capturebuffer where I store the captured bitmaps. After the 
capure I do my imageprocessingstuff where i measure and so on.

The only things that do matter is speed. Most of the customer want to see 
what happens under the first second from the impact.

Ok, the speed is not so bad. The old system with the bitmapcamera could 
process 15-16 fps. Now with the decoding of jpeg it processes 13-15 fps. The 
problem is that, my boss do not accept to go under 15fps processing and the 
old bitmapcamera is discontinued by the manufacturer.

Hard life for a simple programmer.

reg/
PFa