Skywalkerjen
30th December 2005, 18:07
Hi there
DGIndex 1.4.6b2
Gordian Knot 0.35.0
I process the vob using DGIndex and the iDCT Algorithm: IEEE-1180
When I load the .d2v into Gordian Knot I use the advanced Save .avs dialogue.
I then use Gordian Knot to create the .avs file and one option is to change the iDCT used. If I set the idct to 0 then the .d2v value is used - the IEEE-1180 that I specified in DGIndex.
However, if I chose option 4: 64bit IEEE-1180 Reference that Gordian Knot specifies I get a different file - checked with an md5 checksum.
Which one is correct? The DGIndex IEEE-1180 or the Gordian Knot IEEE-1180?
I tested this further and found the following:
DGIndex and Gordian Knot produce exactly the same file when either is set to 32-bitMMX or Skal SSE MMX and any video length.
DGIndex and Gordian Knot produce exactly the same file when both are set to IEEE-1180 Reference but only when the video length is small (around 50 frames).
Thanks for any help
DGIndex 1.4.6b2
Gordian Knot 0.35.0
I process the vob using DGIndex and the iDCT Algorithm: IEEE-1180
When I load the .d2v into Gordian Knot I use the advanced Save .avs dialogue.
I then use Gordian Knot to create the .avs file and one option is to change the iDCT used. If I set the idct to 0 then the .d2v value is used - the IEEE-1180 that I specified in DGIndex.
However, if I chose option 4: 64bit IEEE-1180 Reference that Gordian Knot specifies I get a different file - checked with an md5 checksum.
Which one is correct? The DGIndex IEEE-1180 or the Gordian Knot IEEE-1180?
I tested this further and found the following:
DGIndex and Gordian Knot produce exactly the same file when either is set to 32-bitMMX or Skal SSE MMX and any video length.
DGIndex and Gordian Knot produce exactly the same file when both are set to IEEE-1180 Reference but only when the video length is small (around 50 frames).
Thanks for any help