Will Duncan
Forum Replies Created
-
PC time. Nvidia ftw.
-
LTO is the obvious cold storage choice, a ZFS dataset for final projects that also syncs to Backblaze B2 is a solid system in my head as well.
-
We’ve tried it on a few occasions. I haven’t tried it with the purpose of this problem.
-
This is one of those situations where I’d call an integrator, like ALT Systems or Northshore Automation, who does a lot of sports work with archive/data implementations.
CatDV would be my top choice though, as I’ve used it at 4 sports institutions and being basically a MySQL database, flexible to the workflow you want to build.
It can certainly be handled in house, but there are A LOT of moving parts that I could spend weeks designing/implementing, and I don’t think an out of the box solution is particularly great. I’ve yet to find one. It’s been cost effective for me to have a solution delivered to my door. And I’ve tried to build my own on several occasions, with success and with failures.
-
Not really, there’s a lot of mixed media in the workflow, no proxies. Editing is fine, it’s just opening a project on another client that’s the problem.
-
No, these projects are across many volumes, but even if all the work is linked to just 1 volume, it still happens.
-
Thanks. Yes, I am aware of the BTRFS being the root cause of the slow rebuild time, unfortunately it’s not my box and it’s the cards I was dealt. But 9/10 Synology systems that other people set up will be set to the default without any thought, and it’s a problem I constantly come across.
However on most servers, including btrfs on bigger synology chassis back before I knew better, we’ve been able to work off them during a rebuild. Is the slowness of the server during a rebuild just a lack of horsepower? or bottleneck due to it being a 6-8 drive setup? On a 12 bay chassis I don’t hit the same limitations. On non btrfs systems, it’s never been an issue that I can think of.
-
CatDV doesn’t have to cost a fortune, and it’s expandable over time. I am not 100% a CatDV fanboy, but I do appreciate that it can example and be added to over time and is essentially infinite with how complex of a workflow you can integrate. It just depends how many clients you need to connect and which server you need to run. It does add up quick though when you start buying all the parts to a CatDV infrastructure.
-
I’m currently in the midst of a production that is utilizing a DS1618+ with 10GbE, and I’ve used the 19+ on several occasions. For a single editor or lighter load with up to 3 editors, they’ve held up fine. But under an intensive load (4k+, multicam or too many users) or during any type of maintenance/drive rebuilds they’ve been a pain. Mostly just running slow/bottlenecks for editors and nothing is worse than frustrated editors and nothing you can do about it because you didn’t want to spend $2000 more on much better hardware.
I haven’t used a QNAP in a heavy shared environment though, I was a fan of Synology because of the simplicity of the software/management and ease of setup, but I really only use them as file-servers and personal media servers. A QNAP at 3x the chassis price is well worth it for the hardware alone to avoid bottlenecks down the road. They appear to just be better built with a lot more horsepower.
As Bob was saying, I also haven’t installed or even seen a buffalo 10GbE switch in the wild. I would seriously consider the Netgear options he mentioned. I have been lucky enough to have Aristas for most productions I have worked on.
If you have one off-site editor, and you can control your workflow to have a very organized file structure, you could put a small synology or something on your remote editors desk and have it sync proxies over public internet to them. It’s possible depending on the amount of data you are typically sending at once. It’s also a small hard drive / shipment away if it’s too much to sync. Or consider researching if low-resolution proxies could work. Sometimes we’ve run into complicated problems during final assembly cause an editor worked int he wrong timeline size with low-res proxies and it adds a lot of hours to fix.