Return-Path: Received: from qmta12.emeryville.ca.mail.comcast.net ([76.96.27.227] verified) by media-motion.tv (CommuniGate Pro SMTP 4.2.10) with ESMTP id 5090327 for ae-list@media-motion.tv; Fri, 31 May 2013 22:07:48 +0200 Received: from omta04.emeryville.ca.mail.comcast.net ([76.96.30.35]) by qmta12.emeryville.ca.mail.comcast.net with comcast id ihkj1l0030lTkoC01kHKwM; Fri, 31 May 2013 20:17:19 +0000 Received: from sz0119.ev.mail.comcast.net ([76.96.40.138]) by omta04.emeryville.ca.mail.comcast.net with comcast id ikHK1l00g2yr1eL8QkHKtj; Fri, 31 May 2013 20:17:19 +0000 Date: Fri, 31 May 2013 20:17:19 +0000 (UTC) From: pixelbot@comcast.net To: After Effects Mail List Message-ID: <614043848.1415863.1370031439638.JavaMail.root@sz0119a.emeryville.ca.mail.comcast.net> In-Reply-To: Subject: motion blur weirdness - and fixed MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_1415862_1109363186.1370031439637" X-Originating-IP: [::ffff:107.1.199.10] X-Mailer: Zimbra 6.0.13_GA_2944 (ZimbraWebClient - SAF3 (Mac)/6.0.13_GA_2944) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1370031439; bh=lmyjg6+LG0RvT6aAT0VfatPLfHcwLFww6g3xnYYL+L0=; h=Received:Received:Date:From:To:Message-ID:Subject:MIME-Version: Content-Type; b=c4KPcZS2B6vet5id26mqadnYT1DKCxbUUfRLPsNEizwfZ/4jE1J2ZDT9N808RD8mF iNR+F7JXBL/rfE2T2h/UwyJXaxjBhwIwys8UQ/mdWWHGRxQL+BdU9Cpn6QpjQNegvz //C/zY0pZDw+GZW6cYcTFC60phxKeWW8rBH7sCofeebhHvC4e2KO1mHLCBp41o5hXT iGouorsDSOOOmzLizdeZKp6aG2jQJaFLXrPsQTjWH0RTlinCiklB1g0BVPQWN0IEXl O/xX9nr9xb1go8gufHIpUW9hIqZJ1Cl5U9Af8yckCDFrqKERfjvq11Vf/dV26YO2Pq LfvaLuSoYAhFw== ------=_Part_1415862_1109363186.1370031439637 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit I'm seeing some weird screen artifacts when I am applying the native motion blur on some elements I am using for a wipe transition - smaller bar elements are breaking up into 8 segments for 1 frame (I've loaded some frames up on to drop box so you can see) I also tried using the CC Force Motion Blur but I got some weirdness (which is also up on the dropbox) - it is hard to see as put it is just to the right of the middle - here is the dropbox link http://tinyurl.com/In8ld55 my particulars - this is created using solids in AE CS 6 - 11.0.2.11, and I'm seeing this on both a new iMac running OS 10.8.3 and the latest nVIDIA drivers and a 2008 MacPRO running OS 10.6.8. has anyone seen this or is there a fix - it seem to be when solids are moving off screen and less than 1% in width - In fact I think I just figured it out - when it is less than 1% in width - the image breaks up - If I change it to 1% width, problem goes way (well almost there is one break)- if I change the size of the solid rather than scaling it down so much it fixes it all together. I know I should file a bug report. if you run into this problem, now you know the fix timt ------=_Part_1415862_1109363186.1370031439637 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 7bit
I'm seeing some weird screen artifacts when I am applying the native motion blur on some elements I am using for a wipe transition - smaller bar elements are breaking up into 8 segments for 1 frame (I've loaded some frames up on to drop box so you can see) I also tried using the CC Force Motion Blur but I got some weirdness (which is also up on the dropbox) - it is hard to see as put it is just to the right of the middle - here is the dropbox link http://tinyurl.com/In8ld55

my particulars - this is created using solids in AE CS 6 - 11.0.2.11, and I'm seeing this on both a new iMac running OS 10.8.3 and the latest nVIDIA drivers and a 2008 MacPRO running OS 10.6.8.

has anyone seen this or is there a fix - it seem to be when solids are moving off screen and less than 1% in width - In fact I think I just figured it out - when it is less than 1% in width - the image breaks up - If I change it to 1% width, problem goes way (well almost there is one break)- if I change the size of the solid rather than scaling it down so much it fixes it all together.

I know I should file a bug report. if you run into this problem, now you know the fix

timt
------=_Part_1415862_1109363186.1370031439637--