<?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"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Visual Effects Pipeline Projects and Interapplication Communication With Maya</title>
	<atom:link href="http://eddieoffermann.com/blog/2009/03/07/71/feed/" rel="self" type="application/rss+xml" />
	<link>http://eddieoffermann.com/blog/2009/03/07/71/</link>
	<description>The reel, resume and contact resource for Eddie Offermann, Pipeline TD, Visual Effects Scripter, CG VFX and Integration Artist</description>
	<lastBuildDate>Tue, 09 Mar 2010 22:39:41 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Eddie</title>
		<link>http://eddieoffermann.com/blog/2009/03/07/71/comment-page-1/#comment-106</link>
		<dc:creator>Eddie</dc:creator>
		<pubDate>Tue, 09 Mar 2010 22:39:41 +0000</pubDate>
		<guid isPermaLink="false">http://eddieoffermann.com/blog/?p=71#comment-106</guid>
		<description>A 4-day weekend in New Orleans had my mind a little foggy when I received your comment last night, but it occurred to me today that this is the same behavior (and probably for the same reasons) as a scriptJob.

commandPort functionality is much like a scriptJob - while we may monitor particular attributes or changes in the maya environment and execute a script in response to them, the time in which we may execute those scripts is limited.

Similar to the problem that you&#039;re having with commandPort, scriptJob will not process what are basically attribute-based interrupts during playback because to do so would substantially degrade playback performance. The system overhead required to check various conditions, listen for network signals, etc is too much of a (usually unnecessary) burden.

Or at least... that was the case when these commands were initially implemented. Nowadays, I&#039;d say the system overhead for such would be negligible: but the limitations remain.</description>
		<content:encoded><![CDATA[<p>A 4-day weekend in New Orleans had my mind a little foggy when I received your comment last night, but it occurred to me today that this is the same behavior (and probably for the same reasons) as a scriptJob.</p>
<p>commandPort functionality is much like a scriptJob &#8211; while we may monitor particular attributes or changes in the maya environment and execute a script in response to them, the time in which we may execute those scripts is limited.</p>
<p>Similar to the problem that you&#8217;re having with commandPort, scriptJob will not process what are basically attribute-based interrupts during playback because to do so would substantially degrade playback performance. The system overhead required to check various conditions, listen for network signals, etc is too much of a (usually unnecessary) burden.</p>
<p>Or at least&#8230; that was the case when these commands were initially implemented. Nowadays, I&#8217;d say the system overhead for such would be negligible: but the limitations remain.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Eddie</title>
		<link>http://eddieoffermann.com/blog/2009/03/07/71/comment-page-1/#comment-105</link>
		<dc:creator>Eddie</dc:creator>
		<pubDate>Tue, 09 Mar 2010 00:41:43 +0000</pubDate>
		<guid isPermaLink="false">http://eddieoffermann.com/blog/?p=71#comment-105</guid>
		<description>What platform are you working on?

I haven&#039;t encountered this problem: but I haven&#039;t tried to send signals during playback either.

commandPort has some quirks though: the inability to receive port signals to more than one instance of Maya and the related issue of occasionally not having the port surrendered by a terminated Maya instance, requiring a reboot are my biggest issues that rear their heads on a regular basis.</description>
		<content:encoded><![CDATA[<p>What platform are you working on?</p>
<p>I haven&#8217;t encountered this problem: but I haven&#8217;t tried to send signals during playback either.</p>
<p>commandPort has some quirks though: the inability to receive port signals to more than one instance of Maya and the related issue of occasionally not having the port surrendered by a terminated Maya instance, requiring a reboot are my biggest issues that rear their heads on a regular basis.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jeremy</title>
		<link>http://eddieoffermann.com/blog/2009/03/07/71/comment-page-1/#comment-104</link>
		<dc:creator>jeremy</dc:creator>
		<pubDate>Mon, 08 Mar 2010 19:10:36 +0000</pubDate>
		<guid isPermaLink="false">http://eddieoffermann.com/blog/?p=71#comment-104</guid>
		<description>I&#039;ve been using commandPort a bit and one thing I&#039;ve found to be slightly problematic is that I cannot issue commands during playback - even if I want to issue a play -state 0 command. Do you know if there is something I&#039;m missing?</description>
		<content:encoded><![CDATA[<p>I&#8217;ve been using commandPort a bit and one thing I&#8217;ve found to be slightly problematic is that I cannot issue commands during playback &#8211; even if I want to issue a play -state 0 command. Do you know if there is something I&#8217;m missing?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
