Is there a Mistake in AVS options choices of iDCT in RB 1.06.1?

[feedback]

So, where did iDCT 32 Bit Floating point come from and what's up with 64 Bit SSE2/MMX ?

I believe the iDCT choices been transposed? ;) I usually use iDCT 64 Bit Floating point but it has vanished in RB Pro. v.1.06.1. and instead we have the 32 bit floating point.

Regards,

[Fishman0919]

I think it was a typo in the DGDecodeManual.html because in the DGIndexManual.html it's 64 Bit, it's been like that since the iDCT's were remapped


DGIndexManual.html
iDCT Algorithm Table of Contents

Specify which iDCT algorithm will be used by DGIndex and DGDecode.

32-bit MMX (1 in INI file, D2V file and CLI)
32-bit SSE MMX (2)
32-bit SSE2 MMX (3)
64-bit Floating Point (4)
IEEE-1180 Reference (5)
Skal SSE MMX (6)
Simple MMX (7)

DGDecodeManual.html
idct: 0 to 7 (default: 0)

iDCT Algorithm.
For more infomation on iDCTs please see Appendix B.
Please see Appendix C for supported CPUs.
- 0: Use value specified by DGIndex
- 1: 32-bit MMX
- 2: 32-bit SSEMMX
- 3: 64-bit SSE2MMX
- 4: 32-bit Floating Point
- 5: 64-bit IEEE-1180 Reference
- 6: 32-bit SSEMMX (Skal)
- 7: 32-bit Simple MMX (XviD)

[feedback]

All I know is that when I go to the options section of RB pro. then tick 'AVS Expert Options', then go to 'Set Decoder iDCT', then go down the list of available choices the 64 bit floating point is gone.:scared: and instead we have the 32 bit floating point.

Regards,:)

[Fishman0919]

yeah, but if you go back to DGDecode 1.10 or NaN's 1.11 you get 64-bit Floating Point, I think jdobbs just copy what was in the DGDecodeManual.html for DGDecode 1.45 in to the settings menu and that what's in DVD-RB... still you get 64-bit Floating Point it's just miss labeled

[jdobbs]

Are you positive the documentation is wrong? DGIndex and DGDECODE are two different programs.

[Guest]

Apparently, the DGDecode manual is in error. Thank you for pointing it out.

[jdobbs]

Ok..

@feedback

It's just a display error, then. If you select the "32-Bit Floating Point" option you will actually be getting "64-Bit Floating Point". I've corrected it for the next release of DVD-RB.

[jdobbs]

@Neuron2

Can I assume, then, that "64-bit SSE2MMX" should be "32-bit SSE2MMX" as well?

[Guest]

Can I assume, then, that "64-bit SSE2MMX" should be "32-bit SSE2MMX" as well? Yes, your assumption is correct.

[feedback]

Thanks guys! I thought I had missed some major iDCT change or that I needed a new eyeglasses prescription, as I was seeing things.:D

Regards,

[Sir Didymus]

Sorry for raising again this thread, and forgive me if I am missing something of critical on the matter.

It seems to me after all the correct labels and codes for the IDCT are:

- 0: Decoder default
- 1: 32-bit MMX
- 2: 32-bit SSEMMX
- 3: 32-bit SSE2MMX
- 4: 64-bit Floating Point
- 5: 64-bit IEEE-1180 Reference
- 6: 32-bit SSEMMX (Skal)
- 7: 32-bit Simple MMX (XviD)

Now (1.07) the labels are ok, but their relative position and the actual IDCT values, as they appear in the avs files are wrong, so for example selecting in the GUI the 64-bit Floating Point item, you get in the avs files the IDCT 3, wich is definitely another one respect to what is asked by the user. Am I wrong ?

[jdobbs]

I just tried it and it works correctly for me... the value in the AVS file is is "idct=4".

[Sir Didymus]

I see!!!, You are totally right...

Sorry for the noise...

I was wrongly interpreting the avs values (previous numbering) in conjunction with the NaN release of the Decoder (which is also working perfectly).

I say again: everything is ok. and sorry for bringing your attention again on the matter...

Cheers,
SD

[jdobbs]

:cool:

[spyhawk]

Unless my eyes play trick on me, it still says "64-bit SSE2MMX" instead of "32 bit SSE2MMX" in the Set Decoder iDCT options. The iDCT=3 is correct in the ini and avs.

[jdobbs]

Unless my eyes play trick on me, it still says "64-bit SSE2MMX" instead of "32 bit SSE2MMX" in the Set Decoder iDCT options. The iDCT=3 is correct in the ini and avs.Makes you wonder just how many times a programmer can make the same mistake, doesn't it?