Yes, uStudio supports video file ingest via FTP.
Many of uStudio's corporate customers are set up to transfer batches of video files into the platform via file transfer protocol (FTP). This can make quick work of migrating various libraries as they consolidate onto the platform, or unearth inventories previously stored elsewhere.
Here's what it takes to use the FTP method:
- FTP ingest requires configuration on uStudio's side, as you'll need an FTP account with us. Certain license plans include this capability by default, but not all do. Contact email@example.com if you're not already provisioned with an FTP account.
- You'll also need an FTP client. Cyberduck, Filezilla and FireFTP (Firefox only) are examples of FTP clients you can use, or your company may have a standard client they prefer. YouTube is a great resource for learning how to use common FTP clients.
That's all there is to it, as the client helps you browse your existing inventory and select what to send to uStudio programatically.
What to expect with the FTP method:
- Our Current video file size limit for ingest into uStudio still applies when using FTP for video file ingest.
- When using FTP, you may not overwrite any files currently in your studio, so a newer file with the same file name as an older file will NOT transfer.
- Standard FTP accounts poll for new files roughly every 20-30 minutes, so consider FTP transfer a background task (not realtime).
- When videos are uploaded over FTP, they will show up in the studio as if they had been uploaded via the web. You'll get a filename and a thumbnail will be auto-generated, but any other metadata that may have existed in another system, like keywords, etc., will NOT get ingested.
If your organization could benefit from rich metadata mapping, realtime transfer (and response) instead of background-batch, de-dupe handling, validation rules and more, we suggest you consider our Video API method - the more powerful approach to volume ingest. Learn more here: How to use uStudio APIs to for video ingest