I split this into a separate thread because ultimately, it’s its own problem (originally in the ESP32 port thread SmartMatrix Library ESP32 Port )
So far I had actively avoided using RGBpanels because I knew from experience of seeing others, that they look bad when taking pictures/filming them. That said, neopixels which don’t suffer from those problems, are between hard and impossible to find in P5 or below, and expensive when you’re getting something like 96x64 or higher, so I thought I’d try RGBpanels after finding some flexible ones (it’s for a wearable).
Here is a demo of teensy v3.6 (top) vs ESP32 direct wiring (bottom)
This was taken with my cell phone. Another phone or another camera would probably have yielded slightly different results.
The artifacts when taking a video, are terrible on both
I thought ESP32 refresh rate was not going to change with the code that was being run since one core shouldn’t affect the other one.
Sadly both demos clearly show a refresh sync changing depending on what’s being displayed and generally looking terrible on video, and also shows that the refresh rate with the ESP32 code, seems not to be quite constant either and depends on what code/calculations are being run, it seems.
I’m assuming I’m not the first one to see this. Are there are tips/workarounds around it, or do I have to accept that if I use RGBpanels, they’re going to look like crap when filmed?
(yes, I understand that I can tweak a proper camera to change the sync rate, but in a night club when I’m not the one taking pictures, or people are using cell phones (most common), or appearing on film, I have no control over that and Ideally it would “just work”)