Wow, I forgot about that project, thanks for mentioning it! :)  (It
actually may be very useful for a project I had in mind for
distributed sound generation...)

I was about to write that I tend to do live code with Csound these
days using UDP and csound's --port=10000 (or whatever port number you
want to use) flag.  Using that, you can send orchestra code to Csound
via the port.  The small Vim plugin I have:

https://github.com/kunstmusik/csound-repl

Shows how it uses python to send code to a running Csound via UDP.

Regarding OSCsound, it'd probably be useful to update it to take in
and /orc message with orchestra code. Since I need something like this
anyways, I'll look at updating that Python script this weekend.

On Fri, Feb 17, 2017 at 5:35 PM, Dave Seidel  wrote:
> Steven Yi wrote a nice Python program a few years ago that runs a CSD via
> the Csound API, and sets up a generic OSC server that allows the user to
> send score events, and to set channel values:
> https://github.com/kunstmusik/OSCsound
>
>
> On Fri, Feb 17, 2017 at 5:28 PM, Ed Costello  wrote:
>>
>> I don’t know about OSC but this can be achieved using web sockets so it
>> may be helpful to you, for instance, from a web page you can send an
>> instrument like in the following example, in this case sending a trigger
>> flag value and instrument string when a button is clicked in the web page:
>>
>>             var kvarSocket = new WebSocket("ws://127.0.0.1:8888", "kvar");
>>             var stringSocket = new WebSocket("ws://127.0.0.1:8888",
>> "Sstring");
>>
>>             var trigger = 1;
>>
>>             stringButton.onclick = function() {
>>
>>                 stringSocket.send("\"instr 3\n a1 oscils p4/2, p5 / 2, 0
>> \n out a1 \nendin\"");
>>                 kvarSocket.send(new Float64Array([trigger]));
>>                 trigger = !trigger;
>>             }
>>
>> On the Csound side you can receive like this:
>>
>> 
>> 
>> -odac
>> 
>> 
>> nchnls = 2
>> 0dbfs = 1
>> ksmps = 256
>> sr = 44100
>>
>> instr 1
>>
>> iport init 8888
>> kvarChanged init 0
>> ktrigger init 0
>>
>> kvar, Sstring websocket iport
>>
>> if kvarChanged != kvar then
>> kvarChanged = kvar
>> ktrigger = 1
>> Sscore sprintfk {{i 2 0 -1 %s}}, Sstring
>> endif
>>
>> scoreline Sscore, ktrigger
>> ktrigger = 0
>>
>> endin
>>
>> instr 2
>>
>> prints p4
>> Sstring = p4
>> ires compilestr Sstring
>> scoreline_i "i 3 0 3 .2 415"
>> turnoff
>> endin
>>
>> 
>> 
>> i1 0 100
>> 
>> 
>>
>> Maybe you can repurpose this example to use OSC instead,
>> Cheers,
>> Ed
>>
>> On 17 Feb 2017, at 14:04, free coder  wrote:
>>
>> Hi,
>>
>> I am experimenting with CSound live coding, running it in a terminal with
>> the option  "-L stdin".
>> It is cool, but s there a way to send live code via an OSC port and not
>> just type code in the terminal window ?
>> From what i understand now it is possible to live code from the terminal
>> window (it works !), but I would like to 'live code' from other environments
>> (processing, max, pd ...) sending OSC 'live code' messages.
>>
>> is this already possible ? how is it possible to listen to 'live coding'
>> on an OSC port ? (something live "-L oscport 9999" ?)
>>
>> (note that i am not talking about the existing OSC  possibilities  in a
>> .csd like initOSC etc ... as this is not live coding but parameter control
>> via OSC)
>>
>> many thanks if someone has any hints !
>>
>> 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
>
>
>
>
> --
> http://mysterybear.net
> https://soundcloud.com/mysterybear
> https://mysterybear.bandcamp.com
> 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

Neat!  I'll study the code more carefully but on first glance it looks
nice with the with() syntax support and other more modern Python
practices. Perhaps it might even be better to base things on Felipe's
ctcsound ctypes binding now too.  I'll follow up here once I get
somewhere with all of this. :)

On Fri, Feb 17, 2017 at 5:48 PM, Dave Seidel  wrote:
> Steven, you may want to take a look at my fork. :-) I've added very little
> so far, just been restructuring to make it easier to reuse some of the code.
> My changes may or may not be to your taste (or match you plans), bur may as
> well take a look: https://github.com/DaveSeidel/OSCsound/tree/ds-refactor
>
> On Fri, Feb 17, 2017 at 5:42 PM, Steven Yi  wrote:
>>
>> Wow, I forgot about that project, thanks for mentioning it! :)  (It
>> actually may be very useful for a project I had in mind for
>> distributed sound generation...)
>>
>> I was about to write that I tend to do live code with Csound these
>> days using UDP and csound's --port=10000 (or whatever port number you
>> want to use) flag.  Using that, you can send orchestra code to Csound
>> via the port.  The small Vim plugin I have:
>>
>> https://github.com/kunstmusik/csound-repl
>>
>> Shows how it uses python to send code to a running Csound via UDP.
>>
>> Regarding OSCsound, it'd probably be useful to update it to take in
>> and /orc message with orchestra code. Since I need something like this
>> anyways, I'll look at updating that Python script this weekend.
>>
>> On Fri, Feb 17, 2017 at 5:35 PM, Dave Seidel 
>> wrote:
>> > Steven Yi wrote a nice Python program a few years ago that runs a CSD
>> > via
>> > the Csound API, and sets up a generic OSC server that allows the user to
>> > send score events, and to set channel values:
>> > https://github.com/kunstmusik/OSCsound
>> >
>> >
>> > On Fri, Feb 17, 2017 at 5:28 PM, Ed Costello 
>> > wrote:
>> >>
>> >> I don’t know about OSC but this can be achieved using web sockets so it
>> >> may be helpful to you, for instance, from a web page you can send an
>> >> instrument like in the following example, in this case sending a
>> >> trigger
>> >> flag value and instrument string when a button is clicked in the web
>> >> page:
>> >>
>> >>             var kvarSocket = new WebSocket("ws://127.0.0.1:8888",
>> >> "kvar");
>> >>             var stringSocket = new WebSocket("ws://127.0.0.1:8888",
>> >> "Sstring");
>> >>
>> >>             var trigger = 1;
>> >>
>> >>             stringButton.onclick = function() {
>> >>
>> >>                 stringSocket.send("\"instr 3\n a1 oscils p4/2, p5 / 2,
>> >> 0
>> >> \n out a1 \nendin\"");
>> >>                 kvarSocket.send(new Float64Array([trigger]));
>> >>                 trigger = !trigger;
>> >>             }
>> >>
>> >> On the Csound side you can receive like this:
>> >>
>> >> 
>> >> 
>> >> -odac
>> >> 
>> >> 
>> >> nchnls = 2
>> >> 0dbfs = 1
>> >> ksmps = 256
>> >> sr = 44100
>> >>
>> >> instr 1
>> >>
>> >> iport init 8888
>> >> kvarChanged init 0
>> >> ktrigger init 0
>> >>
>> >> kvar, Sstring websocket iport
>> >>
>> >> if kvarChanged != kvar then
>> >> kvarChanged = kvar
>> >> ktrigger = 1
>> >> Sscore sprintfk {{i 2 0 -1 %s}}, Sstring
>> >> endif
>> >>
>> >> scoreline Sscore, ktrigger
>> >> ktrigger = 0
>> >>
>> >> endin
>> >>
>> >> instr 2
>> >>
>> >> prints p4
>> >> Sstring = p4
>> >> ires compilestr Sstring
>> >> scoreline_i "i 3 0 3 .2 415"
>> >> turnoff
>> >> endin
>> >>
>> >> 
>> >> 
>> >> i1 0 100
>> >> 
>> >> 
>> >>
>> >> Maybe you can repurpose this example to use OSC instead,
>> >> Cheers,
>> >> Ed
>> >>
>> >> On 17 Feb 2017, at 14:04, free coder  wrote:
>> >>
>> >> Hi,
>> >>
>> >> I am experimenting with CSound live coding, running it in a terminal
>> >> with
>> >> the option  "-L stdin".
>> >> It is cool, but s there a way to send live code via an OSC port and not
>> >> just type code in the terminal window ?
>> >> From what i understand now it is possible to live code from the
>> >> terminal
>> >> window (it works !), but I would like to 'live code' from other
>> >> environments
>> >> (processing, max, pd ...) sending OSC 'live code' messages.
>> >>
>> >> is this already possible ? how is it possible to listen to 'live
>> >> coding'
>> >> on an OSC port ? (something live "-L oscport 9999" ?)
>> >>
>> >> (note that i am not talking about the existing OSC  possibilities  in a
>> >> .csd like initOSC etc ... as this is not live coding but parameter
>> >> control
>> >> via OSC)
>> >>
>> >> many thanks if someone has any hints !
>> >>
>> >> 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
>> >
>> >
>> >
>> >
>> > --
>> > http://mysterybear.net
>> > https://soundcloud.com/mysterybear
>> > https://mysterybear.bandcamp.com
>> > 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
>
>
>
>
> --
> http://mysterybear.net
> https://soundcloud.com/mysterybear
> https://mysterybear.bandcamp.com
> 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

Francois Pinot's ctcsound...

and Python3 and numpy. Great combination.

Victor Lazzarini
Dean of Arts, Celtic Studies, and Philosophy
Maynooth University
Ireland

> On 17 Feb 2017, at 23:01, Steven Yi  wrote:
> 
> Neat!  I'll study the code more carefully but on first glance it looks
> nice with the with() syntax support and other more modern Python
> practices. Perhaps it might even be better to base things on Felipe's
> ctcsound ctypes binding now too.  I'll follow up here once I get
> somewhere with all of this. :)
> 
>> On Fri, Feb 17, 2017 at 5:48 PM, Dave Seidel  wrote:
>> Steven, you may want to take a look at my fork. :-) I've added very little
>> so far, just been restructuring to make it easier to reuse some of the code.
>> My changes may or may not be to your taste (or match you plans), bur may as
>> well take a look: https://github.com/DaveSeidel/OSCsound/tree/ds-refactor
>> 
>>> On Fri, Feb 17, 2017 at 5:42 PM, Steven Yi  wrote:
>>> 
>>> Wow, I forgot about that project, thanks for mentioning it! :)  (It
>>> actually may be very useful for a project I had in mind for
>>> distributed sound generation...)
>>> 
>>> I was about to write that I tend to do live code with Csound these
>>> days using UDP and csound's --port=10000 (or whatever port number you
>>> want to use) flag.  Using that, you can send orchestra code to Csound
>>> via the port.  The small Vim plugin I have:
>>> 
>>> https://github.com/kunstmusik/csound-repl
>>> 
>>> Shows how it uses python to send code to a running Csound via UDP.
>>> 
>>> Regarding OSCsound, it'd probably be useful to update it to take in
>>> and /orc message with orchestra code. Since I need something like this
>>> anyways, I'll look at updating that Python script this weekend.
>>> 
>>> On Fri, Feb 17, 2017 at 5:35 PM, Dave Seidel 
>>> wrote:
>>>> Steven Yi wrote a nice Python program a few years ago that runs a CSD
>>>> via
>>>> the Csound API, and sets up a generic OSC server that allows the user to
>>>> send score events, and to set channel values:
>>>> https://github.com/kunstmusik/OSCsound
>>>> 
>>>> 
>>>> On Fri, Feb 17, 2017 at 5:28 PM, Ed Costello 
>>>> wrote:
>>>>> 
>>>>> I don’t know about OSC but this can be achieved using web sockets so it
>>>>> may be helpful to you, for instance, from a web page you can send an
>>>>> instrument like in the following example, in this case sending a
>>>>> trigger
>>>>> flag value and instrument string when a button is clicked in the web
>>>>> page:
>>>>> 
>>>>>            var kvarSocket = new WebSocket("ws://127.0.0.1:8888",
>>>>> "kvar");
>>>>>            var stringSocket = new WebSocket("ws://127.0.0.1:8888",
>>>>> "Sstring");
>>>>> 
>>>>>            var trigger = 1;
>>>>> 
>>>>>            stringButton.onclick = function() {
>>>>> 
>>>>>                stringSocket.send("\"instr 3\n a1 oscils p4/2, p5 / 2,
>>>>> 0
>>>>> \n out a1 \nendin\"");
>>>>>                kvarSocket.send(new Float64Array([trigger]));
>>>>>                trigger = !trigger;
>>>>>            }
>>>>> 
>>>>> On the Csound side you can receive like this:
>>>>> 
>>>>> 
>>>>> 
>>>>> -odac
>>>>> 
>>>>> 
>>>>> nchnls = 2
>>>>> 0dbfs = 1
>>>>> ksmps = 256
>>>>> sr = 44100
>>>>> 
>>>>> instr 1
>>>>> 
>>>>> iport init 8888
>>>>> kvarChanged init 0
>>>>> ktrigger init 0
>>>>> 
>>>>> kvar, Sstring websocket iport
>>>>> 
>>>>> if kvarChanged != kvar then
>>>>> kvarChanged = kvar
>>>>> ktrigger = 1
>>>>> Sscore sprintfk {{i 2 0 -1 %s}}, Sstring
>>>>> endif
>>>>> 
>>>>> scoreline Sscore, ktrigger
>>>>> ktrigger = 0
>>>>> 
>>>>> endin
>>>>> 
>>>>> instr 2
>>>>> 
>>>>> prints p4
>>>>> Sstring = p4
>>>>> ires compilestr Sstring
>>>>> scoreline_i "i 3 0 3 .2 415"
>>>>> turnoff
>>>>> endin
>>>>> 
>>>>> 
>>>>> 
>>>>> i1 0 100
>>>>> 
>>>>> 
>>>>> 
>>>>> Maybe you can repurpose this example to use OSC instead,
>>>>> Cheers,
>>>>> Ed
>>>>> 
>>>>> On 17 Feb 2017, at 14:04, free coder  wrote:
>>>>> 
>>>>> Hi,
>>>>> 
>>>>> I am experimenting with CSound live coding, running it in a terminal
>>>>> with
>>>>> the option  "-L stdin".
>>>>> It is cool, but s there a way to send live code via an OSC port and not
>>>>> just type code in the terminal window ?
>>>>> From what i understand now it is possible to live code from the
>>>>> terminal
>>>>> window (it works !), but I would like to 'live code' from other
>>>>> environments
>>>>> (processing, max, pd ...) sending OSC 'live code' messages.
>>>>> 
>>>>> is this already possible ? how is it possible to listen to 'live
>>>>> coding'
>>>>> on an OSC port ? (something live "-L oscport 9999" ?)
>>>>> 
>>>>> (note that i am not talking about the existing OSC  possibilities  in a
>>>>> .csd like initOSC etc ... as this is not live coding but parameter
>>>>> control
>>>>> via OSC)
>>>>> 
>>>>> many thanks if someone has any hints !
>>>>> 
>>>>> 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
>>>> 
>>>> 
>>>> 
>>>> 
>>>> --
>>>> http://mysterybear.net
>>>> https://soundcloud.com/mysterybear
>>>> https://mysterybear.bandcamp.com
>>>> 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
>> 
>> 
>> 
>> 
>> --
>> http://mysterybear.net
>> https://soundcloud.com/mysterybear
>> https://mysterybear.bandcamp.com
>> 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

Ah oops!  Apologies, I meant Francois, not Felipe (who I both thank
for their many contributions to the community! ;) ).

On Fri, Feb 17, 2017 at 6:05 PM, Victor Lazzarini
 wrote:
> Francois Pinot's ctcsound...
>
> and Python3 and numpy. Great combination.
>
> Victor Lazzarini
> Dean of Arts, Celtic Studies, and Philosophy
> Maynooth University
> Ireland
>
>> On 17 Feb 2017, at 23:01, Steven Yi  wrote:
>>
>> Neat!  I'll study the code more carefully but on first glance it looks
>> nice with the with() syntax support and other more modern Python
>> practices. Perhaps it might even be better to base things on Felipe's
>> ctcsound ctypes binding now too.  I'll follow up here once I get
>> somewhere with all of this. :)
>>
>>> On Fri, Feb 17, 2017 at 5:48 PM, Dave Seidel  wrote:
>>> Steven, you may want to take a look at my fork. :-) I've added very little
>>> so far, just been restructuring to make it easier to reuse some of the code.
>>> My changes may or may not be to your taste (or match you plans), bur may as
>>> well take a look: https://github.com/DaveSeidel/OSCsound/tree/ds-refactor
>>>
>>>> On Fri, Feb 17, 2017 at 5:42 PM, Steven Yi  wrote:
>>>>
>>>> Wow, I forgot about that project, thanks for mentioning it! :)  (It
>>>> actually may be very useful for a project I had in mind for
>>>> distributed sound generation...)
>>>>
>>>> I was about to write that I tend to do live code with Csound these
>>>> days using UDP and csound's --port=10000 (or whatever port number you
>>>> want to use) flag.  Using that, you can send orchestra code to Csound
>>>> via the port.  The small Vim plugin I have:
>>>>
>>>> https://github.com/kunstmusik/csound-repl
>>>>
>>>> Shows how it uses python to send code to a running Csound via UDP.
>>>>
>>>> Regarding OSCsound, it'd probably be useful to update it to take in
>>>> and /orc message with orchestra code. Since I need something like this
>>>> anyways, I'll look at updating that Python script this weekend.
>>>>
>>>> On Fri, Feb 17, 2017 at 5:35 PM, Dave Seidel 
>>>> wrote:
>>>>> Steven Yi wrote a nice Python program a few years ago that runs a CSD
>>>>> via
>>>>> the Csound API, and sets up a generic OSC server that allows the user to
>>>>> send score events, and to set channel values:
>>>>> https://github.com/kunstmusik/OSCsound
>>>>>
>>>>>
>>>>> On Fri, Feb 17, 2017 at 5:28 PM, Ed Costello 
>>>>> wrote:
>>>>>>
>>>>>> I don’t know about OSC but this can be achieved using web sockets so it
>>>>>> may be helpful to you, for instance, from a web page you can send an
>>>>>> instrument like in the following example, in this case sending a
>>>>>> trigger
>>>>>> flag value and instrument string when a button is clicked in the web
>>>>>> page:
>>>>>>
>>>>>>            var kvarSocket = new WebSocket("ws://127.0.0.1:8888",
>>>>>> "kvar");
>>>>>>            var stringSocket = new WebSocket("ws://127.0.0.1:8888",
>>>>>> "Sstring");
>>>>>>
>>>>>>            var trigger = 1;
>>>>>>
>>>>>>            stringButton.onclick = function() {
>>>>>>
>>>>>>                stringSocket.send("\"instr 3\n a1 oscils p4/2, p5 / 2,
>>>>>> 0
>>>>>> \n out a1 \nendin\"");
>>>>>>                kvarSocket.send(new Float64Array([trigger]));
>>>>>>                trigger = !trigger;
>>>>>>            }
>>>>>>
>>>>>> On the Csound side you can receive like this:
>>>>>>
>>>>>> 
>>>>>> 
>>>>>> -odac
>>>>>> 
>>>>>> 
>>>>>> nchnls = 2
>>>>>> 0dbfs = 1
>>>>>> ksmps = 256
>>>>>> sr = 44100
>>>>>>
>>>>>> instr 1
>>>>>>
>>>>>> iport init 8888
>>>>>> kvarChanged init 0
>>>>>> ktrigger init 0
>>>>>>
>>>>>> kvar, Sstring websocket iport
>>>>>>
>>>>>> if kvarChanged != kvar then
>>>>>> kvarChanged = kvar
>>>>>> ktrigger = 1
>>>>>> Sscore sprintfk {{i 2 0 -1 %s}}, Sstring
>>>>>> endif
>>>>>>
>>>>>> scoreline Sscore, ktrigger
>>>>>> ktrigger = 0
>>>>>>
>>>>>> endin
>>>>>>
>>>>>> instr 2
>>>>>>
>>>>>> prints p4
>>>>>> Sstring = p4
>>>>>> ires compilestr Sstring
>>>>>> scoreline_i "i 3 0 3 .2 415"
>>>>>> turnoff
>>>>>> endin
>>>>>>
>>>>>> 
>>>>>> 
>>>>>> i1 0 100
>>>>>> 
>>>>>> 
>>>>>>
>>>>>> Maybe you can repurpose this example to use OSC instead,
>>>>>> Cheers,
>>>>>> Ed
>>>>>>
>>>>>> On 17 Feb 2017, at 14:04, free coder  wrote:
>>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> I am experimenting with CSound live coding, running it in a terminal
>>>>>> with
>>>>>> the option  "-L stdin".
>>>>>> It is cool, but s there a way to send live code via an OSC port and not
>>>>>> just type code in the terminal window ?
>>>>>> From what i understand now it is possible to live code from the
>>>>>> terminal
>>>>>> window (it works !), but I would like to 'live code' from other
>>>>>> environments
>>>>>> (processing, max, pd ...) sending OSC 'live code' messages.
>>>>>>
>>>>>> is this already possible ? how is it possible to listen to 'live
>>>>>> coding'
>>>>>> on an OSC port ? (something live "-L oscport 9999" ?)
>>>>>>
>>>>>> (note that i am not talking about the existing OSC  possibilities  in a
>>>>>> .csd like initOSC etc ... as this is not live coding but parameter
>>>>>> control
>>>>>> via OSC)
>>>>>>
>>>>>> many thanks if someone has any hints !
>>>>>>
>>>>>> 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
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> http://mysterybear.net
>>>>> https://soundcloud.com/mysterybear
>>>>> https://mysterybear.bandcamp.com
>>>>> 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
>>>
>>>
>>>
>>>
>>> --
>>> http://mysterybear.net
>>> https://soundcloud.com/mysterybear
>>> https://mysterybear.bandcamp.com
>>> 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

Nice, emacs+csound <3

2017-02-18 0:25 GMT+01:00 free coder <zfreecoder@gmail.com>:

great !!

many thanks for your answers, i will have a look at the different suggestions (i think websockets and UDP should work rather well from another environment)


Saturday, 18 February 2017, 00:01 +0100 from Steven Yi <stevenyi@GMAIL.COM>:

Neat! I'll study the code more carefully but on first glance it looks
nice with the with() syntax support and other more modern Python
practices. Perhaps it might even be better to base things on Felipe's
ctcsound ctypes binding now too. I'll follow up here once I get
somewhere with all of this. :)

On Fri, Feb 17, 2017 at 5:48 PM, Dave Seidel <dave.seidel@gmail.com> wrote:
> Steven, you may want to take a look at my fork. :-) I've added very little
> so far, just been restructuring to make it easier to reuse some of the code.
> My changes may or may not be to your taste (or match you plans), bur may as
> well take a look: https://github.com/DaveSeidel/OSCsound/tree/ds-refactor
>
> On Fri, Feb 17, 2017 at 5:42 PM, Steven Yi <stevenyi@gmail.com> wrote:
>>
>> Wow, I forgot about that project, thanks for mentioning it! :) (It
>> actually may be very useful for a project I had in mind for
>> distributed sound generation...)
>>
>> I was about to write that I tend to do live code with Csound these
>> days using UDP and csound's --port=10000 (or whatever port number you
>> want to use) flag. Using that, you can send orchestra code to Csound
>> via the port. The small Vim plugin I have:
>>
>> https://github.com/kunstmusik/csound-repl
>>
>> Shows how it uses python to send code to a running Csound via UDP.
>>
>> Regarding OSCsound, it'd probably be useful to update it to take in
>> and /orc message with orchestra code. Since I need something like this
>> anyways, I'll look at updating that Python script this weekend.
>>
>> On Fri, Feb 17, 2017 at 5:35 PM, Dave Seidel <dave.seidel@gmail.com>
>> wrote:
>> > Steven Yi wrote a nice Python program a few years ago that runs a CSD
>> > via
>> > the Csound API, and sets up a generic OSC server that allows the user to
>> > send score events, and to set channel values:
>> > https://github.com/kunstmusik/OSCsound
>> >
>> >
>> > On Fri, Feb 17, 2017 at 5:28 PM, Ed Costello <phasereset@gmail.com>
>> > wrote:
>> >>
>> >> I don’t know about OSC but this can be achieved using web sockets so it
>> >> may be helpful to you, for instance, from a web page you can send an
>> >> instrument like in the following example, in this case sending a
>> >> trigger
>> >> flag value and instrument string when a button is clicked in the web
>> >> page:
>> >>
>> >> var kvarSocket = new WebSocket("ws://127.0.0.1:8888",
>> >> "kvar");
>> >> var stringSocket = new WebSocket("ws://127.0.0.1:8888",
>> >> "Sstring");
>> >>
>> >> var trigger = 1;
>> >>
>> >> stringButton.onclick = function() {
>> >>
>> >> stringSocket.send(""instr 3\n a1 oscils p4/2, p5 / 2,
>> >> 0
>> >> \n out a1 \nendin"");
>> >> kvarSocket.send(new Float64Array([trigger]));
>> >> trigger = !trigger;
>> >> }
>> >>
>> >> On the Csound side you can receive like this:
>> >>
>> >> <CsoundSynthesizer>
>> >> <CsOptions>
>> >> -odac
>> >> </CsOptions>
>> >> <CsInstruments>
>> >> nchnls = 2
>> >> 0dbfs = 1
>> >> ksmps = 256
>> >> sr = 44100
>> >>
>> >> instr 1
>> >>
>> >> iport init 8888
>> >> kvarChanged init 0
>> >> ktrigger init 0
>> >>
>> >> kvar, Sstring websocket iport
>> >>
>> >> if kvarChanged != kvar then
>> >> kvarChanged = kvar
>> >> ktrigger = 1
>> >> Sscore sprintfk {{i 2 0 -1 %s}}, Sstring
>> >> endif
>> >>
>> >> scoreline Sscore, ktrigger
>> >> ktrigger = 0
>> >>
>> >> endin
>> >>
>> >> instr 2
>> >>
>> >> prints p4
>> >> Sstring = p4
>> >> ires compilestr Sstring
>> >> scoreline_i "i 3 0 3 .2 415"
>> >> turnoff
>> >> endin
>> >>
>> >> </CsInstruments>
>> >> <CsScore>
>> >> i1 0 100
>> >> </CsScore>
>> >> </CsoundSynthesizer>
>> >>
>> >> Maybe you can repurpose this example to use OSC instead,
>> >> Cheers,
>> >> Ed
>> >>
>> >> On 17 Feb 2017, at 14:04, free coder <zfreecoder@GMAIL.COM> wrote:
>> >>
>> >> Hi,
>> >>
>> >> I am experimenting with CSound live coding, running it in a terminal
>> >> with
>> >> the option "-L stdin".
>> >> It is cool, but s there a way to send live code via an OSC port and not
>> >> just type code in the terminal window ?
>> >> From what i understand now it is possible to live code from the
>> >> terminal
>> >> window (it works !), but I would like to 'live code' from other
>> >> environments
>> >> (processing, max, pd ...) sending OSC 'live code' messages.
>> >>
>> >> is this already possible ? how is it possible to listen to 'live
>> >> coding'
>> >> on an OSC port ? (something live "-L oscport 9999" ?)
>> >>
>> >> (note that i am not talking about the existing OSC possibilities in a
>> >> .csd like initOSC etc ... as this is not live coding but parameter
>> >> control
>> >> via OSC)
>> >>
>> >> many thanks if someone has any hints !
>> >>
>> >> 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
>> >
>> >
>> >
>> >
>> > --
>> > http://mysterybear.net
>> > https://soundcloud.com/mysterybear
>> > https://mysterybear.bandcamp.com
>> > 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
>
>
>
>
> --
> http://mysterybear.net
> https://soundcloud.com/mysterybear
> https://mysterybear.bandcamp.com
> 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