Re: [DCP-o-matic] DCPomatic Digest, Vol 49, Issue 2

Am 05.09.2016 um 19:36 schrieb Davide Sanvito via DCPomatic: Some people used to compare J2K encoding with 3D rendering. However, the computational load vs. bandwidth makes cloud based rendering much more attractive for 3D rendering applications, SETI@home. Typically, a single 3D frame would need hours or days of rendering. SETI sends and receives very small amount of data, but applies very complicated computations. For J2K, a typical standard PC can now encode about 6-10 fps. You need to send around 10fps of uncompressed source files AND receive about 10-20MByte/s of encoded J2k over your WAN to keep up with that. A suitable scenario would be a location with a very fast internet connection, but very slow single encode machine, e.g. a Core2Duo on a 200MBit/s broadband line. That's not very likely. Sooner or later, there will be GPU aided encoding as well. Currently, a dual CPU second hand XEON can get you near realtime encoding at around 600US$. Add another one, and you will probably get close to 30-40fps encoding rate for the cost of a single high end gaming PC. - Carsten