<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0">
	<channel>
		<title><![CDATA[Modartt user forum - Update 9.2.0. (June 5th 2026)]]></title>
		<link>https://forum.modartt.com/viewtopic.php?id=13274</link>
		<description><![CDATA[The most recent posts in Update 9.2.0. (June 5th 2026).]]></description>
		<lastBuildDate>Tue, 09 Jun 2026 18:30:57 +0000</lastBuildDate>
		<generator>PunBB</generator>
		<item>
			<title><![CDATA[Re: Update 9.2.0. (June 5th 2026)]]></title>
			<link>https://forum.modartt.com/viewtopic.php?pid=1008123#p1008123</link>
			<description><![CDATA[<div class="quotebox"><cite>julien wrote:</cite><blockquote><p>Thanks! There isn&#039;t much to say about the performance improvements. A part of the computation that had become quite prominent in Pianoteq 9 has been vectorized to reduce its CPU load. On Apple Silicon devices, we were also missing a compiler flag that enables fused multiply-add instructions, so there&#039;s some additional performance gain there as well.</p><p>Glad you noticed the velocity indicators, we have updated the gui toolkit we use and have taken advantage of some of its new features regarding animations. A side effect is that we also have a few new bugs so expect a v9.2.1 very soon.</p><p>The 3D keyboard was also quite complicated, so we&#039;re happy you like it <i class="far fa-smile smiley"></i></p></blockquote></div><p>Hi. There&#039;s been some posts on the Dorico forum, about the regression with micromodal rendition. I notice that I can get some results using the Pitch Bend method, but I think Pianoteq did deliver perfect results with VST Note Expression before (or was it detune ? Or Auto ?) <br />Is something here broken? Could it be fixed? (Pianoteq used to work so flawlessly with Dorico that it was an instant go-to for anyone wanting good results fast…)<br />Thanks in advance.</p>]]></description>
			<author><![CDATA[null@example.com (MarcLarcher)]]></author>
			<pubDate>Tue, 09 Jun 2026 18:30:57 +0000</pubDate>
			<guid>https://forum.modartt.com/viewtopic.php?pid=1008123#p1008123</guid>
		</item>
		<item>
			<title><![CDATA[Re: Update 9.2.0. (June 5th 2026)]]></title>
			<link>https://forum.modartt.com/viewtopic.php?pid=1008122#p1008122</link>
			<description><![CDATA[<p>Hi,</p><p>Julien, <br />Did you change something to the sensitivity of velocity ? <br />It seems to me that the high velocities are easier to obtain with the same keyboard setting. </p><p>Thks </p><p>SK</p>]]></description>
			<author><![CDATA[null@example.com (stamkorg)]]></author>
			<pubDate>Tue, 09 Jun 2026 18:03:14 +0000</pubDate>
			<guid>https://forum.modartt.com/viewtopic.php?pid=1008122#p1008122</guid>
		</item>
		<item>
			<title><![CDATA[Re: Update 9.2.0. (June 5th 2026)]]></title>
			<link>https://forum.modartt.com/viewtopic.php?pid=1008118#p1008118</link>
			<description><![CDATA[<div class="quotebox"><cite>julien wrote:</cite><blockquote><p>Thanks! There isn&#039;t much to say about the performance improvements. A part of the computation that had become quite prominent in Pianoteq 9 has been vectorized to reduce its CPU load. On Apple Silicon devices, we were also missing a compiler flag that enables fused multiply-add instructions, so there&#039;s some additional performance gain there as well.</p><p>Glad you noticed the velocity indicators, we have updated the gui toolkit we use and have taken advantage of some of its new features regarding animations. A side effect is that we also have a few new bugs so expect a v9.2.1 very soon.</p><p>The 3D keyboard was also quite complicated, so we&#039;re happy you like it <i class="far fa-smile smiley"></i></p></blockquote></div><p>Yes, the 3D keyboard looks very nice, love it!</p>]]></description>
			<author><![CDATA[null@example.com (Raiasi)]]></author>
			<pubDate>Tue, 09 Jun 2026 17:19:57 +0000</pubDate>
			<guid>https://forum.modartt.com/viewtopic.php?pid=1008118#p1008118</guid>
		</item>
		<item>
			<title><![CDATA[Re: Update 9.2.0. (June 5th 2026)]]></title>
			<link>https://forum.modartt.com/viewtopic.php?pid=1008115#p1008115</link>
			<description><![CDATA[<p>Thanks! There isn&#039;t much to say about the performance improvements. A part of the computation that had become quite prominent in Pianoteq 9 has been vectorized to reduce its CPU load. On Apple Silicon devices, we were also missing a compiler flag that enables fused multiply-add instructions, so there&#039;s some additional performance gain there as well.</p><p>Glad you noticed the velocity indicators, we have updated the gui toolkit we use and have taken advantage of some of its new features regarding animations. A side effect is that we also have a few new bugs so expect a v9.2.1 very soon.</p><p>The 3D keyboard was also quite complicated, so we&#039;re happy you like it <i class="far fa-smile smiley"></i></p>]]></description>
			<author><![CDATA[null@example.com (julien)]]></author>
			<pubDate>Tue, 09 Jun 2026 13:52:42 +0000</pubDate>
			<guid>https://forum.modartt.com/viewtopic.php?pid=1008115#p1008115</guid>
		</item>
		<item>
			<title><![CDATA[Update 9.2.0. (June 5th 2026)]]></title>
			<link>https://forum.modartt.com/viewtopic.php?pid=1008098#p1008098</link>
			<description><![CDATA[<p>Thank you, Modartt team, for this update. I downloaded it this evening and noticed the difference straight away. I loaded up the Steingraeber Warm preset and the attack on this just works for me.</p><p>I see that there have been performance improvements according to the changelog.<br />Are you able to elaborate on this?</p><p>One thing I have noticed is thar the decay of velocity indicators in the velocity pane is quicker. I think this is an improvement.</p><p>I like the 3D keyboard. Very appealing.</p><p>Thanks again all,</p><p>Warmest regards,</p><p>Chris</p>]]></description>
			<author><![CDATA[null@example.com (sigasa)]]></author>
			<pubDate>Mon, 08 Jun 2026 19:50:17 +0000</pubDate>
			<guid>https://forum.modartt.com/viewtopic.php?pid=1008098#p1008098</guid>
		</item>
	</channel>
</rss>
