Validation Errors
Flow Capture has the ability to check the uploads of some files for common mistakes before they're sent up to our platform, saving you the time and stress of waiting to see whether or not your file matches our requirements. When this is enabled, you may receive a notification from us and be directed here for more context about the message you're seeing.
DNx Filename Matching Exception
Video files matching your DNxHD audio file could not be found. Please check that your audio file names are suffixed with "_A01,", "_A02," etc. and otherwise have the same name prior to upload.
What It Means
We can't detect properly matched audio files for the DNxHD video that's being uploaded. MXFs uploaded with a video file can't be processed correctly, so you'll want to make sure the audio and video files use the naming scheme we require.
DNx Filename Multiple Matching Exception
Multiple DNx video files matched this audio file. Please check your upload file names match prior to upload.
What It Means
We're detecting more than one video file for the audio files that are listed in the upload panel. We recommend double-checking that all the file names are correct so that each video is matched to its intended audio files. If there are duplicate video files, removing them would be best, as it would eliminate the likelihood where only one of the videos has an audio track after processing.
Dolby Vision Filename Matching Exception
A matching Dolby Vision metadata and video pair could not be found. Please confirm that your files have the same name, including the “dovi_” prefix, prior to upload.
What It Means
A successful Dolby Vision HDR upload requires a pair of video and XML files with names that match exactly. The files that we can see in your upload have at least one video asset that's missing its XML, or an XML that's missing its matching video file. If you have both, make sure they have the exact same file name that stars with the "dovi_" prefix.
Dolby Vision Filename Multiple Matching Exception
Multiple Dolby Vision video files matched this file. Please check your upload file names match prior to upload.
What It Means
Dolby Vision uploads require one video and one XML file and we've detected more than one video file that can be paired with the XML in your upload. Removing the duplicate videos should fix this for you.
Dolby Vision Metadata Exception
The Dolby Vision metadata could not be validated with the Dolby 'metafier' tool. Please ensure your Dolby Vision metadata is valid prior to upload.
What It Means
The metadata in the XML that you're uploading could not be verified by Dolby's validation tool. Running the XML through the Metafier tool should help you find out what's wrong.
Dolby Vision Metadata Frame Range Mismatch Exception
The Dolby Vision metadata frame count does not match the frame count of the video file that you have uploaded. We recommend double-checking that you uploaded the correct files and verifying the frame counts with Metafier.
What It Means
There is a mismatch in the frame count of your Dolby Vision XML and its associated video file, which can result in incorrect shot timing and processing issues. This is another case where putting the XML through Dolby's Metafier tool should help you find the cause of the issue. You may also need to re-export the video file.
Dolby Vision Metadata Frame Rate Mismatch Exception
The Dolby Vision metadata does not match the frame rate of the video file that you have uploaded. Have you uploaded a mismatched pair of files?
What It Means
The frame rate listed in the XML for your pair of Dolby Vision files does not match the frame rate of its video companion. Double-check our specifications to make sure the two files you're uploading are the right ones and have not accidentally been given the wrong names. You may also need to re-export the video file so it matches the expected from rate of the XML, or vice versa.
Dolby Vision Metadata Start Time Code Mismatch Exception
The Dolby Vision metadata does not match the start time code of the video file that you have uploaded. Have you uploaded a mismatched pair of files?
What It Means
The metadata in the XML half of your Dolby Vision file pair does not match the beginning of the video file's timecode. Check to make sure that the two files you're uploading are the intended pair. If they are, you should check the start timecode for each file to confirm they're the same.
Dolby Vision Not Enabled Exception
It looks like you are trying to upload a Dolby Vision file into a folder where Dolby Vision processing is not enabled. Please check that you are uploading to the right place or confirm that Dolby Vision is active with Flow Capture support before trying again.
What It Means
You're attempting to upload a Dolby Vision file where that setting has not been switched on. Continuing with the upload will result in an asset that cannot be processed correctly. Check with someone on your end to make sure you're uploading in the right place or reach out to Flow Capture Support (support@moxion.io) for further assistance.
Dolby Vision With Spurious Suffix Exception
Your file is prefixed with dovi_, indicating it is a Dolby Vision file, but is also suffixed with _hdr or _sdr. Dolby Vision files cannot have these suffixes. Please remove the suffix prior to upload.
What It Means
The file that you're uploading is sending our system conflicting messages. The dovi_ prefix indicates that it should be a Dolby Vision asset, but it also contains an _sdr or _hdr suffix, which is what we need to create HDR10 assets. If you're uploading a Dolby Vision file, you'll want to remove the _sdr or _hdr suffix. If you're uploading an HDR10 file, you'll want to remove the dovi_ prefix.
External Transcoder With Video Tune Parameter
Your folder is configured to have a processing tune applied to your uploads. Unfortunately your file has not been able to be processed directly by the Flow Capture transcode engine, so the video processing tune could not be applied. To upload this file, please ensure it matches our video upload specifications.
What It Means
You're utilizing one of our specialized video processing tunes which allows for better handling of film grain or animation and the file you uploaded had to be processed in our fallback servers. The processing tune could not be applied because the fallback servers do not have the same customizations as our native processing tools. To make use of the video tunes, you'll need to make sure your file is in line with our video upload specification.
File Truncated Exception
The file metadata indicates this file was truncated during generation. Please export or copy the file again before uploading to Flow Capture as this is unlikely to process
What It Means
This generally indicates the internals of the file do not match the length of the actual file. If you run the file through a program like MediaInfo, it will indicate the file is truncated. If you can play the file locally and scrub right to the end without error, you can try to upload the file and let it process. If it fails to process after that, the first step would be to re-export it. If it still fails after that, reach out to the Flow Capture Success team via support@moxion.io for further assistance.
Frame Rate Mode Missing Exception
No frame rate information was found in your source video and we have been unable to validate aspects of it for conformance with our upload specification. If this is unexpected, please check your file format against our video specifications.
What It Means
A check on your file's metadata indicated that there was no information about its frame rate, which would make our systems unable to process the file successfully. We would recommend checking our video upload specification or seeing if your file type is supported.
Frame Rate Variable Exception
A file's metadata indicates that it has a variable frame rate, which we don't support. Videos may fail to process or playback as it is incompatible with a number of platforms. Please convert the files to a constant frame rate and re-upload them.
What It Means
The video that you're trying to upload has a variable frame rate, typically associated with clips that come from iPhones or iPads. You'll want to bring any variable frame rate files into an editor and export them with a constant frame rate (e.g. 24fps, 23.98fps, etc.).
HDR Not Enabled Exception
It looks like you’re trying to upload HDR assets into a folder where that hasn’t been enabled, which could cause playback and color issues on certain platforms. Please double check that you’re uploading to the correct folder or refer to our upload specification for supported SDR formats.
What It Means
HDR10 and Dolby Vision support are not enabled by default. If your production is making use of either HDR format, then it may only be enabled in a specific folder. Check to make sure that the folder you're attempting to upload into is the correct one for HDR review.
Missing Video Metadata Exception
We are unable to extract video metadata from your source file and cannot validate aspects of it for conformance with our upload specifications. If this is unexpected, please check your file format against our video upload specification.
What It Means
The file that you've uploaded doesn't appear to be compatible with any that we support for upload and encoding for playback in Flow Capture. You should check our video upload specification and may need to re-export and upload the file.
Non-HDR Bit Depth Exception
Dolby Vision files are required to be 1-, 12, or 16-bit pixel depth in the YUV format, your file did not meet these requirements.
What It Means
A file's pixel pixel depth needs to be at least 10-bit in order to successfully produce a high dynamic range asset, whereas SDR clips typically have 8-bit pixel depth. You'll need to check this in your file's metadata and re-encode it to our recommended specifications.
Odd Video Width Resolution
This video’s width is an odd number and cannot be processed. Please re-export the file with an even numbered width and upload it.
What It Means
The resolution of your video's width is not divisible by two (e.g. 1920 x 1081) and our processing servers will not be able to convert the file for playback on Flow Capture. You'll need to re-export the file at a resolution with an even width (e.g 1920 x 1080) and upload the file again.
Requires Fallback Processing With Video Tune Exception
This folder is configured to have a processing tune applied to any uploads. Unfortunately your file cannot be processed directly by Flow Capture's transcode engine and the tune cannot be applied. To upload successfully, please ensure that it matches our video specification or disable the processing tune in the folder.
What It Means
You're uploading a file into a folder where a special processing tune has been enabled (e.g. film grain), but our customized processing servers cannot handle the file. We normally attempt to send the file to a backup option, but that doesn't have the ability to handle the specialized processing tune that's been enabled in the upload folder.
There are several options available to get this working; make sure the file matches our video upload specification, then re-export and upload it. Alternatively, you can either disable the processing tune on the folder you're uploading it to, or upload it into a different folder where no processing tune has been turned on.
Unable to Validate Exception
We have been unable to perform a validation step that we would normally expect to tun on this file. You can continue to upload, but you may experience issues it if does not meet our upload specifications.
What It Means
The pre-upload validation step we normally perform for the type of file you've added to the upload panel has been bypassed. This typically applies to DNx or HDR assets, where the check is designed to save the time of waiting for what could be an unsuccessful upload and processing attempt as a result of easy to catch errors.
We recommend enabling validation on all your uploads so we can do a check before the file is uploaded to Flow Capture.