Uncommon DPX version string is changed in a risky manner

[JeromeMartinez]

DPX spec is not precise, and stipulates "V2.0" for a 8 byte field.
Most DPX encoders put 0x00 bytes for the 4 last bytes, but some others put 0x00 (so the string is null terminated, and it is read as such pas decoders) but some others put e.g. 0x00 0xFF 0xFF 0xFF.
When the file is saved by embARC, the field becomes:

• "V2.0�." with the version on LoC website
• "2.0[0xf" with the version we compile with modern Java

Both may lead to a file not well read by decoders.