<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0">
	<channel>
		<title><![CDATA[Modartt user forum - Parameter resolution higher than UI readouts?]]></title>
		<link>https://forum.modartt.com/viewtopic.php?id=5031</link>
		<description><![CDATA[The most recent posts in Parameter resolution higher than UI readouts?.]]></description>
		<lastBuildDate>Sat, 06 May 2017 00:42:43 +0000</lastBuildDate>
		<generator>PunBB</generator>
		<item>
			<title><![CDATA[Parameter resolution higher than UI readouts?]]></title>
			<link>https://forum.modartt.com/viewtopic.php?pid=947748#p947748</link>
			<description><![CDATA[<p>So tonight I&#039;m getting super subtle on my PT Pro sound design, and I&#039;m noticing that there seems to be far more parameter resolution in the sound engine than the UI values display.&nbsp; It seems that if you use the mouse in fine-tune mode, you can get audible intermediate values by just moving the mouse even just a pixel, way before the UI readout value&#039;s lowest precision digit visually updates.</p><p>While that&#039;s cool (I hear a lot of difference now in the tiniest adjustments), it&#039;s a pain that those values can&#039;t be seen visually.&nbsp; And worse, an adjustment that doesn&#039;t visually change is not recognized as an undoable event, even though it does affect the sound.</p><p>Is there any way to address this?&nbsp; For example, by offering 1 or 2 more digits after the decimal point, and making the Undo system pick those up.&nbsp; This could be an Options setting (the default would be the current behaviour).</p><p>It&#039;s amazing how much difference a sub-visual adjustment can make.&nbsp; A good example is the hammer hardness, which really changes quite noticeably (to me anyway).</p>]]></description>
			<author><![CDATA[null@example.com (ReBased)]]></author>
			<pubDate>Sat, 06 May 2017 00:42:43 +0000</pubDate>
			<guid>https://forum.modartt.com/viewtopic.php?pid=947748#p947748</guid>
		</item>
	</channel>
</rss>
