SILVERSTACK VS SHOTPUT HOW TO

If the validation fails there is likely a ‘bad copy’ in the chain, and you should.

If this does not solve the problem, please contact your assigned Production Workflow Specialist.

If the validation succeeds, then there was likely an error uploading.

Perform MHL validation on the problematic asset on the volume you uploaded from using a data management tool.

At some point files were not verified when copying them between local storage or volumes (from a RAID to a Shuttle or from a shuttle to a SAN, for example) and some files were corrupted.

Situation 2: Checksums of the files in the camera or sound roll being imported don’t match those stated on the MHL Suggested Action : Confirm that there is an MHL at the root folder of the roll being imported (in this case, the MHL file should be inside of ‘P002’ folder as seen resulting on the below image).

MHL Wrong Location - MHL is present, but not in the root folder of the selected camera roll.

MHL Missing - There is no MHL in the selected camera or sound roll.

Situation 1: No MHLs were found on the rolls you’re trying to import

You can click on it to review what the conflict is.Įrrors will almost always be one of the following four conditions: If there is a discrepancy between the MHL of a camera roll or sound roll and the files in Content Hub Workspaces you’ll see this error condition. If you are still encountering errors please contact your assigned production workflow specialist.

SILVERSTACK VS SHOTPUT HOW TO

Below are the troubleshooting steps on how to resolve these issues. When importing original camera files (OCF) and audio files through Footage Backup there are a few common errors that can occur.

Silverstack vs shotput