-
-
Notifications
You must be signed in to change notification settings - Fork 26
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
[Request] Sacrificial pixel (led) support #109
Comments
Hi @gladiatormax, It looks like there is some information missing from this issue that is required to process it:
Please read this guide, especially the troubleshooting section. If you have read this guide, please tick the box in your issue next to 'I have read the Get Help Guide'
If you didn't mean to ask for help, please make sure you used the right template - bugs and requests should have I'm just a bot 🤖, not a human being, so don't expect any replies from me :) Your ticket is read by humans too, I'm just not one of them. |
I probably could, not for the next update (since that needs to be shipped at some point) but I will add it to the backlog. |
Thx , for the rest great work on the plugin ! |
Closes #109 Also fixed a bug in segment implementation
This has been implemented ready for v0.8.0 |
0.8.0 has been released (finally...!) |
I use the first led for the 3.3v -> 5v data signal. Poor man's signal shifter.
See example here,
https://hackaday.com/2017/01/20/cheating-at-5v-ws2812-control-to-use-a-3-3v-data-line/
Could you add the option to ingnore first pixel(led) as also buing used in de wled project.
The text was updated successfully, but these errors were encountered: