54
edits
(Add information about setup) |
(→Setup: Add information about remote video feeds) |
||
Line 46: | Line 46: | ||
We faced several technical challenges on the day, including difficulties getting power and internet to the static cameras resulting in the scrapping of two static locations last-minute. We had several communications issues, including our walkie-talkies not working as intended and issues with the built-in talkback feature of our remote video tool, meaning that static and roaming cameras had almost no communication with the gallery. We also had issues with the studio -> control room feed which was using SRT, this was likely because we were saturating the YSTV -> ITS network and the SRT packets were not prioritised over other traffic. This meant the video feed from the studio was very unreliable and kept dropping out, which was not ideal. This was ultimately fixed by reverting to RTMP. | We faced several technical challenges on the day, including difficulties getting power and internet to the static cameras resulting in the scrapping of two static locations last-minute. We had several communications issues, including our walkie-talkies not working as intended and issues with the built-in talkback feature of our remote video tool, meaning that static and roaming cameras had almost no communication with the gallery. We also had issues with the studio -> control room feed which was using SRT, this was likely because we were saturating the YSTV -> ITS network and the SRT packets were not prioritised over other traffic. This meant the video feed from the studio was very unreliable and kept dropping out, which was not ideal. This was ultimately fixed by reverting to RTMP. | ||
Another large issue we had was lack of techies. Due to illness and no-shows, we had a lot fewer techies than planned which meant that the techies that were there were very stretched. | |||
=== Remote video feeds === | |||
In order to get reasonably low-latency video feeds from static cameras and roaming camera operators who were spread out across campus, we used a remote video tool called [https://vdo.ninja vdo.ninja]. This allowed people to send their camera feed over the internet to the gallery using just their phone and a web browser. | |||
This tool had previously been used in productions during Covid-19, however not on the scale of this production and certainly not when we had people running around campus. | |||
To help get the video feed from people's phones back to the gallery, people were connected to the university's eduroam WiFi network. This did mean that due to inevitable eduroam blind spots, video feeds were at time patchy or were lost altogether. However, due to large scale of the production and people moving around campus very quicky, this was unavoidable. Fortunately, vision mixers were able to cut to other video feeds or go back to the studio or Hunter HQ when this happened. | |||
Another issue we had with [https://vdo.ninja vdo.ninja] was communications. Whilst this tool did have an option for talkback, for reasons unknown this didn't work. This meant that roaming and static camera ops had almost no communication with the gallery; we had to resort to Facebook messenger group chats to enable at least some basic communication. This was very much not ideal. | |||
Despite these technical issues, we were able to capture some really good content and get some really good video footage of the game. Although [https://vdo.ninja vdo.ninja] is a free tool, it worked really well for us, especially considering how many camera feeds were going through this service. |