Settings: Destinations
New Destination
Navigate to Settings > Destinations. Click on the New Destination button. Select a Type and fill in the details.- Filesystem Copy: Copies files to a folder on an attached filesystem. Any mounted drive works, including NAS shares.
- Vantage Cloud: Submits media to the Telestream Vantage Cloud service for processing. Requires a Vantage Cloud API key and an upload destination for the media.
- Vantage: Submits media to an on-premise Vantage server for workflow processing. Requires the host and port of your Vantage server, and optionally an upload destination.
- Amazon S3: Uploads files to an AWS S3 bucket. Requires an access key, secret access key, region, and bucket name.
- FTP: Uploads files to an FTP server. Requires the server address, username, and password.
- Dropbox: Uploads files to a folder in your Dropbox account. Requires signing in to Dropbox from the destination editor.
Edit: Filesystem Copy
When creating / editing a Filesystem Copy destination, these fields are available:- Type: (Required) The kind of destination. Switch to another type to change the fields shown below.
- Name: (Required) Name used throughout the application to identify this destination.
- Description: A short description to help clarify the intent of this destination.
- Destination Path: (Required) Folder that files are copied to. Use the folder button to browse for a location. Any mounted drive works, including external disks and NAS shares.
Edit: Vantage Cloud
When creating or editing a Vantage Cloud destination, these fields are available:- Type: (Required) The kind of destination. Switch to another type to change the fields shown below.
- Name: (Required) Name used throughout the application to identify this destination.
- Description: A short description to help clarify the intent of this destination.
- API Key: (Required) Vantage Cloud API key used to authorize submissions. Once saved, the key is never shown again.
- Upload To: (Required) Pick another destination where media is uploaded for Vantage Cloud to pick up. Currently, only Amazon S3 destinations are supported.
The Test Connection button (bottom left) checks that the API Key and upload target are reachable.
Edit: Vantage
When creating / editing a Vantage destination, these fields are available:- Type: (Required) The kind of destination. Switch to another type to change the fields shown below.
- Name: (Required) Name used throughout the application to identify this destination.
- Description: A short description to help clarify the intent of this destination.
- Vantage API Host and Port: (Required) URL of your on-premise Vantage server, including the port (e.g.
http://192.168.1.2:8676). - Upload To: (Optional) Pick another destination (Filesystem Copy, FTP, S3, Dropbox) to upload media to before Vantage processes it. Leave as ‘Never Upload’ if Vantage can already read the source media directly.
- Vantage Path: Shown when Upload To is a Filesystem Copy or FTP destination. The path Vantage uses to read the uploaded media. Example: an FTP destination that drops files into a folder mounted on the Vantage server as
V:\Uploadswould have a Vantage Path ofV:\Uploads. - Vantage Access Paths per Source: Choose how Vantage reaches files for the source:
- Upload: UP.Ingest copies to the Upload To destination.
- NAS: Vantage reads from a path you provide.
- UNC: Vantage reads the source’s UNC path directly. See below for details on each option.
Why does UP.Ingest need the Upload To destination?
In many cases, the media files are on your local computer or on a camera card attached to your local computer. Vantage has no access to your local computer drive or plugged in camera card. UP.Ingest needs to upload the media to some place that Vantage can have access to the media. Once the media is uploaded, we can then tell Vantage where the media is and it can start processing. That’s what the Vantage Access Path is for: it defines how Vantage accesses the files you’ve copied.Vantage Access Paths per Source
Choose how Vantage reaches the files for each source:- Upload: UP.Ingest copies the media to the Upload To destination, then points Vantage at the copy. This is the default for sources Vantage cannot reach on its own.
- NAS: Vantage reads the source folder directly using a path you enter (typically a mapped drive on the Vantage box). Example: an
smb://192.168.1.20/VantageFilessource. The Vantage server has smb://192.168.1.20 mounted on ‘G:’ drive. You would enterG:\VantageFiles. - UNC: (Windows only) For sources that are themselves UNC paths (
\\server\share\…). Select UNC if Vantage can use the same UNC path. Only available when the source itself is a UNC path.
Edit: Amazon S3
When creating or editing an Amazon S3 destination, these fields are available:- Type: (Required) The kind of destination. Switch to another type to change the fields shown below.
- Name: (Required) Name used throughout the application to identify this destination.
- Description: A short description to help clarify the intent of this destination. AWS Credentials:
- Access Key: (Required) AWS access key ID for the IAM user or role with write access to the bucket. Once saved, the key is never shown again.
- Secret Access Key: (Required) The secret paired with the access key above. Once saved, the secret is never shown again. AWS Location:
- Region: (Required) AWS region that hosts the bucket (e.g. us-east-1).
- Bucket: (Required) Name of the S3 bucket to upload files to.
- Storage Path in S3: (Optional) Relative path (prefix) within the bucket where uploaded files are placed.
The Test Connection button (bottom left) checks the credentials, region, and bucket.
Edit: FTP
When creating / editing an FTP destination, these fields are available:- Type: (Required) The kind of destination. Switch to another type to change the fields shown below.
- Name: (Required) Name used throughout the application to identify this destination.
- Description: A short description to help clarify the intent of this destination.
- FTP Server: (Required) Address of the FTP server (e.g. ftp.somewhere.com).
- Username: (Required) Account used to sign in to the FTP server.
- Password: Password for the account above. Once saved, the password is never shown again.
The Test Connection button (bottom left) checks that the server accepts the supplied credentials.
Edit: Preconfigured Destination
A Preconfigured Destination is a Vantage destination with a saved workflow, variables, and labels baked in. Submitting through one fixes the workflow choice, so you do not need to pick a workflow each time. It always belongs to a parent Vantage Cloud or on-premise Vantage destination and inherits its connection settings (API Key, host, upload target).Creating a Preconfigured Destination
From the Destinations list, open the row menu on a Vantage Cloud or Vantage destination and choose Add Preconfigured Destination. Preconfigured rows appear indented underneath their parent destination.Fields
- Name: (Required) Name shown wherever this destination appears.
- Description: A short description to clarify the intent.
- Configure: Opens an editor where you pick the workflow and set its variables and labels. The values you save here are reused on every submission.
Connection settings (API key, host, upload target) are inherited from the parent Vantage destination — edit the parent to change them.
Edit: Dropbox
When creating / editing a Dropbox destination, these fields are available:- Type: (Required) The kind of destination. Switch to another type to change the fields shown below.
- Name: (Required) Name used throughout the application to identify this destination.
- Description: A short description to help clarify the intent of this destination.
- Path: Folder inside your Dropbox where files are uploaded. Always starts with a leading slash (e.g. /Ingest/Inbox); one is added automatically if you leave it off.
- Authenticate: Sign in to Dropbox to grant UP.Ingest permission to upload to your account. Once authenticated, the button becomes Logout.
The Test Connection button (bottom left) verifies the Dropbox authorization.