<?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: Demystifying Kore Control Pages for Automation and Performance, Pt. I: Different Page Types</title>
	<atom:link href="http://kore.noisepages.com/2008/07/01/demystifying-kore-control-pages-for-automation-and-performance-pt-i-different-page-types/feed/" rel="self" type="application/rss+xml" />
	<link>http://kore.noisepages.com/2008/07/01/demystifying-kore-control-pages-for-automation-and-performance-pt-i-different-page-types/</link>
	<description>Minisite with tutorials, tips, features on making the most of Native Instruments music production tools</description>
	<pubDate>Thu, 20 Nov 2008 21:18:00 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6</generator>
		<item>
		<title>By: Native Instruments Kore, Komplete, Reaktor @ Create Digital Music &#187; Kore Host How-To: Combine Kore with Ableton Live</title>
		<link>http://kore.noisepages.com/2008/07/01/demystifying-kore-control-pages-for-automation-and-performance-pt-i-different-page-types/#comment-3193</link>
		<dc:creator>Native Instruments Kore, Komplete, Reaktor @ Create Digital Music &#187; Kore Host How-To: Combine Kore with Ableton Live</dc:creator>
		<pubDate>Fri, 10 Oct 2008 05:19:23 +0000</pubDate>
		<guid isPermaLink="false">http://kore.noisepages.com/2008/07/01/demystifying-kore-control-pages-for-automation-and-performance-pt-i-different-page-types/#comment-3193</guid>
		<description>[...] Demystifying Kore Control Pages for Automation and Performance: Different Page Types [...]</description>
		<content:encoded><![CDATA[<p>[...] Demystifying Kore Control Pages for Automation and Performance: Different Page Types [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: NI Kore Minisite @ CDM &#187; How to Assign and Choose MIDI Control Changes in Kore</title>
		<link>http://kore.noisepages.com/2008/07/01/demystifying-kore-control-pages-for-automation-and-performance-pt-i-different-page-types/#comment-213</link>
		<dc:creator>NI Kore Minisite @ CDM &#187; How to Assign and Choose MIDI Control Changes in Kore</dc:creator>
		<pubDate>Wed, 09 Jul 2008 14:23:01 +0000</pubDate>
		<guid isPermaLink="false">http://kore.noisepages.com/2008/07/01/demystifying-kore-control-pages-for-automation-and-performance-pt-i-different-page-types/#comment-213</guid>
		<description>[...] Demystifying Kore Control Pages for Automation and Performance, Pt. I: Different Page Types [...]</description>
		<content:encoded><![CDATA[<p>[...] Demystifying Kore Control Pages for Automation and Performance, Pt. I: Different Page Types [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jonathan Adams Leonard</title>
		<link>http://kore.noisepages.com/2008/07/01/demystifying-kore-control-pages-for-automation-and-performance-pt-i-different-page-types/#comment-204</link>
		<dc:creator>Jonathan Adams Leonard</dc:creator>
		<pubDate>Sun, 06 Jul 2008 12:59:34 +0000</pubDate>
		<guid isPermaLink="false">http://kore.noisepages.com/2008/07/01/demystifying-kore-control-pages-for-automation-and-performance-pt-i-different-page-types/#comment-204</guid>
		<description>One thing the readers here should understand about bypassing resources for cpu management in Kore 2.

In many situations it is better to bypass or kill a slot, than the whole source channel.  For some reason and perhaps it is a bug, when source channels are turned back on, they may lose their output connection if using aux busses, direct outs, or if they are inside a nested kore sound.  Instead, bypassing a plugin by bypassing its slot (on the left of the slot) is much more reliable and does not affect the whole output of the channel.

The only thing to remember about THIS is, slot bypasses are not in any page by default, requiring you to create a user page for the source channel for any slot you want to bypass.  It can be a mystery at first - you may begin bypassing slots and notice that nothing is happening when storing performance presets.  Create a user page at the parent channel, assign the kore buttons to your slot bypasses and recall then works perfectly, without output hangups.

This approach could concievably use slightly more cpu in a large kore performance with many channels since the source channels are left on and therefore calculated.  I have not done so for 2, but you could create a performance with 100 empty source channels or so to get a sense of the tradeoff.  With kore 1, each channel used more than you would expect - with 2 it seems less but I have not done the 100 to have a figure per channel on my particular computer.  Open channels chew up cpu and ram.

FWIW,

jonathan adams leonard</description>
		<content:encoded><![CDATA[<p>One thing the readers here should understand about bypassing resources for cpu management in Kore 2.</p>
<p>In many situations it is better to bypass or kill a slot, than the whole source channel.  For some reason and perhaps it is a bug, when source channels are turned back on, they may lose their output connection if using aux busses, direct outs, or if they are inside a nested kore sound.  Instead, bypassing a plugin by bypassing its slot (on the left of the slot) is much more reliable and does not affect the whole output of the channel.</p>
<p>The only thing to remember about THIS is, slot bypasses are not in any page by default, requiring you to create a user page for the source channel for any slot you want to bypass.  It can be a mystery at first - you may begin bypassing slots and notice that nothing is happening when storing performance presets.  Create a user page at the parent channel, assign the kore buttons to your slot bypasses and recall then works perfectly, without output hangups.</p>
<p>This approach could concievably use slightly more cpu in a large kore performance with many channels since the source channels are left on and therefore calculated.  I have not done so for 2, but you could create a performance with 100 empty source channels or so to get a sense of the tradeoff.  With kore 1, each channel used more than you would expect - with 2 it seems less but I have not done the 100 to have a figure per channel on my particular computer.  Open channels chew up cpu and ram.</p>
<p>FWIW,</p>
<p>jonathan adams leonard</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tommy D</title>
		<link>http://kore.noisepages.com/2008/07/01/demystifying-kore-control-pages-for-automation-and-performance-pt-i-different-page-types/#comment-182</link>
		<dc:creator>Tommy D</dc:creator>
		<pubDate>Thu, 03 Jul 2008 04:56:48 +0000</pubDate>
		<guid isPermaLink="false">http://kore.noisepages.com/2008/07/01/demystifying-kore-control-pages-for-automation-and-performance-pt-i-different-page-types/#comment-182</guid>
		<description>Another great page of advice.  

I'm running Kore in a live situation and I am processing my vocals, saxophone &#38; flute, the lead singer's effects and my synths.  I'm using a MOTU Ultralite as my interface.  My big break-through was wrapping my head around Kore's mixer and realizing the endless possibilities I had in front of me.  I can't say that I've even begun to tax Kore for what it can really offer me.  I can say that it has been solid in performance since last Fall when I started using it for live performances.

As I've posted before on this site, pics of my live rig...and for that matter my "studio rig" can be seen at my website.  Just click on my name or visit www.dadadarecords.com</description>
		<content:encoded><![CDATA[<p>Another great page of advice.  </p>
<p>I&#8217;m running Kore in a live situation and I am processing my vocals, saxophone &amp; flute, the lead singer&#8217;s effects and my synths.  I&#8217;m using a MOTU Ultralite as my interface.  My big break-through was wrapping my head around Kore&#8217;s mixer and realizing the endless possibilities I had in front of me.  I can&#8217;t say that I&#8217;ve even begun to tax Kore for what it can really offer me.  I can say that it has been solid in performance since last Fall when I started using it for live performances.</p>
<p>As I&#8217;ve posted before on this site, pics of my live rig&#8230;and for that matter my &#8220;studio rig&#8221; can be seen at my website.  Just click on my name or visit <a href="http://www.dadadarecords.com" rel="nofollow">http://www.dadadarecords.com</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: NI Kore Minisite @ CDM &#187; Quick Tip: Use Mixer View in Kore</title>
		<link>http://kore.noisepages.com/2008/07/01/demystifying-kore-control-pages-for-automation-and-performance-pt-i-different-page-types/#comment-179</link>
		<dc:creator>NI Kore Minisite @ CDM &#187; Quick Tip: Use Mixer View in Kore</dc:creator>
		<pubDate>Wed, 02 Jul 2008 20:15:47 +0000</pubDate>
		<guid isPermaLink="false">http://kore.noisepages.com/2008/07/01/demystifying-kore-control-pages-for-automation-and-performance-pt-i-different-page-types/#comment-179</guid>
		<description>[...] is also worth mentioning in the context of today&#8217;s tutorial on Control Pages, because it&#8217;s a whole lot easier to create Performance-level Control Pages for multiple [...]</description>
		<content:encoded><![CDATA[<p>[...] is also worth mentioning in the context of today&#8217;s tutorial on Control Pages, because it&#8217;s a whole lot easier to create Performance-level Control Pages for multiple [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
