Products > Programming

you have raw bytes: how to understand the used lossless algorithm?

(1/7) > >>

DiTBho:
so, yesterday I found a source shooting two packets of 500K raw byte each ever 208 seconds
I am 100% sure
1) they are not encrypted
2) they are lossless images
3) 24bit color, 3 byte per pixel
which is good, but ...

how to understand the used lossless algorithm?  :o :o :o

AndyBeez:
Any more clues? A RAW image stream off a CCD is lossless. So too is Windows BMP. In what context is the image data? Is it a TS transport stream?

DiTBho:

--- Quote from: AndyBeez on June 14, 2022, 04:52:31 pm ---is the image data?

--- End quote ---

image data

DiTBho:

--- Code: ---0x00, 0x00, 0x00, 0x00, 0x00, 0x01, 0x00, 0xFF, 0x00, 0x01, 0x00,
0x01, 0x01, 0x00, 0x00, 0xFF, 0xFF, 0x00, 0x00, 0x00, 0x05, 0x01,
0x01, 0x03, 0xFF, 0x00, 0x00, 0x03, 0x01, 0x00, 0x01, 0x01, 0x00,
0xFF, 0x00, 0x00, 0x01, 0xFF, 0x01, 0xFF, 0x01, 0x00, 0x00, 0x02,
0xFF, 0x00, 0x00, 0x00, 0x01, 0xFF, 0xFF, 0x00, 0x00, 0x00, 0x00,
0x01, 0x01, 0x00, 0x00, 0x01, 0x00, 0x00, 0x00, 0xFF, 0x01, 0x00,
0xFF, 0xFF, 0x01, 0x01, 0x01, 0x00, 0xFF, 0xFF, 0x00, 0x00, 0x03,
0x00, 0x00, 0x00, 0x01, 0xFF, 0xFE, 0x00, 0x00, 0x01, 0xFF, 0x01,
0x00, 0x01, 0x00, 0xFF, 0xFF, 0x01, 0x00, 0x00, 0x02, 0xFF, 0x01,
0xFF, 0x00, 0x01, 0x00, 0x01, 0x00, 0x00, 0x01, 0xFF, 0xFF, 0x00,
0xFE, 0x01, 0x00, 0x00, 0x00, 0x01, 0x00, 0x01, 0x00, 0xFF, 0xFF,
0x00, 0x00, 0x00, 0x00, 0x01, 0x00, 0x01, 0x00, 0xFF, 0xFF, 0x00,
0x01, 0x00, 0xFF, 0x01, 0xFE, 0x00, 0xFF, 0x00, 0x00, 0x02, 0x01,
0x00, 0x00, 0x00, 0xFF, 0xFF, 0x01, 0x00, 0x00, 0x05, 0xFF, 0xFF,
0x00, 0x00, 0x00, 0x00, 0x01, 0x00, 0x00, 0x00, 0xFF, 0x00, 0xFF,
0x01, 0x01, 0x00, 0x00, 0x01, 0x00, 0xFF, 0x00, 0x01, 0x01, 0x00,
0x00, 0x00, 0x01, 0xFF, 0x01, 0x00, 0x01, 0x01, 0x00, 0x00, 0xFF,
0x01, 0xFF, 0x00, 0x00, 0x01, 0x01, 0x01, 0x01, 0x00, 0x00, 0x00,
0x01, 0x00, 0x00, 0x00, 0x01, 0x00, 0xFF, 0x01, 0x00, 0x00, 0x00,
0xFF, 0x00, 0x00, 0x00, 0x01, 0xFF, 0x00, 0x00, 0x00, 0xFF, 0x00,
0x00, 0x00, 0xFE, 0x01, 0x00, 0xFF, 0x00, 0x01, 0x00, 0xFF, 0x00,
0x01, 0x00, 0x01, 0x00, 0x01, 0x01, 0x00, 0x00, 0x00, 0x02, 0x01,
0x00, 0xFF, 0x00, 0x00, 0x01, 0xFF, 0xFF, 0x00, 0x00, 0xFF, 0x00,
0x00, 0x05, 0x02, 0x01, 0xFF, 0x01, 0xFF, 0xFF, 0x00, 0x00, 0x00,
0x01, 0x01, 0x01, 0x00, 0xFF, 0x00, 0x00, 0x00, 0xFF, 0x00, 0x01,
0x01, 0x00, 0xFF, 0xFF, 0x01, 0x00, 0x00, 0x00, 0x01, 0x00, 0x00,
0x00, 0xFF, 0xFE, 0x00, 0x00, 0x01, 0xFF, 0x00, 0xFF, 0x00, 0x00,
0x00, 0xFF, 0x00, 0x00, 0x02, 0xFF, 0x00, 0x01, 0x01, 0x00, 0x00,
0x00, 0x03, 0x01, 0xFF, 0x00, 0x01, 0xFF, 0x01, 0x00, 0xFF, 0x01,
0x00, 0x00, 0x00, 0x01, 0x00, 0xFF, 0x00, 0xFF, 0x00, 0x00, 0x04,
...

--- End code ---

This is how it looks  :o :o :o

AndyBeez:
Strange indeed. All I can 'suspect' is the 0xFF is some kind of control byte that terminates a data group.
Syntax wise: { [byte]... 0xFF }...

But how it maps to pixels, I have 0.0 idea?

Navigation

[0] Message Index

[#] Next page