22 May 2026

Reflecting on Region 1 “Fix”

I will have to read more into what John-K had discovered about how the lights data are processed. I was thinking, why would the custom audio play until the lights turned on? Why could the projector know when to start playing the lights, but failed to do so at runtime? The error must lie in the values of the lights, but the structure may be retained, lending to a correct timing calculation, but incompatible light values. But is not the lights just RBG set by hex between 0 and 255? I can technically get any colour and shade I want. I’ll have to review John-K’s documentation.

Another aspect of the light seizure and crash: if it still crashes after fixing the pointer, then I am running into multiple errors, compounding into a confounded result. What errors I observe when I run a new flash is the result of many errors interacting. I suppose I could delineate that the wrong pointer seemed to cause the initial light seizure (both the projection light and the back light — which makes sense … except for the projection light control, that is peculiar), but some other error is causing the acute crash and reboot of the whole projector.