Damaging Results of Mandated Return to Office – It's Worse Than We Thought

Re:Damaging Results of Mandated Return to Office – It's Wors... by Solvency on Wednesday June 28, 2023 @01:36AM (#36502687)

Virtually the entire VFX industry has shifted to remote. Let that sync in.

The most hardware/GPU intensive industry of creatives dealing with ungodly complex technical pipelines, terabytes of 32bit EXR frames of rendered data, Houdini fluid simulations, compositing, color grading, the whole works... is almost entirely distributed now.

They've done it. Everyone can do it. And are doing it.

[ Parent | on HN ]

Re:Damaging Results of Mandated Return to Office – It's Wors... by mh- on Wednesday June 28, 2023 @02:49AM (#36503192)

I'm curious (and not really familiar with modern VFX workflows).

Do they work with a mostly thin client approach now? I'm assuming it's impractical for them to regularly transmit terabytes of data back and forth over residential connections.

[ Parent | on HN ]

Re:Damaging Results of Mandated Return to Office – It's Wors... by jhugo on Wednesday June 28, 2023 @04:48AM (#36503952)

My wife works from home in a related industry, and she is quite frequently transmitting work files (up to 100s of GiB) over our residential connection. We have multi-gigabit symmetric FTTH though.

[ Parent | on HN ]

Re:Damaging Results of Mandated Return to Office – It's Wors... by ShadowBanThis01 on Wednesday June 28, 2023 @01:56PM (#36510115)

I think it depends on what they're doing. If they're doing animation (which includes moving elements in live-action footage) and mostly checking the quality of motion, they might get away with proxy renders. But anyone doing critical color or compositing I would think need to do local renders on a calibrated system, and then commit the work to a remote render farm for consistency and accessibility by other team members.

[ Parent | on HN ]