----- Original Message ----- From: "Frederick Umminger" <Frederick_Umminger@xxxxxxxxxxxxxx> To: <gmpi@xxxxxxxxxxxxx> Sent: Thursday, May 08, 2003 7:42 PM Subject: [gmpi] Re: Topic 6: Time representation > > > -----Original Message----- > From: Vincent Burel [mailto:vincent.burel@xxxxxxxxxx] > >just one remark. > >If possible , think to communicate to the plug-in a structure which contain > >all time type in all possible unit. > >i think Tim Hockin said it also. > > > >the typical problem is to avoid redondancy computation. > >Providing a complete time structure to the plug-in means that the time > >conversion and computation will be made one time only (by the host) . > > I think this solution actually increases redundancy. It requires the host to compute > time in various units that the plugin will never use. Nearly all plugins are only going > to need one unit. > > This can be a lot of excess computation if it is being done for time-stamps on all Midi > and automation data in a large multi-track session. i'm affraid i don't understand. For me the time representation for plug-in has to be computed one and only one time per audioframe (whatever the number of plug-in on the system) so where is "more redundancy" !?. Also i don't understand why you are talking about MIDI and Automation, these events are typically not provided to the plug-in with a time representation ! Vincent Burel ---------------------------------------------------------------------- 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: //www.freelists.org/archives/gmpi Email gmpi-request@xxxxxxxxxxxxx w/ subject "unsubscribe" to unsubscribe