<?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: Converting 24PPQ Midi Sync in Java/Processing</title>
	<atom:link href="http://grantmuller.com/converting-24ppq-midi-sync-in-javaprocessing/feed/" rel="self" type="application/rss+xml" />
	<link>http://grantmuller.com/converting-24ppq-midi-sync-in-javaprocessing/</link>
	<description>Not as bad as he seems</description>
	<lastBuildDate>Tue, 07 Sep 2010 14:58:04 +0100</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: Grant Muller</title>
		<link>http://grantmuller.com/converting-24ppq-midi-sync-in-javaprocessing/comment-page-1/#comment-329</link>
		<dc:creator>Grant Muller</dc:creator>
		<pubDate>Fri, 01 Jan 2010 17:33:54 +0000</pubDate>
		<guid isPermaLink="false">http://www.grantmuller.com/?p=664#comment-329</guid>
		<description>No problem Daniel, thanks for the comment. Let me know what you come up with in the end. One of the harder things to wrap your mind around is that amount of time that passes in-between each pulse, and that your implementation will be limited by the number of instructions you can process in that span of time. In a C++ or lower level code implementation its not an issue to drop to 48 or 96 PPQ, but with something like Java you&#039;ll never be able to handle that many pulses per quarter note at &quot;regular&quot; tempos (120 bpm+). One non-code workaround is of course just to double the tempo of the source clock, and count two measures for one on your client. Let me know!</description>
		<content:encoded><![CDATA[<p>No problem Daniel, thanks for the comment. Let me know what you come up with in the end. One of the harder things to wrap your mind around is that amount of time that passes in-between each pulse, and that your implementation will be limited by the number of instructions you can process in that span of time. In a C++ or lower level code implementation its not an issue to drop to 48 or 96 PPQ, but with something like Java you&#8217;ll never be able to handle that many pulses per quarter note at &#8220;regular&#8221; tempos (120 bpm+). One non-code workaround is of course just to double the tempo of the source clock, and count two measures for one on your client. Let me know!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Daniel Rosenstark</title>
		<link>http://grantmuller.com/converting-24ppq-midi-sync-in-javaprocessing/comment-page-1/#comment-328</link>
		<dc:creator>Daniel Rosenstark</dc:creator>
		<pubDate>Fri, 01 Jan 2010 11:32:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.grantmuller.com/?p=664#comment-328</guid>
		<description>I am so amazed and glad I found this article. I just realized that reacting to 24-pulses-per-quarter is totally wrong, but I had no idea what to do. Of course I still have to read, understand, and implement what you wrote, but finding your article was half the battle. I&#039;ll report back when I&#039;ve finished that, but thanks in advance!</description>
		<content:encoded><![CDATA[<p>I am so amazed and glad I found this article. I just realized that reacting to 24-pulses-per-quarter is totally wrong, but I had no idea what to do. Of course I still have to read, understand, and implement what you wrote, but finding your article was half the battle. I&#8217;ll report back when I&#8217;ve finished that, but thanks in advance!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
<!-- WP Super Cache is installed but broken. The path to wp-cache-phase1.php in wp-content/advanced-cache.php must be fixed! -->