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 portal username, see below) and password. You need FTP permissions to access FTP account.
Your other option of ingesting media is to use our API.
Important! Ingest FTP folders are watchfolders. Files are moved from these for security, processing and streaming needs.
Please observe the following folder structure for upload.
|/ (root folder)||none||No upload here|
Uploaded files will be transferred to Files section in the system.
Subfolders up to 5 levels will be created as categories in the Files section and files assigned there.
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 Media section.
Subfolders up to 5 levels will be created as categories in the Media section and media assigned there.
Please observe media file naming convention given below.
Media file processing can be controlled by properly naming the media files.
File name format should be the following: assetID~name~LNG.bitrate.ext
|Part of file name||Description|
All files with the same assetID in the same folder will be grouped together as one video asset.
Adding of additional files to the same asset is supported but adding of media files to a transcoded asset will result in warning, except for subtitles.
Any name that does not contain ~ (tilde) or . (dot)
This field will be used as asset Title.
If an option Update Asset Name From Video is selected in Client Settings, the asset Title will be updated from video file if that comes after any other media file.
|LNG||2 or 3 letter language code according to ISO-639, example: ENG or EN|
|bitrate||Numbers will be treated as kbps value for bitrate, all symbols will be used as bitrate title for players, example: HD2500kbps|
Media file extention, 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.
Or you can have a custom one by setting it in Workflow Profile.
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:
<!-- 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> <input type="VIDEO" file="12345678.ts" size="123456789012345"> <aspect width="16" height="9"/> </input> <input type="AUDIO" file="12345678_oriL.wav" size="123456789"> - audio valodu prioritāte??? xml manifest, file name, media file track metadata, transcoding preset, system default <audioTrack language="eng" channels="1"/> </input> <input type="AUDIO" file="12345678_oriR.wav" size="123456789"> <audioTrack language="eng" channels="1"/> </input> <input type="SUB" file="12345678_eng.srt" size="123456"> <subtitleTrack language="eng"/> </input> <input type="DATA" file="12345678_poster.jpg" size="123456"> </input> </media-asset>
Due to FTP account limitations your username for FTP is sligtly different than the username for Cloudy CDN 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 firstname.lastname@example.org then your ftp username is name_surname_domain_com. You FTP password may be different from the password for the Cloudy CDN web portal.
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.