[gmpi] Re: Reqs 3.9. Time - opening arguments.1
- From: "Michael Stauffer" <michael@xxxxxxxxxxxxxxxxxx>
- To: <gmpi@xxxxxxxxxxxxx>
- Date: Mon, 16 Feb 2004 20:07:47 -0500
Chris wrote:
>A different perspective, FWIW: One of the Nokia guys I work with
>sometimes says "Non-realtime is just a special case of realtime." In
>the absence of long-lookahead, as 'realtime' GMPI has been proposed
>so far, I think that's probably right. So if people have really been
>meaning 'long look-ahead' when they've been saying 'offline,' can we
>consider changing our terminology by starting to call that 'long
>look-ahead,' or something similar?
I *think* I mean actual offline processing. The transport is stopped and
the plug gets a whole chunk (or rather a series of buffers, I s'pose) of
data to process, maybe a whole track or the current user selection. The
plug then, generally, replaces the original data with it's processed
data, e.g. after applying some reverb. Then the user hits 'play' and
hears the results.
Does that sound like 'offline', or is it what you mean by 'long
look-ahead'.
My first thought for 'long look-ahead' would be that it refers to getting
data signifigantly ahead of the conductor/transport/realtime position.
Cheers,
Michael
----------------------------------------------------------------------
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
Other related posts:
