If your playback computer runs Windows, the first question is which parts of your show you need the software to handle. QLab is a macOS application. TuneIT supports Windows and macOS and is worth evaluating when your immediate requirement is live audio playback: firing sound cues, arranging playback pads and running playlists.
TuneIT is not a feature-for-feature replacement for QLab. A show built around QLab’s wider cue programming and multimedia tools needs a requirements check, not a promise that a different application will run the same show unchanged. This comparison focuses on choosing an audio workflow; it does not claim QLab workspace compatibility or automatic show-file conversion.
Start with the show, not the software name
A theatre operator may need a small set of sound effects repeated in rehearsal. A venue engineer may need walk-in music, entrance stings and a dependable way to identify the next track. A more complex production may depend on tightly programmed cue sequences and other media. Write down what must happen at each cue before deciding whether pads and playlists cover the job.
TuneIT’s pad-based workflow suits audio moments that an operator needs to reach directly. Playlists organise ordered material such as preshow music or an interval sequence. These are different operating patterns: a playlist should not be assumed to reproduce the behaviour of a programmed QLab cue list.
TuneIT and QLab: a practical comparison
| Requirement | TuneIT | QLab 5 |
|---|---|---|
| Operating systems | Windows and macOS. Check the current installer requirements before choosing a show computer. | macOS. Figure 53 publishes version-specific system recommendations. |
| Direct cue access | Playback pads for immediately selecting an audio cue. | Cue carts provide a grid for non-sequential cue access. |
| Ordered material | Playlists for arranged audio playback, with playlist crossfade features documented. | Cue lists and cue sequences, including auto-continue, auto-follow and timeline groups. |
| MIDI control | MIDI control and MIDI Learn are described in TuneIT documentation; validate the required mapping on your build. | Documented MIDI and MIDI Show Control input. |
| OSC control | OSC support is documented; use TuneIT’s own verified addresses and settings. | Documented OSC control with a published QLab command dictionary. |
| Scope of this comparison | Evaluate for the audio pads, playlists and control functions your show requires. | Broader cue environment documented for audio, video, lighting and show control. Do not infer equal scope. |
Sources: TuneIT features, TuneIT documentation, QLab system recommendations, cue carts, cue sequences and the QLab manual. Product documentation reviewed 13 October 2026. Consult each vendor for current availability and licensing.
Where TuneIT may fit a Windows playback rig
- Put frequently used effects or stings on pads so an operator can identify and trigger them directly.
- Keep preshow and interval music in clearly named playlists rather than mixing those tracks into the effects layout.
- Use waveform display and trim controls to prepare the start and end of an audio file before rehearsal.
- Evaluate MIDI or OSC control using the exact controller and software build you intend to take to the venue. A shared protocol name does not mean that two apps accept the same commands.
What to test before moving a show
Build a small trial project using your own audio: one short effect, one longer cue and a short playlist. Listen through the intended output device. Check starts, stops, overlaps, trimmed boundaries and recovery after a mistaken trigger. Then repeat the test with your external controller, if the show needs one.
For a production already programmed in QLab, make an inventory of cue types, dependencies, routing and operator actions. Confirm each requirement separately. Where a feature has not been demonstrated in TuneIT, leave it marked as unverified. Rebuilding a cue by hand also means rehearsing its timing and operation again.
When keeping QLab may make more sense
If your production relies on QLab-specific sequencing, media cues or an established workspace, changing the playback application may introduce more work than it removes. Assess the full production, including the operator’s training and the venue’s equipment. Choosing TuneIT for a Windows audio rig does not require treating either product as universally better.
Try the audio workflow first
Read TuneIT’s feature overview, use the official downloads page and check current licence and rental options. Those pages remain the source of current download and purchasing information. For a production-focused example, see theatre sound playback.