[linux-audio-dev] an interesting idea/point/issue from vst-land

New Message Reply About this list Date view Thread view Subject view Author view Other groups

Subject: [linux-audio-dev] an interesting idea/point/issue from vst-land
From: Paul Barton-Davis (pbd_AT_Op.Net)
Date: Mon Mar 27 2000 - 17:14:42 EEST


This seems to raise an interesting issue: a plugin that needs to tell
the engine of the host that "i'm not done yet, even if you think i
should be".

Could we include the notion of a return code to signify "keep me
running" ?

--p

>> sorry Phillipe but that's not how it was supposed to be interpreted :-)
>> with any new method or function since version 1, the default value should
>> always provide the most 'secure' (or convenient) information. the
>> hasTail () method is a means of telling the host how much tail there is
>> (what else), in order to enable host to omit processing the plug and/or
>> determine the length of export operations.
>>in the first case, host may stop processing the plug based on this
>>information. this means that a plug which needs continuous calls to
>>its process method should return 0 (infinite), just like 'old' version 1
>>plugs will, so to ensure that their processing is not disrupted as we
>>don't know if that could make it fail.
>
>Hmm, there is a missunderstanding here. On the
>opposite, the default should be 'no tail at all',
>and not 'infinite' (according to my original
>proposal of "effGetTailSize"). The idea was to
>solve the following problem: eg. the host renders
>a file of 10 seconds. If an EQ is used on that
>file, the resulting file should be 10 seconds (no
>tail).
>But if a reverb plugin is used, then the resulting
>file should be eg. 12 seconds, because the plugins
>wants to add a tail of 2 seconds. If the default
>is "infinite tail", then it is simply not possible
>to render a file.


New Message Reply About this list Date view Thread view Subject view Author view Other groups

This archive was generated by hypermail 2b28 : Mon Mar 27 2000 - 18:01:33 EEST