I was wondering if anyone has come across "streaky" artefacts whilst displaying .bmp images? I've included a sample of the image being displayed through an IDE and also being played through VLC player; each show the same error, but in different locations. Has anyone seen this before? And if so, does anyone know the cause?Attachment 10992
Thanks for your help
Looks like the BMP header is reporting the wrong size for the image...
I'm not using the header. The IDE just uses pixel values to display data. I've had a play with some parameters and it's looking like the number of bytes used for each pixel affects the output. The encoding (from the header) is 24bpp, so by changing the number of pixels in a row to 3 x rowlength, I get more clarity. I'm about to test with just one byte and see what happens. Cheers!
Yeah it was the padding for each row that introduces that effect. Just have to skip the padding; I used fseek but a better way might exist.