<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
	<title type="html"><![CDATA[Modartt user forum - Feature Request: Midi Out Support]]></title>
	<link rel="self" href="https://forum.modartt.com/extern.php?action=feed&amp;tid=11296&amp;type=atom"/>
	<updated>2024-03-02T23:50:36Z</updated>
	<generator>PunBB</generator>
	<id>https://forum.modartt.com/viewtopic.php?id=11296</id>
		<entry>
			<title type="html"><![CDATA[Re: Feature Request: Midi Out Support]]></title>
			<link rel="alternate" href="https://forum.modartt.com/viewtopic.php?pid=995798#p995798"/>
			<content type="html"><![CDATA[<div class="quotebox"><cite>lewisalexander2020 wrote:</cite><blockquote><p>Hello ladies and gentlemen,</p><p>I&#039;m Sorry it&#039;s been a while, a very trying time between hospital, meetings and other matters, this is what cancer does to a family.</p><p>So, as the subject says. This is a feature request for MIDI OUT, whether as MMC or other means. </p><p>Why?</p><p>If you own a console with either lit or motorised draw stops, tab stops, etc and you set up a console to work with your software as midi data from console to organteq 2, great, but when you&#039;re using the console as a tactile experience as a good example, you need midi out from organteq 2 to drive electro-mechanical stops&nbsp; for various functions, or if you&#039;re a sighted person, illuminated stops to indicate whether a stop in a sequence is active or not, especially if you&#039;re running the console and organteq headless.</p><p>So, we need midi out and support to drive particular or any console via midi data out in order to turn a console in to a hardware control on both sides of the scale of use.</p><p>I&#039;ll forward this on to Niclas anway for the team but putting this here for reference.</p><p>Lew</p></blockquote></div><p>Yes, really! MIDI out is a must for my next organ with touch displays as stops on the jambs. I hope it is not far away....</p>]]></content>
			<author>
				<name><![CDATA[akaas]]></name>
				<uri>https://forum.modartt.com/profile.php?id=9327</uri>
			</author>
			<updated>2024-03-02T23:50:36Z</updated>
			<id>https://forum.modartt.com/viewtopic.php?pid=995798#p995798</id>
		</entry>
		<entry>
			<title type="html"><![CDATA[Re: Feature Request: Midi Out Support]]></title>
			<link rel="alternate" href="https://forum.modartt.com/viewtopic.php?pid=995531#p995531"/>
			<content type="html"><![CDATA[<p>Yes! I also hope we don&#039;t have to wait too long for MIDI Out.</p>]]></content>
			<author>
				<name><![CDATA[Pat]]></name>
				<uri>https://forum.modartt.com/profile.php?id=133</uri>
			</author>
			<updated>2024-02-16T08:55:29Z</updated>
			<id>https://forum.modartt.com/viewtopic.php?pid=995531#p995531</id>
		</entry>
		<entry>
			<title type="html"><![CDATA[Re: Feature Request: Midi Out Support]]></title>
			<link rel="alternate" href="https://forum.modartt.com/viewtopic.php?pid=995522#p995522"/>
			<content type="html"><![CDATA[<p>Agreed.&nbsp; While running within a DAW can offer some MIDI message routing features to partially mitigate this, there are a lot of situations--due to the amount of (wonderfully useful) internal automation in OTQ--where MIDI automation becomes badly broken by the lack of two-way MIDI messaging.</p><p>So sorry to hear about your family&#039;s ongoing health struggles!</p>]]></content>
			<author>
				<name><![CDATA[tmyoung]]></name>
				<uri>https://forum.modartt.com/profile.php?id=3155</uri>
			</author>
			<updated>2024-02-15T18:45:41Z</updated>
			<id>https://forum.modartt.com/viewtopic.php?pid=995522#p995522</id>
		</entry>
		<entry>
			<title type="html"><![CDATA[Feature Request: Midi Out Support]]></title>
			<link rel="alternate" href="https://forum.modartt.com/viewtopic.php?pid=995518#p995518"/>
			<content type="html"><![CDATA[<p>Hello ladies and gentlemen,</p><p>I&#039;m Sorry it&#039;s been a while, a very trying time between hospital, meetings and other matters, this is what cancer does to a family.</p><p>So, as the subject says. This is a feature request for MIDI OUT, whether as MMC or other means. </p><p>Why?</p><p>If you own a console with either lit or motorised draw stops, tab stops, etc and you set up a console to work with your software as midi data from console to organteq 2, great, but when you&#039;re using the console as a tactile experience as a good example, you need midi out from organteq 2 to drive electro-mechanical stops&nbsp; for various functions, or if you&#039;re a sighted person, illuminated stops to indicate whether a stop in a sequence is active or not, especially if you&#039;re running the console and organteq headless.</p><p>So, we need midi out and support to drive particular or any console via midi data out in order to turn a console in to a hardware control on both sides of the scale of use.</p><p>I&#039;ll forward this on to Niclas anway for the team but putting this here for reference.</p><p>Lew</p>]]></content>
			<author>
				<name><![CDATA[lewisalexander2020]]></name>
				<uri>https://forum.modartt.com/profile.php?id=7707</uri>
			</author>
			<updated>2024-02-15T10:57:52Z</updated>
			<id>https://forum.modartt.com/viewtopic.php?pid=995518#p995518</id>
		</entry>
</feed>
