Michael Hoefler
Forum Replies Created
-
Hello Greg
We are doing the same here. I have in my office a server (MacPro 2009), and attached to this server is an LTO tape backup system. It is writing a backup once a day of our Project folder (Incremental). A Drobo is attached to this server, too, for additional safety backup (Chrono Sync).
The Project Folder gets synced with Resilio to three more PC Workstations. And additionally, it is selectively syncing to our remote freelance editors. They sync what they need. So, wherever we are editing, instantly, it is back synced to 4 PCs and once a day to an LTO and DROBO. Resilio is writing an Archive of all deleted assets and keeps it five days available on each machine. So a lot of safety. We never lost anything. And yes, the speed we have here in Switzerland is excellent in a lot of places but not all of our freelancers have fast internet. We are working with Proxies, and this is fine.Overall, it is a perfect solution for us. Costs are about $200 per year.
-
Hello Darren
95% of the time, it is a P2P solution. Sometimes, depending on the connection, firewall settings it uses a relay server. But this doesn’t mean you have to upload. It is just slower because a third server handles the connection.
MPAA compliance. I am not sure about this. We are here in Switzerland and doing only corporate video.
If we have to edit a confidential project we are editing it inhouse.I don’t know if this solution fits needs outside our small corporate world but I was surprised that a P2P solution is not discussed here at CC.
Michael
-
Hello Bob
Ok. We are working on Corporate video. It may be different from your needs.
Our project data volume is between 50GB and 800GB. We are working with HD, UHD, and 6k BRAW.First, I do create proxies. The editors sync the proxies and start editing. Then, after they synced the proxies, they start syncing the raw video data. So, over 2 or 3 days, they have even the 800GB of raw data synced to their workstations. There is no need to sync all raw data within some hours. And, we are using Adobe Teams. If we have projects over one or 2TB, they just work with the proxies and me on my workstation open the team project (which has the raw data connected) and export the final videos.
Don’t forget; I don’t have to upload first to a server. It is P2P for over 95% of the time. Sometimes the connection switches to a Relay server. Then the speed is dropping down.
But like with all solutions, the bandwidth has to be fast.Michael
-
Hello
I am reading/watching all the links with a lot of interest. But I want to mention a solution we are using for more than five years successfully for sharing our projects and footage.I am the only internal editor and I am working with 3 Freelancers. In our studio, we have an old Macpro (2009) acting as a server to provide 24h access to our projects through Resilio Sync.
https://www.resilio.com/sync-business/
It is fast, reliable, and P2P (no cloud server) is needed. We never had an issue, we never lost data, we never had a corrupted project. And it is not expensive.
I wonder, based on our very positive experience, why this is not mentioned as an option here for a remote workflow.Take care.
Michael
-
We are using Resilio Sync. Direct Peer to Peer. Our three freelancers get access to working projects, sync whatever they need. We have immediate access to the updated project because all gets synced immediately. We are using this system for over 5 years. Not one problem yet. Fast internet connections are necessary.
-
Hi Dave
well, actually I cannot help her. I think she is referring to the feature “Shared Projects” within a local team. We are working with editors in Switzerland, Germany, and the US. So, we are using the “Team Project” feature. Have no plan how the local version performs.
Sorry, Denisa.
-
Hello Dave
I have to say that Adobe Team works quite well for us (Team of 3 editors) since almost 6 months. We worked on about 30 projects so far and had not one serious problem. Well, in 1 out of 10 times it needs a second start to reconnect but that’s it. To be on the safe side we copy very often the team project back to a regular project in case we run into problems. For us, this adds so many opportunities and we will expand the usage. And we are avoiding some problems. For example, we have often problems opening regular projects on diverse platforms. Going from Mac to Win and vice versa. At some time during the lifeline of the project, it won’t open anymore on the Mac. If we convert to a Team Project, we can open this project on any platform at any time.
What you definitely need is a stable and reliable internet connection. Create snapshots of the project (save to a regular project).
We are very happy with Team Projects so far.
Michael
-
-
I don’t know if it is a value information for your plans, but I want to share our setup. We are not using a centralized server for data delivery.
We have 4 edit stations. Two Macs and two PCs. Our central server is a super micro workstation with a RAID 6, 16TB. All is connected with Gigabit Ethernet. Our server does not act as an central delivery station. It is only used for LTO Backup, all 2h, and redundant RAID 6 BackUp. All Workstations have a cheap RAID 0 attached. The syncing is done by BitTorrent Sync. The advantages are that all data is synced immediately to all workstations and to the server and we can use local RAID 0 performance for the editing. This way all workstations have all the data available at all time with RAID 0 speed. So, we have in total a backup on 5 workstations (included is RAID 6 on server) and a LTO incremental backup all 2h. Very safe.
BitTorrent sync is very reliable. We have small problems one or two times a year, with fast fix. Nothing got lost yet or corrupted. It is not expensive, fast and safe.Michael
-
Difficult decision.
Maybe this helps a little bit:
https://www.youtube.com/watch?v=NJt3av99e8k&spfreload=10
Michael
Some contents or functionalities here are not available due to your cookie preferences!This happens because the functionality/content marked as “Google Youtube” uses cookies that you choosed to keep disabled. In order to view this content or use this functionality, please enable cookies: click here to open your cookie preferences.