+1 Thanks for sharing, very much enjoyed it!

Some thoughts:

1. It was neat watching this from the perspective of what code got
evaluated rather than seeing it in the context of text editor.  It's
also great to look through the CSD and see the evolution of the
performance. Are you using some intermediary recording system that
records your changes before sending out the change to Csound?

2. Interesting use of chnset/chnget to create an identity for saving
state for the iterArr UDO.  I have been trying to figure out how to
implement the same idea and will probably add something similar to
livecode.orc today based on your work.  (I've been using numeric
identifiers for the fade system I have been using in my livecode.orc,
which uses a similar idea.)

3. One thing I'd note is I've found using p3 handy for duration of the
current impulse.  In my case, my main instr P1 acts as a callback
rather than using temporal recursion, but I think it could work in the
same way here. I usually pass p3 as the duration of the current beat,
which lets me write "p3" when I write schedule() calls use p3 * x to
get multiples of the beat pretty quickly.  Anyways, don't know if
you'd consider this before or not but I thought it worth mentioning.

Thanks again!
steven

On Mon, Nov 20, 2017 at 9:55 AM, jpff <jpff@codemist.co.uk> wrote:
> Nice -- I enjoyed that
>
>
> On Mon, 20 Nov 2017, thorin kerr wrote:
>
>> Hi all,
>> Here's some music I'd like to share.
>>
>> This came about through a live-coded improv session. I then... well...
>> cheated ...  by editing it a bit later. But not much... honest:) It still
>> sounds... well... 'improvised'.
>>
>> It'll probably render realtime for most of you. If not, well... change the
>> output to a file. Best of all, if you watch the console messages you can
>> see
>> all my coding mistakes which is just as - if not more - entertaining.
>>
>> Anyway... Here 'tis.
>>
>>
>> Thorin
>>
>
> Csound mailing list
> Csound@listserv.heanet.ie
> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
> Send bugs reports to
>        https://github.com/csound/csound/issues
> Discussions of bugs and features can be posted here

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

Link to Diving I... hmm.... I had an old Google Sites page - looks a bit broken now,

You could try these links:

https://sites.google.com/site/thorinkerr/zenith/works/Diving_I.mp3

If you're brave enough to try and render for yourself, you could get

https://sites.google.com/site/thorinkerr/zenith/works/Diving_I.csd

 - and it uses a sample.

https://sites.google.com/site/thorinkerr/zenith/works/marmstk44100.wav

Back in the day it took many hours to render.

Unfortunately, it doesn't render for me at all anymore, but that might just be a Csound For Android issue.

Thorin

On 21 Nov 2017 3:16 AM, "Rory Walsh" <rorywalsh@ear.ie> wrote:

Very nice. Now I'm curious about Diving 1. Is there a link anywhere?

On 20 November 2017 at 15:20, Steven Yi <stevenyi@gmail.com> wrote:

+1 Thanks for sharing, very much enjoyed it!

Some thoughts:

1. It was neat watching this from the perspective of what code got
evaluated rather than seeing it in the context of text editor.  It's
also great to look through the CSD and see the evolution of the
performance. Are you using some intermediary recording system that
records your changes before sending out the change to Csound?

2. Interesting use of chnset/chnget to create an identity for saving
state for the iterArr UDO.  I have been trying to figure out how to
implement the same idea and will probably add something similar to
livecode.orc today based on your work.  (I've been using numeric
identifiers for the fade system I have been using in my livecode.orc,
which uses a similar idea.)

3. One thing I'd note is I've found using p3 handy for duration of the
current impulse.  In my case, my main instr P1 acts as a callback
rather than using temporal recursion, but I think it could work in the
same way here. I usually pass p3 as the duration of the current beat,
which lets me write "p3" when I write schedule() calls use p3 * x to
get multiples of the beat pretty quickly.  Anyways, don't know if
you'd consider this before or not but I thought it worth mentioning.

Thanks again!
steven

On Mon, Nov 20, 2017 at 9:55 AM, jpff <jpff@codemist.co.uk> wrote:
> Nice -- I enjoyed that
>
>
> On Mon, 20 Nov 2017, thorin kerr wrote:
>
>> Hi all,
>> Here's some music I'd like to share.
>>
>> This came about through a live-coded improv session. I then... well...
>> cheated ...  by editing it a bit later. But not much... honest:) It still
>> sounds... well... 'improvised'.
>>
>> It'll probably render realtime for most of you. If not, well... change the
>> output to a file. Best of all, if you watch the console messages you can
>> see
>> all my coding mistakes which is just as - if not more - entertaining.
>>
>> Anyway... Here 'tis.
>>
>>
>> Thorin
>>
>
> Csound mailing list
> Csound@listserv.heanet.ie
> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
> Send bugs reports to
>        https://github.com/csound/csound/issues
> Discussions of bugs and features can be posted here

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here