Image 4: An example spreadsheet of the information collected from collaborators to determine what equipment needed to be sent as well as additional technology that could be used. | Courtesy of TAPS. Image 5: One list of equipment sent to an assistant technical director (Similar to the equipment sent to performers depending on need). | Courtesy of TAPS. 30 | THEATRE DESIGN & TECHNOLOGY | SPRING 2021 step was testing to see if the NDI capture feed was making it through to the NDI virtual camera. This was done with the NDI monitor. Hood then logged into the " audience Zoom meeting " and set the camera output to be the NDI virtual camera. Through this method, the audience now saw everything that happened in the rehearsal Zoom as if it were one Zoom square. This instance of " computer inception " was only the stage set up to permit production control of audience viewing. A much more elaborate interweaving of computers needed to be done to put together a fully live production. See the image of how different computers were connected and how many were needed to run the show. Sutton describes the setup of ZoomOSC as follows: " We had two instances of ZoomOSC running on a remote machine, each one connected to a different meeting (actors/audience). Genny (the ZoomOSC operator) just had to log into the Zoom meetings and then run the QLab file. QLab sent most of the OSC messages directly, but large cues (such as the ones that turned on video for the entire audience) were run indirectly through a python script that QLab called. " The biggest problem was finicky Internet connectivity. The show was truly at its mercy. If a performer's home WiFi cut out, there was nothing to do but wait to get them back onto the call. Other specific connection issues randomly occurred with the computer inception set up for which the only reliable solution was restarting the computer that was not making the remote connection. WiFi wasn't the only problem, however. Throughout the process, sound issues were challenging and troubleshooting them from a distance was difficult. With everyone on a different computer and with several different operating systems, it was hard to maintain uniformity across the board. Captioning was one technical issue that was a continuing problem, and unsolvable within the time frame. Using TouchDesigner with Google speech-totext didn't convert the songs well. Sutton tried to provide the captions manually by " loading each line of the show into a TSV file and clicking to trigger the next line, but [the team] decided against that