Reaper Imgur Compression

Before we've got the Tece original file, I was looking to reverse enginer the process by putting the original reaper img on imgur. The idea was to get a similar file to compare with.

Got a promising start, visualy, comparing the img as text file the header was similar.
With tool like JPEGsnoop, the first MCU was at the same adress (0x1C50). But where the first visual change happen MCU[146,21], those adresse wasn't the same. Bliz:0x1387C7 Tece:0x138A25

I've start to look at difference starting a the first MCU[0,0] and a long stream of difference have start at 0x38B6. Classic datamosh should not produce those king of difference.

So, I've start looking to the Binary stream. I've found that, from the start of the difference, if you replace the next 11 byte [10000000010] by [01], all the other byte align.


Adress:        0x38B5  0x38B6  0x38B7  0x38B8  0x38B9  0x38Ba  0x38Bb  0x38Bc  0x38Bd  0x38Be  0x38Bf
Blizzard-Imgur 0100111111111110100101111101011111001001111011001111110110111101010011000011100011101100
               |       |       |       |       |       |       |       |       |       |       |
Tece-Imgur     0100111111111111000000001000101111101011111001001111011001111110010011001010011000011100
                           ->|10000000010|<-
Tece-Imgur     010011111111111           00101111101011111001001111011001111110010011001010011000011100
Blizzard-Imgur 01001111111111101         00101111101011111001001111011001111110110111101010011000011100011101100
                              ??|-shift->