<?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"
	>
<channel>
	<title>Comments on: Kenton Releases Merge 4 MIDI Merge Box</title>
	<atom:link href="http://www.synthtopia.com/content/2008/02/06/kenton-midi-merge-box/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.synthtopia.com/content/2008/02/06/kenton-midi-merge-box/</link>
	<description>Electronic music news, synthesizers, reviews and more!</description>
	<pubDate>Sun, 06 Jul 2008 10:37:00 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: kent</title>
		<link>http://www.synthtopia.com/content/2008/02/06/kenton-midi-merge-box/#comment-124128</link>
		<dc:creator>kent</dc:creator>
		<pubDate>Wed, 06 Feb 2008 18:05:47 +0000</pubDate>
		<guid isPermaLink="false">http://www.synthtopia.com/content/2008/02/06/kenton-midi-merge-box/#comment-124128</guid>
		<description>I wonder if there's anything to distinguish this from every other midi merger in the world.  Since there's no limit on the size of sysex dumps, the only 100% effective midi merger would need infinite memory to buffer up midi messages. 

Even avoiding that fact, it's inevitable that a merger would have a couple of milleseconds latency. Something to think about before latching onto a merger.</description>
		<content:encoded><![CDATA[<p>I wonder if there&#8217;s anything to distinguish this from every other midi merger in the world.  Since there&#8217;s no limit on the size of sysex dumps, the only 100% effective midi merger would need infinite memory to buffer up midi messages. </p>
<p>Even avoiding that fact, it&#8217;s inevitable that a merger would have a couple of milleseconds latency. Something to think about before latching onto a merger.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Dynamic Page Served (once) in 0.240 seconds -->
