You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
They mention "(info based on mplayer ColorLight 5a-75 video output patch)" and I assumed I would be able to find more thorough documentation there but haven't been able to find the patch they're referring to.
They mention "(info based on mplayer ColorLight 5a-75 video output patch)" and I assumed I would be able to find more thorough documentation there but haven't been able to find the patch they're referring to.
There isn't much info in the mplayer patch, I think my code in FPP is more documented, but here is a link to the mplayer patch:
We are also looking into adding more detail and packet types to FPP. We have a user who is doing some testing currently because he has seen 0x0100 and 0x0107 initialization packets. The 0x100 packets were sent to a receiver running a different firmware which allows panels with PWM drivers to be used. He has been able to get FPP sending to these receivers by changing our initialization packet and copying some details from a packet capture, but is currently testing more to see if we can get more details about the different packets.
Has the network protocol for sending video to the Colorlight cards been reversed?
I'd like to use them to drive some LED panels with a RPi4.
I'm aware of this: https://github.com/FalconChristmas/fpp/blob/master/src/channeloutput/ColorLight-5a-75.cpp as a partial reversed protocol. I'm wondering if there is a more complete one.
They mention "(info based on mplayer ColorLight 5a-75 video output patch)" and I assumed I would be able to find more thorough documentation there but haven't been able to find the patch they're referring to.
I found a few alternative implementations such as this project: https://github.com/NiklasFauth/colorlight-led-cube but don't really have the Verilog background to edit them for my needs. :(
The text was updated successfully, but these errors were encountered: