• 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: How to keep view and audio unit aware of each other
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: How to keep view and audio unit aware of each other


  • Subject: Re: How to keep view and audio unit aware of each other
  • From: "Robert Fehse" <email@hidden>
  • Date: Sat, 31 Jan 2009 14:05:02 +0100

Theoretically Brian is right, and for simple 8 knob plugins this will work,
but in reallife there are many problems which can't be solved via pure
property communication.

You can request a pointer to your engine when your gui is created, then you
can do your own construction/deconstruction checking.

I wonder in which circumstances GB is deleting the engine but not the view ?

Robert


----- Original Message -----
From: "Brian Willoughby" <email@hidden>
To: <email@hidden>
Cc: <email@hidden>
Sent: Saturday, January 31, 2009 8:38 AM
Subject: Re: How to keep view and audio unit aware of each other


> The word is that you should write your audio code and view(s) as
> completely independent.  You have to do everything with listeners and
> properties.  You cannot even be certain that there aren't multiple
> views open at the same time.
>
>
> On Jan 30, 2009, at 20:19, Brent Lehman wrote:
>
> Sorry if this question is answered all the time.  I searched for it
> but couldn't find it.
>
> What is the best way for an audio unit and its associated view to be
> notified of each other's constructions and destructions?  In some
> cases it looks like GarageBand kills and reconstructs the unit but
> keeps the view, and it's causing problems in the code base I'm
> maintaining.  Maybe I could figure something out with listeners and
> properties, but if there's a more elegant way I'd rather use it.
>
> If there's a way for the unit to query whether or not an associated
> view exists, that would work too.
>
>  _______________________________________________
> 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

 _______________________________________________
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

References: 
 >How to keep view and audio unit aware of each other (From: Brent Lehman <email@hidden>)
 >Re: How to keep view and audio unit aware of each other (From: Brian Willoughby <email@hidden>)

  • Prev by Date: Re: How to keep view and audio unit aware of each other
  • Next by Date: AIFFWriter - Select Output Encoding Format dialog box
  • Previous by thread: Re: How to keep view and audio unit aware of each other
  • Next by thread: AIFFWriter - Select Output Encoding Format dialog box
  • Index(es):
    • Date
    • Thread