Ce6: How to verify that the the latest version of a proxy or a source track are being used

Overview

Whenever we're working on a file, it's important that we're using the correct version of the assets we need to complete the task. During a revision, we need to be sure that we're correctly revising against an up-to-date proxy, and during a conform we want to be sure we're referencing the latest version of the source file.

Using the wrong version of a proxy or source file can cause discrepancies and errors, as well as result in wasted time and work having to be repeated. Whenever we see unexplained divergences between the proxy, the source track or our file, we should investigate for safety.

This article will explain some of the steps we can take to confirm that we're using the correct version of a proxy or asset track, as well as what to do if we discover that we're not.

File versions explained

First of all, we need to be familiar with the name of the proxy version we should be working on and, if applicable, which versions came before. These are likely to be different depending on the client and workflow we are following. For example, P1, P2, P3, Final, Final DCP, etc. in Theatrical, or Lock, Final, Final V2, etc. in streaming. We might also need to be working on a specific version of the proxy, such as an STX proxy or a dubbed proxy.

The proxy version will typically be indicated in the OM job name. We can check this from within the Tasks/Jobs view or in the Reports tab in OM.

Checking the proxy version

A revision involves updating previously completed configurations against a new version of a proxy. As such, a revision cannot be done against an old version of a proxy – any proxy-related changes will be missed.

Remember:

• scripting jobs will have a new job for each proxy version
• subtitling jobs will have a single job that is re-run for each successive proxy version.

Occasionally, an incorrect version of a proxy may be mistakenly attached to a job or a re-run might not correctly update the proxy version. In these cases, we'll likely notice that expected proxy-related changes aren't present. For example, a change listed in a change log may not be present or placeholder elements from the previous version may still be present in your proxy.

How can we check we're using the right proxy version?

There are a couple of ways we can check that you're using the correct version of a proxy. The version name is typically present in the "Proxy" input shell:

Clicking on the Input shell will also take you to the following Asset page, where the proxy version can be found:

From within CE, this Asset page can be reached by clicking on the Asset ID# to the right above the proxy:

What to do if proxy version and job name don't match?

If the version name in the Job name and "version name" fields does not match the one you are working on (e.g. you are working at Final, but the version name displayed in the Input shell and Asset page is "Lock"), please flag this to Coordination immediately.

• IMPORTANT: This will need to be resolved before work can continue.

Checking the version of the view-only source track

When working on an English conform job from a different configuration, Ce6 is designed to display the source file we are conforming from in the track on the right side of our screen. 

The system is designed to load the latest version of this source file, so that when updates or version-ups have occurred, the track displaying on the right side should be updated in real time with any new deliveries of the asset.

However, due to accidental setup issues with the publishing of OM jobs, the source track can fail to pull the latest version of the configuration. So, it's important to know how to check for this.

Working with an out-of-date source track can cause editors to unnecessarily question discrepancies between the two displayed tracks and can easily become a source of confusion. Furthermore, it prevents the editor from having correct and reliable access to the latest version of the configuration the file was originally conformed from.

How can we check that the source track is pulling the latest version of the file?

We can click on the Version ID above our source track. This is the second numerical ID, displayed further to right, as per image below:

Clicking on this ID will open a separate page which will display which version of the source file is currently visible in the source track, in the fields highlighted below:

What to do if the asset track isn't the latest version?

If the version you're working on and the version name in the asset page do not match (e.g. you're working at P3, but the version name displayed in the Asset page is P1), please flag to Coordination. They will check if it possible to amend this or whether it will be best to just hide the source track altogether.

You can generally continue working when this issue occurs, but you will need to be aware that the file you are seeing in the source track is not from the same pass you are working on, so discrepancies are to be expected and the source track will not be reliable in any way for comparing against the content of the live track you are actively working in.