Csound Csound-dev Csound-tekno Search About

[Csnd] Signals practice

Date2019-02-18 20:00
FromSteven Yi
Subject[Csnd] Signals practice
Attachments2019-02-18_signals.orc  
Hi All,

I had a nice live code practice and I thought I'd share the end state here. The session used always-on instruments in a modular synth fashion.  The .orc code uses code from csound-live-code[1], particularly livecode.orc[2]. You can copy/paste the code into live.csound.com, select all, and hit ctrl-enter to evaluate it. 

Cheers!
Steven



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

Date2019-02-18 20:11
FromTarmo Johannes
SubjectRe: [Csnd] Signals practice
Works very nicely!

I must admit I have not tried https://live.csound.com/ much before, but it is 
really smooth and cool tool, thank you!

tarmo

On Monday, February 18, 2019 10:00:42 PM EET you wrote:
> Hi All,
> 
> I had a nice live code practice and I thought I'd share the end state here.
> The session used always-on instruments in a modular synth fashion.  The
> .orc code uses code from csound-live-code[1], particularly livecode.orc[2].
> You can copy/paste the code into live.csound.com, select all, and hit
> ctrl-enter to evaluate it.
> 
> Cheers!
> Steven
> 
> [1] - https://github.com/kunstmusik/csound-live-code/
> [2] -
> https://github.com/kunstmusik/csound-live-code/blob/master/livecode.orc
> 
> 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

Date2019-02-18 20:16
FromTarmo Johannes
SubjectRe: [Csnd] Signals practice
And one question from the code, I am really curious about, the syntax:

kpch = oscil(0.03, array(550, 660, 770, 880))

(originally commented out)

here the second parameter is array. I can truly hear the pitch changing but 
how does it work? What controls when the change happen? Never seen such 
possibility before...

tarmo


On Monday, February 18, 2019 10:00:42 PM EET you wrote:
> Hi All,
> 
> I had a nice live code practice and I thought I'd share the end state here.
> The session used always-on instruments in a modular synth fashion.  The
> .orc code uses code from csound-live-code[1], particularly livecode.orc[2].
> You can copy/paste the code into live.csound.com, select all, and hit
> ctrl-enter to evaluate it.
> 
> Cheers!
> Steven
> 
> [1] - https://github.com/kunstmusik/csound-live-code/
> [2] -
> https://github.com/kunstmusik/csound-live-code/blob/master/livecode.orc
> 
> 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

Date2019-02-18 23:36
FromSteven Yi
SubjectRe: [Csnd] Signals practice
Hi Tarmo,

Thanks!  Yes, it's a custom oscil UDO in the livecode.orc file[1]. It's used in the Sig2 instrument, but was commented out in Sig3 (in the live code session, I wrote the mixer, then Sig1, then copied/pasted Sig1 to Sig2, then to Sig3, as I developed).  The changing pitch should probably be coming from the Sig2 instrument. 

The oscillator is non-interpolating and reads through the table at k-rate at the given frequency. I've been using a similar oscillator at event-rate (see xosc in that file) for doing pitch lines with events.  Audio-rate oscil with a small array or ftable works well too:

instr Sig
  ifreq = 12
  apch = oscil(1, ifreq, ftgentmp(0,0, 4,-2, 1,2,4,8)) * 440
  apch *= oscili(1, 0.05, ftgentmp(0, 0, 513, -5, 1, 512, 4))
  asig = oscil3(0.2, apch)
  
  out(asig, asig)
  
endin
start("Sig")

(Though, I'd prefer to use array over ftgens, but I think oscil works with i[] and not k[], and I'm not sure there's an easy way to fill an i[]).  

The frequency value determines how fast the wavetable/array is read. 

Hope that clarifies that!
steven


On Mon, Feb 18, 2019 at 3:16 PM Tarmo Johannes <trmjhnns@gmail.com> wrote:
And one question from the code, I am really curious about, the syntax:

kpch = oscil(0.03, array(550, 660, 770, 880))

(originally commented out)

here the second parameter is array. I can truly hear the pitch changing but
how does it work? What controls when the change happen? Never seen such
possibility before...

tarmo


On Monday, February 18, 2019 10:00:42 PM EET you wrote:
> Hi All,
>
> I had a nice live code practice and I thought I'd share the end state here.
> The session used always-on instruments in a modular synth fashion.  The
> .orc code uses code from csound-live-code[1], particularly livecode.orc[2].
> You can copy/paste the code into live.csound.com, select all, and hit
> ctrl-enter to evaluate it.
>
> Cheers!
> Steven
>
> [1] - https://github.com/kunstmusik/csound-live-code/
> [2] -
> https://github.com/kunstmusik/csound-live-code/blob/master/livecode.orc
>
> 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

Date2019-02-19 12:35
From"Dr. Richard Boulanger"
SubjectRe: [Csnd] Signals practice
Thanks Steven,

All your examples and models are extremely helpful.  

-dB
_____________________________________________
Dr. Richard Boulanger
Professor of Electronic Production and Design
Professional Writing and Music Technology Division
Berklee College of Music
______________________________________________
OFFICE: 1126 Boylston St., Suite 201 (EPD), Suite 208 (Boulanger)
______________________________________________


On Mon, Feb 18, 2019 at 3:01 PM Steven Yi <stevenyi@gmail.com> wrote:
Hi All,

I had a nice live code practice and I thought I'd share the end state here. The session used always-on instruments in a modular synth fashion.  The .orc code uses code from csound-live-code[1], particularly livecode.orc[2]. You can copy/paste the code into live.csound.com, select all, and hit ctrl-enter to evaluate it. 

Cheers!
Steven



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

Date2019-02-20 21:30
Fromjoachim heintz
SubjectRe: [Csnd] Signals practice
hi steven -

wow!  it is so inspiring to read your code!  all this livecode.orc is 
such a wonderful example how readable code can be created.

thanks for sharing and keep us posted -

	joachim



On 18/02/19 21:00, Steven Yi wrote:
> Hi All,
>
> I had a nice live code practice and I thought I'd share the end state
> here. The session used always-on instruments in a modular synth
> fashion.  The .orc code uses code from csound-live-code[1], particularly
> livecode.orc[2]. You can copy/paste the code into live.csound.com
> , select all, and hit ctrl-enter to evaluate it.
>
> Cheers!
> Steven
>
> [1] - https://github.com/kunstmusik/csound-live-code/
> [2]
> - https://github.com/kunstmusik/csound-live-code/blob/master/livecode.orc
>
>
> 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

Date2019-02-21 21:22
From"Dr. Richard Boulanger"
SubjectRe: [Csnd] Signals practice
I agree!  Super clear.  Super inspiring.
_____________________________________________
Dr. Richard Boulanger
Professor of Electronic Production and Design
Professional Writing and Music Technology Division
Berklee College of Music
______________________________________________
OFFICE: 1126 Boylston St., Suite 201 (EPD), Suite 208 (Boulanger)
______________________________________________


On Wed, Feb 20, 2019 at 4:31 PM joachim heintz <jh@joachimheintz.de> wrote:
hi steven -

wow!  it is so inspiring to read your code!  all this livecode.orc is
such a wonderful example how readable code can be created.

thanks for sharing and keep us posted -

        joachim



On 18/02/19 21:00, Steven Yi wrote:
> Hi All,
>
> I had a nice live code practice and I thought I'd share the end state
> here. The session used always-on instruments in a modular synth
> fashion.  The .orc code uses code from csound-live-code[1], particularly
> livecode.orc[2]. You can copy/paste the code into live.csound.com
> <http://live.csound.com>, select all, and hit ctrl-enter to evaluate it.
>
> Cheers!
> Steven
>
> [1] - https://github.com/kunstmusik/csound-live-code/
> [2]
> - https://github.com/kunstmusik/csound-live-code/blob/master/livecode.orc
>
>
> Csound mailing list Csound@listserv.heanet.ie
> <mailto: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

Date2019-02-22 12:10
FromSteven Yi
SubjectRe: [Csnd] Signals practice
Thanks Dr. B and Joachim! 

BTW: In that project, there is doc/csdoc.py[1], a script to generate cheatsheet[2] and reference[3] page information in Markdown.  It's got a bug at the moment for UDOs with multiple output values, but I figure it might be useful for others to use for their own documentation generation. 



On Thu, Feb 21, 2019 at 4:22 PM Dr. Richard Boulanger <rboulanger@berklee.edu> wrote:
I agree!  Super clear.  Super inspiring.
_____________________________________________
Dr. Richard Boulanger
Professor of Electronic Production and Design
Professional Writing and Music Technology Division
Berklee College of Music
______________________________________________
OFFICE: 1126 Boylston St., Suite 201 (EPD), Suite 208 (Boulanger)
______________________________________________


On Wed, Feb 20, 2019 at 4:31 PM joachim heintz <jh@joachimheintz.de> wrote:
hi steven -

wow!  it is so inspiring to read your code!  all this livecode.orc is
such a wonderful example how readable code can be created.

thanks for sharing and keep us posted -

        joachim



On 18/02/19 21:00, Steven Yi wrote:
> Hi All,
>
> I had a nice live code practice and I thought I'd share the end state
> here. The session used always-on instruments in a modular synth
> fashion.  The .orc code uses code from csound-live-code[1], particularly
> livecode.orc[2]. You can copy/paste the code into live.csound.com
> <http://live.csound.com>, select all, and hit ctrl-enter to evaluate it.
>
> Cheers!
> Steven
>
> [1] - https://github.com/kunstmusik/csound-live-code/
> [2]
> - https://github.com/kunstmusik/csound-live-code/blob/master/livecode.orc
>
>
> Csound mailing list Csound@listserv.heanet.ie
> <mailto: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

Date2019-02-22 13:05
From"Dr. Richard Boulanger"
SubjectRe: [Csnd] Signals practice
Thanks Steven,  

I will follow those links and get the "cheat sheet" and "reference" right away.  
(I did already PDF much of your code and documentation and tutorials!)

What do you think about the idea of proposing to play a live.csound duet/trio/quartet/jam to play at the 2019 ICSC?
- how might we synchronze the clocks/tempi on a number of laptops runing live.csound for this purpose?

Maybe you and I (and others) get together and rehearse as we get closer to September?
- or we share some UDOs, Scripts, etc.

A thought.

-dB

-dB
_____________________________________________
Dr. Richard Boulanger
Professor of Electronic Production and Design
Professional Writing and Music Technology Division
Berklee College of Music
______________________________________________
OFFICE: 1126 Boylston St., Suite 201 (EPD), Suite 208 (Boulanger)
______________________________________________


On Fri, Feb 22, 2019 at 7:10 AM Steven Yi <stevenyi@gmail.com> wrote:
Thanks Dr. B and Joachim! 

BTW: In that project, there is doc/csdoc.py[1], a script to generate cheatsheet[2] and reference[3] page information in Markdown.  It's got a bug at the moment for UDOs with multiple output values, but I figure it might be useful for others to use for their own documentation generation. 



On Thu, Feb 21, 2019 at 4:22 PM Dr. Richard Boulanger <rboulanger@berklee.edu> wrote:
I agree!  Super clear.  Super inspiring.
_____________________________________________
Dr. Richard Boulanger
Professor of Electronic Production and Design
Professional Writing and Music Technology Division
Berklee College of Music
______________________________________________
OFFICE: 1126 Boylston St., Suite 201 (EPD), Suite 208 (Boulanger)
______________________________________________


On Wed, Feb 20, 2019 at 4:31 PM joachim heintz <jh@joachimheintz.de> wrote:
hi steven -

wow!  it is so inspiring to read your code!  all this livecode.orc is
such a wonderful example how readable code can be created.

thanks for sharing and keep us posted -

        joachim



On 18/02/19 21:00, Steven Yi wrote:
> Hi All,
>
> I had a nice live code practice and I thought I'd share the end state
> here. The session used always-on instruments in a modular synth
> fashion.  The .orc code uses code from csound-live-code[1], particularly
> livecode.orc[2]. You can copy/paste the code into live.csound.com
> <http://live.csound.com>, select all, and hit ctrl-enter to evaluate it.
>
> Cheers!
> Steven
>
> [1] - https://github.com/kunstmusik/csound-live-code/
> [2]
> - https://github.com/kunstmusik/csound-live-code/blob/master/livecode.orc
>
>
> Csound mailing list Csound@listserv.heanet.ie
> <mailto: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
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

Date2019-03-05 18:02
FromSteven Yi
SubjectRe: [Csnd] Signals practice
Hi Dr. B,

All sounds great!  Synced clocks has been on my mind but little time to investigate. Hoping to get caught up with various projects this spring/summer.  I'd love to get together and collaborate for a live performance at ICSC. (I'll email you offlist later today to get things going.)

Thanks and all best!
Steven



On Fri, Feb 22, 2019 at 8:06 AM Dr. Richard Boulanger <rboulanger@berklee.edu> wrote:
Thanks Steven,  

I will follow those links and get the "cheat sheet" and "reference" right away.  
(I did already PDF much of your code and documentation and tutorials!)

What do you think about the idea of proposing to play a live.csound duet/trio/quartet/jam to play at the 2019 ICSC?
- how might we synchronze the clocks/tempi on a number of laptops runing live.csound for this purpose?

Maybe you and I (and others) get together and rehearse as we get closer to September?
- or we share some UDOs, Scripts, etc.

A thought.

-dB

-dB
_____________________________________________
Dr. Richard Boulanger
Professor of Electronic Production and Design
Professional Writing and Music Technology Division
Berklee College of Music
______________________________________________
OFFICE: 1126 Boylston St., Suite 201 (EPD), Suite 208 (Boulanger)
______________________________________________


On Fri, Feb 22, 2019 at 7:10 AM Steven Yi <stevenyi@gmail.com> wrote:
Thanks Dr. B and Joachim! 

BTW: In that project, there is doc/csdoc.py[1], a script to generate cheatsheet[2] and reference[3] page information in Markdown.  It's got a bug at the moment for UDOs with multiple output values, but I figure it might be useful for others to use for their own documentation generation. 



On Thu, Feb 21, 2019 at 4:22 PM Dr. Richard Boulanger <rboulanger@berklee.edu> wrote:
I agree!  Super clear.  Super inspiring.
_____________________________________________
Dr. Richard Boulanger
Professor of Electronic Production and Design
Professional Writing and Music Technology Division
Berklee College of Music
______________________________________________
OFFICE: 1126 Boylston St., Suite 201 (EPD), Suite 208 (Boulanger)
______________________________________________


On Wed, Feb 20, 2019 at 4:31 PM joachim heintz <jh@joachimheintz.de> wrote:
hi steven -

wow!  it is so inspiring to read your code!  all this livecode.orc is
such a wonderful example how readable code can be created.

thanks for sharing and keep us posted -

        joachim



On 18/02/19 21:00, Steven Yi wrote:
> Hi All,
>
> I had a nice live code practice and I thought I'd share the end state
> here. The session used always-on instruments in a modular synth
> fashion.  The .orc code uses code from csound-live-code[1], particularly
> livecode.orc[2]. You can copy/paste the code into live.csound.com
> <http://live.csound.com>, select all, and hit ctrl-enter to evaluate it.
>
> Cheers!
> Steven
>
> [1] - https://github.com/kunstmusik/csound-live-code/
> [2]
> - https://github.com/kunstmusik/csound-live-code/blob/master/livecode.orc
>
>
> Csound mailing list Csound@listserv.heanet.ie
> <mailto: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
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

Date2019-03-08 00:43
From"Dr. Richard Boulanger"
SubjectRe: [Csnd] Signals practice
Steven,

YES.  For sure let's collaborate on a Live.Csound duet!
- that would be fantastic.
- world premiere at the ICSC

Looking forward.

Best,

-dB
_____________________________________________
Dr. Richard Boulanger
Professor of Electronic Production and Design
Professional Writing and Music Technology Division
Berklee College of Music
______________________________________________
OFFICE: 1126 Boylston St., Suite 201 (EPD), Suite 208 (Boulanger)
______________________________________________


On Tue, Mar 5, 2019 at 1:02 PM Steven Yi <stevenyi@gmail.com> wrote:
Hi Dr. B,

All sounds great!  Synced clocks has been on my mind but little time to investigate. Hoping to get caught up with various projects this spring/summer.  I'd love to get together and collaborate for a live performance at ICSC. (I'll email you offlist later today to get things going.)

Thanks and all best!
Steven



On Fri, Feb 22, 2019 at 8:06 AM Dr. Richard Boulanger <rboulanger@berklee.edu> wrote:
Thanks Steven,  

I will follow those links and get the "cheat sheet" and "reference" right away.  
(I did already PDF much of your code and documentation and tutorials!)

What do you think about the idea of proposing to play a live.csound duet/trio/quartet/jam to play at the 2019 ICSC?
- how might we synchronze the clocks/tempi on a number of laptops runing live.csound for this purpose?

Maybe you and I (and others) get together and rehearse as we get closer to September?
- or we share some UDOs, Scripts, etc.

A thought.

-dB

-dB
_____________________________________________
Dr. Richard Boulanger
Professor of Electronic Production and Design
Professional Writing and Music Technology Division
Berklee College of Music
______________________________________________
OFFICE: 1126 Boylston St., Suite 201 (EPD), Suite 208 (Boulanger)
______________________________________________


On Fri, Feb 22, 2019 at 7:10 AM Steven Yi <stevenyi@gmail.com> wrote:
Thanks Dr. B and Joachim! 

BTW: In that project, there is doc/csdoc.py[1], a script to generate cheatsheet[2] and reference[3] page information in Markdown.  It's got a bug at the moment for UDOs with multiple output values, but I figure it might be useful for others to use for their own documentation generation. 



On Thu, Feb 21, 2019 at 4:22 PM Dr. Richard Boulanger <rboulanger@berklee.edu> wrote:
I agree!  Super clear.  Super inspiring.
_____________________________________________
Dr. Richard Boulanger
Professor of Electronic Production and Design
Professional Writing and Music Technology Division
Berklee College of Music
______________________________________________
OFFICE: 1126 Boylston St., Suite 201 (EPD), Suite 208 (Boulanger)
______________________________________________


On Wed, Feb 20, 2019 at 4:31 PM joachim heintz <jh@joachimheintz.de> wrote:
hi steven -

wow!  it is so inspiring to read your code!  all this livecode.orc is
such a wonderful example how readable code can be created.

thanks for sharing and keep us posted -

        joachim



On 18/02/19 21:00, Steven Yi wrote:
> Hi All,
>
> I had a nice live code practice and I thought I'd share the end state
> here. The session used always-on instruments in a modular synth
> fashion.  The .orc code uses code from csound-live-code[1], particularly
> livecode.orc[2]. You can copy/paste the code into live.csound.com
> <http://live.csound.com>, select all, and hit ctrl-enter to evaluate it.
>
> Cheers!
> Steven
>
> [1] - https://github.com/kunstmusik/csound-live-code/
> [2]
> - https://github.com/kunstmusik/csound-live-code/blob/master/livecode.orc
>
>
> Csound mailing list Csound@listserv.heanet.ie
> <mailto: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
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