Bassam Kurdali at 2016-01-03T07:54:45Z

sorry I'm late to the party! for 'source' files you don't (often) want jpg, though it can work - we often like to use lossless compression and even higher bitdepth for image sources, increasing storage requirements even further! though it depends a lot on the nature of the particular project, I can see 'optimizing' projects for ease of sharing / hosting rather than quality as such. Other source files include blend (3d models/animation), raw data from cameras, svg, etc.

Git-LFS might be part of the solution, but it's not the solution on it's own. There are some specific problems related to work on animation/film projects that might be good to target before looking for a specific technology to use - another lil' issue is that artists tend to be much less tolerant of technical/command based interfaces, and we want to have a lower barrier of entry for them.

Claes Wallin (韋嘉誠) , Alex Jordan like this.

Claes Wallin (韋嘉誠) shared this.

Yeah, egardless if one uses git-lfs, git-annex or whatever solution, in the end someone needs to store all those bytes. :-)

Not to mention providing bandwidth for people to download them.

I guess the hopeful part is that Moore (for storage and bandwidth) might outrun increasing video bandwidth?

Claes Wallin (韋嘉誠) at 2016-01-21T19:06:01Z

Bassam Kurdali , Christopher Allan Webber like this.

@clacke - If increasing video bandwidth is a concern, keep an eye on the Daalva video codec, or NetVC or whatever it ends up being called.

Jason Self at 2016-01-22T03:47:33Z

Bassam Kurdali , Alex Jordan like this.

I wonder if a torrent-like method to distribute files would be suitable.

Bassam Kurdali at 2016-01-27T23:12:49Z

I wonder if a torrent-like method to distribute files would be suitable.
IPFS perhaps, or Freenet. If one, as a creator, has the storage and bandwidth to provide this, when one moves onto the next project.

Claes Wallin (韋嘉誠) at 2016-01-28T06:52:13Z

Bassam Kurdali likes this.