Journalist Workflow Example
A journalist is in the field and uses ioGates’ upload App on the cell phone to upload a video clip. The journalist sets the option to add a prefix on the video clip filename, let’s say it is “Alert_filename” The file is uploaded to ioGates. ioGates will look for “Alert_filename” on all ingested filenames, and when detected, move the file to the shared folder and transcode the file to DNxHD.
The io App is then installed on the Media Composer workstation. When the DNxHD file is processed, the Desktop App will download the DNxHD file, and if the download location is the media bin, the files would be ready to edit as soon as the Media Composer updates the database.
NLE Workflow Example
Use the “Send to” option in the Media Composer and point the “Send to” to the io App upload location folder, then you will have an automatic upload to the ioGates Library. If the folder the uploaded files arrive in is shared, then share users will receive a notification mail that new files are ready.
Distribution Workflow Example
You need to set-up an automatic workflow to distribute video files in several formats to multiple destinations, and without your clients to manually download each selected codec.
From your internal workflow, your source file is ProRes HQ. Your local io App has a watch folder that is monitoring for new video files and will upload to ioGates. After upload ioGates will automatically transcode the ProRes to DNxHD, H264, HXCAM.
Your clients have three separate destinations, and each has a io App installed. As soon as the transcoded formats are ready, the io App on each destination will download only the format that you have created in the workflow for their respective client with the codec they prefer.