RE: [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: RE: [linux-audio-dev] an interesting idea/point/issue from vst-land
From: Richard W.E. Furse (richard_AT_muse.demon.co.uk)
Date: Mon Mar 27 2000 - 21:24:00 EEST


Interesting idea, but when will the reverb KNOW that is is done? One can
check for zero output (i.e. the sound has 'faded away'), however the 'zero'
level will depend on the resolution at which data is stored further down
the signal chain - and the signal may go through amps in the meantime.
Also, there might be data in the delay lines that has not yet begun to feed
out.

That's not to say it cannot be done - I had problems with this issue in
VSpace a while back and came up with a non-generic solution based on zero
checking. I'd be interested in new ideas.

The LAPSPA example plugin host has a "-s" parameter to add silence to the
end of the input file to get around this. I think this is practical (if not
beautiful!) solution.

-- Richard

-----Original Message-----
From: Paul Barton-Davis [SMTP:pbd_AT_Op.Net]
Sent: Monday, March 27, 2000 3:15 PM
To: linux-audio-dev_AT_ginette.musique.umontreal.ca
Subject: [linux-audio-dev] an interesting idea/point/issue from vst-land

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 - 22:29:26 EEST