<?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"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>ProToolsProfessional.com &#187; DControl</title>
	<atom:link href="http://www.brentheber.com/tag/dcontrol/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.brentheber.com</link>
	<description>Info for PT users of all levels</description>
	<lastBuildDate>Wed, 18 Aug 2010 12:15:50 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
		<item>
		<title>Preview Mode</title>
		<link>http://www.brentheber.com/2009/06/10/preview/</link>
		<comments>http://www.brentheber.com/2009/06/10/preview/#comments</comments>
		<pubDate>Wed, 10 Jun 2009 05:10:36 +0000</pubDate>
		<dc:creator>Brent</dc:creator>
				<category><![CDATA[Tips for Pro Tools HD users]]></category>
		<category><![CDATA[automation]]></category>
		<category><![CDATA[Dcommand]]></category>
		<category><![CDATA[DControl]]></category>
		<category><![CDATA[ICON]]></category>
		<category><![CDATA[Pro Tools]]></category>
		<category><![CDATA[Pro Tools HD 7.2]]></category>

		<guid isPermaLink="false">http://brentheber.com/?p=67</guid>
		<description><![CDATA[Here&#8217;s another quick video to demonstrate a key automation feature from the PTHD7.2 release. Its called Preview mode. Many clients want to audition a change in their automation from region to region, scene to scene, before committing to &#8220;Writing&#8221; it. The most common way of...]]></description>
			<content:encoded><![CDATA[<p>Here&#8217;s another quick video to demonstrate a key automation feature from the PTHD7.2 release. Its called Preview mode. Many clients want to audition a change in their automation from region to region, scene to scene, before committing to &#8220;Writing&#8221; it. The most common way of doing that pre-7.2 was to suspend your automation, find the sweet spot for your settings, then Write them to your selection and re-engage automation.</p>
<p>Preview mode allows you to skip the &#8220;suspend automation&#8221; step, and &#8220;dynamically suspends&#8221; only the parameters of your mix that you touch. So you can hear your changes in the context of your mix, without turning off global automation families like Inserts or volume.</p>
<p style="text-align: center;"><a href="http://vimeo.com/5076807" target="_blank">Preview mode and Latch Prime in Stop</a></p>
<p style="text-align: left;">&#8220;ICON Bootcamp&#8221; up next&#8230;</p>
<script type="text/javascript">
  addthis_url    = 'http%3A%2F%2Fwww.brentheber.com%2F2009%2F06%2F10%2Fpreview%2F';
  addthis_title  = 'Preview+Mode';
  addthis_pub    = '';
</script><script type="text/javascript" src="http://s7.addthis.com/js/addthis_widget.php?v=12" ></script>
]]></content:encoded>
			<wfw:commentRss>http://www.brentheber.com/2009/06/10/preview/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>Custom Fader Plug in Maps</title>
		<link>http://www.brentheber.com/2008/09/11/custom-fader-plug-in-maps/</link>
		<comments>http://www.brentheber.com/2008/09/11/custom-fader-plug-in-maps/#comments</comments>
		<pubDate>Thu, 11 Sep 2008 05:55:41 +0000</pubDate>
		<dc:creator>Brent</dc:creator>
				<category><![CDATA[Tips for ICON users]]></category>
		<category><![CDATA[Custom fader plug in map]]></category>
		<category><![CDATA[Custom Faders]]></category>
		<category><![CDATA[DCommand mapping]]></category>
		<category><![CDATA[DControl]]></category>
		<category><![CDATA[digidesign]]></category>
		<category><![CDATA[ICON]]></category>
		<category><![CDATA[plug in map]]></category>

		<guid isPermaLink="false">http://brentheber.com/?p=24</guid>
		<description><![CDATA[Before we look at plug in mapping &#8211; a reminder, the HD Workflow tour starts on Monday in Adelaide! If you havent RSVP&#8217;ed for the Adelaide, Sydney, Auckland or Wellington events, please do so! OK, first, here&#8217;s a video explaining what Plug in maps is...]]></description>
			<content:encoded><![CDATA[<p><strong>Before we look at plug in mapping &#8211; a reminder, the HD Workflow tour starts on Monday in Adelaide! If you havent RSVP&#8217;ed for the Adelaide, Sydney, Auckland or Wellington events, please do so!</strong></p>
<p>OK, first, here&#8217;s a video explaining what Plug in maps is about&#8230;.</p>
<p><script src="http://flash.revver.com/player/1.0/player.js?mediaId:1165882;affiliateId:230770;backColor:#000000;frontColor:#FFFFFF;gradColor:#000000;width:480;height:392;shareUrl:embedUrl;" type="text/javascript"></script></p>
<p>Now you&#8217;ve watched the video, a few extra notes. The &#8220;maps&#8221; that you create of plug ins all get added into a file kept on your CPU. Thats a *.PIO file, and they can be imported and exported from your ICON from the soft key section.</p>
<p>Why would you want to do this? Well, there are alot of plugs out there that aren&#8217;t EQ or Dyn and consequently wont map to your centre section. As a result, all your other plugs will come up slightly differently when you focus them into the custom fader section. why not map them for some consistency?  Input and output levels always in the same spot? Reverbs mapped down similarly, so its only the character/timbre of them that changes, but you drive them the same&#8230;there are alot of options here.</p>
<p>SO, you have your pio file, and its how you access your plugs, put it on a thumb drive and take it with you to another ICON studio and there you go! You can import it and youre driving their system the way you like to!</p>
<p>If you dont move around alot, then I guess its not a big deal, apart from backing it up for redundancy &#8211; last thing you want is to have a fantastic detailed map file for hundreds of plugs lost because you had to reinstall your OS&#8230;</p>
<p>Last thought on the topic, when a pio file is made, it seems to take a snapshot of all the installed plugs on your system. Consequenty its not representative of your map of a single plug in, but rather of ALL plugs on your rig. Why is this important? Well, what if you want to find a map that you used to use&#8230;so you import that old pio file into your current rig, and you have your old map for that plug in&#8230;problem is, you may have created new maps since that file was backed up, and on those plug ins that previously had no map, the default state will have copied over on top of your maps, putting EVERY installed plugin back to its state&#8230;</p>
<p>So its NOT incremental, its a system state file &#8211; so beware if you intend to tinker with it! If you think of these files as system snapshots taken in series, getting more complex over time, then you should be fine.</p>
<p>To import and export the files, its in your preferences menu, 4 or 5 pages deep.</p>
<p><em>More &#8220;Custom Fader&#8221; goodness coming soon&#8230;</em></p>
<script type="text/javascript">
  addthis_url    = 'http%3A%2F%2Fwww.brentheber.com%2F2008%2F09%2F11%2Fcustom-fader-plug-in-maps%2F';
  addthis_title  = 'Custom+Fader+Plug+in+Maps';
  addthis_pub    = '';
</script><script type="text/javascript" src="http://s7.addthis.com/js/addthis_widget.php?v=12" ></script>
]]></content:encoded>
			<wfw:commentRss>http://www.brentheber.com/2008/09/11/custom-fader-plug-in-maps/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
	</channel>
</rss>
