-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Slow rendering with 128x96 pixels #25
Comments
Hello |
We both have the same panel size and it sounds like you are able to have a much higher fps with a less powerful chip. I wonder what I am doing wrong. |
Hello |
I'm driving some HUB75 panels. I don't know how many pins are being used, but that is not the issue. I can drive these panels over 200fps for example. From the little statistics printed in my earlier message, the delay sending the data only accounts for about 1% of the total delay. hpwit, how long does it take to render a frame on your end? Do you have any video showing these animations being played? |
Hello, I have the same issue running esp32-c3. @hpwit could you share your "special driver" info and setup? I am using a string of WS2811 LEDs with a single pin output from esp32. Thanks! |
This driver will only for esp32 and esp32s3 |
@hpwit I've actually made the switch to ESP32 now (previously C3), can you kindly share what driver you are referring too? I'd like to avoid using the Teensy 4 for cost purposes. |
@twintersx I am using the https://github.com/hpwit/I2SClocklessVirtualLedDriver |
Great animations.
Have you tried running with a large panel before? It looks great (some only render a small circle in the middle of the screen). The problem is I average about 5fps :/. I'm using Teensy 4.1. I'm guessing this is to be expected when trying to drive 12,288 pixels.
The text was updated successfully, but these errors were encountered: