Topic by lewisalexander2020

  • Avatar
  • lewisalexander2020
  • Member
  • Offline
  • From: North Wales. United Kingdom
  • Registered: 18-03-2021
  • Posts: 218

Topic: Feature Request: Midi Out Support

Hello ladies and gentlemen,

I'm Sorry it's been a while, a very trying time between hospital, meetings and other matters, this is what cancer does to a family.

So, as the subject says. This is a feature request for MIDI OUT, whether as MMC or other means.

Why?

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're using the console as a tactile experience as a good example, you need midi out from organteq 2 to drive electro-mechanical stops  for various functions, or if you're a sighted person, illuminated stops to indicate whether a stop in a sequence is active or not, especially if you're running the console and organteq headless.

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.

I'll forward this on to Niclas anway for the team but putting this here for reference.

Lew

Blind Music Producer, Composer, pianist and Church Organist. Accessibility development specialist for MacOS. Developing a solution for blind organists to have an accessible digital organ solution.

Reply by tmyoung

  • Avatar
  • tmyoung
  • Member
  • Offline
  • From: USA
  • Registered: 20-09-2012
  • Posts: 448

Re: Feature Request: Midi Out Support

Agreed.  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.

So sorry to hear about your family's ongoing health struggles!

Spotify: https://open.spotify.com/artist/2xHiPcCsm29R12HX4eXd4J
Pianoteq Pro & Organteq 2
Steinways, Grotrian, Steingraeber, Bechstein, Petrof, Blüthner, K2, Karsten, & Kremsegg
Casio GP300

tmyoung's Website

Reply by Pat

  • Avatar
  • Pat
  • Member
  • Offline
  • Registered: 21-06-2007
  • Posts: 187

Re: Feature Request: Midi Out Support

Yes! I also hope we don't have to wait too long for MIDI Out.

Reply by akaas

  • Avatar
  • akaas
  • Member
  • Offline
  • From: 3370 Vikersund, Norway
  • Registered: 03-10-2023
  • Posts: 6

Re: Feature Request: Midi Out Support

lewisalexander2020 wrote:

Hello ladies and gentlemen,

I'm Sorry it's been a while, a very trying time between hospital, meetings and other matters, this is what cancer does to a family.

So, as the subject says. This is a feature request for MIDI OUT, whether as MMC or other means.

Why?

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're using the console as a tactile experience as a good example, you need midi out from organteq 2 to drive electro-mechanical stops  for various functions, or if you're a sighted person, illuminated stops to indicate whether a stop in a sequence is active or not, especially if you're running the console and organteq headless.

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.

I'll forward this on to Niclas anway for the team but putting this here for reference.

Lew

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....