Skip to content
An independent guide to international theatreMany cultures. A shared stage.
The InternationalistsTHEATRE ACROSS BORDERS

A GUIDE TO THEATRE ACROSS BORDERS

Touring, Festivals & Mobility

What Should Festivals Know Before Programming a Networked Performance?

THE SHORT ANSWER

Festivals should programme a networked performance as a production with two or more sites, not as a simple livestream. They need to define whether performers are interacting in real time, test the actual venues and network, assign technical and editorial roles, rehearse across sites, and plan documentation and audience access. The curatorial decision and the technical decision are linked.

At a glance Quick facts
Definition
A networked music performance is a musical performance done in real time over a computer network between separated locations.
Key distinction
A networked performance involves live interaction between sites; a livestream may be only a one-way broadcast.
Typical roles
Performers, administrators, technicians and event organisers, with responsibilities that often overlap.
Documented example
ACCAD describes networked music performances led by Marc Ainger and Federico Cámara Halac, with performers and software or consultation contributors across locations.
Audience concern
Audiences at each site need documentation of the parts of the performance they cannot physically see.
Festival planning point
Test the actual sites and network, agree decision rights and budget for technical rehearsal before announcing the event.

Start with the format: performance, hybrid event or broadcast

Festivals should answer a basic question before announcing a networked performance: is the work a live two-way collaboration between separated performers, a hybrid event with remote participants and local audiences, or a broadcast of an existing production? The answer determines the budget, the technical plan and the artistic risk. A networked performance is not simply a festival livestream with a more ambitious title.

In a networked music performance (NMP), musicians in different places perform together in real time over a computer network, aiming to act as if they were in the same room (The MCT Blog, 11 December 2023). The Advanced Computing Center for the Arts and Design at Ohio State University describes a related principle in its networked performance project: real-time interaction over the internet allows people and computers in separated locations to perform as if they were co-present (ACCAD, Networked Performance). Theatre festivals may use the term networked performance for remote acting, telematic theatre, distributed rehearsals or mixed live and remote work. The same planning questions apply: who is interacting, where, with what delay, and for which audience?

This distinction matters because much virtual festival guidance begins with livestreaming and platform choice. A beginner’s guide to hosting a virtual festival, for example, treats livestreaming as a possible future for festivals and discusses platforms such as Hopin and Twitch as ways to stage live digital events (Youth Music). That is useful for audience-facing broadcast, but it does not by itself answer the questions raised by two-way performance. If the festival only needs a one-way transmission, a broadcast workflow may be appropriate. If performers must respond to each other in real time, the festival needs a networked production plan.

Why festivals need a different planning assumption

A festival adds public audiences, fixed schedules, multiple venues, front-of-house teams and documentation obligations. Network performance also adds roles that are easy to underestimate. A 2020 article on administering network performances notes that such work requires performers, administrators, technicians and event organisers, and that these roles are intertwined (McMillan and Morreale, 2020). The same article connects the growth of network performance during the COVID-19 crisis with efforts by music communities to maintain connection beyond their immediate surroundings. For a festival, that means the remote site is not a passive feed. It is part of the production.

The ACCAD project shows how broad the credit list can become. The project team is described as being led by Music professor Marc Ainger and Federico Cámara Halac, with performers and project contributors listed across multiple locations and institutions; the contributors include software and consultation roles (ACCAD). A festival does not need to reproduce that scale, but it should recognise that software, network support and consultation may be creative-labour credits, not invisible backstage assistance.

Verify the sites, network and time zones before announcing

Site and network survey

Test the actual venues, not only an office or a home studio. A festival should check the network path between each performance site, the audio and video routing, the power supply, the lighting and camera positions, and the local audience sightlines. Exact bandwidth and latency thresholds depend on the software, the instruments or voices, and the artistic team’s tolerance for delay. The available sources do not prescribe universal numbers, so festivals should test with the actual tools and performers rather than assume that a venue’s ordinary Wi-Fi will suffice.

Latency is not only a technical metric. It affects cueing, ensemble, timing and the performers’ sense of contact. A festival should decide in advance what degree of delay is acceptable, who can make adjustments during the performance, and whether the work can continue if the connection degrades. It should also plan a contingency: a backup connection where possible, a fallback version of the performance, a local recording, and a clear stop signal agreed by all sites.

Time zones and schedule

Networked performance can connect places that cannot easily meet, but it also complicates scheduling. A public performance time in one city may be an unreasonable hour in another. Technical rehearsals, sound checks and access to technical staff must be planned across time zones, not only for the advertised show. Festivals should publish the performance time in each participating location and state clearly whether the event is live, partly recorded or repeated.

Assign roles and decision rights

Before the festival commits, it should name the people responsible for each site and each layer of the production. Depending on scale, this may include a festival producer, a site coordinator at every venue, a network or audio technician, a stage manager, a documentation lead and an access lead. The 2020 article on administering network performances identifies performers, administrators, technicians and event organisers as core roles, while stressing that their work is intertwined (McMillan and Morreale, 2020). A festival should go further and state who has authority when something fails.

Useful decision rights include: who can stop the performance; who decides whether to continue with degraded audio or video; who speaks to the audience if the connection drops; who manages the remote site’s local audience; and who approves changes to the running order. Without these decisions, a networked performance can leave performers and technicians improvising under pressure.

Rehearse the network, not only the material

The aspiration that separated performers can act as if they are in the same room is not a guarantee. It is a production goal that must be rehearsed. Festivals should budget for technical rehearsal in the actual configuration, with the actual sites, cameras, microphones and network conditions. A separate artistic rehearsal may be needed after the technical set-up is stable, because performers must learn how the system behaves.

Rehearsal should test more than connectivity. It should test opening announcements, camera framing, sound balance, cueing, translation or surtitle cues, and the audience’s view of remote participants. If the performance is multilingual, festivals should test captions, surtitles or interpretation in the same rehearsal cycle rather than adding them at the last minute. The point is not to make the technology invisible; it is to make its effects legible to performers and audiences.

Plan the audience experience at every site

Networked performance creates a specific audience problem: no single audience sees the whole event from the same position. Guidance on documenting networked music performances argues that every audience member in any location should have adequate documentation of the parts of the performance they are not physically in the room to see (The MCT Blog, 11 December 2023). For a festival, this means thinking about screens, camera mixing, programme notes and front-of-house explanation at each venue. It also means deciding whether online audiences are watching a performance, a relay or a separate edited stream.

Access should be planned with the same care. Festivals should consider captioning, audio description where appropriate, sign language interpretation, language access and clear information about the format. Network performance can extend a festival’s reach, but it can also create new exclusions if audiences are assumed to have fast connections, suitable devices or prior knowledge of the set-up. The 2020 article notes that network performance has been used to enhance communities’ connectivity beyond intimate surroundings (McMillan and Morreale, 2020); festivals should treat that connective aim as a design requirement, not a by-product.

Document the work and its conditions

Documentation is not an afterthought in networked performance. The MCT Blog describes documentation as a crucial part of any NMP, both for audiences who cannot see every location and for academic or research purposes where evidence must support the questions being asked (The MCT Blog, 11 December 2023). A festival should decide early what the documentation is for: audience relay, archive, funder report, research evidence or future programming. That purpose determines what to capture and who can access it.

A practical documentation plan may include the running order, site plans, technical set-up, software versions, credits, audience materials, still images and a recording of the performance. It should also record the conditions that shaped the event, such as time-zone differences, connection problems or changes to the planned format. Consent, rights and attribution should be agreed with performers, technicians and audiences before recording or publishing. Legal requirements vary by jurisdiction, so festivals should verify contracts and permissions with the relevant rights holders and advisers.

Budget, contracts and common problems

Networked performance can add costs that are easy to miss: site coordination, technical staff, equipment hire, extra rehearsal, connectivity, documentation, access services and contingency planning. The sources cited here do not provide fee scales or standard budgets, and festivals should not treat them as cost guidance. They should obtain quotes for the actual configuration and state clearly which partner supplies which resource.

Contracts should clarify who provides the venue, network, power, equipment, technical support, insurance and recording rights, and what happens if a site loses connection. They should also address cancellation, postponement, credit and the ownership of documentation. These are general planning points rather than legal advice; the applicable rules depend on the jurisdiction and the agreements between parties.

Common problems include treating a networked performance as a livestream; leaving network testing until the week of the festival; failing to budget for technical rehearsal; assigning roles without decision rights; promising co-presence without acknowledging delay; and documenting the event only after it has ended. A festival can avoid many of these problems by making the format, sites, roles and contingencies explicit before the public programme is published.

Before committing: a festival checklist

  • Define whether the event is a networked performance, a hybrid event or a broadcast.
  • Name every performance site and the local audience capacity at each.
  • Test the actual network, power, audio and video at each site.
  • Agree acceptable latency and a stop or fallback procedure.
  • Assign a coordinator, technician and decision-maker for each site.
  • Budget for technical rehearsal as well as artistic rehearsal.
  • Plan the audience view, programme information and access provision at every site.
  • Agree documentation purpose, consent and credits before recording.
  • Clarify contracts, rights, insurance and cancellation terms.
  • Publish accurate information about what is live, remote or recorded.

If a festival can answer these questions with named people, tested sites and a documentation plan, it is better placed to programme networked performance as a real production rather than an experiment added late to the programme.

FAQ

Is a networked performance the same as a livestream?

No. A livestream can be one-way broadcast, while a networked performance involves live interaction between performers or sites over a network. A festival should decide which format it is actually presenting.

What should a festival check first?

It should first define the format and the sites. Then it should test the actual venue networks, audio and video, assign decision-making roles, and budget for technical rehearsal.

How much rehearsal does a networked performance need?

There is no universal figure. The amount depends on the software, the number of sites, the artistic form and the performers' needs. Festivals should rehearse in the actual configuration rather than assume that a standard sound check is enough.

Who should be credited in a networked performance?

Credits may need to include performers, site coordinators, technicians, software or consultation contributors, documenters and access workers. The ACCAD project, for example, lists software and consultation contributors alongside performers.

What happens if the network fails during a festival performance?

Festivals should agree a contingency in advance: a backup connection where possible, a fallback version, a local recording, and a named person who can pause or stop the performance. The exact plan depends on the work and the venues.

READ FURTHER

Sources & references

  1. Juliana Bigelow, 'Documenting Networked Music Performances: Tips, Tricks and Best Practices', The MCT Blog, 11 December 2023, https://mct-master.github.io/networked-music/2023/12/11/julianmb-documenting-nmp-best-practices.html
  2. Advanced Computing Center for the Arts and Design, 'Networked Performance', ACCAD, Ohio State University, https://accad.osu.edu/networked-performance
  3. Andrew McMillan and Fabio Morreale, 'Purpose and Well-Being Through Administering Network Performances', Academic Commons, Stony Brook University, 2020, https://commons.library.stonybrook.edu/jonma/vol2/iss1/3
  4. Madeline Wrench, 'A beginners guide to hosting a great virtual festival', Youth Music, https://www.youthmusic.org.uk/resources/beginners-guide-hosting-great-virtual-festival

THE LANGUAGE OF PRACTICE

Related terms

Networked music performance (NMP)
A real-time music performance over a computer network between performers in separated locations; a common form of networked performance.
Telepresence
Technologies and staging choices that aim to give participants a sense of presence in another location.
Hybrid performance
A performance that combines in-person and remote participants, venues or audiences.
Latency
The delay between a signal being sent and received over a network, which can affect timing and interaction.
Technical rider
A document specifying the equipment, network, staffing and support a production needs at a venue.
Documentation
Records of a performance and its conditions, created for audiences, archives, funders or research.

A SHARED BODY OF KNOWLEDGE

Something to add or correct? Help us keep the conversation informed.

Corrections & updates

Leave a Reply

Your email address will not be published. Required fields are marked *

THE CONVERSATION CONTINUES

Keep a window open to the world.

Fresh perspectives and practical reading, straight to your feed reader.

Subscribe via RSS

FOLLOW YOUR CURIOSITY

Find your next idea.

Search the journal, practical guides, and pages.

THE PRACTICAL TOOLKIT / 01

Your first conversations.

Use these prompts to begin planning with your collaborators. Your progress is saved in this browser.

A starting point for discussion. Adapt it to your project and check local requirements with the relevant organisations.

THE PRACTICAL TOOLKIT / 02

A time to come together.

Choose a date and time in UTC to see when your collaborators would meet. Times account for daylight saving on your chosen date.

Shaded times fall outside 09:00–18:00 local time. Agree working hours and access needs with your team.

BEHIND THE IMAGES

Photography credits

Editorial stock photographs illustrate themes; they do not document the productions discussed on this site. Used under the Pexels licence.