• 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: Using an AU directly
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Using an AU directly


  • Subject: Re: Using an AU directly
  • From: "Ross Bencina" <email@hidden>
  • Date: Tue, 8 Sep 2009 15:19:34 +1000

Hi

I'm following this with interest since I need to implement the same thing in the coming months. I already have my own cross-platform graph framework I just need to adapt individual AUs to work with my synchronous evaluation graph (which, btw, currently uses a pre-compiled evaluation schedule not a run-time pull graph traversal).

Darrell: can you please summarise what you are finding difficult about invoking the AU synchronously -- all this multi-threading hackery you're discussing is definitely something I intend to avoid...

Thanks!

Ross.






=================================== AudioMulch 2.0 is here!

http://www.audiomulch.com
----- Original Message ----- From: "Darrell Gibson" <email@hidden>
To: <email@hidden>
Sent: Monday, September 07, 2009 11:14 PM
Subject: RE: Using an AU directly



Th,

Unless I am missing something an AUGraph has to have an output unit/device. This is kind of the same problem I'm running into now without using the AUGraph, but when I started out I thought not using an AUGraph would allow me to create a network of AUs without an output device. I now realize the same problem exists as there needs to be something to initiate the "pull" and as I result I don't think it would matter if I used a graph or not.

Darrell.

________________________________________
From: coreaudio-api-bounces+gibsond=email@hidden [coreaudio-api-bounces+gibsond=email@hidden] On Behalf Of tahome izwah [email@hidden]
Sent: 07 September 2009 13:08
To: email@hidden
Subject: Re: Using an AU directly


I can't help you with this I'm afraid, but I am curious: what is your
rationale behind not wanting to use an AUGraph?

--th
_______________________________________________
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




BU - the UK's Number One New University The Guardian University Guide 2009 & 2010

This email is intended only for the person to whom it is addressed and may contain confidential information. If you have received this email in error, please notify the sender and delete this email, which must not be copied, distributed or disclosed to any other person.
Any views or opinions presented are solely those of the author and do not necessarily represent those of Bournemouth University or its subsidiary companies. Nor can any contract be formed on behalf of the University or its subsidiary companies via email.



_______________________________________________ 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


  • Follow-Ups:
    • RE: Using an AU directly
      • From: Darrell Gibson <email@hidden>
    • Re: Using an AU directly
      • From: Brian Willoughby <email@hidden>
References: 
 >Using an AU directly (From: Darrell Gibson <email@hidden>)
 >Re: Using an AU directly (From: tahome izwah <email@hidden>)
 >RE: Using an AU directly (From: Darrell Gibson <email@hidden>)

  • Prev by Date: Re: Implementing FFT for an EQ filter on iPhone
  • Next by Date: Re: Using an AU directly
  • Previous by thread: RE: Using an AU directly
  • Next by thread: Re: Using an AU directly
  • Index(es):
    • Date
    • Thread