Doom9's Forum - View Single Post - .ti3 Parser / .3dlut Generator for madVR + .3dlut toolset

cyberbeing · 25th August 2011, 10:20

If I'm understanding you correctly, --reset was loading the exact 16-bit ramp CLUT you had it coded to use:

Code:

#GammaRamp
0	0	0	0
1	256	256	256
2	512	512	512
3	768	768	768
4	1024	1024	1024
...

Using --load resulted in a different CLUT, because the 16-bit linear ramp I was trying to load actually was a different CLUT than what -reset was using?

It makes me wonder if

Code:

#GammaRamp
0	0	0	0
1	256	256	256
2	512	512	512
3	768	768	768
4	1024	1024	1024
...

is more optimal than

Code:

#GammaRamp
0	0	0	0
1	257	257	257
2	514	514	514
3	771	771	771
4	1028	1028	1028
...

if your GPU only does CLUT processing in 8-bit, or if they would both ultimately result in the same thing.

25th August 2011, 10:20	#78 \| Link
cyberbeing Broadband Junkie Join Date: Oct 2005 Posts: 1,859	If I'm understanding you correctly, --reset was loading the exact 16-bit ramp CLUT you had it coded to use: Code: #GammaRamp 0 0 0 0 1 256 256 256 2 512 512 512 3 768 768 768 4 1024 1024 1024 ... Using --load resulted in a different CLUT, because the 16-bit linear ramp I was trying to load actually was a different CLUT than what -reset was using? It makes me wonder if Code: #GammaRamp 0 0 0 0 1 256 256 256 2 512 512 512 3 768 768 768 4 1024 1024 1024 ... is more optimal than Code: #GammaRamp 0 0 0 0 1 257 257 257 2 514 514 514 3 771 771 771 4 1028 1028 1028 ... if your GPU only does CLUT processing in 8-bit, or if they would both ultimately result in the same thing.