Page tree
Skip to end of metadata
Go to start of metadata

There are three ways how to ingest your media files – FTP, upload manager in the browser, API. We can also provide an S3 bucket (push-based ingest) that you can upload your videos and asset files to. Please contact your account manager for access information. 

By using these upload types there are few important things to remember e.g. file naming pattern so that the files are packaged correctly!

To upload additional files to an asset after it is already ingested, in the editing panel click on Actions and choose Upload files.

To enable the use of Metadata editor and metadata upload, please contact you account manager, it is not available in self-service mode at the moment! 

Media File Naming

Media file processing can be controlled by properly naming the media files.

The file name format should be the following: assetID~name~LNG.bitrate.ext

Part of file nameDescription
assetID

All files with the same assetID in the same category will be grouped as one video asset.

Adding additional files to the same asset is supported but adding media files to a transcoded asset will result in a warning, except for subtitles.

name

Any name that does not contain ~ (tilde) or . (dot)

This field will be used as an asset Title.

If an option Update Asset Name From Video is selected in Client Settings, the asset Title will be updated from the video file if that comes after any other media file.

LNG2 or 3 letter language code according to ISO-639, example: ENG or EN
bitrateNumbers will be treated as kbps value for bitrate, all symbols will be used as bitrate title for players, for example: HD2500kbps
ext

Media file extension, example: mp4, wav, srt etc.

This will be used to recognize how the file should be processed.

There is certain processing for XML files. If they can be recognized as subtitles they are processed as such. Otherwise, they are processed as meta-data.

Above mentioned pattern including asset ID is the default. If you do not use ID and multiple files should be grouped, to add additional files e.g. subtitles, file name format should be following: videoassetname~subtitlename~LNG.ext

Or you can have a custom one by setting it in Workflow Profile.

Upload manager in the browser

Please note, that this is a new feature and some limitations may apply! Please follow file naming pattern suggestions and do not forget to choose category before existing upload manager.

Click on the Upload Media button in the Media section. 

Add one or many media files at once (video and audio tracks, subtitles) and press Upload. Do not close the pop-up window while files are uploading!

 After it is done you will be able to save these files to ONE of the Media Categories that already exist. Choose the category and click Save files in category.

It may take several minutes for the asset to appear in the media list! After the asset appears it will be processed automatically based on set Transcoding Presets and Workflow Profiles, that are assigned to a specific category. Or you can continue by editing media asset manually. 

FTP ingest

To ingest media files you have to use the FTP client software like FileZilla, Windows Explorer, command line FTP utility or any other. Connect to the FTP server address ftp://ftp.cloudycdn.services/ with your username (different from the portal username, see below) and password. You need FTP permissions to access your FTP account.

FTP Folders

Please observe the following folder structure for upload.

FolderFile typesComments
/ (root folder)noneNo upload here
/filesany

Uploaded files will be transferred to the Files section in the system.

Subfolders up to 5 levels will be created as categories in the Files section and files assigned there.

/media

media files:

mp4, mpg, m4v, mxf, avi,

ts, m2v, mkv, vob, webm, mov,

ac3, wav, mp3, acc, ogg, ifo,

bup, stl, vtt, ttml, srt, xml

Uploaded files will be transferred to the Media section.

Subfolders up to 5 levels will be created as categories in the Media section and media assigned there.

Please observe the media file naming convention given above.

Important! Ingest FTP folders are watchfolders. Files are moved from these for security, processing and streaming needs.

FTP username and password

Due to FTP account limitations, your username for FTP is slightly different than the username for Telia Video Cloud web portal. It retains the same user e-mail structure but all dots ('.') and '@' symbols are replaced by underscores ('_').

For instance, if your portal username is name.surname@domain.com then your ftp username is name_surname_domain_com.

You can change the FTP password in the portal by clicking your name on the top right corner and choosing Change Password from the menu. Make sure which password you are changing as there are both on the same popup window.

Media asset ingest validation for transcoding

To validate if all media asset files have ingested correctly and start automated transcoding as set in Workflow Profile, the XML ingest manifest file is used.

The sample XML file with possible tags and parameters:

XML ingest manifest
<!--
  TAGS:
    input - mandatory tag, any number of input tags per asset, each corresponding one media asset file
    type - VIDEO/AUDIO/SUB/DATA, this value is used to know how to check and process this file
    size - integrity check is performed to validate if the real size of the file is equal to the one in manifest
     
  Parameters per type:
    VIDEO - one video type track per asset allowed
        aspect - can be used to override the incorrect aspect ratio in the video metadata, option set in the transcoding preset
         
    AUDIO - single or multiple channels per audio track
        audioTrack - additional parameters
            language - the following priority list (highest=first) is used to set the audio track language - parameter in this manifest, file name language field, audio track metadata, transcoding preset setting, system default
            channels - number of channels in the audio track
    SUB - subtitle track
        subtitleTrack - additional parameters
            language - the following priority list (highest=first) is used to set the subtitle track language - parameter in this manifest, file name language field, transcoding preset setting, system default
    DATA - any data file
-->
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<media-asset>
  <!-- for video files -->
  <input type="VIDEO" file="12345678.ts" size="123456789012345">
    <aspect width="16" height="9"/>
	<!-- for audio tracks muxed into video file -->
    <audioTrack language="lav" channels="2"/>
    <audioTrack language="eng" channels="2"/>
  </input>
  <!-- for audio tracks in separate audio files -->
  <input type="AUDIO" file="12345678_lav.m4a" size="123456789">
    <audioTrack language="lav" channels="2"/>
  </input>
  <input type="AUDIO" file="12345678_oriL.wav" size="123456789">
    <audioTrack language="eng" channels="1"/>
  </input>
  <input type="AUDIO" file="12345678_oriR.wav" size="123456789">
    <audioTrack language="eng" channels="1"/>
  </input>
  <!-- for subtitle tracks -->
  <input type="SUB" file="12345678_lav.srt" size="123456">
    <subtitleTrack language="lav"/>
  </input>
  <!-- for additional files -->
  <input type="DATA" file="12345678_poster.jpg" size="123456">
  </input>
</media-asset>

Your other option of ingesting media is to use our API.

  • No labels