This page covers exporting part of a rundown instead of all of it. One block — the notices, the opening, a set of adverts — as a file somebody else can drop into their own list.
Exporting
Right-click a group header:
| Entry | What you get |
|---|---|
| Export group… | A .playoutgroup: the block and its settings, pointing at media where it lives now. |
| Export group as bundle… | A .playoutbundle: the same, with every file packed inside. |
You can also export a selection rather than a whole group: select the lines, right-click, and the same two entries appear with the number of lines behind them.
Exports go to DocumentsUltimate PlayoutExports.
Getting one back in
Three ways, all equivalent:
- Load group in the toolbar.
- Drag the file onto the cue list.
- Drop it onto a group header to put it inside that group.
The block arrives with its structure, its trims, its volumes and its follow actions intact, and is renumbered into its new surroundings.
Which of the two
A group file where everyone reaches the same media: within a building, on a shared server. Small, and everybody stays on one copy of the material.
A bundle where the media has to travel: another location, another organisation, a machine that is not on your network. See bundles.
What it is good for
| Situation | Why a group file fits |
|---|---|
| The same notices block on two campuses | Made once, sent, dropped in |
| An opening you reuse every week | Keep it as a file, drop it into each new list |
| Handing preparation to a colleague | They build one block, you assemble the show |
| A supplier who delivers a set of adverts | They send a bundle, you drop it in |
Practical notes
Name the group before exporting. The file takes its name from the group, and Group tells the person receiving it nothing.
A group file is not a backup. It holds one block; for the whole show, save the list.
Check the media paths after importing on a different machine. A group file that arrived from elsewhere is exactly the case where the missing-file warning does its work.