Closed cymplecy closed 6 years ago
I'm guessing - albeit a very tentative guess - that the underlying rpi_ws281x library is using a DMA channel that Chrome is also attempting to use. I can't think of any other resources they should be contending for- although I guess Chrome could be using the analog audio... normally that makes Unicorn HAT go horribly garbled long before any specific audio application is loaded.
Have you disabled analog audio?
[ignore] - I need to test more things before writing :)
Luckily - it does seem to just be a sound issue. If I use raspi-config and send sound output to HDMI, I can run the demo with Scratch3 loaded. Thanks for the pointing me in right direction :)
I seem to be having a clash between controlling Neopixels and running Scratch3 beta on Pi3B+ at same time
Simplest repeatability test for me is to run sudo python demo.py
Launch Chromium (All OK still) Load https://beta.scratch.mit.edu/
and then things go bad :(