Patrick Dowling

Hm. AFAIK so far no one's been able to give a reproduceable scenario. I've seen the glitchy display only once, and that was running totally experimental code that had 1001...

Yeah, newer versions do seem to exacerbate it. FWIW it was still on 1.35 where I saw it, but just the once. Intentionally (because it would never happen otherwise :smile:)...

So, FWIW... [fix/display_glitch](https://github.com/patrickdowling/O_C/commits/fix/display_glitch) [This commit](https://github.com/patrickdowling/O_C/commit/3dbaab16fa936a01d376a48c72aefbec4242f686) seems to suppress the symptom (*) of glitching display when built with 1.8.12 + Teensy 1.51, at least on the test bench. It still builds...

I'm pretty sure that was addressed with this commit: https://github.com/mxmxmx/O_C/commit/55125b49092f2149f3dcd932cd31cf8d15873285 so it should be handled in the v1.3.6 version.

Did Shay specify if it's an issue just with OCP, or in general with 1.3.6 (i.e. on stock hardware, that's gone unnoticed)? If there's something to be fixed in the...

Ok, thanks for the sanity check on regular hardware. I mean it's not inconceivable that it's been there all along, but someone should have noticed :) Admittedly it's kind of...

I see. Honestly I haven't looked too closely at the specifics of the offsettery beyond that it's provided by the Teensy's internal DAC. So that might not have the same...

Yeah, for implementation access to hardware is somewhat optional, but it has to be tested at some point :) The "firmware development team" has always been a somewhat loose collaboration...

Yes, that is frustrating. We don't really have any control over the market though... So after someone posted some hints on MW it smells like the offset stems from the...

See [here](https://www.muffwiggler.com/forum/viewtopic.php?p=3312875#p3312875) After coffee an alternative explanation might also be "something" in the additional circuitry but the effect will be the same.