A remote editor shouldn't need to download 400GB of footage.
When footage, versions, and feedback live in separate places, every revision round costs time. NGDS keeps the whole production connected so editors can start cutting sooner.
Before
The revision round bottleneck
Footage too large to send
A single day's 4K footage can run into hundreds of gigabytes, making it impractical to upload to a client or a remote editor over a normal connection.
Feedback loses its timestamp
A client says "fix the cut around the middle" over email, and there's no way to pin that comment to the exact frame they meant.
Which export is the final one?
After three rounds of revisions, editors end up with v2_final, v2_final_FINAL, and v3, with no clear record of which one the client actually approved.
Proxies eat local storage
Keeping both the original 4K footage and lower-resolution proxies for editing quickly fills up a laptop's drive on longer projects.
After
The NGDS review workflow
Upload once, edit remotely
Upload raw footage once to a shared project folder, and let remote editors work from lightweight proxies without downloading the full files.
Comments pinned to the timeline
Clients leave feedback tied to a specific timestamp in the cut, so "fix this part" always points to an exact frame.
One labeled version, always
Every export is versioned automatically, so the approved cut is always the one clearly marked as final - not a guess between file names.
Proxies live in the cloud
Keep editing proxies in the workspace instead of on a local drive, freeing up space without losing quick access to footage.
Stop guessing which cut the client approved. Know exactly which version is final.
