[gmpi] Re: Requirements sections 3.4 and 3.5
- From: Marc Poirier <fipnid@xxxxxxxxx>
- To: gmpi@xxxxxxxxxxxxx
- Date: Sun, 30 Nov 2003 21:04:06 -0800 (PST)
--- Tim Hockin wrote:
> However, this has made me start to rethink the REAL requirement.
>
> I think the REAL requirement is that a plugin that cares should be
> notified as to whether it is running realtime or offline.
Yeah, I also think that that's the only thing that should come of this. I
think that also hardware DSP (like those PCI cards, PowerCore, UA, etc.)
need this sort of info. I might be wrong about that, though. But there
are cases when it's very useful. Like a sampler that does streaming from
disk, for example, may do certain threading and optimizations for realtime
that just make no sense offline. That sort of thing. So yeah, I think
that that level of info about the current context (offline or realtime) is
a requirement.
> GMPI must provide information about the mode in which the graph is
> operating (realtime or offline) to plugins which request that
> information.
This sounds good although it seems to me that saying "the host" (specific)
rather than "GMPI" (wuh?) makes more sense, no?
> Then the host can provide a draft/final toggle at rendering. Setting it
> to "draft" will run plugins at realtime quality (they'll think they are
> realtime). Setting it to "final" will tell plugins they are running
> offline and can chew up CPU.
I'd rather not think of realtime as a "quality". It's a rendering context
(okay, maybe there's a better word than "context", but it's not
"quality"), and it may have nothing to do with sound quality. Let those
plugs make a quality parameter when it's really possible and useful (which
I think 99% of the time, both are not the case).
Marc
__________________________________
Do you Yahoo!?
Free Pop-Up Blocker - Get it now
http://companion.yahoo.com/
----------------------------------------------------------------------
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
- References:
- [gmpi] Re: Requirements sections 3.4 and 3.5
- From: Tim Hockin
Other related posts:
- » [gmpi] Requirements sections 3.4 and 3.5
- » [gmpi] Re: Requirements sections 3.4 and 3.5
- » [gmpi] Re: Requirements sections 3.4 and 3.5
- » [gmpi] Re: Requirements sections 3.4 and 3.5
- » [gmpi] Re: Requirements sections 3.4 and 3.5
- » [gmpi] Re: Requirements sections 3.4 and 3.5
- » [gmpi] Re: Requirements sections 3.4 and 3.5
- » [gmpi] Re: Requirements sections 3.4 and 3.5
- » [gmpi] Re: Requirements sections 3.4 and 3.5
- » [gmpi] Re: Requirements sections 3.4 and 3.5
- » [gmpi] Re: Requirements sections 3.4 and 3.5
- » [gmpi] Re: Requirements sections 3.4 and 3.5
- » [gmpi] Re: Requirements sections 3.4 and 3.5
- » [gmpi] Re: Requirements sections 3.4 and 3.5
- » [gmpi] Re: Requirements sections 3.4 and 3.5
- » [gmpi] Re: Requirements sections 3.4 and 3.5
- » [gmpi] Re: Requirements sections 3.4 and 3.5
- » [gmpi] Re: Requirements sections 3.4 and 3.5
- » [gmpi] Re: Requirements sections 3.4 and 3.5
- » [gmpi] Re: Requirements sections 3.4 and 3.5
- » [gmpi] Re: Requirements sections 3.4 and 3.5
- [gmpi] Re: Requirements sections 3.4 and 3.5
- From: Tim Hockin