• 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: AU parameter notify vs. writing automation
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: AU parameter notify vs. writing automation


  • Subject: Re: AU parameter notify vs. writing automation
  • From: Marc Poirier <email@hidden>
  • Date: Mon, 2 Dec 2002 05:11:24 +0100 (CET)

> What if a user doesn't really care about MIDI CC, and so does not record it,
> but wants to record the translated control parameters? I can see a lot of
> utility to using MIDI CC as a way to create automation data, but once created
> and translated, there may no longer be any reason to preserve the original MIDI
> CC data. Applications like Logic allow you to edit automated control
> parameter data as easily as MIDI data, so there is no reason that every
> playback should be using CPU power to translate from MIDI CC to control
> parameters if you can just record the translated data in the first place.
>
> It does seem like there might be examples of parameters which should not be
> automated. I'm not disagreeing with your idea, I merely wanted to point out
> that you shouldn't assume that translated control parameters should never be
> recorded for automation - or that you would want to force users to record the
> MIDI CC data when they might want the option of recording the translated data.

Yeah, good point, I hadn't thought of that. For me, I definitely want
MIDI recorded because I use a MIDI fader box which has a MIDI-in and all
of the faders respond to incoming messages to calibrate themselves (i.e.
the fader positions/values are relative, not absolute), so without the
MIDI feeding back in, the fader values will be all out of wack whenever I
go back into the song. Also, I would add that translating CCs to
parameter values uses a totally trivial amount of CPU. But anyway, it
sounds like having a switchable preference here makes sense...

But the original issue remains: Can an AU change a parameter and notify
listeners without causing the host to record automation data?

Marc
_______________________________________________
coreaudio-api mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/coreaudio-api
Do not post admin requests to the list. They will be ignored.

  • Prev by Date: AudioCodec
  • Next by Date: Re: AU parameter notify vs. writing automation
  • Previous by thread: AU parameter notify vs. writing automation
  • Next by thread: Re: AU parameter notify vs. writing automation
  • Index(es):
    • Date
    • Thread