Since all unit generator classes are subclasses of UGen, that is the one to use. But you should use extension methods for your ops, not a subclass. There's no multiple inheritance in SC, so if you have MyThing which is a subclass of UGen, and SomeOtherUGen that is a subclass of UGen, SomeOtherUGen can't inherit methods from MyThing. But if you add methods to UGen, then all ugen classes inherit them. See "External Method Files" in Writing-Classes help. One reason why I'm skeptical of this approach, though, is a loss of runtime flexibility. Tuning synths is one of those activities that especially benefits from the ability to make changes on the fly. If you hardcode your filters into methods, the only way to change them is to edit the method and recompile the library, blowing away all the objects you were working on. My feeling is that this gets old really fast, so it's better to keep such things in a structure that you can tweak at runtime without recompiling the class lib. hjh On Dec 31, 2008, at 12:12 AM, David Etlinger wrote:
: H. James Harkins .::!:.:.......:.::........:..!.::.::...:..:...:.:.:.:..: "Come said the Muse, Sing me a song no poet has yet chanted, Sing me the universal." -- Whitman |