Re: 2 AUCocoaView implementation questions: How to deal with uninitialized AU, and restrict Host to single view.
Re: 2 AUCocoaView implementation questions: How to deal with uninitialized AU, and restrict Host to single view.
- Subject: Re: 2 AUCocoaView implementation questions: How to deal with uninitialized AU, and restrict Host to single view.
- From: Robert Fehse <email@hidden>
- Date: Mon, 19 Jul 2010 16:16:27 +0200
You cannot share objects between View and engine because there is no
guarantee that the two types of entities will be running in the same
address space, or even on the same machine. If you are literally
sharing the same object between View and audio engine, then you have a
broken AudioUnit implementation.
As i remember that the hard seperation of view and engine was not
mandatory. An AU should not be regarded as broken if you ask me, just as
an AU which is not able to live in different address spaces.
There are many questions unanswered related to address seperation.
For example how you would choose a file on the engine machine in a
filechooser on the gui machine then?
Write your own filechooser which transports directory information via
properties ?
If you need more examples just imagine what would be needed to let the
Kore gui exist on another machine ;)
If you need a gui on another machine, why not use existing technologies
like VNC, this would feel much smarter to me.
And pure parameter remoting is anyway possible via parameter communication.
just my 2 cents
Robert
_______________________________________________
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