This is a nice problem, thank you. We could use track references, of course, perhaps one way (‘pick a track as the root for one source’) or bi-directional. Bi-directional becomes unmanageable, of course, if there are many tracks per source. We would need a crisp definition of ‘the same source’ no matter what we do. Or perhaps not (the writing application can choose, it can be application specific).
We are going to try ‘csrc’ (common source) track references, and say that tracks coming from a common source should have at least a single track reference from each track except one, to a ‘root’ track for each source, and that there may be more track references (e.g. to create a full mesh).
Dostları ilə paylaş: |
