<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0">
	<channel>
		<title><![CDATA[Modartt user forum - Bug: MIDI channel "octave" offset is hardcoded to 1200 cents]]></title>
		<link>https://forum.modartt.com/viewtopic.php?id=8879</link>
		<description><![CDATA[The most recent posts in Bug: MIDI channel "octave" offset is hardcoded to 1200 cents.]]></description>
		<lastBuildDate>Sat, 16 Oct 2021 23:18:18 +0000</lastBuildDate>
		<generator>PunBB</generator>
		<item>
			<title><![CDATA[Bug: MIDI channel "octave" offset is hardcoded to 1200 cents]]></title>
			<link>https://forum.modartt.com/viewtopic.php?pid=978271#p978271</link>
			<description><![CDATA[<p>When using the &quot;Extended layout for up to 16*128 notes,&quot; we have that MIDI channel 2 is 1 octave higher than channel 1, MIDI channel 16 is 1 octave lower than channel 1, etc.</p><p>But, if you are using a tuning for which the &quot;octave&quot; isn&#039;t 1200 cents, but something else, it still uses a 1200 cent octave, but should use the &quot;formal octave&quot; from that scale instead.</p><p>Pianoteq already has this built in to some degree when it reads scala files. For instance, if you load the Bohlen-Pierce scale into Pianoteq, it correctly notes that the &quot;octave&quot; in this scale - aka the interval of equivalence - is now 1901.955 cents or 3/1 (aka the &quot;tritave&quot; rather than the octave). This is just the last line of the Scala file - if the last line is 1200 cents, it will say that&#039;s the interval of equivalence; if it&#039;s 1901.955 cents, it&#039;ll say that, etc.</p><p>So when you go to the adjacent channels, it should simply use that possibly-non-octave interval of equivalence it&#039;s already parsing from the Scala file, rather than hard-coding it to 1200 cents.</p>]]></description>
			<author><![CDATA[null@example.com (battaglia01)]]></author>
			<pubDate>Sat, 16 Oct 2021 23:18:18 +0000</pubDate>
			<guid>https://forum.modartt.com/viewtopic.php?pid=978271#p978271</guid>
		</item>
	</channel>
</rss>
