This update have focused on improving the experience for users working with Two Factor Authentication (2FA), which is now an optional setting in the Settings menu where administrators can set it as on, off or optional per user. We have also added support for automatically displaying multiple audio streams as unique tracks when loaded to the timeline. The best thing about this feature is that any content uploaded with multiple audio streams, will see all tracks displayed when loaded to the timeline from this point forward.
In this update we have been working hard on some of the underlying architecture in Vimond IO and this update has taken a little longer than normal due to some extensive testing. The result is that we have a new “Input” tab in the Settings menu that will allow users to add external sources to their workspace. As an administrator you can open the settings menu and connect external file based sources, such as S3 and Dropbox, or if you have accounts with Iconik and Mimir connect to those cloud based MAM solutions.
With all external sources the content remains external, meaning no duplicate copies or waiting time required until you can see your content in IO. Just connect the sources and voila! You can browse through all media (video, images and audio) in the input source without creating a local copy, if you wish to use the content in IO then simply localise it to your workspace. We have also included an update that allows users to add MediaPackage as a Live Streaming source. With this comes the ability to connect Vimond IO to your existing MediaPackage sources and pull live content when you need it. For customers with large amounts of live channels this is a great tool for saving costs, as ingesting that content is no longer required, you only pay for the time it takes you to playback and create clips.
Due to adding external sources we have decided to alter the Search provider list in the main editor. The difference between the old and the new is shown below. This change is made to clearly show what content is “Localised” in IO, and available in the Search Provider “IO Content” and what is external. We have also included quick filter buttons that can be enabled or disabled to see or hide Videos, Images, Music and Voice Over files.
Finally, we have also added support for Geo Restrictions in Facebook. For users that wish to publish content to Facebook to certain territories, they can specify where they have rights to content in Vimond IO and then publish to Facebook with those restrictions already in place.
Old Search Provider List
New Search Provider
filters (top) list (bottom)
AWS Elemental MediaPackage HLS Pull Live Input Source
Integrate Vimond IO with AWS Elemental MediaPackage, using
streams processed as a source for clipping, editing and distribution to digital platforms. Scale to any number of live input channels in Vimond IO without paying for additional outputs.
Geo Restrictions for Facebook
Enable the users of IO to geo-fence Facebook posts as required by rightsholder.
Iconik Input Source
Connect Vimond IO to your Iconik account, making all content available to the editor as a searchable source, localising a copy of the assets you wish to work with.
AWS S3 Input Source
Connect Vimond IO to your S3 buckets, making all content available to the editor as a searchable source, localising a copy of the assets you wish to work with.
Dropbox Input Source
Connect Vimond IO to Dropbox, making all content available to the editor as a searchable source, only localising the assets you wish to work with.
It is the third catch-up release before the delivery process can be properly streamlined to reduce time-to-production by being in step with the development cycle.
In this release we have provided a new feature supported by changes to our backend and user interface in the editor that allows any uploaded Image or Audio file to be stored as a source in the search provider list in the left hand panel in our editor. Additionally any voice over recording is stored. These are available in a new look list that sorts content types into discrete search providers.
Additionally it will now be possible to upload multiple files, including multiple types (image, audio & video) in a single upload action. This supports our belief that cloud editing should leverage single instance storage, providing more efficiency of making one file available to everyone instantly. By uploading once and using many times cloud editing will offer lower costs with a lower environmental impact.
Audio & Images Upload as Source Media - with multiple file upload support
The list of search providers is shown in the dropdown menu. For content that is uploaded manually via the UI, it is sorted into pre-set search providers common to all customer tenants. These are collections of content for audio & video (with or without audio, images and voice overs recorded on the timeline).
Adds the ability to set the publish flag in IO when publishing through the VIA platform. This speeds up the time to publish for VIA customers by giving the users the ability to skip the publishing step in VIA.
When publishing from Vimond IO to our VIA Content Management System, powering customers OTT
platforms, it is now possible to set a flag to “publish” those assets or not with a check box in the publish window that can be set by a user with an io-admin role as a Default.
The result will be assets created in the VIA platform are published and available for playback if available in the customers front end applications. Streamlining workflows for customers that just want to work in the Curation tool and trust all content is ready to be presented to the end users on the OTT platform. For customers that want a control step, the box can be unchecked requiring a manual “Publish” action in the VIA Content tool.
Vimond IO users are now able to add editable video and audio transitions to the timeline. These transitions can be cross dissolves, fade to/from black and audio fades.
The update also includes enhancements to the Render Settings menu, renamed “Outputs”, enables custom names to be assigned to each render output, such as “Facebook Square”, “YouTube 16x9”, “Twitter Profile” and “CMS 16x9 - Clean”.
In addition, users can choose to render their video file without graphics. This gives the users the ability to create renditions with branding for your customer facing platforms and a clean version for archiving, production or linear transmission workflows.