Hi, folks!
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.
Any suggestions to how ?
Thanks...
Hi, folks!
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.
Any suggestions to how ?
Thanks...
If you'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.
unless you'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'm a little unsure of why you'd need sysex and custom assign, but it's something we'd benefit from for custom console builds, especially midi out for motor control or sysex to other resources.
good luck with the organ build, we'd love to hear the progress on this and your design ideas, thoughts, if you want to share them, that's up to you. I'm doing the same as well, it's amazing how many design concepts you come up with, which ones work, which ones don't and the surprise ideas in between.
lew
akaas wrote:Hi, folks!
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.
Any suggestions to how ?
Thanks...If you'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.
unless you'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'm a little unsure of why you'd need sysex and custom assign, but it's something we'd benefit from for custom console builds, especially midi out for motor control or sysex to other resources.
good luck with the organ build, we'd love to hear the progress on this and your design ideas, thoughts, if you want to share them, that's up to you. I'm doing the same as well, it's amazing how many design concepts you come up with, which ones work, which ones don't and the surprise ideas in between.
lew
To clear up a bit, I'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.
As I can see, the only way of communicate these names will be via midi sysex messages.
lewisalexander2020 wrote:akaas wrote:Hi, folks!
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.
Any suggestions to how ?
Thanks...If you'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.
unless you'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'm a little unsure of why you'd need sysex and custom assign, but it's something we'd benefit from for custom console builds, especially midi out for motor control or sysex to other resources.
good luck with the organ build, we'd love to hear the progress on this and your design ideas, thoughts, if you want to share them, that's up to you. I'm doing the same as well, it's amazing how many design concepts you come up with, which ones work, which ones don't and the surprise ideas in between.
lew
To clear up a bit, I'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.
As I can see, the only way of communicate these names will be via midi sysex messages.
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'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's the way it currently supports things. This would be something to raise with modartt, if I get chance, I'll send over some of this to the guys and see what they think.
I'm guessing that you'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's something that could be achieved. If I'm right, I think hauptwerk supports something like that, but I would say that to trigger this, you're going to need a good midi out logic board / encode / decode board with display drivers, that'll set you back quite a bit.
lew
Just precisely. Each of the touch display is driven from a multiplexer board (for up to 64 touch displays), one per jamb.
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.
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'm working on the schematics for the controller board.
If I can use Organteq 2 engine I also have in mind may be using the engine on a Rasberry Pi 4. Many possibilities !!
Just precisely. Each of the touch display is driven from a multiplexer board (for up to 64 touch displays), one per jamb.
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.
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'm working on the schematics for the controller board.
If I can use Organteq 2 engine I also have in mind may be using the engine on a Rasberry Pi 4. Many possibilities !!
that's a great idea and I like what you're doing.
At present though, organteq won'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's see what happens in the near future.
lew
akaas wrote:Just precisely. Each of the touch display is driven from a multiplexer board (for up to 64 touch displays), one per jamb.
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.
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'm working on the schematics for the controller board.
If I can use Organteq 2 engine I also have in mind may be using the engine on a Rasberry Pi 4. Many possibilities !!that's a great idea and I like what you're doing.
At present though, organteq won'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's see what happens in the near future.
lew
Ok, thanks for the help, lew !