2 Read an existing DCP, adjust it, write it back out again, preserving things we didn't adjust;
3 perhaps being variably strict and pointing out errors.
4 Read multiple DCPs and pull bits out
5 Create a new DCP without having to remember to fill in every detail
7 Structures & their unique (important) components
10 "playlist"; entry points, durations of assets, frame rates, aspect ratios
16 MXF filenames (also CPL/PKL filenames)
19 Nothing (unless we support multiple volumes)
28 Load a DCP -> we get some assets [each with hash, size, filename] and a CPL (pointing to assets via real pointer or ID)
29 CPL its own class; then we can do things like
31 cpl->add_asset (picture, ...)
35 Can't see a drawback with this, and it's pretty much what is happening now.