<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=windows-1250">
<META content="MSHTML 6.00.2900.3020" name=GENERATOR></HEAD>
<BODY>
<DIV dir=ltr align=left><SPAN class=526264222-15012007><FONT face=Arial
color=#0000ff size=2>Thank you, Kas, for the insights:</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=526264222-15012007> </SPAN></DIV>
<DIV dir=ltr align=left><SPAN
class=526264222-15012007>> </SPAN>Somewhere about a year ago or so there
was a fair amount of talk on the list about using arrays of floats to record
to,<SPAN class=526264222-15012007><FONT face=Arial color=#0000ff
size=2> </FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=526264222-15012007><FONT face=Arial
color=#0000ff size=2>></FONT> </SPAN>then chuck <FONT
face=Arial><FONT color=#0000ff><FONT size=2><SPAN
class=526264222-15012007> </SPAN><SPAN
class=526264222-15012007> </SPAN></FONT></FONT></FONT>values in them to
Impulse or Step once per sample. That might be a interesting place to start, you
could do some <SPAN class=526264222-15012007><FONT face=Arial color=#0000ff
size=2> </FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=526264222-15012007><FONT face=Arial
color=#0000ff size=2>></FONT> </SPAN>variations on Karplus-Strong using
that. You could also implement anything found in texts on DSP or your own
concoctions doing it <SPAN class=526264222-15012007><FONT face=Arial
color=#0000ff size=2> </FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=526264222-15012007><FONT face=Arial
color=#0000ff size=2>></FONT> </SPAN>this way but be prepared to spend a
lot of time optimising. Do use Gain in it's various modes for all
multiplications at sample-rate; <SPAN class=526264222-15012007><FONT
face=Arial color=#0000ff size=2> </FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=526264222-15012007><FONT face=Arial
color=#0000ff size=2>></FONT> </SPAN>this <SPAN
class=526264222-15012007><FONT face=Arial color=#0000ff
size=2> </FONT></SPAN>realy saves a lot of cpu time at the expense of some
readablity. <SPAN class=526264222-15012007><FONT face=Arial color=#0000ff
size=2> </FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=526264222-15012007></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=526264222-15012007><FONT face=Arial
color=#0000ff size=2>ok, I will search the archives. However, DSP code fragments
is exactely</FONT> <FONT face=Arial color=#0000ff size=2>what I thought to
do. Some 15 years ago I coded on DSP level, but since than lost track of
all those new chip types, developement kits etc... also, compiling and uploading
code to a chip (I had to burn EPROMS for every little change in those days)
is not as efficient as klicking on "Replace Shred" in the
Mini..--)))</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=526264222-15012007><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=526264222-15012007><FONT face=Arial
color=#0000ff size=2><U>Question:</U> would it be possible to give rough numbers
of processing "costs" for each operation of ChucK? (not right now, but in some
later revision of the manual). I remember in those very thick books about the
DSP assembler language they always gave some kind of DSP cycles per operation,
helping us to optimize code and maybe use 100 "dumb" instructions instead of 1
elegant, but enormousely DSP intensive...</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=526264222-15012007></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=526264222-15012007>>for moments when this
method sounds like real fun. </SPAN></DIV>
<DIV><SPAN class=526264222-15012007></SPAN> </DIV>
<DIV><SPAN class=526264222-15012007><FONT color=#0000ff>YES!</FONT></DIV>
<DIV dir=ltr align=left><BR> </SPAN><BR><BR><FONT size=2><BR></DIV></FONT>
<P><FONT face=Arial size=2></FONT></P></BODY></HTML>
<BR>
<P><FONT SIZE=2>--<BR>
No virus found in this outgoing message.<BR>
Checked by AVG Free Edition.<BR>
Version: 7.5.432 / Virus Database: 268.16.10/626 - Release Date: 14.01.2007 20:29<BR>
</FONT> </P>