I will say though, I do miss the "selective sync" feature from Resilio. I currently use Syncthing to send huge media and project files back and forth between computers and it's been great during the pandemic. Syncthing has been working perfectly non-stop once I set it up. Resilio was easier to setup, but needed some regular maintenance to keep running. Syncthing just added support for untrusted folders (encrypted on other machines you don't trust), which is a feature that Resilio had for a while. I found sometimes with Resilio it would take up all my server's RAM for larger folders. I will say that Syncthing has been a bit faster and used fewer system resources. Syncthing is a bit easier to get ahold of since it's open source and free to use, however I think that Resilio is way more user-friendly for people not used to terminal commands. I ran it on Mac, PC, Android, and a Linux server. I used Resilio for years and have had decently good results. Nextcloud is the self-proclaimed evolution of ownCloud.The one thing that I do like about Resilio is being able to use the placeholders to selectively sync individual files.
In which case they'd have to wait a few hours in the morning before getting started. Nextcloud vs seafile I am currently using Resilio to sync files between my devices and my storage server, And i am looking to switch. I do have an editor who's wifi is spotty, and so they'd sometimes drop con during the night and not have footage in the morning. The system is smart enough to push and pull from whatever packets of data are most efficient. Make sure that the Agent is running under the 'Local System' account. A simple shut down of the project and pushing changes seems to solve it. This is done locally, and will also allow but not reveal the network share credentials to Management Console Administrators. We think it has something to do with client side markers being set, and teams trying to reconcile those differences.
The ONLY issue that sometimes comes up is metadata conflicts within Premiere. We just didn't have enough time to test and qualify. We're using TEAMS, rather than PRODUCTIONS, because of the fact that it's not local shared storage. The last thing I wanted to do was have the editor have to relink media because the drive name was different. This is a premiere show, and so I wanted to keep things within the same namespace for simplicity. (Dailies station drive SHOW1, Editor drive SHOW1, etc.). Now, I don't know if this is the right way to do things, but I come from an Avid BG, and so I decided to name the drives exactly the same for all parties. We have a MEDIA and COMMON folder structure. The Dailies account shares folders and sets permissions for workspaces. We have 5 Resilio accounts in total, 1 on the dailies station and the rest for each editor and assist. Hooked up are two editorial drives (SHOW1 & SHOW2). We have a central managing account running on our dailies station.
0 kommentar(er)
