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
Unreal Engine 5 is increasingly being used for broadcast graphics, and supposedly the Q2 release of it will have even more first-class features for them. It would be great if there were an official plugin for UE5 that provided an API for Messages and Replicants over the Socket.IO server.
The current implementation of NodeCG's "Graphics" tab on the Dashboard is entirely webpage-centric, and it wouldn't know what to do with a UE5 graphic. It would be great if this page was expanded to have data and controls that make sense for UE5.
Very nice that they will have first class NDI output support in their Video IO providers list. Would you want to use that for graphics out of the selection? Also you might not have to stitch in too much for communication with NodeCG if the Control Application API exposes a web server (seems like it might given web dashboards were a talking point earlier in the presentation.
Motivation
Unreal Engine 5 is increasingly being used for broadcast graphics, and supposedly the Q2 release of it will have even more first-class features for them. It would be great if there were an official plugin for UE5 that provided an API for Messages and Replicants over the Socket.IO server.
Context
See https://www.youtube.com/watch?v=XAtjoawRN_Y for more details on how UE5 does broadcast graphics.
Technical considerations
There is already a first-party C++ implementation of Socket.IO that we would use, so that part is taken care of: https://github.com/socketio/socket.io-client-cpp
UI/UX considerations
The current implementation of NodeCG's "Graphics" tab on the Dashboard is entirely webpage-centric, and it wouldn't know what to do with a UE5 graphic. It would be great if this page was expanded to have data and controls that make sense for UE5.
Prior Art
https://www.youtube.com/watch?v=sJvBqW_oUrI
The text was updated successfully, but these errors were encountered: