Especially as we all stay at home. But very few have an idea what that means. So we figured: Let’s just show what a remote collaborative session can be with the Quine tools and Adobe Teams.
We set up a session connected by a 10 mbit 4G line and a sloppy home wifi, with a windows laptop on one side and a Mac on the other based on 1,5 TB of originals + media we shot, captured and rendered along the way.
Most of this video consist of realtime screen-recordings as we communicate, share and edit a project and share new assets in realtime under sub-optimal conditions. Sound comes from shabby internet-lines as well.
Now let's break it down
Most of the functionality you see in the video is due to the automation in QI.
QI ingests, transcodes and distribute media from each participant
QI manages local smart watch-folder programmed to treat specific types of media.
QI runs the automatic download and sync of selected assets at each user’s station. You can sync any file-type, not only audio and video
QI recognizes media and treats assets according to project rules.
Using QI is mostly Drag and Drop operations, and your files will be delivered where they should be, without needing your attention.
The QuineCore webUI for mobile and desktop is the common workspace for all participants in a production.
We have different UI’s for mobile and desktop, and you can browse your assets by different category (like camera-originals, screen-captures, review files, location files or VFX renders)
With the consistency and metadata-matching throughout the process, we are able to share projects and timeline with remote participant in Premiere Teams with a click, as seen in the video.
In Premiere, updating the shared edit-project is as simple as hitting the “share” button.
The edit can be exported to a QI Smart Watchfolder, where it will be uploaded to QuineCore, in the review file Category with all notes and scene references from the original assets intact.
Anyone authorized, can review and add comments the edit you just did.
This video has taken you the process from ingest to delivery
Today, internet bandwidth is precious. As QuineCore keeps track of ALL assets in the production, we would only share the originals by request when needed.
In this example we only share the large files that actually needs sharing, and use proxies to get through the edit-phase. In addition to saving bandwith, this approach significantly speeds up turnaround and workflows.
How many have a P3 8k monitor at home, anyway?
For this particular session, the practical numbers were:
Upload 1,5 TB of original data through a web browser and manually tag all assets.
With the bandwith we had available, that would practcally ever have worked.
Share 50GB of automatically categorized Prores Proxy 720p and original audio.
1/30th of the original data size, which simply put made this possible, WITHOUT taking away access to the originals we might need and let Birk work on full quality edit-proxies on a 10mBit 4G line.
As many of us are staying at home and still need to keep up with work, many have asked, what is the tech requirement?
Technically, there are no specific requirements for your editing computer or your network outside a reasonably new laptop (2015 or newer) with Windows 10 or MacOSX 10.13 or higher.
As shown in the live demo, Birk was sitting in the forest with only a 4G 10mbit line. Working through a VM would not have been possible under those conditions.
There are many more ways to use the Quine tool-set, but we hope this video give you a hint of what is possible to achieve, even in non-optimum situations.
Like most of us face these days.
Any questions, or any specific production-needs in this special time.
Don’t hesitate to say hi.