Skip to content

For DAW-led shows

PagePilot Conductor

The DAW-side companion that sends playback position and song changes into Viewer.

PagePilot Conductor bridges the DAW side of a show — playback position and song changes — into the live score workflow used by Viewer. It extends a manual tablet workflow into one that can follow the actual playback of the show.

Public page in progress

The standalone public-facing Conductor page will be expanded here over time.

You can sync without a PC

If you want the same following with just your bandmates' tablets — no DAW, no PC — Sync Together is the shorter path. This page covers integration for shows that use a DAW on a PC as the timing source.

What Conductor is meant to handle

In simple terms, it passes song number and playback position from the DAW side into Viewer so the on-stage score can stay aligned with the show.

  • Send DAW playback position to Viewer
  • Map song numbers or song changes into the Viewer setlist
  • Help the on-stage score follow where the show actually is

One DAW timeline, multiple scores that turn themselves

The key idea behind PagePilot Conductor is that the DAW becomes the timing source, while each Viewer follows with its own score and its own page-turn map.

Every performer does not need to see the same score. The pianist can open a piano part, the guitarist can open a chord chart, and the vocalist can open a lyric score. Each Viewer stores its own page-turn data, such as “show page 2 at 42 seconds from the start of the song.” When playback starts in the DAW, Conductor sends the song number and playback position, and each tablet turns pages according to its own setup.

1

The DAW is the clock

The song plays on a Mac or PC. Conductor reads the current song number and playback position from the DAW side.

2

Conductor broadcasts to every Viewer

Nearby iPad and Android tablets receive the same show timeline, so every Viewer follows the same source of truth.

3

Each Viewer turns its own score

The score files can differ. Each Viewer uses the page-turn timings saved for that score, while staying aligned with the DAW.

Mac / PC DAW now 0:47 Conductor in the DAW PagePilot Conductor Song #3 0:47.000 BLE / LAN Viewer A 42 sec 0:47 Viewer B 58 sec 0:47 Viewer C 76 sec 0:47
Conductor does not send the score files themselves. It sends song number and playback position. Each Viewer uses its own score and page-turn data to follow the same DAW timeline.

Where it becomes most valuable

Backing-track driven shows

When the song's flow and playback position are already set by the DAW, having the score follow that same flow adds real value. It suits shows where you want to reduce the burden of turning pages by hand.

Shows that need song-number management

If you want to make setlist song order and number mapping explicit, Conductor lets you tighten up that song-and-number mapping more than Viewer alone. It is especially helpful when you want the computer side and the tablet side to open the same song reliably.

When Viewer alone is enough, and when Conductor matters

What you are deciding Viewer alone is often enough when... Conductor becomes important when...
Page-turn timing Manual control or the Viewer timeline is enough The score should follow DAW playback position
Song switching You drive the setlist directly on the tablet Song numbers or show flow should stay aligned with the DAW
What leads the show The tablet side is the main control point DAW playback is the source of truth on stage

What already exists today

  • On the Viewer side, the Conductor scan and setlist-mapping entry points already exist, and the current route into them is documented from the Viewer manual page.
  • On the public site side, this page will gradually explain the role, setup ideas, and how it fits into a show.

What you need before trying it

  • PagePilot Conductor running on the DAW side
  • A device with PagePilot Viewer installed (a tablet is recommended; smartphones are also supported)
  • A Viewer setlist prepared for the show
  • Song-number mapping on the Viewer side if you want the DAW side and tablet side to match by explicit numbers

The setup flow

  1. Build the show setlist in Viewer
  2. Open Connect to Conductor and connect to the nearby Conductor
  3. Open Conductor Setlist and confirm that the DAW-side song numbers point to the right Viewer songs
  4. Rehearse song changes and score following before the show

Good to know before rollout

  • On the Viewer side you can choose BLE or LAN as the connection path. Which one you can actually use depends on what the Conductor you connect to supports.
  • For LAN, Viewer and Conductor must be on the same network and able to reach each other directly. Guest Wi-Fi that blocks device-to-device traffic will not work.
  • Conductor does not replace Viewer. It extends Viewer for shows where the DAW is the source of truth.
  • If Conductor switches to a song that has no mapping on the Viewer side, automatic following pauses and the current page stays on screen.

Current status

This is an early introduction page rather than a full product manual. Detailed setup guidance, screenshots, compatibility notes, and a fuller public explanation will be added as the release takes shape.