7 Oct
2012
7 Oct
'12
12:28 p.m.
Also there is an off-by-one bug in checking hashes
where it does not find the last j2c file -- at least in the case of a "range"
job. Has 00000000.j2c upto 00000479.j2c in <output>/<...>/j2c/, wants
00000480.j2c.
Sorry, bad english day. What I meant to say: 0.54 handles the sequence in j2c/ correctly,
meaning there is are md5 values computed for all files -- 00000000.j2c through to
00000479.j2c.
But it mistakenly expects a 00000480.j2c (for a range job of first 480 frames) which is
the off-by-one.
Wolfgang