<?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>Plugin Developer</title>
	<atom:link href="http://www.plugindeveloper.com/feed" rel="self" type="application/rss+xml" />
	<link>http://www.plugindeveloper.com</link>
	<description>A resource for VST plugin development</description>
	<lastBuildDate>Sat, 11 Jul 2009 11:16:49 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1.4</generator>
		<item>
		<title>Decibel to value calculator online</title>
		<link>http://www.plugindeveloper.com/05/decibel-calculator-online</link>
		<comments>http://www.plugindeveloper.com/05/decibel-calculator-online#comments</comments>
		<pubDate>Wed, 06 May 2009 05:23:28 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Utility]]></category>
		<category><![CDATA[calculator]]></category>
		<category><![CDATA[converter]]></category>

		<guid isPermaLink="false">http://www.plugindeveloper.com/?p=134</guid>
		<description><![CDATA[Use this online calculator to quickly convert between decibels and float values. Float: dB: I have used this for all sorts of double checking my calculations and assumptions during my VST plugin development. I hope this decible to float converter comes in as handy for you as it does for me!]]></description>
		<wfw:commentRss>http://www.plugindeveloper.com/05/decibel-calculator-online/feed</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>IPlug: Bug in AppendTimestamp</title>
		<link>http://www.plugindeveloper.com/04/appendtimestamp-bug</link>
		<comments>http://www.plugindeveloper.com/04/appendtimestamp-bug#comments</comments>
		<pubDate>Sat, 25 Apr 2009 09:00:18 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[VST Plugin Development]]></category>
		<category><![CDATA[bug]]></category>
		<category><![CDATA[IPlug]]></category>
		<category><![CDATA[VST]]></category>
		<category><![CDATA[WDL]]></category>

		<guid isPermaLink="false">http://www.plugindeveloper.com/?p=120</guid>
		<description><![CDATA[A subtle bug has been discovered in one of the logging functions in the IPlug portion of the WDL framework. Details below: First the bug in the logging code. Check out wdl\IPlug\Log.cpp const char* AppendTimestamp(const char* Mmm_dd_yyyy, const char* hh_mm_ss, const char* cStr) { static WDL_String str(cStr); WDL_String tStr; CompileTimestamp(Mmm_dd_yyyy, hh_mm_ss, &#38;tStr); str.Append(" "); str.Append(tStr.Get()); <a href='http://www.plugindeveloper.com/04/appendtimestamp-bug'>[...]</a>]]></description>
		<wfw:commentRss>http://www.plugindeveloper.com/04/appendtimestamp-bug/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>IPlug: sprintf and you, one step float formatting</title>
		<link>http://www.plugindeveloper.com/03/sprintf-precision</link>
		<comments>http://www.plugindeveloper.com/03/sprintf-precision#comments</comments>
		<pubDate>Sun, 22 Mar 2009 23:02:06 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[VST Plugin Development]]></category>
		<category><![CDATA[IPlug]]></category>
		<category><![CDATA[sprintf]]></category>
		<category><![CDATA[VST]]></category>
		<category><![CDATA[WDL]]></category>

		<guid isPermaLink="false">http://www.plugindeveloper.com/?p=112</guid>
		<description><![CDATA[Most of us who have used C++ for a while have crossed path with sprintf once or twice. It comes in handy in a variety of places. There are all the standard things you can do with %d, %s, %f and even diving into precision with %.2f to write two decimal places of precision to <a href='http://www.plugindeveloper.com/03/sprintf-precision'>[...]</a>]]></description>
		<wfw:commentRss>http://www.plugindeveloper.com/03/sprintf-precision/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>IPlug: Full version numbers</title>
		<link>http://www.plugindeveloper.com/03/iplug-full-version-numbers</link>
		<comments>http://www.plugindeveloper.com/03/iplug-full-version-numbers#comments</comments>
		<pubDate>Tue, 17 Mar 2009 02:25:54 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[VST Plugin Development]]></category>
		<category><![CDATA[IPlug]]></category>
		<category><![CDATA[preprocessor]]></category>
		<category><![CDATA[VST]]></category>
		<category><![CDATA[WDL]]></category>

		<guid isPermaLink="false">http://www.plugindeveloper.com/?p=107</guid>
		<description><![CDATA[The IPlug framework has a convenient way to manage your VST plugin&#8217;s version numbers. By design though, these version numbers only print out to the last non-zero digit. So a VST plugin at development version 1.0.0 will print as v1. I&#8217;d rather have it at least print the first digit after the decimal instead of <a href='http://www.plugindeveloper.com/03/iplug-full-version-numbers'>[...]</a>]]></description>
		<wfw:commentRss>http://www.plugindeveloper.com/03/iplug-full-version-numbers/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Version control on Windows with SVN</title>
		<link>http://www.plugindeveloper.com/03/windows-version-control</link>
		<comments>http://www.plugindeveloper.com/03/windows-version-control#comments</comments>
		<pubDate>Sun, 08 Mar 2009 23:04:24 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[VST Plugin Development]]></category>
		<category><![CDATA[Git]]></category>
		<category><![CDATA[SmartSVN]]></category>
		<category><![CDATA[SVN]]></category>
		<category><![CDATA[VisualSVN]]></category>
		<category><![CDATA[Windows]]></category>

		<guid isPermaLink="false">http://www.plugindeveloper.com/?p=103</guid>
		<description><![CDATA[If you&#8217;ve worked with a version control system then you know how powerful that tool can be. I work with such a system at my job every day where we have dedicated system administrators to keep it running. Having such a tool available for my VST development projects at home is very valuable but I <a href='http://www.plugindeveloper.com/03/windows-version-control'>[...]</a>]]></description>
		<wfw:commentRss>http://www.plugindeveloper.com/03/windows-version-control/feed</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
		<item>
		<title>IPlug: Prompt user input at &#8216;proper&#8217; width</title>
		<link>http://www.plugindeveloper.com/03/wide-user-inpu</link>
		<comments>http://www.plugindeveloper.com/03/wide-user-inpu#comments</comments>
		<pubDate>Fri, 06 Mar 2009 08:08:15 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[VST Plugin Development]]></category>
		<category><![CDATA[gui]]></category>
		<category><![CDATA[IPlug]]></category>
		<category><![CDATA[VST]]></category>
		<category><![CDATA[WDL]]></category>
		<category><![CDATA[Windows]]></category>

		<guid isPermaLink="false">http://www.plugindeveloper.com/?p=92</guid>
		<description><![CDATA[The IPlug framework with its associated gui makes it fairly easy to allow audio engineers to type plugin parameter values directly. Using the IPlug gui you can right click any control (default behavior, but we also covered how to allow editing with the left mouse button too) and get an input box to type your <a href='http://www.plugindeveloper.com/03/wide-user-inpu'>[...]</a>]]></description>
		<wfw:commentRss>http://www.plugindeveloper.com/03/wide-user-inpu/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>IPlug: Bug in SetValueFromPlug</title>
		<link>http://www.plugindeveloper.com/03/setvaluefromplug-bug</link>
		<comments>http://www.plugindeveloper.com/03/setvaluefromplug-bug#comments</comments>
		<pubDate>Mon, 02 Mar 2009 11:39:31 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[VST Plugin Development]]></category>
		<category><![CDATA[bug]]></category>
		<category><![CDATA[gui]]></category>
		<category><![CDATA[IPlug]]></category>
		<category><![CDATA[VST]]></category>
		<category><![CDATA[WDL]]></category>

		<guid isPermaLink="false">http://www.plugindeveloper.com/?p=84</guid>
		<description><![CDATA[I stumbled across something I consider to be a bug while creating some custom controls for IPlug. This is not a bug that is going to cause any strange behavior or crashes but rather a slight inefficiency that does not seem to match the intent of the original coder. Let&#8217;s take a look. Here is <a href='http://www.plugindeveloper.com/03/setvaluefromplug-bug'>[...]</a>]]></description>
		<wfw:commentRss>http://www.plugindeveloper.com/03/setvaluefromplug-bug/feed</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>IPlug: Altered mouse button behavior</title>
		<link>http://www.plugindeveloper.com/02/altered-mouse-behavior</link>
		<comments>http://www.plugindeveloper.com/02/altered-mouse-behavior#comments</comments>
		<pubDate>Tue, 10 Feb 2009 05:54:49 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[VST Plugin Development]]></category>
		<category><![CDATA[gui]]></category>
		<category><![CDATA[IPlug]]></category>
		<category><![CDATA[mouse]]></category>
		<category><![CDATA[VST]]></category>
		<category><![CDATA[WDL]]></category>
		<category><![CDATA[Windows]]></category>

		<guid isPermaLink="false">http://www.plugindeveloper.com/?p=46</guid>
		<description><![CDATA[Developing a slick and polished gui for your VST plugin is less about graphics and more about creating a smooth customer experience. The default behavior of IPlug is to block mouse input when an ICaptionControl has edit focus (that&#8217;s the object you use to allow someone to type values into your parameters). If I have <a href='http://www.plugindeveloper.com/02/altered-mouse-behavior'>[...]</a>]]></description>
		<wfw:commentRss>http://www.plugindeveloper.com/02/altered-mouse-behavior/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>IPlug: Fix for invisible user edit bug</title>
		<link>http://www.plugindeveloper.com/02/invisible-edit-bugfix</link>
		<comments>http://www.plugindeveloper.com/02/invisible-edit-bugfix#comments</comments>
		<pubDate>Mon, 09 Feb 2009 04:28:48 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[VST Plugin Development]]></category>
		<category><![CDATA[bug]]></category>
		<category><![CDATA[gui]]></category>
		<category><![CDATA[IPlug]]></category>
		<category><![CDATA[VST]]></category>
		<category><![CDATA[WDL]]></category>
		<category><![CDATA[Windows]]></category>

		<guid isPermaLink="false">http://www.plugindeveloper.com/?p=40</guid>
		<description><![CDATA[The IPlug library for developing VST plugins has a bug causing the user edit window to get stuck open (but invisible) under some circumstances. This results in some sluggish UI behavior. This bug occurs in Windows with VST plugins and I have not been able to check for the bug in AU or Mac plugins <a href='http://www.plugindeveloper.com/02/invisible-edit-bugfix'>[...]</a>]]></description>
		<wfw:commentRss>http://www.plugindeveloper.com/02/invisible-edit-bugfix/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>LICE: &#8220;already defined in LIBCMT.lib&#8221;</title>
		<link>http://www.plugindeveloper.com/02/lice-libcmt-errors</link>
		<comments>http://www.plugindeveloper.com/02/lice-libcmt-errors#comments</comments>
		<pubDate>Sun, 08 Feb 2009 04:45:48 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[VST Plugin Development]]></category>
		<category><![CDATA[LICE]]></category>
		<category><![CDATA[linker]]></category>
		<category><![CDATA[Visual Studio]]></category>
		<category><![CDATA[WDL]]></category>
		<category><![CDATA[Windows]]></category>

		<guid isPermaLink="false">http://www.plugindeveloper.com/?p=27</guid>
		<description><![CDATA[Having trouble compiling the LICE solution for your plugins because you&#8217;re getting lots of errors like about LIBCMT.lib? The fix should be relatively easy. Right click the LICE project in Visual Studio and open the properties panel. Navigate to: Configuration Properties &#124; C/C++ &#124; Code Generation And set the option for Runtime Library to the <a href='http://www.plugindeveloper.com/02/lice-libcmt-errors'>[...]</a>]]></description>
		<wfw:commentRss>http://www.plugindeveloper.com/02/lice-libcmt-errors/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
