• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Controller mapping
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Controller mapping


  • Subject: Re: Controller mapping
  • From: Brian Willoughby <email@hidden>
  • Date: Mon, 10 May 2010 22:50:04 -0700


On May 10, 2010, at 22:05, john smith wrote:
A: Logic has no support for hardware controllers, like HUI, outside MIDI support. That is, parameters from AU's are not mapped onto a controllers switches and rotaries (outside what the plug-in does with MIDI). Can this really be true? A host like Logic with no support for changing parameters from a hardware controller, that seems very strange to me.

(If I'm wrong about A, then this seems to be true: Logic has support, and can map the parameters onto the controllers switches and rotaries, but... AU has no way for the plug-in to tell the host which parameters should be in which positions)

and

B: A plug-in can listen to a HW controllers MIDI messages. Honestly, that is not good enough for us, so there's no need to go down this road any further.

Logic manages the hardware controller centrally, which makes way more sense to me than having each individual plugin attempt to manage the controller separately. Have you even considered how your plugin could possibly instruct the host where to place parameters when it has no idea what positions are available? Mackie makes a number of different kinds of control surfaces and extensions, and each has a different layout. You could create a GUI in your plugin for mapping to one of these, but would you try to support every option from Mackie? What about hardware controllers from other companies like Behringer and Euphonix? Logic also supports hardware controllers from companies like TASCAM, which is why I prefer to have the host handle as much as possible.


I do not understand your complete dismissal of MIDI. The fact is that these hardware controllers send MIDI messages to the host, so you can't really expect support for anything fancier than what the controllers themselves are using. The interface between the primary Mackie MCU Pro and the extension modules is quite literally a MIDI cable. The extenders are nothing more than simple MIDI controllers with a particular protocol. It sounds like what you're asking for is a new hardware controller standard in the industry, rather than compatibility with what is currently on the market.

Admittedly, I am not 100% familiar with everything that Logic supports, or whether there are any particular limitations based upon plugin format (proprietary versus AudioUnit), but I hope that others here can comment on whether there are any real problems.

Brian Willoughby
Sound Consulting

_______________________________________________
Do not post admin requests to the list. They will be ignored.
Coreaudio-api mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden


  • Follow-Ups:
    • RE: Controller mapping
      • From: john smith <email@hidden>
References: 
 >dynamic parameter lists (From: Paul Davis <email@hidden>)
 >Re: dynamic parameter lists (From: Stephen Blinkhorn <email@hidden>)
 >Controller mapping (From: john smith <email@hidden>)
 >Re: Controller mapping (From: Brian Willoughby <email@hidden>)
 >RE: Controller mapping (From: john smith <email@hidden>)
 >Re: Controller mapping (From: William Stewart <email@hidden>)
 >Re: Controller mapping (From: john smith <email@hidden>)
 >Re: Controller mapping (From: William Stewart <email@hidden>)
 >RE: Controller mapping (From: john smith <email@hidden>)

  • Prev by Date: RE: Controller mapping
  • Next by Date: RE: Controller mapping
  • Previous by thread: RE: Controller mapping
  • Next by thread: RE: Controller mapping
  • Index(es):
    • Date
    • Thread