Entry № 041-3 / V-4361 · 0:00 synced

Our 36 Core Video Rendering Server – Finally Explained

Linus Tech Tips@LinusTechTips867.7K viewsOct 9, 201512:30
Source
YT
Views
867.7K
Subscribers
16.8M
Critic
?
Audience
?

0 up · 0 down · 0 ratings

Channels and socials

Our workflow has improved by leaps and bounds over the past few months. Today, we explain how... TunnelBear link: tunnelbear.com Logitech link: linustechtips.com Pricing & discussion: linustechtips.com Support us: linustechtips.com Join our community forum: bit.ly twitter.com @LinusTech Intro Screen Music Credit: Title: Laszlo - Supernova Video Link: youtube.com iTunes Download Link: itunes.apple.com Artist Link: soundcloud.com Outro Screen Music Credit: Approaching Nirvana - Sugar High youtube.com

Start
AI OverviewDefault language

Our 36 Core Video Rendering Server – Finally Explained walks through the origin and motivation for building a high performance render farm to accelerate a professional video editing workflow. The video begins with crediting Intel, Supermicro, Kingston, Noctua, and FSP for hardware and support, then frames the challenge: how to effectively leverage a multi–hundred core system to speed up encoding, transcoding, and final export without stalling editors. It explains that traditional encoding on a single workstation created long wait times, and that the team sought a scalable solution that could handle 4K workflows while keeping editors productive. Through a series of hands-on tests and comparisons, the presenters describe the exploration of multiple codecs and tools, the trade-offs of stability, and the ultimate choice of a pipeline that balances speed, quality, and integration with existing software. The narrative emphasizes the need for redundancy and a workflow that allows video editors to keep working while background tasks complete, which is positioned as a key win for the team’s productivity and timeline control. By the end of the segment, the team outlines the final ingest, transcode, and export process, highlighting the improvements to timeline scrubbing, render speed, and overall project throughput as a proof point of their approach. They also hint at broader implications for workflow design and the potential to scale the setup for smaller teams, underscoring that the demonstrated concepts are accessible beyond a full-scale studio environment.

Topics · technology · video production · hardware · workflow optimization · networking · 4k

Questions answered

What prompted the team to explore a render farm in their editing workflow?
The team faced long encoding times on single workstations and sought a scalable solution to speed up transcoding and export while keeping editors productive.
Which codecs and tools were considered before settling on the final pipeline?
They tested Telestream Episode, Sorenson Squeeze, and then evaluated DNxHD with CineForm as a mezzanine codec, ultimately combining Prelude for ingest and Media Encoder for transcoding.
What is the final workflow described for ingest to export?
Footage is ingested with Adobe Prelude, transcoded to a mezzanine codec via Media Encoder, monitored in watch folders, and finally exported to H.264 for distribution.