Csound Csound-dev Csound-tekno Search About

R: Re: [Csnd] Csound 6 - Live Coding Demo

Date2013-03-15 13:29
From"vallste@libero.it"
SubjectR: Re: [Csnd] Csound 6 - Live Coding Demo

Wow! It'amazing, thank you

<CsoundSynthesizer>
<CsOptions>
-o dac
</CsOptions>
<CsInstruments>
sr = 44100
ksmps = 32
0dbfs = 1
nchnls = 1
instr 1
aout vco2 0.7, 440
event_i "i", p1, p3 * 2, p3
outs aout, aout
endin
</CsInstruments>
<CsScore>
f 0 3600
i 1 0 1
</CsScore>
</CsoundSynthesizer>

 

----Messaggio originale----
Da: thorin.kerr@gmail.com
Data: 15/03/2013 14.14
A: <csound@lists.bath.ac.uk>
Ogg: Re: [Csnd] Csound 6 - Live Coding Demo

For what it's worth: A trick often used in some livecoding environments (Impromptu, Fluxus, Extempore) is 'temporal recursion', which is just a function which schedules a call to itself. In Csound it might be something like:
------------------
instr 1

aout vco2 0.7, 440

event_i "i", p1, 0.5, p3

outs aout, aout
endin
-------------------------

just a recursive beep, but then then of course you get to edit it into something much more exciting. 

It'd be nice to do this in emacs... hmm

Thorin





On Fri, Mar 15, 2013 at 8:03 PM, Steven Yi <stevenyi@gmail.com> wrote:
Hi Thorin,

I think it's implemented such that when a new instrument replaces an
old one, existing instances continue using the old instrument
definition.  New notes will use the new definition.  I remember
discussing with Victor and John what to do in this situation, and I
think the current implementation has a dead pool where replaced
instruments go.  That way existing notes can keep processing and do
release segments, and the old definition finally gets removed when all
existing notes are complete.

I'm not sure what happens if notes are currently held when the switch
happens, if they get signaled to turnoff and do release processing.
Perhaps Victor could clarify.

I'll put up a video of a more interesting live coding example in just
a bit that might show a little more of what's possible.

Thanks!
steven

On Fri, Mar 15, 2013 at 4:59 AM, thorin kerr <thorin.kerr@gmail.com> wrote:
> This looks very promising. I have a quick question Steven. Do you need to
> create a new 'i' score event to realise the changes? Or... can you have an
> 'always on' instrument which can be modified 'on the fly'?
>
> Thorin
>
>
>
>
>
> On Fri, Mar 15, 2013 at 10:14 AM, Steven Yi <stevenyi@gmail.com> wrote:
>>
>> Hi All,
>>
>> I was doing some testing tonight and thought I'd post a video of some
>> live coding with Csound 6:
>>
>> http://www.youtube.com/watch?v=xQAesz-ViKk
>>
>> To note, I put together the editor and got the Csound code done pretty
>> quickly (all tonight).  Also, while the demo is showing live coding, I
>> think it's important to note that the capabilities added to the Csound
>> API for CS6 are going to be useful for API users in general for
>> building dynamic Csound applications.
>>
>> Enjoy! :)
>>
>> steven
>>
>>
>> Send bugs reports to the Sourceforge bug tracker
>>             https://sourceforge.net/tracker/?group_id=81968&atid=564599
>> Discussions of bugs and features can be posted here
>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
>> csound"
>>
>


Send bugs reports to the Sourceforge bug tracker
            https://sourceforge.net/tracker/?group_id=81968&atid=564599
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"