<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0">
	<channel>
		<title><![CDATA[Modartt user forum - Getting the stopnames from Organteq]]></title>
		<link>https://forum.modartt.com/viewtopic.php?id=10915</link>
		<description><![CDATA[The most recent posts in Getting the stopnames from Organteq.]]></description>
		<lastBuildDate>Wed, 11 Oct 2023 08:08:44 +0000</lastBuildDate>
		<generator>PunBB</generator>
		<item>
			<title><![CDATA[Re: Getting the stopnames from Organteq]]></title>
			<link>https://forum.modartt.com/viewtopic.php?pid=993022#p993022</link>
			<description><![CDATA[<div class="quotebox"><cite>lewisalexander2020 wrote:</cite><blockquote><div class="quotebox"><cite>akaas wrote:</cite><blockquote><p>Just precisely. Each of the touch display is driven from a multiplexer board (for up to 64 touch displays), one per jamb.<br />These boards gets the addresses and signals to/from a controller card with the MCU which communicates with the organ engine as well as midi in/out for the keyboards and so on.<br />So far I have finished the schematics for the multiplexer bord and the little control card sitting on the touch display. So these days I&#039;m working on the schematics for the controller board.<br />If I can use Organteq 2 engine I also have in mind may be using the engine on a Rasberry Pi 4. Many possibilities !!</p></blockquote></div><p>that&#039;s a great idea and I like what you&#039;re doing.</p><p>At present though, organteq won&#039;t yet support this kind of data output as there is no midi out or MMC / MCU communication out. I have discussed this so let&#039;s see what happens in the near future.</p><p>lew</p></blockquote></div><p>Ok, thanks for the help, lew !</p>]]></description>
			<author><![CDATA[null@example.com (akaas)]]></author>
			<pubDate>Wed, 11 Oct 2023 08:08:44 +0000</pubDate>
			<guid>https://forum.modartt.com/viewtopic.php?pid=993022#p993022</guid>
		</item>
		<item>
			<title><![CDATA[Re: Getting the stopnames from Organteq]]></title>
			<link>https://forum.modartt.com/viewtopic.php?pid=993018#p993018</link>
			<description><![CDATA[<div class="quotebox"><cite>akaas wrote:</cite><blockquote><p>Just precisely. Each of the touch display is driven from a multiplexer board (for up to 64 touch displays), one per jamb.<br />These boards gets the addresses and signals to/from a controller card with the MCU which communicates with the organ engine as well as midi in/out for the keyboards and so on.<br />So far I have finished the schematics for the multiplexer bord and the little control card sitting on the touch display. So these days I&#039;m working on the schematics for the controller board.<br />If I can use Organteq 2 engine I also have in mind may be using the engine on a Rasberry Pi 4. Many possibilities !!</p></blockquote></div><p>that&#039;s a great idea and I like what you&#039;re doing.</p><p>At present though, organteq won&#039;t yet support this kind of data output as there is no midi out or MMC / MCU communication out. I have discussed this so let&#039;s see what happens in the near future.</p><p>lew</p>]]></description>
			<author><![CDATA[null@example.com (lewisalexander2020)]]></author>
			<pubDate>Wed, 11 Oct 2023 06:34:10 +0000</pubDate>
			<guid>https://forum.modartt.com/viewtopic.php?pid=993018#p993018</guid>
		</item>
		<item>
			<title><![CDATA[Re: Getting the stopnames from Organteq]]></title>
			<link>https://forum.modartt.com/viewtopic.php?pid=993016#p993016</link>
			<description><![CDATA[<p>Just precisely. Each of the touch display is driven from a multiplexer board (for up to 64 touch displays), one per jamb.<br />These boards gets the addresses and signals to/from a controller card with the MCU which communicates with the organ engine as well as midi in/out for the keyboards and so on.<br />So far I have finished the schematics for the multiplexer bord and the little control card sitting on the touch display. So these days I&#039;m working on the schematics for the controller board.<br />If I can use Organteq 2 engine I also have in mind may be using the engine on a Rasberry Pi 4. Many possibilities !!</p>]]></description>
			<author><![CDATA[null@example.com (akaas)]]></author>
			<pubDate>Tue, 10 Oct 2023 21:32:19 +0000</pubDate>
			<guid>https://forum.modartt.com/viewtopic.php?pid=993016#p993016</guid>
		</item>
		<item>
			<title><![CDATA[Re: Getting the stopnames from Organteq]]></title>
			<link>https://forum.modartt.com/viewtopic.php?pid=993001#p993001</link>
			<description><![CDATA[<div class="quotebox"><cite>akaas wrote:</cite><blockquote><div class="quotebox"><cite>lewisalexander2020 wrote:</cite><blockquote><div class="quotebox"><cite>akaas wrote:</cite><blockquote><p>Hi, folks!<br />I am projecting my next organ, and want to use touch display on the jambs. I than case I need to get the stop names etc from Organteq 2 so they can be shown in the displays.<br />Any suggestions to how ?<br />Thanks...</p></blockquote></div><p>If you&#039;re using touch displays for left and right jambs, you do know that organteq 2 has split jamb view and as such both displays will show the left and right jambs independently.</p><p>unless you&#039;re using a custom UI and relying on organteq 2 as the engine and sending midi out to a custom app as a jamb view, then I&#039;m a little unsure of why you&#039;d need sysex and custom assign, but it&#039;s something we&#039;d benefit from for custom console builds, especially midi out for motor control or sysex to other resources.</p><p>good luck with the organ build, we&#039;d love to hear the progress on this and your design ideas, thoughts, if you want to share them, that&#039;s up to you. I&#039;m doing the same as well, it&#039;s amazing how many design concepts you come up with, which ones work, which ones don&#039;t and the surprise ideas in between.</p><p>lew</p></blockquote></div><p>To clear up a bit, I&#039;ll want to use a single touch display for each stop, say 4 col and 8 rows per jamb (2 divisions per jamb). To display the stop name and eventual division name on the display I need these names from the engine in some way. The touch display will therefore act like a electro mechanical draw stop, toggling the stop on and off.<br />As I can see, the only way of communicate these names will be via midi sysex messages.</p></blockquote></div><p>hmmm, depending on the OS, are you looking at routing organteq via an external midi app for anything like this? I ask as what you&#039;re looking at requires two major elements, the first is midi out from organteq which would need to support sysex and midi machine control as an example, the second would be a way to recognise modular display units as a combination midi switch and display output. How organteq 2 works is it supports 2 external displays by using the dual jamb view and as such that&#039;s the way it currently supports things. This would be something to raise with modartt, if I get chance, I&#039;ll send over some of this to the guys and see what they think.</p><p>I&#039;m guessing that you&#039;re looking at a concept similar to that of a johannus live 3 AGO model which uses refreshable LED displays but physical stops, but in your case you want to achieve stops as touch elements with the display serving two functions, a midi actuator and a refreshable stop display. I like the concept and I wonder if it&#039;s something that could be achieved. If I&#039;m right, I think hauptwerk supports something like that, but I would say that to trigger this, you&#039;re going to need a good midi out logic board / encode / decode board with display drivers, that&#039;ll set you back quite a bit.</p><p>lew</p>]]></description>
			<author><![CDATA[null@example.com (lewisalexander2020)]]></author>
			<pubDate>Tue, 10 Oct 2023 07:49:56 +0000</pubDate>
			<guid>https://forum.modartt.com/viewtopic.php?pid=993001#p993001</guid>
		</item>
		<item>
			<title><![CDATA[Re: Getting the stopnames from Organteq]]></title>
			<link>https://forum.modartt.com/viewtopic.php?pid=992990#p992990</link>
			<description><![CDATA[<div class="quotebox"><cite>lewisalexander2020 wrote:</cite><blockquote><div class="quotebox"><cite>akaas wrote:</cite><blockquote><p>Hi, folks!<br />I am projecting my next organ, and want to use touch display on the jambs. I than case I need to get the stop names etc from Organteq 2 so they can be shown in the displays.<br />Any suggestions to how ?<br />Thanks...</p></blockquote></div><p>If you&#039;re using touch displays for left and right jambs, you do know that organteq 2 has split jamb view and as such both displays will show the left and right jambs independently.</p><p>unless you&#039;re using a custom UI and relying on organteq 2 as the engine and sending midi out to a custom app as a jamb view, then I&#039;m a little unsure of why you&#039;d need sysex and custom assign, but it&#039;s something we&#039;d benefit from for custom console builds, especially midi out for motor control or sysex to other resources.</p><p>good luck with the organ build, we&#039;d love to hear the progress on this and your design ideas, thoughts, if you want to share them, that&#039;s up to you. I&#039;m doing the same as well, it&#039;s amazing how many design concepts you come up with, which ones work, which ones don&#039;t and the surprise ideas in between.</p><p>lew</p></blockquote></div><p>To clear up a bit, I&#039;ll want to use a single touch display for each stop, say 4 col and 8 rows per jamb (2 divisions per jamb). To display the stop name and eventual division name on the display I need these names from the engine in some way. The touch display will therefore act like a electro mechanical draw stop, toggling the stop on and off.<br />As I can see, the only way of communicate these names will be via midi sysex messages.</p>]]></description>
			<author><![CDATA[null@example.com (akaas)]]></author>
			<pubDate>Mon, 09 Oct 2023 20:48:01 +0000</pubDate>
			<guid>https://forum.modartt.com/viewtopic.php?pid=992990#p992990</guid>
		</item>
		<item>
			<title><![CDATA[Re: Getting the stopnames from Organteq]]></title>
			<link>https://forum.modartt.com/viewtopic.php?pid=992955#p992955</link>
			<description><![CDATA[<div class="quotebox"><cite>akaas wrote:</cite><blockquote><p>Hi, folks!<br />I am projecting my next organ, and want to use touch display on the jambs. I than case I need to get the stop names etc from Organteq 2 so they can be shown in the displays.<br />Any suggestions to how ?<br />Thanks...</p></blockquote></div><p>If you&#039;re using touch displays for left and right jambs, you do know that organteq 2 has split jamb view and as such both displays will show the left and right jambs independently.</p><p>unless you&#039;re using a custom UI and relying on organteq 2 as the engine and sending midi out to a custom app as a jamb view, then I&#039;m a little unsure of why you&#039;d need sysex and custom assign, but it&#039;s something we&#039;d benefit from for custom console builds, especially midi out for motor control or sysex to other resources.</p><p>good luck with the organ build, we&#039;d love to hear the progress on this and your design ideas, thoughts, if you want to share them, that&#039;s up to you. I&#039;m doing the same as well, it&#039;s amazing how many design concepts you come up with, which ones work, which ones don&#039;t and the surprise ideas in between.</p><p>lew</p>]]></description>
			<author><![CDATA[null@example.com (lewisalexander2020)]]></author>
			<pubDate>Sun, 08 Oct 2023 07:36:18 +0000</pubDate>
			<guid>https://forum.modartt.com/viewtopic.php?pid=992955#p992955</guid>
		</item>
		<item>
			<title><![CDATA[Getting the stopnames from Organteq]]></title>
			<link>https://forum.modartt.com/viewtopic.php?pid=992868#p992868</link>
			<description><![CDATA[<p>Hi, folks!<br />I am projecting my next organ, and want to use touch display on the jambs. I than case I need to get the stop names etc from Organteq 2 so they can be shown in the displays.<br />Any suggestions to how ?<br />Thanks...</p>]]></description>
			<author><![CDATA[null@example.com (akaas)]]></author>
			<pubDate>Tue, 03 Oct 2023 02:47:12 +0000</pubDate>
			<guid>https://forum.modartt.com/viewtopic.php?pid=992868#p992868</guid>
		</item>
	</channel>
</rss>
