Thankyou for the offer, Paul. are you not feeling a little deja vu? We've already been down this road, ref
msg 14.
As previously mentioned, I can also test the same 'broken' sketch on a different PC and it will work reliably, using the same T4laser synth module. I have disabled installing updates on that Arduino's IDE, in hopes of protection against kremlins. So far, so good.
The only difference is using different computers, both Win 10, both I5 intel, but the Surface is several years older, with an out of date HAL for MS to upgrade. to Win 11.
Yes, I understand that you don't have the ability to troubleshoot, without being able to reproduce it at your end. I can't detect any problems on the miniPC, either.
I was simply wondering whether the library was mistakenly referencing the DeviceID, instead of the class. That would explain why the Audio Design Tool briefly threw up a warning, as if it mistook the pt8211_2 for the pt8211. Seemed to fit the scenario.
Just a thought. Lookit, there it goes ..;:" '
The only workaround that I can see is to make backups for every change in code, until it breaks. Then, go back to a working sketch and continue coding with a known working sketch. tht means always coding on the Surface, otherwise I won't know when it breaks from the miniPC.
Somehow, I'll just have to deal with it.
Ill let you know if I have any more epiphanies.