2 Jun
2008
2 Jun
'08
3:08 p.m.
2008/6/2 Arnold Krille <arnold(a)arnoldarts.de>de>:
Am Montag, 2. Juni 2008 schrieb Stefano D'Angelo:
Exactly.
#4. Support for time stretching when using non
real-time audio sources.
Time-stretching is an effect and therefor a plugin! Otherwise you will get
_very_ bad audio because every plugin-author will implement its own
time-stretching with very varying results.
You probably mean that the system should support that the number of
input-samples is different than the number of output-samples (per plugin and
process()-run). This requires that the plugins themself need to tell the host
how many samples of output result from how many samples of input.
Which would actually be a good thing for an api. And why is time-stretching limited to non-realtime
audio?
It can be suitable for real-time processing, but it's not suitable for
audio loopbacks (real world input connected to real world output),
because you can't read the future and you can't have infinite memory.
Stefano