I just thought I'd share some video of the app in use that I was able to complete by courtesy of @Erel updating JMQTT to support websockets as per this thread.
All done with B4J, the app has two forms, with one the UI to set various parameters:
while the second is fullscreen which displays a basketball venue scoreboard via a serial interface to the venue scoreboard controller and player nos/names, points and fouls for each team adjacent to a "blue screen" rectangle so it can be used as an overlay in video mixing software such as vMix or OBS to show game video, sponsor info, etc.:
The displayed player nos/names, points and fouls data is sourced using an MQTT based API to access data uploaded in real time by courtside Statisticians.
The video is actually the output of the vMix which I display on a large video screen in the stadium to enhance the spectators experience and it can be seen that the player points and fouls update shortly after the action occurs:
.
Read about the journey I've been on to arrive at this point in a B4X Blog entry.
All done with B4J, the app has two forms, with one the UI to set various parameters:
while the second is fullscreen which displays a basketball venue scoreboard via a serial interface to the venue scoreboard controller and player nos/names, points and fouls for each team adjacent to a "blue screen" rectangle so it can be used as an overlay in video mixing software such as vMix or OBS to show game video, sponsor info, etc.:
The displayed player nos/names, points and fouls data is sourced using an MQTT based API to access data uploaded in real time by courtside Statisticians.
The video is actually the output of the vMix which I display on a large video screen in the stadium to enhance the spectators experience and it can be seen that the player points and fouls update shortly after the action occurs:
Read about the journey I've been on to arrive at this point in a B4X Blog entry.
Last edited: