<?xml version="1.0" encoding="utf-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments on: If the FxTree crashes when you open it, it is because&#8230;.</title>
	<atom:link href="http://www.xsi-blog.com/archives/206/feed" rel="self" type="application/rss+xml" />
	<link>http://www.xsi-blog.com/archives/206</link>
	<description>People and thoughts behind XSI in production...</description>
	<pubDate>Tue, 06 Jan 2009 07:12:46 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6</generator>
		<item>
		<title>By: Sam</title>
		<link>http://www.xsi-blog.com/archives/206#comment-15180</link>
		<dc:creator>Sam</dc:creator>
		<pubDate>Mon, 07 May 2007 05:07:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.xsi-blog.com/archives/206#comment-15180</guid>
		<description>I was able to successfully composite together a 2k film res animation that had many layers for a movie company logo and the FXtree worked wonderfully. Of course, I never saw it on big screen, but it looked good on my computer. :')</description>
		<content:encoded><![CDATA[<p>I was able to successfully composite together a 2k film res animation that had many layers for a movie company logo and the FXtree worked wonderfully. Of course, I never saw it on big screen, but it looked good on my computer. :&#8217;)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: chemkid</title>
		<link>http://www.xsi-blog.com/archives/206#comment-15172</link>
		<dc:creator>chemkid</dc:creator>
		<pubDate>Sat, 05 May 2007 22:02:52 +0000</pubDate>
		<guid isPermaLink="false">http://www.xsi-blog.com/archives/206#comment-15172</guid>
		<description>thank you very much!!

chem!</description>
		<content:encoded><![CDATA[<p>thank you very much!!</p>
<p>chem!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Luc-Eric</title>
		<link>http://www.xsi-blog.com/archives/206#comment-15170</link>
		<dc:creator>Luc-Eric</dc:creator>
		<pubDate>Sat, 05 May 2007 19:09:10 +0000</pubDate>
		<guid isPermaLink="false">http://www.xsi-blog.com/archives/206#comment-15170</guid>
		<description>The depth of field effect  needs to allocate a temporary RGBA floating-point buffer of the size of the color image, so that's going to be quite big - four times the RAM an RGBA 8-bit will take.  The size of the PIC file in disk, if that's what you mean, has no meaning, since it's a compressed format and must be decompressed.  But the .Zpic is uncompressed.  So if that one is  64 meg, and since the ZPic is only one channel, it tells me the the DOF is going to need a temporary buffer of 64x4 = 256 Megs of RAM.  That's a huge freaking amount of RAM, and it's only for the temporary buffer in the DOF effect.

So you may be saying you're compositing a single image, those images you're working with are  unusually big.  The FxTree isn't really thought to work on images large than 2000 pixels.   To handle very large images in 32-bit, software like Shake cut the image in tiles but the Fx Tree doesn't do this, it focuses on compositing images rapidly for video and HD, not IMAX.</description>
		<content:encoded><![CDATA[<p>The depth of field effect  needs to allocate a temporary RGBA floating-point buffer of the size of the color image, so that&#8217;s going to be quite big - four times the RAM an RGBA 8-bit will take.  The size of the PIC file in disk, if that&#8217;s what you mean, has no meaning, since it&#8217;s a compressed format and must be decompressed.  But the .Zpic is uncompressed.  So if that one is  64 meg, and since the ZPic is only one channel, it tells me the the DOF is going to need a temporary buffer of 64&#215;4 = 256 Megs of RAM.  That&#8217;s a huge freaking amount of RAM, and it&#8217;s only for the temporary buffer in the DOF effect.</p>
<p>So you may be saying you&#8217;re compositing a single image, those images you&#8217;re working with are  unusually big.  The FxTree isn&#8217;t really thought to work on images large than 2000 pixels.   To handle very large images in 32-bit, software like Shake cut the image in tiles but the Fx Tree doesn&#8217;t do this, it focuses on compositing images rapidly for video and HD, not IMAX.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: chemkid</title>
		<link>http://www.xsi-blog.com/archives/206#comment-15167</link>
		<dc:creator>chemkid</dc:creator>
		<pubDate>Sat, 05 May 2007 15:31:28 +0000</pubDate>
		<guid isPermaLink="false">http://www.xsi-blog.com/archives/206#comment-15167</guid>
		<description>thanks, that`s just fine!

but why do i have to change the image memory size to 720(!!!!) to composite a single image + zpic to create a dof-effect?!!! the pic is 30mb and the zpic 64mb. the final swap-file created is 740mb... hmmm.

everything lower than that keeps crashing the composite with a nice message to raise my image memory size settings to something like 900mb.

the tempdisk is on a seperate drive... so space shouldn`t be the problem.

sorry to bother all the pros with a somewhat ...question, it`s like i solved the problem for me (for a stillimage comp only) and now i got a hint that i messed up my memorysettings, again...?!!!

have fun and happy xsing!!!! 


chem!</description>
		<content:encoded><![CDATA[<p>thanks, that`s just fine!</p>
<p>but why do i have to change the image memory size to 720(!!!!) to composite a single image + zpic to create a dof-effect?!!! the pic is 30mb and the zpic 64mb. the final swap-file created is 740mb&#8230; hmmm.</p>
<p>everything lower than that keeps crashing the composite with a nice message to raise my image memory size settings to something like 900mb.</p>
<p>the tempdisk is on a seperate drive&#8230; so space shouldn`t be the problem.</p>
<p>sorry to bother all the pros with a somewhat &#8230;question, it`s like i solved the problem for me (for a stillimage comp only) and now i got a hint that i messed up my memorysettings, again&#8230;?!!!</p>
<p>have fun and happy xsing!!!! </p>
<p>chem!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
