Re: a reason to not access AU from AUView via a direct pointer
Re: a reason to not access AU from AUView via a direct pointer
- Subject: Re: a reason to not access AU from AUView via a direct pointer
- From: email@hidden
- Date: Fri, 27 Dec 2002 17:53:40 +0100
Hi Marc, hi list,
I have
still been using direct pointers for some things as a matter of
convenience, but I just thought of a pretty good reason to not do this
anymore.
The way that Apple choose to handle AUView respectively to AU is
probably the best way to do it, but in my humble opinion, they
should have not said then that "making AU is just a port".
In all other famous plugin norms, gui & dsp are in the same
address space. Then for all plugin companies that made plugins
for those norm, it was easier to link gui & dsp using direct
pointer.
Then if I want to do it the way Apple want it me to do, I'll
have to rewrite a huge part of our common libs (which is more
than 95% of code, I'm not lying for sure).
The only thing I'm sure is that I will only use 'pipe
communication' if and only if one program do the feature that
you're describing, otherwise I will never do it. I've simply not
enough time to implement it (and benefice in term of features
are small in my opinion).
I would prefer from Apple to implement some modified MMU
handling with virtual memory to fetch data across the
network !!! ;) (which seems to be possible BTW, ethernet
interface at 100Mb are almost as fast as disk, hey, I should
patent that idea ;P )
Thanks,
Raphael
_______________________________________________
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.