Replies: 2 comments 1 reply
-
I might be misinterpreting your request, but VPX has nothing to do with this tool. It's a completely separate item. There is a bridge to interface, but it has its own code and structure. If that were to be desired, the request would be made to VPX to change their structure. |
Beta Was this translation helpful? Give feedback.
-
I have gone down the track of modifying the code to have separate rgb channels for RGB's. I had to make a few changes across both VPX (VBS) and MPF (python) but I have gotten it to work. Although it works, from a performance standpoint, I would like to go back to using a singular value representing an RGB LED to minimise the chattiness that is a result of splitting the channels up. I.e. the interface currently sends one value per LED (which equates to 3 calls to VPX) - and the value ideally could be sent across in one call but split up according to some form of masking. At the moment, I have spent enough time on it to get it to work correctly with the 3 values but at a later stage I will get stuck back into it. My "hack" was more a workaround to test the table so that I could visually see the correct LED color. Since this topic is quite old, if you would like more details about this I can share it. |
Beta Was this translation helpful? Give feedback.
-
The VPX Platform should have the same parse light number to channels logic as the smart virtual platform so that light color information can be sent to vpx.
The led subtype should expose -r, -g, -b channels
Beta Was this translation helpful? Give feedback.
All reactions