Text selection and highlights states in the application are now more legible.
Toast notifications are now applied throughout the entire application.
Different message states in the Upload Manager are now clearer and more explicit.
Airbus and Boeing are the two top airliner manufacturers. Their planes are by far the most frequently seen in the skies. Yet Airbus pilots can’t fly Boeing aircraft without extensive retraining and vice versa. The vast majority of pilots spend their entire careers flying one brand or the other, but not both.
It’s easy to understand why pilots prefer to stay with their chosen aircraft manufacturer, and it’s equally easy to see why video editors remain loyal to their chosen editing systems. It’s the investment in time and money spent learning the product. It’s the muscle memory. It’s the experience and the know-how. It’s an editor’s confidence that she or he can get the job done for the customer. It’s being productive. It’s being able to sleep at night.
Workflow changes
Most editors are reluctant to make big changes to their workflows. That’s understandable – a stable, dependable workflow is a wonderful thing. And yes, experience and knowledge matter here too.
Sometimes though, things have to change. Occasionally the industry pivots to a new set of requirements that demand a new way of working. And when it does, the experience can be painful.
Why is it painful? Even with the best intentions, and the best technology, it’s very likely new skills will be required. Some people simply don’t like change. They are happy with the status quo and their feeling is “if it ain’t broke don’t fix it”. But it’s always wise to review working methods: can we make the production process easier, better and faster by implementing new workflow procedures?
Even slight differences can act as major roadblocks if they’re not well thought out. Bigger changes stop workflows in their tracks. Old production methods used to run without the user having to think about them, while new methods bring unwanted problems that suddenly loom ahead like an undocumented mountain range.
Mandatory media management
When Adobe’s NLE, Premiere, was first introduced in 1991, there were few, if any, competitors. As you’d expect, Adobe’s video editing software has changed radically since then. Computers are thousands of times faster. Storage is hundreds or thousands times bigger. And it needs to be, because acquisition, post production and display resolutions – and hence file sizes – have increased around eighty times since the ‘90s.
On top of all of this, video consumption has exploded, with new outlets, destinations and video-capable devices appearing so fast that it’s hard to keep track of them.
What’s more, tapes were physical. Every tape had a number and a location – probably on a shelf. They were tangible and simple to track. After the transition to digital, we started dealing with digital files. These had abstract naming conventions that were not obviously related to the content. As drives became bigger, content became more unstructured – and therefore harder to track.
This is the background to the story of how media asset management (MAM) systems have become crucial to virtually any size of post production facility, where it’s common for editors to collaborate on larger projects, and for storage to be shared and centrally managed.
It’s the inevitable result of complexity. Without effective media management, on all but the smallest projects, there would be chaos.
Adobe’s focus on video production has culminated in today’s Premiere Pro, which is used everywhere including Hollywood, where $100m+ blockbusters like Terminator Dark Fate and Deadpool have been cut on Adobe software. Partly to achieve scalability, but also to allow “best of breed” third party inclusion, Adobe has responded to this level of success by creating an accessible architecture where external software can appear though extension “panels” within the Adobe UI.
The above image showcases its new Flow panel connected directly into the Adobe Premiere Pro UI.
Meeting in the middle
EditShare’s FLOW Panel for Premiere Pro is a portal between two worlds. On one side is enterprise-level media management and on the other is the creative world of editing and post production with Premiere Pro. Two different specialties, each with an essential job.
Editors have their own set of priorities. Their skills marry productivity with artistic and aesthetic choices. Understandably, they are reluctant to step outside their optimized personal work environment.
The FLOW panel allows editors to stay inside their productive zone. To an editor, it is instant access to the power and scope of FLOW, without having to leave Premiere Pro. An immediate connection to their media from a shared and collaborative storage system without having to learn a new user interface.
Let’s have a closer look at why interfaces grow up differently, and why our FLOW panel is such a big leap for Adobe users.
The above image showcases its new FLOW panel connected directly into the Adobe Premiere Pro UI.
Center of gravity
Every successful company has its area of expertise which you could see as a “center of gravity”. EditShare is media management, collaborative storage, ingest, logging, and scalability (on premise and in the cloud). Adobe’s is all about editing, VFX, audio and easy interchange between these disciplines within the Adobe environment (between Premiere Pro, After Effects and Audition, for example).
This means each company has a differently evolved, separately optimized user interface. And, this is what defined the challenge of building the FLOW panel. Specifically – how do you present a significant element of FLOW functionality from within the Premiere Pro interface?
In technical terms, much of the heavy lifting was already done. Adobe has a developer partner program with a very deep, wide ranging SDK. EditShare also has well developed, published APIs.
So the tools were there for a reliable and stable connection. It was then a question of selecting the aspects of FLOW that editors would need to have the most direct connection with.
The panel will continue to evolve, but it already has some remarkable time saving features. It gives Premiere Pro editors the ability to search for content and get direct and instant access to all their media spaces on the EditShare video content management system, to see content that may have been archived long ago on LTO tapes or cloud video storage, see all metadata associated with each clip – user markers, automated audio transcripts, AI-assisted object recognition information, and more. Simply select and import media directly from the FLOW panel into a Premiere Pro project. Instantly switch between proxy and full resolution. Never leave the Adobe UI to find the clips you want.
Designed by editors for editors
The FLOW panel was designed by editors, for editors. Editors save time by not having to switch working environments. No duplication of effort. Most of all, there is a true and friction free round trip from Premiere Pro to FLOW and back again. The FLOW panel has a powerful core functionality, but it is full of thoughtful touches. For example, if you’re searching for some media in a tree of folders, the panel will remember where you were the next time you have to go back there. You don’t have to start again from scratch. There’s also the flexibility to switch between high resolution files and proxies. If you’re in the field and you find you don’t have the high resolution material to hand: the system can automatically download the fully editable proxy version to a local drive of their choice.
The continuous connection between your Adobe project and FLOW makes it possible for other remote users to review your footage, adding markers and comments on the fly, while you’re working in Premiere Pro.
Technical and artistic co-operation
EditShare’s FLOW Panel for Premiere Pro is the result of openness by both companies.The FLOW panel is an editors-first interface within Premiere Pro. It provides the maximum efficiency with the minimum friction.
When editing a Spotlight template, you can now customize the height of assets in a grid.
Back and forward buttons in Spotlight are improved.
Our guest Stacy Jones delves into how film production and brand marketing work hand-in-hand to bring some of your favorite consumer brands to the big screen.
The following interview is an excerpt from our video series, Production – In Conversation. To watch the full interview and see more video content, click here. Or you can listen to the Shift In Conversation podcast here.
Stacy Jones – CEO – Hollywood Branded Grace Amodeo – Marketing Manager – Shift Media
Grace: I’d love to start off by introducing yourself. Tell us about your company and what you do.
Stacy: I founded Hollywood Branded back in 2007 and we are a pop culture content marketing agency. What that means is we leverage Hollywood, celebrities, and influencers in order to have them become part of a brand’s marketing campaign or have the brand become part of their content. We work on TV shows, feature films, and music videos and we create product placement opportunities for the brand to be interwoven in the storyline to be used as a prop, a set or location, or a wardrobe item.
Our guest Darian Chornodolsky explores how interactivity can bring new life to all of your old digital content.
The following interview is an excerpt from our video series, Marketing – In Conversation. To watch the full interview and see more video content, click here. Or you can listen to the Shift In Conversation podcast here.
Darian Chornodolsky – VP of Platform Growth – WIREWAX Grace Amodeo – Marketing Manager – Shift Media
Grace: To get started, could you introduce us to WIREWAX and yourself?
Darian: I’m Darian and I lead platform growth at WIREWAX. WIREWAX is interactive video, and interactive video is WIREWAX. So I’ll get a little bit into what interactive video is, some of the use cases, and specifically how it pertains to reusing and recycling existing assets. Also talking about how in today’s reality of a halt in production, how content creators and content owners can really maximize their results with their existing video library. Recently I’ve been thinking about defining interactive video as the technology that allows content owners and creators to bridge that gap from passive viewing to engaging, active, and action-driven viewing. We’re used by brands, agencies, retailers, marketers, broadcasters — the bottom line is anybody who is looking to make their video work harder and to drive results with their video that go way beyond just a view count.
Our guest Zach Basner outlines how video content can streamline your sales team, and how to get started.
The following interview is an excerpt from our video series, Marketing – In Conversation. To watch the full interview and see more video content, click here. Or you can listen to the Shift In Conversation podcast here.
Zach Basner – Director of Inbound Training and Video Strategy, IMPACT Grace Amodeo – Marketing Manager – Shift Media
Grace: I’d love if you could start off by telling us about IMPACT on a high level, and more specifically what you do at the company.
Zach: IMPACT is a digital sales and marketing company. We specialize in training and consulting, so we train our clients to be fully self-sufficient when it comes to their digital sales and marketing success. We work with our clients for sometimes up to a couple of years to get them to the point where they’re fully confident, fully insourced, and fully in-house. And my role within the company is to oversee all of our training offerings, and also the way that we teach and talk about video strategy.
A MAM philosophy for a world requiring nimble production workflow from any location By Sunil Mudholkar – VP Product Management – EditShare
Media Asset Management Systems are everywhere. There’s a small MAM at the heart of every video editing system (NLE). These are, after all, essentially databases whose reports are in the form of a timeline. And, on a larger scale, in every modern media production facility there will be one form of video content management system or another. Most of these solutions have grown over time adding features and functions to a monolithic software stack that may end up providing the set of features you are looking for. However, these monolithic systems also end up with a lot of stuff you don’t need, and consequently, things you don’t want to pay for.
As more remote production workflows are supported and as media production workflows move to the cloud, the requirements of a media management system also change. One way to address these new requirements would be to continue adding to the stack. However, this isn’t actually helping solve the problem.
The better path: Skinny MAM
There are two essential parts to achieving skinny software, and hence Skinny MAMs. These are microservices and APIs. Microservices are the smallest possible fragments of software that still do something useful. An API is a standardized way to exchange data between software, including microservices.
Let’s just drill down here into what exactly defines a microservice. How do you distinguish a microservice from another, similar-looking piece of code that isn’t one? Simply this: ask what it does. If, in the description of the functionality of a piece of software there’s an “and” (as in: “it does this and that”), then it’s not a microservice. You can’t use an “and” when it only does one thing.
Microservices would be of little use if they were like single cell amoeba, floating around in an electronic sea, with no means to communicate with each other. That’s where APIs change everything. APIs are standardized, published interfaces to software modules. And because they’re public and fully documented, there are no surprises: if you send the right data through an API, it will respond with whatever it is you’ve asked for, as long as you stay within its capabilities, and obey its rules.
APIs aren’t just used for communication between microservices: they are for liaising with the outside world as well. This makes a microservice-based Skinny MAM incredibly flexible. All kinds of external services have APIs, so building a highly customized workflow becomes simply a matter of integration. New and previously untried workflows become dependable solutions, not science experiments, simply by selecting from the API a la carte menu.
Our FLOW media management solution embodies the characteristics of the Skinny MAM. It is lightweight, modular, and open – composed from the start as a set of microservices and complemented with a robust set of open APIs. Our strict adherence to a solution composed of microservices and APIs, allows us to deliver all the advantages of this modern architecture.
Applying microservices and APIs to collaborative video editing workflows
Imagine an educational establishment that uses Zoom for online teaching. Even though Zoom can record sessions, the options are limited and quite inflexible for anything other than a broad-brush approach. However, Zoom has a useful API that can talk to EditShare’s FLOW (a Skinny MAM). It means that a far more granular approach is possible. More importantly, it means you can make use of FLOW to edit and manage the content of your Zoom recordings leveraging Zoom as an input to build your content.
Another example: Closed Captions. Legally required in the US, closed captions contain text that can be utilized as metadata for the related video content. Since they exist with every piece of video, it makes sense to capitalize on the information they contain, treating them as free, instant metadata. FLOW’s openness allows you to connect with third party speech to text APIs, allowing you to build a system that will programmatically search for video footage according to what is being said in the closed captions.
There is an almost limitless roster of ways that the FLOW APIs can be used in combination with external data and other services to create an extended palette of capabilities.
A complete solution suite
EditShare’s Skinny MAM approach is the key to secure an open MAM functionality that’s also able to integrate with best of breed third party hardware, software and services, without any compromise.
FLOW sits at the top of the MAM technology stack. It’s equally at home on-premise and in the cloud, but it’s not the only part of the EditShare technology suite. At the other end of the stack, there’s storage, which can be implemented in on-prem, cloud, or hybrid configurations. Like FLOW, EditShare’s file system and storage management layer, EFS, has a full set of APIs. This set of APIs not only connect with the upper levels of the stack, but also allow EditShare users to work across storage platforms, with full redundancy and scalability, while maintaining superior performance.
