It looks like you're taking input that's meant to be RGB and treating it as RGBA (32-bit bitmap instead of 24-bit).
Jerry Coffin
2010-03-26 01:55:25
A:
+1
A:
One of the most common causes of the left image is a buffer that is not properly aligned.
I believe Windows expects a DWORD aligned buffer.
One issue I see with the above code is that you do not want to use winRowSize to copy the actual pixels, you want to use a variable with the (width of the image * bytes per pixel). winRowSize copies the DWORD aligned size which is probably too big (although some images may work as they fall on DWORD alignment by default.)
Change the for loop:
for(i = 0; i < (width of the image * bytes per pixel); i++){
rawImage[location++] = row_pointer[i];
}
(You may also have to adjust the rgb to bgr code.)
You beat me by 1 minute but you forgot to mention that DWORD alignment is needed for each row not just for the beginning of the buffer.
Windows programmer
2010-03-26 01:58:39
Thanks for that catch, But that didn't solve my problem.
zipcodeman
2010-03-26 02:25:12
Thank you. I fixed the RGB/BGR converter.
zipcodeman
2010-03-26 02:32:15
Instead of converting the entire image from rgb to bgr, try doing it per scanline and again use (width of image * bytes per pixel). Once that's done if it still doesn't work, try posting your modified code.
2010-03-26 02:33:07
Ok, glad to see it worked.
2010-03-26 02:35:12
A:
Maybe you forgot to pad each row of pixels to occupy an integral number of DWORDs.
Windows programmer
2010-03-26 01:57:40
I did that. It helped with each line being shifted over, but not the color problem.
zipcodeman
2010-03-26 01:59:58
A:
maybe the problem jpeg is not is rgb, but is cmyk instead (or even grayscale). not all jpegs are rgb.
PS, (yes I know jpegs are not actually rgb - are yuv instead, just trying to keep this answer simple)
steelbytes
2010-03-26 02:11:16