AUMonotimbralInstrumentBase (synthesiser) best design practices
AUMonotimbralInstrumentBase (synthesiser) best design practices
- Subject: AUMonotimbralInstrumentBase (synthesiser) best design practices
- From: Jon Crooke <email@hidden>
- Date: Thu, 17 Jun 2010 19:15:55 +0100
hi all,
i'm finally getting properly stuck into my CS synthesiser project now, and have spent some time examining the AU instrument template in xcode, performed quite a few experiments, and am more or less ready to get stuck into the nuts and bolts of designing my instrument
i did, however, want to take advantage of the experience on here with regards to design. i certainly want to make my instrument as portable as possible, and was wondering the best way to go about this. from what i can see, a Note class (subclass of SynthNote) will define a single voice of the instrument. since i would like the instrument to be loosely coupled to the AU framework, i'm wondering what the most appropriate design pattern would be:
at the moment i'm thinking of making creating a Voice class, which with be a member of the Note (SynthNote subclass). this class will probably encapsulate a single synthesiser voice, in this way the Note class is just a wrapper. i imagine i'll need to store a pointer back to the Note as well, in order to take advantage of the inherited SynthNode member functions?
also, i was wondering why the TestNote "class" is defined as a struct in the provided AU instrument template. are there performance benefits? a convention? or just because all members should be public? sorry, my C++ isn't the best!
apologies for the newbie questions! i hope someone can't let me know if i'm on the right path, or save me wasting a lot of my time!
thanks in advance
-Jon
_______________________________________________
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