<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Notes from Figure 53 &#187; Bugs</title>
	<atom:link href="http://figure53.com/blog/category/bugs/feed/" rel="self" type="application/rss+xml" />
	<link>http://figure53.com/blog</link>
	<description></description>
	<lastBuildDate>Mon, 07 May 2012 23:05:03 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
		<item>
		<title>Video Cue updated</title>
		<link>http://figure53.com/blog/2008/04/24/video-cue-updated/</link>
		<comments>http://figure53.com/blog/2008/04/24/video-cue-updated/#comments</comments>
		<pubDate>Thu, 24 Apr 2008 13:49:46 +0000</pubDate>
		<dc:creator>Christopher</dc:creator>
				<category><![CDATA[Bugs]]></category>
		<category><![CDATA[Releases]]></category>

		<guid isPermaLink="false">http://figure53.com/blog/2008/04/24/video-cue-updated/</guid>
		<description><![CDATA[I&#8217;ve released a small update to the Video Cue. It fixes: at least one scenario in which an initial white frame could be displayed instead of the first video frame a bug that could lead to a crash when a Video Cue is first run It is a small change and I recommend that you [...]]]></description>
			<content:encoded><![CDATA[<p>
I&#8217;ve released a small update to the Video Cue.  It fixes:
</p>
<ul>
<li>at least one scenario in which an initial white frame could be displayed instead of the first video frame</li>
<li>a bug that could lead to a crash when a Video Cue is first run</li>
</ul>
<p>
It is a small change and I recommend that you update.  The new version of the cue is available from the update manager at &#8220;Cues&#8221; &rarr; &#8220;Install/Update Cues&#8230;&#8221;</p>
]]></content:encoded>
			<wfw:commentRss>http://figure53.com/blog/2008/04/24/video-cue-updated/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Video Cue rolled back to 1.1.4</title>
		<link>http://figure53.com/blog/2007/09/08/video-cue-rolled-back-to-114/</link>
		<comments>http://figure53.com/blog/2007/09/08/video-cue-rolled-back-to-114/#comments</comments>
		<pubDate>Sat, 08 Sep 2007 15:50:17 +0000</pubDate>
		<dc:creator>Christopher</dc:creator>
				<category><![CDATA[Bugs]]></category>
		<category><![CDATA[Releases]]></category>

		<guid isPermaLink="false">http://figure53.com/blog/2007/09/08/video-cue-rolled-back-to-114/</guid>
		<description><![CDATA[Three days ago we released Video Cue 1.1.5, which was intended to provide more aggressive buffering for higher performance. Several users have reported this version of the cue has caused serious problems on their systems. Therefore, we are rolling back to version 1.1.4, available from the Update Manager. Apologies for any trouble this may have [...]]]></description>
			<content:encoded><![CDATA[<p>Three days ago we released Video Cue 1.1.5, which was intended to provide more aggressive buffering for higher performance.</p>
<p>Several users have reported this version of the cue has caused serious problems on their systems.  Therefore, we are rolling back to version 1.1.4, available from the Update Manager.</p>
<p>Apologies for any trouble this may have caused.</p>
]]></content:encoded>
			<wfw:commentRss>http://figure53.com/blog/2007/09/08/video-cue-rolled-back-to-114/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Sound and Video Cues Updated</title>
		<link>http://figure53.com/blog/2007/05/26/sound-and-video-cues-updated/</link>
		<comments>http://figure53.com/blog/2007/05/26/sound-and-video-cues-updated/#comments</comments>
		<pubDate>Sat, 26 May 2007 21:33:59 +0000</pubDate>
		<dc:creator>Christopher</dc:creator>
				<category><![CDATA[Bugs]]></category>

		<guid isPermaLink="false">http://www.figure53.com/blog/2007/05/26/sound-and-video-cues-updated/</guid>
		<description><![CDATA[The Sound and Video Cues have been updated today to fix a bug relating to the way start and end times were set when the target file changes or becomes invalid. You can grab the new cues from the Update Manager.]]></description>
			<content:encoded><![CDATA[<p>The Sound and Video Cues have been updated today to fix a bug relating to the way start and end times were set when the target file changes or becomes invalid.</p>
<p>You can grab the new cues from the Update Manager.</p>
]]></content:encoded>
			<wfw:commentRss>http://figure53.com/blog/2007/05/26/sound-and-video-cues-updated/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Video Cue 1.0.4 Available</title>
		<link>http://figure53.com/blog/2007/04/22/video-cue-104-available/</link>
		<comments>http://figure53.com/blog/2007/04/22/video-cue-104-available/#comments</comments>
		<pubDate>Sun, 22 Apr 2007 21:57:41 +0000</pubDate>
		<dc:creator>Christopher</dc:creator>
				<category><![CDATA[Bugs]]></category>
		<category><![CDATA[Releases]]></category>

		<guid isPermaLink="false">http://www.figure53.com/blog/2007/04/22/video-cue-104-available/</guid>
		<description><![CDATA[This release fixes a handful of important bugs with the Video Cue; I recommend updating. Changes are as follows: Fixed a bug that could cause QLab to crash when playing multiple Video Cues. Fixed a problem where the final frame of a video could pop to 100% visibility when &#8220;stop target when done&#8221; was checked [...]]]></description>
			<content:encoded><![CDATA[<p>This release fixes a handful of important bugs with the Video Cue; I recommend updating.</p>
<p>Changes are as follows:</p>
<ul>
<li>Fixed a bug that could cause QLab to crash when playing multiple Video Cues.</li>
<li>Fixed a problem where the final frame of a video could pop to 100% visibility when &#8220;stop target when done&#8221; was checked on a Video Fade Cue.</li>
<li>Mouse is now hidden when a Video Cue is started only if the workspace is locked <i>and</i> the video is going full screen <i>and</i> the video is on the main screen.</li>
</ul>
<p>So go to &#8220;QLab&#8221; &rarr; &#8220;Check for Updates&#8230;&#8221; and grab yerself the new version.</p>
]]></content:encoded>
			<wfw:commentRss>http://figure53.com/blog/2007/04/22/video-cue-104-available/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Quicktime 7.1.5 crashes the party</title>
		<link>http://figure53.com/blog/2007/03/16/quicktime-715-crashes-the-party/</link>
		<comments>http://figure53.com/blog/2007/03/16/quicktime-715-crashes-the-party/#comments</comments>
		<pubDate>Fri, 16 Mar 2007 23:25:29 +0000</pubDate>
		<dc:creator>Christopher</dc:creator>
				<category><![CDATA[Bugs]]></category>
		<category><![CDATA[Rants]]></category>

		<guid isPermaLink="false">http://www.figure53.com/blog/2007/03/16/quicktime-715-crashes-the-party/</guid>
		<description><![CDATA[Just in time for the release of the new Video Cue, Apple goes and releases Quicktime 7.1.5; aka &#8220;Major Breakage Edition.&#8221; The breakage in QLab is that Video Cues will stutter and drop frames for the first half second or two when a Video Cue starts playing. I&#8217;m actively exploring a fix, but if you [...]]]></description>
			<content:encoded><![CDATA[<p>Just in time for the release of the new Video Cue, Apple goes and releases Quicktime 7.1.5; aka <a href="http://www.macfixit.com/article.php?story=20070313102251723">&#8220;Major Breakage Edition.&#8221;</a></p>
<p>The breakage in QLab is that Video Cues will stutter and drop frames for the first half second or two when a Video Cue starts playing.</p>
<p>I&#8217;m actively exploring a fix, but if you haven&#8217;t upgraded yet to Quicktime 7.1.5 I would recommend waiting until either a fix from me or a fix from Apple is available.</p>
<p>Yarrrrr.</p>
]]></content:encoded>
			<wfw:commentRss>http://figure53.com/blog/2007/03/16/quicktime-715-crashes-the-party/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>The Most Ironic of All Possible Bugs</title>
		<link>http://figure53.com/blog/2006/09/29/the-most-ironic-of-all-possible-bugs/</link>
		<comments>http://figure53.com/blog/2006/09/29/the-most-ironic-of-all-possible-bugs/#comments</comments>
		<pubDate>Fri, 29 Sep 2006 21:41:32 +0000</pubDate>
		<dc:creator>Christopher</dc:creator>
				<category><![CDATA[Bugs]]></category>

		<guid isPermaLink="false">http://www.figure53.com/blog/2006/09/29/the-most-ironic-of-all-possible-bugs/</guid>
		<description><![CDATA[When QLab first starts, it checks for a recent crash log and offers to send it back to Figure 53 so we can examine the crash information. Under certain circumstances, this check can&#8230;yes, you guessed it, lead to a crash. It&#8217;d be funny if it weren&#8217;t so annoying. At the moment, if you run into [...]]]></description>
			<content:encoded><![CDATA[<p>When QLab first starts, it checks for a recent crash log and offers to send it back to Figure 53 so we can examine the crash information.  Under certain circumstances, this check can&#8230;yes, you guessed it, lead to a crash.  It&#8217;d be funny if it weren&#8217;t so annoying.</p>
<p>At the moment, if you run into this problem, you can fix it simply by removing the crash log from your crash log directory.  The crash log may be found here:</p>
<p>/Users/YOUR_USER_NAME/Library/Logs/CrashReporter/QLab.crash.log</p>
<p>Just remove that file, and you should be back to business.</p>
<p>I will be putting out a new release in the next few days that fixes this bug.  My apologies for any inconvenience!</p>
]]></content:encoded>
			<wfw:commentRss>http://figure53.com/blog/2006/09/29/the-most-ironic-of-all-possible-bugs/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>One more MIDI note</title>
		<link>http://figure53.com/blog/2006/09/13/one-more-midi-note/</link>
		<comments>http://figure53.com/blog/2006/09/13/one-more-midi-note/#comments</comments>
		<pubDate>Wed, 13 Sep 2006 22:55:15 +0000</pubDate>
		<dc:creator>Christopher</dc:creator>
				<category><![CDATA[Bugs]]></category>

		<guid isPermaLink="false">http://www.figure53.com/blog/2006/09/13/one-more-midi-note/</guid>
		<description><![CDATA[For those of you playing with MIDI and finding that ugly crashing bug the second time you fire a MIDI Cue, don&#8217;t worryâ€”this was a simple and stupid bug that crept into the last release. It has been fixed and will not be present in the next release&#8230;which should be available some time tonight. Heh. [...]]]></description>
			<content:encoded><![CDATA[<p>For those of you playing with MIDI and finding that ugly crashing bug the second time you fire a MIDI Cue, don&#8217;t worryâ€”this was a simple and stupid bug that crept into the last release.  It has been fixed and will not be present in the next release&#8230;which should be available some time tonight.</p>
<p><small>Heh.  &#8220;One more MIDI note&#8221;.  I kill myself.</small></p>
]]></content:encoded>
			<wfw:commentRss>http://figure53.com/blog/2006/09/13/one-more-midi-note/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Oops!  MIDI Cues won&#8217;t load on Intel machines</title>
		<link>http://figure53.com/blog/2006/09/09/oops-midi-cues-wont-load-on-intel-machines/</link>
		<comments>http://figure53.com/blog/2006/09/09/oops-midi-cues-wont-load-on-intel-machines/#comments</comments>
		<pubDate>Sat, 09 Sep 2006 13:57:55 +0000</pubDate>
		<dc:creator>Christopher</dc:creator>
				<category><![CDATA[Bugs]]></category>

		<guid isPermaLink="false">http://www.figure53.com/blog/2006/09/09/oops-midi-cues-wont-load-on-intel-machines/</guid>
		<description><![CDATA[There was one oversight in the recent merging of QLab and QLab Pro: the status of each component as a Universal or PPC-only binary. Everything in QLab is compiled as a Universal binary except the MIDI cues. Thus, on an Intel machine the application is loaded as a Universal binary, but when it gets to [...]]]></description>
			<content:encoded><![CDATA[<p>There was one oversight in the recent merging of QLab and QLab Pro: the status of each component as a Universal or PPC-only binary.</p>
<p>Everything in QLab is compiled as a Universal binary except the MIDI cues. Thus, on an Intel machine the application is loaded as a Universal binary, but when it gets to the MIDI cues it can&#8217;t load them because it can&#8217;t mix the two kinds of code.</p>
<p>This was not a problem with QLab Pro, because QLab Pro was PPC only.</p>
<p>For the moment, if you are wanting to try the MIDI cues on an Intel machine you can <a href="http://developer.apple.com/documentation/MacOSX/Conceptual/universal_binary/universal_binary_exec_a/chapter_7_section_5.html#//apple_ref/doc/uid/TP40002217-CH210-240406">force QLab to start on Rosetta</a>, and that should fix the problem.</p>
<p>Sorry for the inconvenience!</p>
]]></content:encoded>
			<wfw:commentRss>http://figure53.com/blog/2006/09/09/oops-midi-cues-wont-load-on-intel-machines/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Wanted: Help Recreating the &#8220;drag onto workspace&#8221; Crash</title>
		<link>http://figure53.com/blog/2006/05/25/wanted-help-recreating-the-drag-onto-workspace-crash/</link>
		<comments>http://figure53.com/blog/2006/05/25/wanted-help-recreating-the-drag-onto-workspace-crash/#comments</comments>
		<pubDate>Fri, 26 May 2006 02:50:36 +0000</pubDate>
		<dc:creator>Christopher</dc:creator>
				<category><![CDATA[Bugs]]></category>

		<guid isPermaLink="false">http://www.figure53.com/blog/?p=38</guid>
		<description><![CDATA[Since adding the automatic crash report feature, I have received only one kind of crash log. Namely, QLab will occasionally crash when dragging sound files onto the workspace. If you have experienced this, and can help describe the circumstances in which this crash happens, please add your feedback to ticket 154: http://figure53.com/trac/index.fcgi/ticket/154 Since this is [...]]]></description>
			<content:encoded><![CDATA[<p>Since adding the automatic crash report feature, I have received only one kind of crash log.  Namely, QLab will occasionally crash when dragging sound files onto the workspace.  If you have experienced this, and can help describe the circumstances in which this crash happens, please add your feedback to ticket 154:</p>
<p><a href="http://figure53.com/trac/index.fcgi/ticket/154">http://figure53.com/trac/index.fcgi/ticket/154</a></p>
<p>Since this is the <i>only</i> issue for which I am receiving crash logs, we&#8217;ll be doing very well stability-wise if we can nail this bug.</p>
]]></content:encoded>
			<wfw:commentRss>http://figure53.com/blog/2006/05/25/wanted-help-recreating-the-drag-onto-workspace-crash/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>0.9.511 Available, and an important warning</title>
		<link>http://figure53.com/blog/2006/04/30/09511-available-and-an-important-warning/</link>
		<comments>http://figure53.com/blog/2006/04/30/09511-available-and-an-important-warning/#comments</comments>
		<pubDate>Mon, 01 May 2006 01:23:03 +0000</pubDate>
		<dc:creator>Christopher</dc:creator>
				<category><![CDATA[Bugs]]></category>
		<category><![CDATA[Releases]]></category>

		<guid isPermaLink="false">http://www.figure53.com/blog/?p=35</guid>
		<description><![CDATA[There are some helpful workflow features added in this version. Cues now have command-key shortcuts to add them to your workspace, and you can reorder the order of the cues in the Qbox by dragging them to new locations. Important: Recently a crash occurred when running QLab on 10.4.6 that appears to be the same [...]]]></description>
			<content:encoded><![CDATA[<p>There are some helpful workflow features added in this version.  Cues now have command-key shortcuts to add them to your workspace, and you can reorder the order of the cues in the Qbox by dragging them to new locations.</p>
<p><b>Important:</b></p>
<p>Recently a crash occurred when running QLab on 10.4.6 that appears to be the same as the crash I was seeing on 10.3.9.  It&#8217;s the first time I&#8217;ve seen this crash on 10.4, and it is very important because Apple has still not responded to my bug report and sample code discussing the problem.  This puts me in a real spot trying to figure out what is going on, because the crash is happening in their code, and according to them I am using their code the way it is supposed to be used.  You can see the dilemma.</p>
<p>You can bet your butt that I&#8217;ll be redoubling my efforts to try to track this down and/or pester Apple until I can  determine what is going on.  But please be aware that this problem may potentially affect you!  Beta software requires caution!</p>
]]></content:encoded>
			<wfw:commentRss>http://figure53.com/blog/2006/04/30/09511-available-and-an-important-warning/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

