I know this is OT but i finally got Improsculpt working properly 
with Csound5!

pp


On Tue Sep 29 03:53:52 EDT 2009, Oeyvind Brandtsegg 
 wrote:

> Thanks a lot, this is clear.
> 
> ... well, but there is one more thing I can't get my head around:
> Why do we not get added latency when ksmps < vectorsize ?
> I understand that this is probably the same reason as why we 
> don't get
> added latency when patching signals through jack, but I haven't 
> been
> able to understand that either. Hope someone could have the 
> patience
> to try to explain this, as I really would like to know.
> 
> best
> Oeyvind
> 
> 
> 2009/9/29 dp51 :
>> 
>> The -b flag will have no effect. ??csound~ communicates directly
>> with Csound. ??Think of Max's DSP settings as replacing the need
>> for -b and -B. ??Don't pay attention to the "audio buffered in 
>> 128
>> sample-frame blocks" messages.
>> 
>> However, there is buffering. ??Here's a short explanation:
>> 
>> When csound~ receives vectors of audio from Max, it will try to
>> fill up Csound's input buffers. ??The size of these input 
>> buffers = ksmps.
>> When they're full, Csound processes one k-cycle and outputs ksmps
>> sized vectors. ??csound~ will fill the Max output buffers with 
>> data from
>> these output vectors. ?? For any given set of vectors received 
>> from
>> Max, Csound may process zero or more k-cycles.
>> 
>> So, the only way this buffering can induce latency is by making
>> ksmps > Max signal vector size. ??An extreme example would be
>> Max signal vector size = 1 and ksmps = 44100. ??If sr = 44100, 
>> then
>> the latency would be 1 second.
>> 
>> Remember, to prevent latency between Max and csound~, make sure
>> ksmps <= Max signal vector size. ??I hope this clears up any 
>> confusion.
>> 
>> Davis
>> 
>> --
>> View this message in context: 
>> http://www.nabble.com/csound%7E-question-tp25643571p25654833.html
>> Sent from the Csound - General mailing list archive at 
>> Nabble.com.
>> 
>> 
>> 
>> Send bugs reports to this list.
>> To unsubscribe, send email sympa@lists.bath.ac.uk with body 
>> "unsubscribe csound"
>> 
> 
> 
> Send bugs reports to this list.
> To unsubscribe, send email sympa@lists.bath.ac.uk with body 
> "unsubscribe csound"
> 



Patrick Pagano,M.F.A
Digital Media Engineer
Digital Worlds Institute
GAINESVILLE  FL  US  32611-5900
University Of Florida
(352) 294-2081

Oh, sorry if you've had problems with it for so long.
Is this the old version (from 2002 or 2003 or somewhere) ?
That version is now called "Improsculpt Classic" (hehe), and is available at
http://sourceforge.net/projects/improsculpt/files/ImproSculptClassic/ImproSculptClassic/ImproSculptClassic.zip/download

The new version ImproSculpt4 is kind of harder to install, as it
requires certain addon python modules. I haven't updated the file
release in a while, but the cvs is quite up to date.

best
Oeyvind

2009/9/29 shreeswifty :
> I know this is OT but i finally got Improsculpt working properly with
> Csound5!
>
> pp
>
>
> On Tue Sep 29 03:53:52 EDT 2009, Oeyvind Brandtsegg 
> wrote:
>
>> Thanks a lot, this is clear.
>>
>> ... well, but there is one more thing I can't get my head around:
>> Why do we not get added latency when ksmps < vectorsize ?
>> I understand that this is probably the same reason as why we don't get
>> added latency when patching signals through jack, but I haven't been
>> able to understand that either. Hope someone could have the patience
>> to try to explain this, as I really would like to know.
>>
>> best
>> Oeyvind
>>
>>
>> 2009/9/29 dp51 :
>>>
>>> The -b flag will have no effect. ??csound~ communicates directly
>>> with Csound. ??Think of Max's DSP settings as replacing the need
>>> for -b and -B. ??Don't pay attention to the "audio buffered in 128
>>> sample-frame blocks" messages.
>>>
>>> However, there is buffering. ??Here's a short explanation:
>>>
>>> When csound~ receives vectors of audio from Max, it will try to
>>> fill up Csound's input buffers. ??The size of these input buffers =
>>> ksmps.
>>> When they're full, Csound processes one k-cycle and outputs ksmps
>>> sized vectors. ??csound~ will fill the Max output buffers with data from
>>> these output vectors. ?? For any given set of vectors received from
>>> Max, Csound may process zero or more k-cycles.
>>>
>>> So, the only way this buffering can induce latency is by making
>>> ksmps > Max signal vector size. ??An extreme example would be
>>> Max signal vector size = 1 and ksmps = 44100. ??If sr = 44100, then
>>> the latency would be 1 second.
>>>
>>> Remember, to prevent latency between Max and csound~, make sure
>>> ksmps <= Max signal vector size. ??I hope this clears up any confusion.
>>>
>>> Davis
>>>
>>> --
>>> View this message in context:
>>> http://www.nabble.com/csound%7E-question-tp25643571p25654833.html
>>> Sent from the Csound - General mailing list archive at Nabble.com.
>>>
>>>
>>>
>>> Send bugs reports to this list.
>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
>>> csound"
>>>
>>
>>
>> Send bugs reports to this list.
>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
>> csound"
>>
>
>
>
> Patrick Pagano,M.F.A
> Digital Media Engineer
> Digital Worlds Institute
> GAINESVILLE  FL  US  32611-5900
> University Of Florida
> (352) 294-2081
>
>
>
> Send bugs reports to this list.
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
> csound"
>