Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Lookup Tables 255 vs. 256 #1

Open
jeremyselan opened this issue Dec 19, 2012 · 0 comments
Open

Lookup Tables 255 vs. 256 #1

jeremyselan opened this issue Dec 19, 2012 · 0 comments

Comments

@jeremyselan
Copy link
Owner

Appendix 4.1

"However, one mayobserve that no matter how complex the function, it can evaluate to only one of 255 output values (corresponding to each unique input). Thus, an alternate implementation would be to tabulate the function's result for each possible input value, then to transform each pixel at runtime by looking up the stored solution. Assuming that integer table lookups are efficient (they are), and that the rasterized image has more than 255 total pixels (it likely does), using a LUT will lead to a significant speedup."

References to 255 should be 256 here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant