-----Original Message----- From: Tim Hockin [mailto:thockin@xxxxxxxxxx] > >It gives accuracy of manipulation and it gives flexibility to the USER, >where it belongs. The user can set up 10000000 ticks per beat, if they so >desire, or they can set up 10. Whichever suits their needs. It was argued >in XAP that ticks_per_beat should be fixed at some very high value, so as to >be essentially seamless. > >I don't see the need. > ---------------------------------------------------------------------- It does not really give any flexibility, it just gives something else that needs to be worried about. The user does not need to be able to control the accuracy, they need something that is accurate. What is the point of having a "do things inaccurately" control? Why should I have to worry about what the tick per beat setting is? Why should I even have to know what ticks are? If a person wants to quantize their music to tenths of a beat, that's what the quantize function is for. Or is there some large performance gain enabled by this? -Frederick Umminger ---------------------------------------------------------------------- Generalized Music Plugin Interface (GMPI) public discussion list Participation in this list is contingent upon your abiding by the following rules: Please stay on topic. You are responsible for your own words. Please respect your fellow subscribers. Please do not redistribute anyone else's words without their permission. Archive: http://www.freelists.org/archives/gmpi Email gmpi-request@xxxxxxxxxxxxx w/ subject "unsubscribe" to unsubscribe