Originally Posted by buzzard767
Ultimate provides the option to produce various LUTs, 65x and 64x included. The 65s load, the 64s don't.
That is because when we create the file for the eeColor we always drop the last entry. So a 65 becomes 64 and a 64 would have become a 63. So yes you are correct a 64 will load and a 63 will not.
Code clip from the file formattter for the eeColor format:
red = LUT_POINTS[r];
green = LUT_POINTS[g];
blue = LUT_POINTS[b];
line = NULL;
DWORD len = 0;
len = sprintf_s(line,256,"%.08f %.08f %.08f %.08f %.08f %.08f\n",red/double(maxValue),green/double(maxValue),blue/double(maxValue),red/double(maxValue),green/double(maxValue),blue/double(maxValue));
How much misinformation are we going to have to clean up after LS. Why is this being debated I have all the low level docs, have been working with this hardware for over two years and know exactly how it stores and uses its internal memory.
Easy test take any of the LUT files created for the eeColor by TruVue, CalMAN or LightSpace. Open it up and count the lines you will find 262144 lines so 64^3.