We carried out tests with Vimond IO, an “off-the-shelf” SaaS cloud transcoding product and a MacBook Pro running some NLE software. We created six sequences of varying durations from 2 minutes to 60 and timed how long it took to create 5 difference variants, with different aspect ratios and bitrates.
Using Vimond IO, the rendering process beats the traditional approach for rendering when using a Desktop Editor, it even beats the modern Cloud based SaaS transcoder, which has impressive times but would still require a workflow and orchestration element that Vimond IO removes with it’s one click Rendering.
Vimond IO took under 5 minutes to render a 60 minute clip in 5 bitrates that could then be published instantly to the end destinations or packaged up and sent to a CMS for playout.
Export step with a traditional NLE
Lets examine how this critical export step can affect the entire workflow. When using a traditional on premise NLE or on premise Transcoding farm you are limited not only to the maximum parallel job capacity (how many jobs it can do at once) of the render service, but also any other bottlenecks in the entire end-to-end process: from network transfer speeds, storage read/writes, download and upload operations and the time it takes to jump between software suites.
For a 2 minute highlight clip, publishing a single story out to 5 locations, say Facebook, YouTube, Twitter, Instagram, your Website and an Archive Copy, this could take around 20 minutes. Not only will the render time take 5 times as long as Vimond IO, but you will have your device locked while it takes place, with any other tasks potentially slowing down the export. Then you’ll need to manually upload the file to each platform taking up the remaining 13 minutes. This is for one clip, now if you start to multiply this by the number of clips you need to publish each day it soon starts to add up making people and devices much less productive than they need to be.
Exporting with Vimond IO
With Vimond IO, we can reduce that total time to air down from 20 minutes to 3 minutes, not only is the render time reduced to under 1 minute, but the publish time is also much faster because you only need to enter the text for your post, hit publish and let Vimond IO do the work.
Obviously there are other variables, you could add graphics, other clips, voice overs or audio or still images and the time it takes to type the post varies from person to person. But in our test, taking one 2 minute clip from a live source - pressing render and publishing to 5 destinations took just under 3 minutes.
For 1 clip you save 17 minutes, for 10 clips you would save 170 minutes, for 50 clips you would save 850 minutes or 14 hours.
Of course not all clips are highlights and only two minutes long, with Vimond IO the longer the duration the shorter the relative time to render. A single 2 minute clip will take 25 seconds, creating 5 versions with different bitrates and aspect ratio takes 50 seconds. But a 60 minute clip will only take 2 minutes and 45 seconds to render, creating 5 versions with different bitrates and aspect ratios only takes 4 minutes and 5 seconds. Meaning if the publish time takes the same as the two minute example in the previous slide, you can have a 60 minute sequence published to 5 destinations in around 5 minutes.
Interested in learning more about how Vimond IO can benefit you?