Known Limitations for Draft Sequences

• You cannot combine MediaCentral Asset Management and MediaCentral Production Management assets in a Sequence. This workflow is currently supported with shotlists and news sequences only.

• MediaCentral Production Management draft sequences cannot be opened in an editor such as Avid Media Composer.

• If you are working on a sequence created in the Production Management database, all assets in the sequence must have the same frame rate.

• If you add Production Management assets that contain markers to an Asset Management EDL, the markers are not retained.

Markers included in a Production Management sequence are retained during the editing process and are saved during sequence synchronization.

• After you save a sequence as a draft, some apps such as Browse or Search might not reflect the sequences updated draft status until you refresh the app. If you double-click on the original sequence without refreshing, the original (non-draft) sequence is loaded. The reverse is also true – where the app does not reflect the updated status after performing a Sync on a draft sequence.

• The draft sequence synchronization process does not support proxy-only Asset Management media. Assets must include high-res media to participate in the workflow.

• If your draft sequence began as a Production Management sequence, you cannot add audio-only assets to the sequence. If your draft sequence began as an Asset Management sequence, Avid supports adding audio-only assets to the sequence.

• If you plan to add a non-native asset to your sequence, the sequence must not already contain Production Management group clips. If your draft sequence began as a Production Management sequence, it must also not contain any audio-only assets.

• If you save a sequence as a draft and use the Hoverscrub feature in the Browse app you will scrub a proxy of the source sequence and not the draft sequence.

• You cannot perform “actions” on a draft sequence. If you right-click on a draft sequence in the Browse app, the context menu reports that there are No Actions available.

• If you create a draft sequence and then delete the original sequence from the source database, the draft sequence is lost and cannot be recovered.

• You must synchronize the sequence prior to using it in other workflows, such as Send to Playback.

• Draft sequences are not included in the Search app’s results list. After you synchronize the sequence, the asset can once again be found through the Search app.

If you use the Search app to load and convert an existing sequence into a draft sequence, Avid recommends that you verify the location of the source sequence using the Browse app. Since the sequence is removed from the search index after being converted into a draft, you will not be able to use the Search app to find the sequence in subsequent user sessions. You must use the Browse app or the tools included with your asset management system to locate the asset.

• If the status of a sequence changes from standard to draft, or the inverse, and you have the Browse or Search apps open with the sequence in view, you must refresh the app’s view before attempting to load the sequence. If you do not, you might load a copy of the sequence that does not reflect its current state.

• If your MediaCentral Cloud UX system is configured in a multi-site environment, you cannot add remote assets to a local draft sequence. For more information, see Working with Remote Assets.

• Additional limitations might exist. See the Avid MediaCentral | Cloud UX ReadMe for limitations found after the publication of this document.

In some cases, the Enterprise Editing workflow might allow you to perform actions on a draft sequence that should not be allowed. See the following example workflows for more information.

1. Use the Browse or Search app to load a standard (non-draft) sequence into the Asset Editor.

Result: Since the docked app has not been refreshed, it displays the original (non-draft) version of the sequence. If you load the sequence (e.g. double-click) from the docked app, non-draft sequence is loaded into the Asset Editor. Additionally if you right-click on the sequence, the context menu displays actions available for a standard sequence. If you attempt to perform an action on the (now) draft sequence, the action will fail.

Workaround: If you refresh the docked app, you can load this sequence into the Asset Editor to see the draft updates. The status of the sequence is updated and the context menu displays no actions — as expected.

Also note that the reverse workflow applies. If you use the Browse app to load a draft sequence into the Asset Editor and you synchronize the sequence without refreshing the app, the Browse app does not allow actions in the context menu. Refresh the Browse app to update the sequence’s status.

1. User 1 opens the Browse or Search app and loads a standard sequence into the Asset Editor.

Result: In this case User 1 has the original sequence loaded and the user interface has not been updated to reflect the new draft status. In this case User 1 might be able to perform certain actions which should not be allowed.