<?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"

			>

	<channel>
		<title>Cycling 74  &#187;  Topic: max 5 &#8211; possible very very strange bug?</title>
		<atom:link href="http://cycling74.com/forums/topic/max-5-possible-very-very-strange-bug/feed" rel="self" type="application/rss+xml" />
		<link>http://cycling74.com/forums/topic/max-5-possible-very-very-strange-bug/feed</link>
		<description></description>
		<pubDate>Wed, 19 Jun 2013 08:05:14 +0000</pubDate>
		<generator>http://bbpress.org/?v=2.2.4</generator>
		<language></language>

		
														
					
				<item>
					<guid>http://cycling74.com/forums/topic/max-5-possible-very-very-strange-bug/#post-37203</guid>
					<title><![CDATA[max 5 &#8211; possible very very strange bug?]]></title>
					<link>http://cycling74.com/forums/topic/max-5-possible-very-very-strange-bug/#post-37203</link>
					<pubDate>Thu, 24 Apr 2008 22:49:12 +0000</pubDate>
					<dc:creator>thezer0ist@gmail.com</dc:creator>

					<description>
						<![CDATA[
						<p>this is what happened:<br />
i had been running max 4, using both of the 2 midi controllers attached.<br />
then i launched max 5.<br />
it opened successfully, and was able to open a patch.<br />
then i closed max 4.<br />
then i started to launch Reason 4.<br />
before it successfully opened, i double clicked on a send object in the patch.<br />
max was frozen for a bit, so i assumed it would come back (my computer does that sort of thing regularly)&#8230;<br />
then reason popped up a message about trouble with midi drivers.<br />
&#8230; and max never became unfrozen.<br />
then, i tried to kill the process. it didn&#8217;t work. i&#8217;ve attempted to kill the process in a variety of ways, with no effect. i have never seen anything like it before, and i&#8217;ll have a degree in computer science in a month.<br />
also, reason is similarly crashed, and impossible to kill.<br />
both processes cannot be debugged, because they are &#8220;crashed&#8221;<br />
they&#8217;ve been like that for 10 minutes now.</p>
<p>i&#8217;m not sure if this is a problem with max, or with reason, but i figure i should mention it. it&#8217;s really quite amazing&#8230;</p>
<p>.. as though it&#8217;s taunting me and refusing to die&#8230;</p>
						]]>
					</description>

					
					
				</item>

			
				<item>
					<guid>http://cycling74.com/forums/topic/max-5-possible-very-very-strange-bug/#post-128372</guid>
					<title><![CDATA[Re: max 5 &#8211; possible very very strange bug?]]></title>
					<link>http://cycling74.com/forums/topic/max-5-possible-very-very-strange-bug/#post-128372</link>
					<pubDate>Thu, 24 Apr 2008 22:50:22 +0000</pubDate>
					<dc:creator>thezer0ist@gmail.com</dc:creator>

					<description>
						<![CDATA[
						<p>i forgot to mention that i&#8217;m using Windows XP.</p>
						]]>
					</description>

					
					
				</item>

			
				<item>
					<guid>http://cycling74.com/forums/topic/max-5-possible-very-very-strange-bug/#post-128373</guid>
					<title><![CDATA[Re: max 5 &#8211; possible very very strange bug?]]></title>
					<link>http://cycling74.com/forums/topic/max-5-possible-very-very-strange-bug/#post-128373</link>
					<pubDate>Fri, 25 Apr 2008 02:45:09 +0000</pubDate>
					<dc:creator>Rob Sussman</dc:creator>

					<description>
						<![CDATA[
						<p>I believe what might be happening is that the mouse is moving between when you press the button and when you release it.  If so, the menu wouldn&#8217;t show. </p>
<p>Please try the upcoming 5.0.1 which will be out quite soon.  The context menu should be more forgiving in that version.  Hopefully that will help. </p>
<p>Thanks,<br />
Rob</p>
						]]>
					</description>

					
					
				</item>

					
		
	</channel>
	</rss>

