This is the first box is just for me.

Whoever is in the app, just enough with the same protocol is I choose the location on the Cloud Store where I want all of this information to go.

So right now, I have a media folder, I have a shared folder.

I'm going to go ahead and just create a new one and call it docs.

I'm going ahead.

So that creates a folder on the finder level in my cloud store.

I'm then going to go to the Dropbox location post here on Cloud for this purposes, the training video that we have set up, I'm just going to create a new folder docs set and then this interaction is very important.

It tells you which way the media is going to live.

So if you have read or write permissions essentially.

So if you do both ways, you have read and write access to every single file in that folder.

Same thing with anybody else that sets the access the same way.

If you wanted to just send it from your cloud storage to Dropbox, this would be the option.

And then as people connect their cloud storage, they would then head from Dropbox to Cloud Store.

And then with that option, all of the media that you then upload will download to their Cloud Stores only you have permission to that folder if they're just setting up their box to do Dropbox to Cloud Store, then they only have read permissions.

And this is the safest way for whoever is in control of their own media to stay in control of that raw media and not have someone else mess with it.

So if we're going to do cameras or any important documents that you don't want to have someone be able to modify it all, that's the workflow that we would use.

Anything else we would do both ways.

So anything that's in like a shared folder, any kind of music or graphics or sound effects that anybody can move around, anybody can copy and modify, You want to put those in to a shareholder and have the same direction people place.

That put your show on.

On Hulu, you were the only one that had access to the raw and you were making proxies that were sent to everybody but then correct anyone else.

Nobody could like mess with or affect the proxies on the main drive or the cloud or the raw media.

But if anybody added a song or any archival or stuff, wherever they were, it automatically sunk to everybody's boxes, right?

That that was correct.

Yeah.

So just as an example, in this case, the way that we did the same direction, this media folder only I have access to read and write everybody else that has a Cloud Store that's connected to this folder structure only has read access to it.

So that would be in the case of the Hulu show.

I would put the original camera media in here and then anybody that I wanted to access, they would only be able to download these proxies that are in here.

Just and while you're talking about that on Hulu, on Hulu, they shot for how many days a week, right?

And that there is a the eight terabyte drives, everybody had plenty of space to host all the proxies, but we didn't send all to anybody.

Right.

So it was like how much media did we use on that?

Correct.

We have about 40 terabytes on that big cloud store that you have with you right now that still has the right media on there.

And then this this cloud server that I have also has that media.

So on there, it took about 1.8 terabytes worth of proxies.

So going from 40 terabytes to 1.8 is a pretty, pretty big difference in the way that we did.

That was not how to set up the proxy generator to use H2 64 instead of process.

You can use whatever workflow fits you best just to save space, because we knew that we were going to have plenty of shoot days and plenty of terabytes to chew through.

HQ six four was the best option.