2 Oct
2012
2 Oct
'12
3:53 p.m.
Hi all,
DVD-o-matic version 0.54 is available from:
http://carlh.net/software/dvdomatic/download.php
This release fixes 3 bugs; a crash on encoding, a duplicated scan of
thumbnails, and bad audio-video sync when encoding 23.976
frames-per-second content.
Have fun
Carl
7 Oct
7 Oct
12:19 p.m.
Carl,
apparently 0.54, when transcoding to j2c (21303 frames source video, selected first 480
frames in "Range") reports remaining time as if it were about to transcode the
whole film.
Percentage done, however, is correct -- as expected in relation to the selected range.
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.
Best, Wolfgang
On 02.10.2012, at 17:53, Carl Hetherington wrote:
Hi all,
DVD-o-matic version 0.54 is available from:
http://carlh.net/software/dvdomatic/download.php
This release fixes 3 bugs; a crash on encoding, a duplicated scan of thumbnails, and bad
audio-video sync when encoding 23.976 frames-per-second content.
Have fun
Carl
_______________________________________________
DVDomatic mailing list
DVDomatic(a)carlh.net
http://carlh.dnsalias.org/cgi-bin/mailman/listinfo/dvdomatic
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
9 Oct
9 Oct
10:17 p.m.
On Sun, 7 Oct 2012, Wolfgang Woehl wrote:
Hi Wolfgang,
These bugs should be fixed in version 0.55. Let me know if you are
still having problems.
Regards
Carl Hetherington
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.
4584
days inactive
4591
days old
3 comments
2 participants
participants (2)
-
Carl Hetherington -
Wolfgang Woehl