Hacker News new | past | comments | ask | show | jobs | submit login

Kind of funny to me that they have to go so "thin client" with this.

You'd think there'd be some kind of "mipmap gateway" component to network-aware video editors, that incrementally re-renders scrub-quality and preview-quality renders of the timeline as the client tells it about project changes, and then streams those rendered changes back down the pipe to the client, proactively, into a local cache — without the client ever needing to (or even being allowed to!) hold the raw assets.

Then the local "fat client" editing UI could be snappy at pretty much all times — except for just after modifying the timeline, when it'd have to flush (some variable amount of) the preview cache. (And even then, the controls would still respond; just the preview and timeline-thumbnails would jitter, until the [active part of the] re-cache finished.)

Would this enable piracy? No! Who's going to want to release a 480p rip of a TV episode at this point? (And 480ps is all you need, for a functional live preview, when lining up ADB or B-roll or whatever else. Anything needing closer examination — VFX, say — could be rendered and sent by the gateway "on demand", as stills [on play-head stop] or as short clips [on first play after range-selection].)

(It would enable leaks... but so does RDP, if you combine it with local video-capture software. So that's nothing new.)




Join us for AI Startup School this June 16-17 in San Francisco!

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: