There are always various things that might be candidates for revision ie Events use of dur for inter-onset-interval and sustain for duration. But I think it just happens that these decisions get made by the originator, and in the future you have to work with the consequences.
best N On 26 Aug 2005, at 17:12, Tom Hall wrote:
Thanks all for responses. On 26 Aug 2005, at 14:29, nick collins wrote:I think you should assume that all UGen names are reserved words and change your own Pitch class to something even more descriptive of its functionality.Nick, I take your first point, but think Pitch could be improved in terms of its name IMHO (eg PitchFollower or whatever). For those of us sometimes working in set-class theory land - and this has included you! - Pitch has a *much* more usual meaning, no?Tom On 26 Aug 2005, at 14:40, James Harkins wrote:Workaround (sorry if the formatting is poor). The idea is to use a custom-named class to return an instance of Pitch, which the server will understand. MyPitch {*kr { arg in = 0.0, initFreq = 440.0, minFreq = 60.0, maxFreq = 4000.0,execFreq = 100.0, maxBinsPerOctave = 16, median = 1, ampThreshold = 0.01, peakThreshold = 0.5, downSample = 1;^Pitch.kr(in, initFreq, minFreq, maxFreq, execFreq, maxBinsPerOctave,median, ampThreshold, peakThreshold, downSample); } } hjh On 8/26/05, nick collins <nikolaicollinsky@xxxxxxxxxxx> wrote:best not to change the Pitch UGen's name, it's possible but you'd haveto alter the source code for this (and it would only work on your system). I think you should assume that all UGen names are reserved words and change your own Pitch class to something even more descriptive of its functionality._______________________________________________ sc-users mailing list sc-users@xxxxxxxxxxxxxxx http://www.create.ucsb.edu/mailman/listinfo/sc-users