>With XAP I suggested a per-voice SEEK control. If a Plugin implements the >SEEK control (totally optional) the host can jump into the middle of your >sustained pads by issuing a seek on the voice. This doesn't work so well >for reverbs and stuff. > That is one way to accomplish it, but it puts the burden on the plugin writer. If we made it convenient for the plugin writer to allocate internal buffers and parameters (i.e. the entire state) via GMPI, then this could happen magically in the host. Hence 3 different styles of parameters that have been discussed earlier: static (set at startup) public (available to GUI/realtime automation) private (internal data blob, available to snapshots) >I don't get what you're suggesting - you want to be able to jump to any >point in time and have the buffers still be there? > Why is this so foreign? This is how an audio recorder works, right? Why would the typical, untechnical user expect a sequencer to work any differently? Musician: Hey, why isn't the drum loop playing back during my punch-in? TechHead: Oh, you started playback after the "MIDI ON" message to the sampler plugin. Roll back a few more measures. Musician: ?? The musician is obviously a guitarist, but I leave the proof to the reader :) I think it is important to maintain sample accuracy, but I see I am not gaining any converts, so I will drop it until the next opportunity arises :) Maybe CPU's will get so fast that we can instantly prebuffer from the beginning every time. -Ben Loftis ---------------------------------------------------------------------- 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