@ Cyberia:
Of course, when comparing iDCTs, I try to use as few additional "brakes" as possible. Those two examples came from a different short comparison, that's just why I told that...
_
@ trbarry:
SSEMMX shall be supported.
And of course, I could have tried DebugView, I just have no experience with it yet. I hope I will gain some that I can report more details - I'll answer soon...
_
@ all:
I know that the iDCT alone won't make much difference compared to other parts of the decoding process; but almost no measurable at all?! Wow - then I wonder why some people made such an effort in ancient MPEG2AVI and Flask/Xmpeg times: In those times it must have been important to chose one (I can remember a range between 4 and 23 fps in Xmpeg), but in MPEG2DEC3 they all must have been optimised to the hilt - and that's really remarkable on your programming efforts! Therefore, thanks to all you developers for your great work!
_____
P.S.:
Not as much output as expected. AVS code:
Code:
LoadPlugin("H:\Programme\GordianKnot.new\mpeg2dec3.dll")
mpeg2source("N:\Movies\Trailer\Mortal_Kombat_2\trMK2.d2v", CPU=0, fastMC=true)
Started DebugView, opened this AVS script in VDubMod 1.5.1.1a, edited the script [Ctrl]+[E], added "iDCT=#" parameter, entered values from 1 to 7 and refreshed [F5] each time (scanning for video errors doesn't produce any more output). Got the following results (iDCT=2 in d2v project file):
Code:
00000000 07:29:59.520 [1016] mmmmmm
00000001 07:30:15.884 [1016] Overiding iDCT With: 1
00000002 07:30:23.505 [1016] Overiding iDCT With: 3
00000003 07:30:26.759 [1016] Overiding iDCT With: 4
00000004 07:30:29.604 [1016] Overiding iDCT With: 5
00000005 07:30:32.177 [1016] Overiding iDCT With: 6
00000006 07:30:35.141 [1016] Overiding iDCT With: 7
Is there any switch for more debug output which I missed (e.g. due to the lack of a flatrate and therefore not much time to search the forum for a longer time)?