Transcoding and Non-Transcode Folders

Whenever you upload a file to Flow Capture, we run that file through a number of processes that optimizes it for playback, including transcoding to different bitrates and resolutions, DRM-related processes, streaming-related process, etc. 

There are a number of front-end transcode options available to admin users found in Folder Settings, including:

Allowable Playback Resolutions

When a video asset is uploaded, Flow Capture will automatically transcode a number of proxy files. You then have the ability to either enable or disable each of these proxies for playback by toggling them ON or OFF:

Importantly, since we always transcode these proxy files, you can toggle these ON or OFF either before or after uploading these assets. In other words, these toggles determine which proxy files are playable, not which proxy files are generated.

Having lower resolutions enabled can be handy if the production or someone on it is in a remote area and won't have a lot of bandwidth to work with.

Video Walkthrough Below

Transcoding to MXF

Typically used with our Immediates workflow, this allows files that are uploaded into a Folder to be transcoded into DNxHD36 or 45 formats alongside the standard playback files we create. They won't be viewable within Flow Capture, but they can be made available for download for anyone who needs something of better quality or that's more compatible with their timeline.

A user will need Admin or Downloader (No Watermark) permissions in order to be able to download DNx/MXFs and untouched original files.

Unlike lower playback resolution proxies described above, it's important to note that MXF transcodes are NOT automatically done, and therefore, this will need to be toggled ON before uploading. MXF transcoding cannot be done retroactively.

It's also important to note that transcoding to MXF increases the total amount of storage within your production on Flow Capture. Therefore, the creation of those files will impact any storage-related costs. 

Lastly, original files that you upload to make use of transcoding to MXF will need to have a resolution of either 1920x1080 or 1280x720.

Video Walkthrough Below:

Dynamic Range Transcode Options

Anytime you upload an HDR asset to Flow Capture, the platform will automatically transcode an SDR proxy. This will ensure that anyone who has access to view the asset who isn’t in an HDR enabled environment will still be able to view it, so long as you have "Allow All Playback" selected (which it is by default).

When then do, it will be labeled as SDR, so that they’re aware they’re viewing a proxy file, and not the original HDR file.

If you're working with HDR and want full control over the specifics of the SDR proxy, you can select the "HDR & User-Provided SDR" option. This alternative allows you to upload an HDR and SDR pair of files, and Flow Capture will combine them into a single playable asset. The dynamic range that plays back will then depend on the environment the viewer is in (HDR or SDR).

For more on this option, review our HDR & Dolby Vision help doc.

If you’re working with HDR and you don’t want viewers to be able to view in SDR at all, you can disable it by selecting HDR Only. Anyone with access who attempts to view in SDR will be met with an error message, and won’t be able to view the content at all.

Video Walkthrough Below:

Non-Transcode Folder

A non-transcode folder is essentially what it sounds like. Anytime an asset is uploaded with this toggled turned ON, Flow Capture will disable transcoding altogether, which means that we won't process the files at all, and simply store them on the platform.

Files uploaded can then be downloaded in their original, untouched state, by anyone who has download permissions. Since no transcoding happens at all, this should only be used when uploading files to Flow Capture that are not intended for playback or viewing within the platform.

A few things to note:

  • Transcoding of files cannot happen retroactively. In other words, toggling this to OFF will not make previously non-transcoded files available for playback, and therefore any files that a user would like to be make playable/viewable must be re-uploaded.
  • Similarly, if an asset is uploaded with this OFF and transcoded for playback, and then this toggle is turned ON, the original asset will still be playable/viewable within the platform.
  • Assets uploaded with non-transcode toggled ON will not be watermarked, since the assets are left untouched.
  • For any assets that are uploaded with non-transcoded toggled ON, iOS offlining will not be possible, since playing back assets that are offlined for an iOS device requires transcoding.

Video Walkthrough Below