Difference between revisions of "User:Mokurai/Moviemaking"
m (User:Mokurai/Moviemaking moved to Mokurai/Moviemaking: Correct name space) |
m (moved Anal bleaching 2/Moviemaking to User:Mokurai/Moviemaking over redirect: revert) |
| (2 intermediate revisions by 2 users not shown) | |
(No difference)
| |
Latest revision as of 18:04, 21 February 2010
See Kids with Cameras, which we should emulate everywhere. There are a number of other such organizations.
Limitations
The primary limitation of the OLPC for video editing is local storage. Assuming that there's 1G of storage, that 200MB is occupied by system code, and that half of the rest is used for other documents: that leaves 400MB, or, at a decent level of compression, about 15-25 minutes of video. If you're actually editing the video, at least half of it ends up unused, so really you have enough material for little more than a 5 minute short.
If you can rely on the backup storage, however, you could easily expect 3-5GB to be available to those editing video. This becomes more realistic/useful.
The trouble, then, is the network: using maximum throughput, without saturating and killing performance for the rest of the mesh.
Is there a way to get off the mesh and request a direct connection? The servers should have enough antennas to accomodate this, so it's more a matter of software.