[gmpi] Re: New Reqs 3.8 - Events
- From: Steve Harris <S.W.Harris@xxxxxxxxxxxxxxx>
- To: gmpi@xxxxxxxxxxxxx
- Date: Wed, 17 Dec 2003 11:36:09 +0000
On Tue, Dec 16, 2003 at 08:00:37PM -0800, Tim Hockin wrote:
> Keeping timestamps absolute is nice because you have one consistent
> numerical stream.
>
> Making timestamps relative to block-start may be easier for plugins to
> handle, emphasizes the "there is no future" model, and saves 4 bytes per
> event (as well as saving 64 bit math).
[stating the obvious]
Which is more convienient depends on how the canonical plugin's inner loop
looks, if its
for (pos = start; pos != end; pos++) (a)
then absolute, unsigned 64bit will be easier, but if its
for (pos = 0; pos < num_samples; pos++) (b)
then we want relative.
Frankly it doesnt matter, but it should tie into how the block size/scope
is communicated to the plugin (start+end or length).
If there is some conversion to be done then it probably makes more sense
for the host to do it, as there are intended to be more plugins than hosts.
Converting 64bit numbers to 32bit is cheap (especially in little endian
systems), doing 64bit maths is not.
- Steve
----------------------------------------------------------------------
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:
