<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
	<title type="html"><![CDATA[Modartt user forum - Pianoteq 5.2.1 Crashing]]></title>
	<link rel="self" href="https://forum.modartt.com/extern.php?action=feed&amp;tid=3949&amp;type=atom"/>
	<updated>2015-07-08T00:51:52Z</updated>
	<generator>PunBB</generator>
	<id>https://forum.modartt.com/viewtopic.php?id=3949</id>
		<entry>
			<title type="html"><![CDATA[Re: Pianoteq 5.2.1 Crashing]]></title>
			<link rel="alternate" href="https://forum.modartt.com/viewtopic.php?pid=938756#p938756"/>
			<content type="html"><![CDATA[<div class="quotebox"><cite>Mossy wrote:</cite><blockquote><p>It could be some other rogue program on your system periodically taking up all CPU.</p></blockquote></div><p>Hello Messrs. AMS001 and Mossy,</p><p>I concur with Mossy&#039;s assessment that some program might devour your CPU availabliity.&nbsp; </p><p>Since you are in Mac OS 10.9, you might try opening your Activity Monitor located in the Utilities Folder inside your Applications folder.&nbsp; This will reveal which program is hogging your CPU.&nbsp; In the past, I have determined that my Apogee Duet Daemon was consuming gobs of %CPU power for no apparent reason.&nbsp; All I had to do was to force the Duet Daemon to quit, and my four processors each dropped from almost 100% usage to almost no usage.&nbsp; Haven&#039;t had a problem since.&nbsp; In fact, I keep the Activity Monitor available in my toolbar, so as to refer to it from time to time.</p><p>Food for thought.</p><p>Cheers, </p><p>Joe</p>]]></content>
			<author>
				<name><![CDATA[jcfelice88keys]]></name>
				<uri>https://forum.modartt.com/profile.php?id=734</uri>
			</author>
			<updated>2015-07-08T00:51:52Z</updated>
			<id>https://forum.modartt.com/viewtopic.php?pid=938756#p938756</id>
		</entry>
		<entry>
			<title type="html"><![CDATA[Re: Pianoteq 5.2.1 Crashing]]></title>
			<link rel="alternate" href="https://forum.modartt.com/viewtopic.php?pid=938754#p938754"/>
			<content type="html"><![CDATA[<div class="quotebox"><cite>Mossy wrote:</cite><blockquote><p>In a separate terminal window, keep TOP running nonstop w/ a 1 second delay and whenever you run into the Pianoteq problem, immediately bring up the top terminal to see what processes is listed at the top.</p></blockquote></div><p>Actually you don&#039;t really need to set the delay to 1 second. (this takes up some CPU by itself) ...you can press space at any time in the top window to have it immediately update.</p>]]></content>
			<author>
				<name><![CDATA[delt]]></name>
				<uri>https://forum.modartt.com/profile.php?id=3623</uri>
			</author>
			<updated>2015-07-07T15:10:37Z</updated>
			<id>https://forum.modartt.com/viewtopic.php?pid=938754#p938754</id>
		</entry>
		<entry>
			<title type="html"><![CDATA[Re: Pianoteq 5.2.1 Crashing]]></title>
			<link rel="alternate" href="https://forum.modartt.com/viewtopic.php?pid=938753#p938753"/>
			<content type="html"><![CDATA[<p>It could be some other rogue program on your system periodically taking up all CPU.</p><p>In a separate terminal window, keep TOP running nonstop w/ a 1 second delay and whenever you run into the Pianoteq problem, immediately bring up the top terminal to see what processes is listed at the top.</p>]]></content>
			<author>
				<name><![CDATA[Mossy]]></name>
				<uri>https://forum.modartt.com/profile.php?id=3856</uri>
			</author>
			<updated>2015-07-07T14:30:11Z</updated>
			<id>https://forum.modartt.com/viewtopic.php?pid=938753#p938753</id>
		</entry>
		<entry>
			<title type="html"><![CDATA[Re: Pianoteq 5.2.1 Crashing]]></title>
			<link rel="alternate" href="https://forum.modartt.com/viewtopic.php?pid=938750#p938750"/>
			<content type="html"><![CDATA[<p>Thank you, I&#039;ll try that.</p><p>I&#039;m concerned the problem is there to begin with......</p>]]></content>
			<author>
				<name><![CDATA[AMS001]]></name>
				<uri>https://forum.modartt.com/profile.php?id=4561</uri>
			</author>
			<updated>2015-07-07T08:15:52Z</updated>
			<id>https://forum.modartt.com/viewtopic.php?pid=938750#p938750</id>
		</entry>
		<entry>
			<title type="html"><![CDATA[Re: Pianoteq 5.2.1 Crashing]]></title>
			<link rel="alternate" href="https://forum.modartt.com/viewtopic.php?pid=938748#p938748"/>
			<content type="html"><![CDATA[<p>Latest version is 5.3.0, so try updating.</p>]]></content>
			<author>
				<name><![CDATA[EvilDragon]]></name>
				<uri>https://forum.modartt.com/profile.php?id=618</uri>
			</author>
			<updated>2015-07-07T06:53:55Z</updated>
			<id>https://forum.modartt.com/viewtopic.php?pid=938748#p938748</id>
		</entry>
		<entry>
			<title type="html"><![CDATA[Pianoteq 5.2.1 Crashing]]></title>
			<link rel="alternate" href="https://forum.modartt.com/viewtopic.php?pid=938747#p938747"/>
			<content type="html"><![CDATA[<p>I&#039;ve been running pianoteq as part of my live rig now for over 2 years without any problems whatsoever until about a month ago....</p><p>The situation seems to be that pianoteq maxes out, and the sound stops abruptly then after a few seconds it recovers and comes back on.</p><p>The polyphony isn&#039;t working hard at the time it maxes out either.....</p><p>I&#039;m running a Macbook pro Processor&nbsp; 2.5 GHz Intel Core i5 Memory&nbsp; 4 GB 1600 MHz DDR3 Software&nbsp; OS X 10.9.5.</p><p>It&#039;s crashed randomly three times whilst performing now...... </p><p>Has anybody else had the same thing happen? Any explanations??</p><p>Thanks in advance</p>]]></content>
			<author>
				<name><![CDATA[AMS001]]></name>
				<uri>https://forum.modartt.com/profile.php?id=4561</uri>
			</author>
			<updated>2015-07-07T03:33:33Z</updated>
			<id>https://forum.modartt.com/viewtopic.php?pid=938747#p938747</id>
		</entry>
</feed>
