Return-Path: Received: from mail-ie0-f169.google.com ([209.85.223.169] verified) by media-motion.tv (CommuniGate Pro SMTP 4.2.10) with ESMTP-TLS id 4893219 for AE-List@media-motion.tv; Wed, 07 Nov 2012 14:33:07 +0100 Received: by mail-ie0-f169.google.com with SMTP id 10so2206347ied.28 for ; Wed, 07 Nov 2012 05:36:09 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=from:content-type:message-id:mime-version:subject:date:references :to:in-reply-to:x-mailer:x-gm-message-state; bh=uRhMO4IavIPrtD3YK+0GAA54TIQD0y0SLjr1hwWSwTc=; b=jzGQ4Sw5FaFnNCcNjWfgq+hso0VJw3W2Q8gv8emya3r0BVMx/spZMxg7aGfJHM+Gjk cDolnxfwwS+JbfsDubM8VTma1DPr+UFuQSoHZsdXadZ4EZYdcz/CG6NHqghBN9zGEGAD naxBzERzVzn/RQt+y2rF/6MxXiycXS6zT31Y6OXL27/0mbgbVs0gAe7lJq0NGeU8c/xW ecvm5xksPViMvNAVVVrTfGJvg6PHb3BdsAtDSGuCylc6M57/2dgpqZjxJQFPR9yIHajC xV9faG3kx6XEfa0C5d60UsVQBtphXCK7y7sPXbWGHrnGfgbHxFa6ehx+csU9NO+Rv/qH i9Xg== Received: by 10.50.190.232 with SMTP id gt8mr4542515igc.69.1352295369160; Wed, 07 Nov 2012 05:36:09 -0800 (PST) Return-Path: Received: from [192.168.1.227] (c-71-63-186-29.hsd1.mn.comcast.net. [71.63.186.29]) by mx.google.com with ESMTPS id ex10sm2038389igc.15.2012.11.07.05.36.04 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 07 Nov 2012 05:36:06 -0800 (PST) From: Carey Dissmore Content-Type: multipart/alternative; boundary="Apple-Mail=_D83C125A-3D45-4105-AD61-C3BEEA54716C" Message-Id: <4DFF5B8E-E5EC-4C01-B3DB-FE40CB41C1E0@imugonline.com> Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\)) Subject: Re: [AE] OT: Apple contemplating switching from Intel CPUs Date: Wed, 7 Nov 2012 07:36:02 -0600 References: To: "After Effects Mail List" In-Reply-To: X-Mailer: Apple Mail (2.1499) X-Gm-Message-State: ALoCoQmO7/d+EVFHIpPnpY8BUTSsx+EHiGFCjbm4VkLUUmKvlrBiUiEY4LvlwDGT9lfr2qZ/tQwL --Apple-Mail=_D83C125A-3D45-4105-AD61-C3BEEA54716C Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=windows-1252 Hey Teddy, Just to be clear, I'm actually saying I think the whole "image = processing on the cloud" thing actually will happen at some point, but I = see the most obvious bottleneck being how to get massive source material = from point of acquisition up to the cloud servers in short order. Once = it's "up there" a lot of things can become possible with thin clients = and streaming a single video output stream back to the user. Look at the = OnLive gaming platform. The tech is good even if the business model, in = that case, suffered. But at the same time I'm also not saying we are all = dumping desktop computing in short order either.=20 Carey On Nov 6, 2012, at 6:01 PM, Teddy Gage wrote: > I'm with Carey. I was in the middle of an email about this when I read = all the replies, so I scrapped it. He said everything I was saying. = Basically, I don't think the "desktop" will ever just go away. Once you = start getting into physical simulations, like realflow or fumeFX, even a = brand new hex core workstation feels like working on a cellphone from = 1993. Not even to mention rendering that stuff at 4K with GI and = raytracing etc. I don't even think we'll hit some kind of limit where = "ok, this is fast enough", because it can always look better or render = faster.=20 --Apple-Mail=_D83C125A-3D45-4105-AD61-C3BEEA54716C Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=windows-1252 Hey = Teddy,

Just to be clear, I'm actually saying I think = the whole "image processing on the cloud" thing actually will happen at = some point, but I see the most obvious bottleneck being how to get = massive source material from point of acquisition up to the cloud = servers in short order. Once it's "up there" a lot of things can become = possible with thin clients and streaming a single video output stream = back to the user. Look at the OnLive gaming platform. The tech is good = even if the business model, in that case, suffered. But at the same time = I'm also not saying we are all dumping desktop computing in short order = either. 

Carey

On Nov 6, 2012, at 6:01 PM, Teddy Gage <teddygage@gmail.com> = wrote:

 
= --Apple-Mail=_D83C125A-3D45-4105-AD61-C3BEEA54716C--