Frame.io is a service used in the film/tv industry to upload takes/proxies to a collaboration share in the cloud. This allows editors to rapidly create dailies for the very same day. It would be great if Frame.io became a recognized application in the SpeedFusion Connect “Optimize Cloud Application” settings. Right now, we have to send the entire client device via SFC, which burns SFC bandwidth on other protocols/applications that don’t require the benefits of SFC.
Thanks
I think you should be able to do what you want using an outbound policy that matches traffic with frame.io domain as the destination and sets the connection to use SFC.
From memory a few sub domains are involved for assets / proxies / api calls etc. but they are all under the frame.io domain, there also used to be some s3/AWS related ones too but pretty sure those are legacy and are not required anymore.
We have clients using Frame.io Transfer, though for us the desire was to keep that traffic off the SF tunnels as the software multiplexes file uploads/downloads across multiple sessions/connections we found just standard session based load balancing actually worked well enough in most cases.
As an aside depending on your workflow and volume of data you might want to consider whether running your own FusionHub somewhere in the cloud, or potentially anywhere with suitable bandwidth might be more cost effective. SFC is a good service but can become costly if you are transferring significant data over it.
I will give the frame.io destination outbound policy a try.
I am the soundie, so my files are a lot smaller than the video guys. But will keep an eye on the usage and maybe a FusionHub Solo will make sense in the long run.
Some shoots are in cellular fringe areas and I was hoping FEC would help upload performance (I don’t have a dual modem Peplink, so the smoothing option I don’t believe would add much value since it’d be sending the redundant streams over the same fringe connection).
The device doing the uploads is a Sound Devices Scorpio which supports Frame.io’s “Camera to Cloud” solution. I don’t know if C2C hardware is smart enough to use multiple upload streams like their Mac/Windows software does…
When you make the rule you may find you need to place it above the grey box that says “PepVPN / OSPF / BGP routes” etc. to get it to take effect.
Gotcha, running your own FH Solo does add a couple of features in that you can also forward traffic to internal addresses from the public IP of the hub, might be a useful consideration if you ever wanted remote access to equipment behind your Peplink on site.
I’m actually going to have to go test how FEC works when you only have a single WAN, FEC maybe sends some data but smoothing certainly relies on having multiple paths. I mostly use smothing when doing live TX stuff and we care about getting a reliable few Mbps of traffic from one location to another, for bulk data upload you probably wouldn’t need either as they add overheads in terms of bandwidth consumption and as a result typically will reduce capacity.
I am not familiar with that bit of equipment, however if you were to fire it up and start sending data you might be able to see some of its behaviour if you navigate to “Status > Active Sessions” and on the “Search” tab put the IP of your Scorpio into the source box and see if it is looking like opening multiple connections to the same destiation.