A few reasons we are looking forward to trying out Frame.io

Posted

There are no right and wrong ways of delivering video content to clients over the internet these days. Many production houses use a variety of platforms from e-mail, large file transfer websites such as wetransfer and hightail, vimeo, youtube, google drive or wistia just to name a few.

We currently use a mix of vimeo pro and google drive to deliver draft and finished versions of videos to our clients and this has worked well for the last few years.

There is a new kid on the block coming though – and it looks very promising. Frame.io aims to “pick up where vimeo left off” in a sense that it offers a lot more features for client review, further ability for team collaboration and video sharing.

We are quite excited with the prospect Frame.io offers as having the ability to offer clients a seamless process to viewing their video content, providing changes and thoughts (on a frame by frame basis if they want), and downloading final versions all on a cloud based private viewing platform.

Frame.io seem to be keeping a lot of details close to their chest but according to their facebook page, the platform will be launched by the end of March 2015…

We will be providing our thoughts as soon as we get our hands on it!

Here are some of the frequently asked questions that Frame.io have answered:

 

Some Frequently Ask Questions for Frame.io

  • I signed up, now what?
    Sit tight. We’re still working on getting to our 1.0 release. You’ll get an email when it’s ready.
  • Is the product in the demo video an actual working app?
    Absolutely. It’s being used by real humans on real projects right now.
  • How do uploads work? Is it through the browser or FTP based?
    Browser. Our acceleration makes browser uploading as fast or faster than FTP.
  • How are you accelerating uploads, that sounds like bullshit.
    True, but we really are. We’ve built technology that overcomes inherent limitations in the http protocol.
  • Is there a max upload size?
    No. Upload anything (up to 5 terabytes per file).
  • Where is the media physically stored?
    It is stored on our servers which are currently located in the United States. Your media may be physically stored in a location nearest you.
  • Where is Frame.io physically stored?
    Our office is in New York City. Stop by and say hello.
  • Can I only upload video?
    You can upload anything. On day 1 we’ll have support for many video, audio, and still formats. If we don’t have support for something you can still upload it and use Frame.io for file sharing, you just may not be able to preview it inFrame.io.
  • When will it be ready?
    I’d tell you but then I’d have to kill you. In all serious, we’re not sure. We’re working as quickly as we can but we’re not ready to announce a release date just yet.
  • Will you restrict the use of copy written music like Vimeo?
    No. Frame.io’sy purpose is for fostering the creative process and we know that often involves using temporary music before it is licensed or before final music is selected/composed.
  • Do I ever have to worry about privacy or handing over copyrights?
    Absolutely not. You are and always will be the sole copyright owner.
  • Does Frame.io have the ability to be hosted locally?
    No
  • Can I invite clients/collaborators to view something without requiring them to login?
    Not yet. You’re talking to someone who hates managing logins and passwords so I completely get why you want this. But really good collaboration requires identity. Imagine Facebook with no identity, doesn’t work. We’ve made the invitation process as seamless and smooth as possible. We will be supporting Google Login which means after receiving an email invite, your collaborators could be in with 2 clicks. Link in email, first click. Login with Google, second click. Done. For those that don’t want to use Google Login, there will be other options. Once you’re in, there are no individual passwords that have to be remembered for projects. Rest assured we understand the importance of access without logins and we’ll have more to announce about this at a later date.
  • I heard something about cloud transcoding, can you explain that?
    Everything you upload is converted on our server into a high quality MP4 and WebM format. We understand how important quality is. Dropbox encoding is garbage, Vimeo and YouTube are pretty good. We’ll be on par with 1080p Youtube encoding, but slightly better. That means you don’t need to be compression expert. Just give us a high quality file and we’ll make sure it looks great and plays back great. We’re also going to try our darndest to manage gamma and color accurately. Give us time to untangle the Quicktime gamma management mess but we are committed to getting it right.
  • What are you doing about security?
    The entire Frame.io site uses 256 bit SSL encryption. This is the same level of security banks use to handle your online transactions. Media URLs are authenticated and signed on request to ensure only the appropriate parties can access them. Resources are authenticated at the object level which means each project, file, and even comment needs to be authenticated by a user by ID. Our data centers use state of the art electronic surveillance and multi-factor access control systems. They are staffed 24×7 by trained security guards. We are also looking into MPAA certification.
  • This sounds expensive, do you have the money to pull this off?
    Yes. Frame.io is privately financed.
  • You’ve built up a lot of hype, can you deliver?
    First, we never intended to build up hype. We just shared our vision and the hype happened on its own. Second, we can definitely live up to what we’ve promised but we won’t be perfect on day 1 and we’ll stay open and honest with our development.
  • How much will it cost?
    We’re crunching the numbers on this as we speak. We want to make it accessible and we’re still figuring out the best way to do that.

 

You can sign up to frame.io here


468 ad

Leave a Reply

Your email address will not be published. Required fields are marked *