• 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: View >> AU communication
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: View >> AU communication


  • Subject: Re: View >> AU communication
  • From: Olivier Tristan <email@hidden>
  • Date: Fri, 4 Sep 2009 01:07:45 +0200

Problem is, it gives headaches for complex plugin.
I wonder why Logic Nodes do not run the whole plugin on the distant
system while the UI is displayed
on the main system using some export display like X or VNC.

Any ideas ?


On Fri, Sep 4, 2009 at 12:58 AM, William Stewart<email@hidden> wrote:
> That's an assumption that is not always valid.
>
> For instance, one way you can implement something like logic nodes is to
> have a proxy audio unit on the host side (where the view is running) and
> then this AU just proxies all of the calls to the other machine where your
> AU is actually running. From the view's perspective, its still talking to
> your audio unit, but it actually isn't (at least not directly). So, if you
> pass pointers around, the pointer won't be valid for the address space of
> the view and <bang>
>
> One of the problems with Logic Nodes is the fact that many AUs that could
> work this way don't, because of their built-in assumptions about view and AU
> being in the same process (there are other problems too, but if you don't
> have that right, the rest don't matter)
>
> Bill
>
> On Aug 31, 2009, at 4:00 PM, tahome izwah wrote:
>
>> The AU and its view are associated via -setAU, right? So whenever I
>> update the pointer to the DSP class that the view holds in this call
>> it should be safe. I don't see why not (not that I wouldn't agree that
>> your solution is cleaner!).
>>
>> --th
>>
>> 2009/9/1 Sophia Poirier [dfx] <email@hidden>:
>>>
>>> But no, it's not safe.  Bill already mentioned earlier in the thread a
>>> context where it won't work (Logic nodes: separate address spaces).  And
>>> if
>>> you look at the Filter example, you'll see that it is doing what I
>>> describe
>>> (passing buffers of the data itself), not passing a reference to data or
>>> a
>>> class instance.
>>>
>>> Sophia
>>
>> _______________________________________________
>> 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
>



--
Olivier Tristan
 _______________________________________________
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: View >> AU communication
      • From: William Stewart <email@hidden>
    • Re: View >> AU communication
      • From: Brian Willoughby <email@hidden>
References: 
 >Re: View >> AU communication (From: William Stewart <email@hidden>)

  • Prev by Date: Re: IMA4 Audio Format on MultiChannel Mixer - iPhone
  • Next by Date: Re: Very short junk audio signal on 10.5 x86
  • Previous by thread: Re: View >> AU communication
  • Next by thread: Re: View >> AU communication
  • Index(es):
    • Date
    • Thread