Originally Posted by DeReader
Pauli and TGS, thanks for testing this! So it is an issue with the current firmware.
It is, in fact, an issue in the Adobe renderer used in the 1.0x firmware. The upcoming firmware has a newer Adobe RMSDK implementation which displays the image correctly.