<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0">
	<channel>
		<title><![CDATA[Modartt user forum - Organteq tuning diapason overridden by Logic Pro]]></title>
		<link>https://forum.modartt.com/viewtopic.php?id=11758</link>
		<description><![CDATA[The most recent posts in Organteq tuning diapason overridden by Logic Pro.]]></description>
		<lastBuildDate>Mon, 02 Sep 2024 20:17:08 +0000</lastBuildDate>
		<generator>PunBB</generator>
		<item>
			<title><![CDATA[Re: Organteq tuning diapason overridden by Logic Pro]]></title>
			<link>https://forum.modartt.com/viewtopic.php?pid=998419#p998419</link>
			<description><![CDATA[<div class="quotebox"><cite>tmyoung wrote:</cite><blockquote><p>While I haven&#039;t used Logic, it sounds like the virtual OTQ VST MIDI I/O setting for diapason is listening for a MIDI event that Logic is obligingly setting to A440.&nbsp; I&#039;d suggest checking the specific VST MIDI routing for your OTQ instance and see if there&#039;s a listener that&#039;s editing the diapason and disable that.</p><p>If that doesn&#039;t work, &quot;File &gt; Project Settings &gt; Tuning &gt; Software Instrument Pitch&quot; should allow you to set the Logic parameter that&#039;s passing A440 (though if you can get the other to work, so much the better).</p></blockquote></div><p>Thanks for responding. I have looked and can&#039;t find anywhere either in Organteq or Logic&#039;s settings to disable. Tuning in Logic is a clumsier way than within OTQ. I normally use 440 so it&#039;s more an irritation that it is forcing a change I don&#039;t want. So if I can&#039;t find a solution it&#039;s not a major problem - just means I have to use Reaper or in standalone mode when I want to play around with diapason other than 440.</p>]]></description>
			<author><![CDATA[null@example.com (acharman)]]></author>
			<pubDate>Mon, 02 Sep 2024 20:17:08 +0000</pubDate>
			<guid>https://forum.modartt.com/viewtopic.php?pid=998419#p998419</guid>
		</item>
		<item>
			<title><![CDATA[Re: Organteq tuning diapason overridden by Logic Pro]]></title>
			<link>https://forum.modartt.com/viewtopic.php?pid=998402#p998402</link>
			<description><![CDATA[<p>While I haven&#039;t used Logic, it sounds like the virtual OTQ VST MIDI I/O setting for diapason is listening for a MIDI event that Logic is obligingly setting to A440.&nbsp; I&#039;d suggest checking the specific VST MIDI routing for your OTQ instance and see if there&#039;s a listener that&#039;s editing the diapason and disable that.</p><p>If that doesn&#039;t work, &quot;File &gt; Project Settings &gt; Tuning &gt; Software Instrument Pitch&quot; should allow you to set the Logic parameter that&#039;s passing A440 (though if you can get the other to work, so much the better).</p>]]></description>
			<author><![CDATA[null@example.com (tmyoung)]]></author>
			<pubDate>Mon, 02 Sep 2024 06:31:43 +0000</pubDate>
			<guid>https://forum.modartt.com/viewtopic.php?pid=998402#p998402</guid>
		</item>
		<item>
			<title><![CDATA[Organteq tuning diapason overridden by Logic Pro]]></title>
			<link>https://forum.modartt.com/viewtopic.php?pid=998399#p998399</link>
			<description><![CDATA[<p>When using Organteq 2 in Logic, if I have an organ preset such as the historical ones with a diapason that isn&#039;t 440Hz then as soon as play starts a message pops up in Organteq &quot; Organteq has received a MIDI Master Coarse/Fine Tuning SysEx message. The diapason of the current preset has been overriden with 440Hz (coarse: -, fine: 0 cents).&quot; and Organteq resets the pipes to 440Hz. This overriding of tuning doesn&#039;t occur with Pianoteq and isn&#039;t an issue within Reaper.</p><p>Just wondering if anyone has experienced this and solved the issue. I can just use standalone or Reaper when I want to play around with tunings other than 440Hz but that is limiting as I do prefer to work within Logic.</p>]]></description>
			<author><![CDATA[null@example.com (acharman)]]></author>
			<pubDate>Sun, 01 Sep 2024 21:15:12 +0000</pubDate>
			<guid>https://forum.modartt.com/viewtopic.php?pid=998399#p998399</guid>
		</item>
	</channel>
</rss>
