Hi All,

I'm happy to announce the Csound Notebook server is available at:

http://csound-notebook.kunstmusik.com

It allows creating notebooks filled with Csound notes (projects).  It
uses the pNaCl version of Csound to render projects in realtime and
allows live coding by re-evaluating selected text. With pNaCl, you do
not have to have Csound previously installed.  This does require that
you use Google Chrome or Chromium browsers that support pNaCl.

To get started, use the register button to create an account. Upon
successful creation, you will receive an email to activate your
account. Once you activate, you will be able to login.  From there,
click "My Notebook" and you can get started with Csound.

To note, use the Play button to start Csound.  Once Csound starts, you
can start evaluating code.  The Play button becomes a Pause button
which you can use to pause csound.

Some notes: currently there's no warning to save a Note if you've
modified it and moved on to another note.  Please be careful to save
before changing notes.  Also, I don't think there's a way to restart
Csound to a clean state without refreshing the page.  We may need to
add some changes to pNaCl Csound to support this.

I think there's a lot of potential here to further develop this web
application.  I look forward to hearing any feedback.

Thanks!
steven


Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

Hi All,

I'm happy to announce the Csound Notebook server is available at:

http://csound-notebook.kunstmusik.com

It allows creating notebooks filled with Csound notes (projects).  It
uses the pNaCl version of Csound to render projects in realtime and
allows live coding by re-evaluating selected text. With pNaCl, you do
not have to have Csound previously installed.  This does require that
you use Google Chrome or Chromium browsers that support pNaCl.

To get started, use the register button to create an account. Upon
successful creation, you will receive an email to activate your
account. Once you activate, you will be able to login.  From there,
click "My Notebook" and you can get started with Csound.

To note, use the Play button to start Csound.  Once Csound starts, you
can start evaluating code.  The Play button becomes a Pause button
which you can use to pause csound.

Some notes: currently there's no warning to save a Note if you've
modified it and moved on to another note.  Please be careful to save
before changing notes.  Also, I don't think there's a way to restart
Csound to a clean state without refreshing the page.  We may need to
add some changes to pNaCl Csound to support this.

I think there's a lot of potential here to further develop this web
application.  I look forward to hearing any feedback.

Thanks!
steven


Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

I was a little confused at first. Forrest, have you tried this?

1) Click Play.
2) Select the entire instr code and click Evaluate.
3) Select the entire orc code and click Evaluate.

That works for me (in Chrome in Windows 7.) It's a bit counter-intuitive,
because clicking Play by itself does nothing. That just starts the Csound
engine -- it doesn't seem to actually compile and execute any code. That
seems to happen when you evaluate the code.

If I'm correct in my analysis of this, perhaps "Play" is a confusing label.
Perhaps it should say "Activate" or "Run." Just a thought.



--
View this message in context: http://csound.1045644.n5.nabble.com/Csound-Notebook-tp5734285p5734290.html
Sent from the Csound - General mailing list archive at Nabble.com.

Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

Hi All,

Thanks for the feedback!  I think there's still a lot to do, but it
seems like a nice start and hopefully enough is there to start getting
some ideas on ways to improve it all.  I would love to see this grow
to be usable for education purposes, as well as general sound art
needs.

Anthony: I don't believe Chrome on iOS supports pNaCl at this time.
One of the things I'd like to see is adding support for both pNaCl and
Emscripten Csound builds.  The idea would be then to use pNaCl if
available, and fall back to Emscripten otherwise.  The Emscripten
build certainly needs a lot more attention, and in general there are
limitations just due to it using WebAudio.  On the other hand, it at
least does run on most mobile browsers as I think they're all
supporting WebAudio these days.  Ed and I were just chatting over
email about doing a new Emscripten Csound build with the newer
toolchain, though it looks like there might be some issues there.
Something to work through.

Also to note, I am pondering open sourcing the whole notebook server.
I am curious: are there members of the community who are Rails and/or
AngularJS developers who are interested to contribute to this project?
 I'd have to do some research on what's the best way to ensure no
private data (i.e. db passwords, server credentials, etc.) is checked
in.  (Looking at Figaro at the moment).  I don't know if I could
develop this alone and be able to move it forward at the pace I'd like
to see, so making it a community project might be the way forward.

Thanks!
steven

On Thu, Apr 17, 2014 at 8:54 AM, Anthony Palomba <apalomba@austin.rr.com> wrote:
> Hey Steven,
>
> Will CSound NoteBook work with Chrome on iOS?
>
>
>
> Anthony
>
>
> On Thu, Apr 17, 2014 at 12:28 AM, Jim Aikin <midiguru23@sbcglobal.net>
> wrote:
>>
>> I was a little confused at first. Forrest, have you tried this?
>>
>> 1) Click Play.
>> 2) Select the entire instr code and click Evaluate.
>> 3) Select the entire orc code and click Evaluate.
>>
>> That works for me (in Chrome in Windows 7.) It's a bit counter-intuitive,
>> because clicking Play by itself does nothing. That just starts the Csound
>> engine -- it doesn't seem to actually compile and execute any code. That
>> seems to happen when you evaluate the code.
>>
>> If I'm correct in my analysis of this, perhaps "Play" is a confusing
>> label.
>> Perhaps it should say "Activate" or "Run." Just a thought.
>>
>>
>>
>> --
>> View this message in context:
>> http://csound.1045644.n5.nabble.com/Csound-Notebook-tp5734285p5734290.html
>> Sent from the Csound - General mailing list archive at Nabble.com.
>>
>>
>> Send bugs reports to
>>         https://github.com/csound/csound/issues
>> 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
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

Hi Steven,

This is great. It makes me wonder whether it's time to bundle all of the csound syntax into a new format, so you don't have to be jumping around between orchestra and score, but have a single format for this kind of live coding. It would be ideal if it was supported by csound itself, that way there are no divergences between different front ends.

For example, how about some syntax for score events within the orc section:

score

i 1 0 10
...

endsco

I first though of using some shorter character like:

{

}

But then it looked so different to the rest of the language and using a keyword makes it more readable.

Also I think this should go in the news section of the github webpage. We should start keeping that page in mind for announcements, so it's visible for external people how active Csound development is.

Cheers,
Andrés

On Thu, Apr 17, 2014 at 6:22 AM, Steven Yi <stevenyi@gmail.com> wrote:

Hi All,

Thanks for the feedback!  I think there's still a lot to do, but it
seems like a nice start and hopefully enough is there to start getting
some ideas on ways to improve it all.  I would love to see this grow
to be usable for education purposes, as well as general sound art
needs.

Anthony: I don't believe Chrome on iOS supports pNaCl at this time.
One of the things I'd like to see is adding support for both pNaCl and
Emscripten Csound builds.  The idea would be then to use pNaCl if
available, and fall back to Emscripten otherwise.  The Emscripten
build certainly needs a lot more attention, and in general there are
limitations just due to it using WebAudio.  On the other hand, it at
least does run on most mobile browsers as I think they're all
supporting WebAudio these days.  Ed and I were just chatting over
email about doing a new Emscripten Csound build with the newer
toolchain, though it looks like there might be some issues there.
Something to work through.

Also to note, I am pondering open sourcing the whole notebook server.
I am curious: are there members of the community who are Rails and/or
AngularJS developers who are interested to contribute to this project?
 I'd have to do some research on what's the best way to ensure no
private data (i.e. db passwords, server credentials, etc.) is checked
in.  (Looking at Figaro at the moment).  I don't know if I could
develop this alone and be able to move it forward at the pace I'd like
to see, so making it a community project might be the way forward.

Thanks!
steven

On Thu, Apr 17, 2014 at 8:54 AM, Anthony Palomba <apalomba@austin.rr.com> wrote:
> Hey Steven,
>
> Will CSound NoteBook work with Chrome on iOS?
>
>
>
> Anthony
>
>
> On Thu, Apr 17, 2014 at 12:28 AM, Jim Aikin <midiguru23@sbcglobal.net>
> wrote:
>>
>> I was a little confused at first. Forrest, have you tried this?
>>
>> 1) Click Play.
>> 2) Select the entire instr code and click Evaluate.
>> 3) Select the entire orc code and click Evaluate.
>>
>> That works for me (in Chrome in Windows 7.) It's a bit counter-intuitive,
>> because clicking Play by itself does nothing. That just starts the Csound
>> engine -- it doesn't seem to actually compile and execute any code. That
>> seems to happen when you evaluate the code.
>>
>> If I'm correct in my analysis of this, perhaps "Play" is a confusing
>> label.
>> Perhaps it should say "Activate" or "Run." Just a thought.
>>
>>
>>
>> --
>> View this message in context:
>> http://csound.1045644.n5.nabble.com/Csound-Notebook-tp5734285p5734290.html
>> Sent from the Csound - General mailing list archive at Nabble.com.
>>
>>
>> Send bugs reports to
>>         https://github.com/csound/csound/issues
>> 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
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

Have you looked at the LuaJIT opcodes? They enable quite sophisticated algorithmic composition to be done by evaluating embedded Lua code in the orchestra header, to be run by the lua_exec opcode. This is actually the main way I work now. I use CsoundQt so I can fine-tune my instruments and levels with sliders, and I just write my pieces as Lua right in the orchestra header.

Oh, but I see you are speaking in the context of live coding. Oops, the orchestra header is only evaluated when Csound starts to run and then not again, is that not correct?

Is it possible to send a multi-line string from the sco to Csound? In that case a UDO could just evaluate any Lua code in that string. You could do live coding that way.

Regards,

Mike

-----------------------------------------------------

Michael Gogins
Irreducible Productions
http://michaelgogins.tumblr.com
Michael dot Gogins at gmail dot com

On Thu, Apr 17, 2014 at 12:47 PM, Andres Cabrera <mantaraya36@gmail.com> wrote:

Hi Steven,

This is great. It makes me wonder whether it's time to bundle all of the csound syntax into a new format, so you don't have to be jumping around between orchestra and score, but have a single format for this kind of live coding. It would be ideal if it was supported by csound itself, that way there are no divergences between different front ends.

For example, how about some syntax for score events within the orc section:

score

i 1 0 10
...

endsco

I first though of using some shorter character like:

{

}

But then it looked so different to the rest of the language and using a keyword makes it more readable.

Also I think this should go in the news section of the github webpage. We should start keeping that page in mind for announcements, so it's visible for external people how active Csound development is.

Cheers,
Andrés

On Thu, Apr 17, 2014 at 6:22 AM, Steven Yi <stevenyi@gmail.com> wrote:

Hi All,

Thanks for the feedback!  I think there's still a lot to do, but it
seems like a nice start and hopefully enough is there to start getting
some ideas on ways to improve it all.  I would love to see this grow
to be usable for education purposes, as well as general sound art
needs.

Anthony: I don't believe Chrome on iOS supports pNaCl at this time.
One of the things I'd like to see is adding support for both pNaCl and
Emscripten Csound builds.  The idea would be then to use pNaCl if
available, and fall back to Emscripten otherwise.  The Emscripten
build certainly needs a lot more attention, and in general there are
limitations just due to it using WebAudio.  On the other hand, it at
least does run on most mobile browsers as I think they're all
supporting WebAudio these days.  Ed and I were just chatting over
email about doing a new Emscripten Csound build with the newer
toolchain, though it looks like there might be some issues there.
Something to work through.

Also to note, I am pondering open sourcing the whole notebook server.
I am curious: are there members of the community who are Rails and/or
AngularJS developers who are interested to contribute to this project?
 I'd have to do some research on what's the best way to ensure no
private data (i.e. db passwords, server credentials, etc.) is checked
in.  (Looking at Figaro at the moment).  I don't know if I could
develop this alone and be able to move it forward at the pace I'd like
to see, so making it a community project might be the way forward.

Thanks!
steven

On Thu, Apr 17, 2014 at 8:54 AM, Anthony Palomba <apalomba@austin.rr.com> wrote:
> Hey Steven,
>
> Will CSound NoteBook work with Chrome on iOS?
>
>
>
> Anthony
>
>
> On Thu, Apr 17, 2014 at 12:28 AM, Jim Aikin <midiguru23@sbcglobal.net>
> wrote:
>>
>> I was a little confused at first. Forrest, have you tried this?
>>
>> 1) Click Play.
>> 2) Select the entire instr code and click Evaluate.
>> 3) Select the entire orc code and click Evaluate.
>>
>> That works for me (in Chrome in Windows 7.) It's a bit counter-intuitive,
>> because clicking Play by itself does nothing. That just starts the Csound
>> engine -- it doesn't seem to actually compile and execute any code. That
>> seems to happen when you evaluate the code.
>>
>> If I'm correct in my analysis of this, perhaps "Play" is a confusing
>> label.
>> Perhaps it should say "Activate" or "Run." Just a thought.
>>
>>
>>
>> --
>> View this message in context:
>> http://csound.1045644.n5.nabble.com/Csound-Notebook-tp5734285p5734290.html
>> Sent from the Csound - General mailing list archive at Nabble.com.
>>
>>
>> Send bugs reports to
>>         https://github.com/csound/csound/issues
>> 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
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

I'm thinking more of a format that is not meant to be executed directly with csound, but that can hold everything you would need for live-coding. I'm not entirely sure if that really makes sense though...

Cheers,
Andrés

On Thu, Apr 17, 2014 at 9:57 AM, Michael Gogins <michael.gogins@gmail.com> wrote:

Have you looked at the LuaJIT opcodes? They enable quite sophisticated algorithmic composition to be done by evaluating embedded Lua code in the orchestra header, to be run by the lua_exec opcode. This is actually the main way I work now. I use CsoundQt so I can fine-tune my instruments and levels with sliders, and I just write my pieces as Lua right in the orchestra header.

Oh, but I see you are speaking in the context of live coding. Oops, the orchestra header is only evaluated when Csound starts to run and then not again, is that not correct?

Is it possible to send a multi-line string from the sco to Csound? In that case a UDO could just evaluate any Lua code in that string. You could do live coding that way.

Regards,

Mike

-----------------------------------------------------

Michael Gogins
Irreducible Productions
http://michaelgogins.tumblr.com
Michael dot Gogins at gmail dot com

On Thu, Apr 17, 2014 at 12:47 PM, Andres Cabrera <mantaraya36@gmail.com> wrote:

Hi Steven,

This is great. It makes me wonder whether it's time to bundle all of the csound syntax into a new format, so you don't have to be jumping around between orchestra and score, but have a single format for this kind of live coding. It would be ideal if it was supported by csound itself, that way there are no divergences between different front ends.

For example, how about some syntax for score events within the orc section:

score

i 1 0 10
...

endsco

I first though of using some shorter character like:

{

}

But then it looked so different to the rest of the language and using a keyword makes it more readable.

Also I think this should go in the news section of the github webpage. We should start keeping that page in mind for announcements, so it's visible for external people how active Csound development is.

Cheers,
Andrés

On Thu, Apr 17, 2014 at 6:22 AM, Steven Yi <stevenyi@gmail.com> wrote:

Hi All,

Thanks for the feedback!  I think there's still a lot to do, but it
seems like a nice start and hopefully enough is there to start getting
some ideas on ways to improve it all.  I would love to see this grow
to be usable for education purposes, as well as general sound art
needs.

Anthony: I don't believe Chrome on iOS supports pNaCl at this time.
One of the things I'd like to see is adding support for both pNaCl and
Emscripten Csound builds.  The idea would be then to use pNaCl if
available, and fall back to Emscripten otherwise.  The Emscripten
build certainly needs a lot more attention, and in general there are
limitations just due to it using WebAudio.  On the other hand, it at
least does run on most mobile browsers as I think they're all
supporting WebAudio these days.  Ed and I were just chatting over
email about doing a new Emscripten Csound build with the newer
toolchain, though it looks like there might be some issues there.
Something to work through.

Also to note, I am pondering open sourcing the whole notebook server.
I am curious: are there members of the community who are Rails and/or
AngularJS developers who are interested to contribute to this project?
 I'd have to do some research on what's the best way to ensure no
private data (i.e. db passwords, server credentials, etc.) is checked
in.  (Looking at Figaro at the moment).  I don't know if I could
develop this alone and be able to move it forward at the pace I'd like
to see, so making it a community project might be the way forward.

Thanks!
steven

On Thu, Apr 17, 2014 at 8:54 AM, Anthony Palomba <apalomba@austin.rr.com> wrote:
> Hey Steven,
>
> Will CSound NoteBook work with Chrome on iOS?
>
>
>
> Anthony
>
>
> On Thu, Apr 17, 2014 at 12:28 AM, Jim Aikin <midiguru23@sbcglobal.net>
> wrote:
>>
>> I was a little confused at first. Forrest, have you tried this?
>>
>> 1) Click Play.
>> 2) Select the entire instr code and click Evaluate.
>> 3) Select the entire orc code and click Evaluate.
>>
>> That works for me (in Chrome in Windows 7.) It's a bit counter-intuitive,
>> because clicking Play by itself does nothing. That just starts the Csound
>> engine -- it doesn't seem to actually compile and execute any code. That
>> seems to happen when you evaluate the code.
>>
>> If I'm correct in my analysis of this, perhaps "Play" is a confusing
>> label.
>> Perhaps it should say "Activate" or "Run." Just a thought.
>>
>>
>>
>> --
>> View this message in context:
>> http://csound.1045644.n5.nabble.com/Csound-Notebook-tp5734285p5734290.html
>> Sent from the Csound - General mailing list archive at Nabble.com.
>>
>>
>> Send bugs reports to
>>         https://github.com/csound/csound/issues
>> 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
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

Have you seen the current issue of Computer Music Journal? It is all about live coding. There are two live encoding environments in the "Products of Interest" section, at least one of which is open source, I think probably both of them are actually.

Regards,

Mike

-----------------------------------------------------

Michael Gogins
Irreducible Productions
http://michaelgogins.tumblr.com
Michael dot Gogins at gmail dot com

On Thu, Apr 17, 2014 at 1:01 PM, Andres Cabrera <mantaraya36@gmail.com> wrote:

I'm thinking more of a format that is not meant to be executed directly with csound, but that can hold everything you would need for live-coding. I'm not entirely sure if that really makes sense though...

Cheers,
Andrés

On Thu, Apr 17, 2014 at 9:57 AM, Michael Gogins <michael.gogins@gmail.com> wrote:

Have you looked at the LuaJIT opcodes? They enable quite sophisticated algorithmic composition to be done by evaluating embedded Lua code in the orchestra header, to be run by the lua_exec opcode. This is actually the main way I work now. I use CsoundQt so I can fine-tune my instruments and levels with sliders, and I just write my pieces as Lua right in the orchestra header.

Oh, but I see you are speaking in the context of live coding. Oops, the orchestra header is only evaluated when Csound starts to run and then not again, is that not correct?

Is it possible to send a multi-line string from the sco to Csound? In that case a UDO could just evaluate any Lua code in that string. You could do live coding that way.

Regards,

Mike

-----------------------------------------------------

Michael Gogins
Irreducible Productions
http://michaelgogins.tumblr.com
Michael dot Gogins at gmail dot com

On Thu, Apr 17, 2014 at 12:47 PM, Andres Cabrera <mantaraya36@gmail.com> wrote:

Hi Steven,

This is great. It makes me wonder whether it's time to bundle all of the csound syntax into a new format, so you don't have to be jumping around between orchestra and score, but have a single format for this kind of live coding. It would be ideal if it was supported by csound itself, that way there are no divergences between different front ends.

For example, how about some syntax for score events within the orc section:

score

i 1 0 10
...

endsco

I first though of using some shorter character like:

{

}

But then it looked so different to the rest of the language and using a keyword makes it more readable.

Also I think this should go in the news section of the github webpage. We should start keeping that page in mind for announcements, so it's visible for external people how active Csound development is.

Cheers,
Andrés

On Thu, Apr 17, 2014 at 6:22 AM, Steven Yi <stevenyi@gmail.com> wrote:

Hi All,

Thanks for the feedback!  I think there's still a lot to do, but it
seems like a nice start and hopefully enough is there to start getting
some ideas on ways to improve it all.  I would love to see this grow
to be usable for education purposes, as well as general sound art
needs.

Anthony: I don't believe Chrome on iOS supports pNaCl at this time.
One of the things I'd like to see is adding support for both pNaCl and
Emscripten Csound builds.  The idea would be then to use pNaCl if
available, and fall back to Emscripten otherwise.  The Emscripten
build certainly needs a lot more attention, and in general there are
limitations just due to it using WebAudio.  On the other hand, it at
least does run on most mobile browsers as I think they're all
supporting WebAudio these days.  Ed and I were just chatting over
email about doing a new Emscripten Csound build with the newer
toolchain, though it looks like there might be some issues there.
Something to work through.

Also to note, I am pondering open sourcing the whole notebook server.
I am curious: are there members of the community who are Rails and/or
AngularJS developers who are interested to contribute to this project?
 I'd have to do some research on what's the best way to ensure no
private data (i.e. db passwords, server credentials, etc.) is checked
in.  (Looking at Figaro at the moment).  I don't know if I could
develop this alone and be able to move it forward at the pace I'd like
to see, so making it a community project might be the way forward.

Thanks!
steven

On Thu, Apr 17, 2014 at 8:54 AM, Anthony Palomba <apalomba@austin.rr.com> wrote:
> Hey Steven,
>
> Will CSound NoteBook work with Chrome on iOS?
>
>
>
> Anthony
>
>
> On Thu, Apr 17, 2014 at 12:28 AM, Jim Aikin <midiguru23@sbcglobal.net>
> wrote:
>>
>> I was a little confused at first. Forrest, have you tried this?
>>
>> 1) Click Play.
>> 2) Select the entire instr code and click Evaluate.
>> 3) Select the entire orc code and click Evaluate.
>>
>> That works for me (in Chrome in Windows 7.) It's a bit counter-intuitive,
>> because clicking Play by itself does nothing. That just starts the Csound
>> engine -- it doesn't seem to actually compile and execute any code. That
>> seems to happen when you evaluate the code.
>>
>> If I'm correct in my analysis of this, perhaps "Play" is a confusing
>> label.
>> Perhaps it should say "Activate" or "Run." Just a thought.
>>
>>
>>
>> --
>> View this message in context:
>> http://csound.1045644.n5.nabble.com/Csound-Notebook-tp5734285p5734290.html
>> Sent from the Csound - General mailing list archive at Nabble.com.
>>
>>
>> Send bugs reports to
>>         https://github.com/csound/csound/issues
>> 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
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

Thanks for the pointers.

I do know Gibber is open source and it is developed by Charlie Roberts here at MAT. Cool project to checkout if you haven't. It is slowly turning the editor into an interface (i.e. the editor shows where in a drum pattern you currently are, and has other nice usability features). It actually has two separate rendering engines, one using web audio, and the other using javescript for the DSP with some clever optimization techniques to improve performance.

http://charlie-roberts.com/gibber/info/

Overtone is also open source, and interestingly it uses the supercollider engine for audio and processing for visual. So it is more of a clojure front-end to both.
http://overtone.github.io/

Cheers,
Andrés

On Thu, Apr 17, 2014 at 11:08 AM, Michael Gogins <michael.gogins@gmail.com> wrote:

Have you seen the current issue of Computer Music Journal? It is all about live coding. There are two live encoding environments in the "Products of Interest" section, at least one of which is open source, I think probably both of them are actually.

Regards,

Mike

-----------------------------------------------------

Michael Gogins
Irreducible Productions
http://michaelgogins.tumblr.com
Michael dot Gogins at gmail dot com

On Thu, Apr 17, 2014 at 1:01 PM, Andres Cabrera <mantaraya36@gmail.com> wrote:

I'm thinking more of a format that is not meant to be executed directly with csound, but that can hold everything you would need for live-coding. I'm not entirely sure if that really makes sense though...

Cheers,
Andrés

On Thu, Apr 17, 2014 at 9:57 AM, Michael Gogins <michael.gogins@gmail.com> wrote:

Have you looked at the LuaJIT opcodes? They enable quite sophisticated algorithmic composition to be done by evaluating embedded Lua code in the orchestra header, to be run by the lua_exec opcode. This is actually the main way I work now. I use CsoundQt so I can fine-tune my instruments and levels with sliders, and I just write my pieces as Lua right in the orchestra header.

Oh, but I see you are speaking in the context of live coding. Oops, the orchestra header is only evaluated when Csound starts to run and then not again, is that not correct?

Is it possible to send a multi-line string from the sco to Csound? In that case a UDO could just evaluate any Lua code in that string. You could do live coding that way.

Regards,

Mike

-----------------------------------------------------

Michael Gogins
Irreducible Productions
http://michaelgogins.tumblr.com
Michael dot Gogins at gmail dot com

On Thu, Apr 17, 2014 at 12:47 PM, Andres Cabrera <mantaraya36@gmail.com> wrote:

Hi Steven,

This is great. It makes me wonder whether it's time to bundle all of the csound syntax into a new format, so you don't have to be jumping around between orchestra and score, but have a single format for this kind of live coding. It would be ideal if it was supported by csound itself, that way there are no divergences between different front ends.

For example, how about some syntax for score events within the orc section:

score

i 1 0 10
...

endsco

I first though of using some shorter character like:

{

}

But then it looked so different to the rest of the language and using a keyword makes it more readable.

Also I think this should go in the news section of the github webpage. We should start keeping that page in mind for announcements, so it's visible for external people how active Csound development is.

Cheers,
Andrés

On Thu, Apr 17, 2014 at 6:22 AM, Steven Yi <stevenyi@gmail.com> wrote:

Hi All,

Thanks for the feedback!  I think there's still a lot to do, but it
seems like a nice start and hopefully enough is there to start getting
some ideas on ways to improve it all.  I would love to see this grow
to be usable for education purposes, as well as general sound art
needs.

Anthony: I don't believe Chrome on iOS supports pNaCl at this time.
One of the things I'd like to see is adding support for both pNaCl and
Emscripten Csound builds.  The idea would be then to use pNaCl if
available, and fall back to Emscripten otherwise.  The Emscripten
build certainly needs a lot more attention, and in general there are
limitations just due to it using WebAudio.  On the other hand, it at
least does run on most mobile browsers as I think they're all
supporting WebAudio these days.  Ed and I were just chatting over
email about doing a new Emscripten Csound build with the newer
toolchain, though it looks like there might be some issues there.
Something to work through.

Also to note, I am pondering open sourcing the whole notebook server.
I am curious: are there members of the community who are Rails and/or
AngularJS developers who are interested to contribute to this project?
 I'd have to do some research on what's the best way to ensure no
private data (i.e. db passwords, server credentials, etc.) is checked
in.  (Looking at Figaro at the moment).  I don't know if I could
develop this alone and be able to move it forward at the pace I'd like
to see, so making it a community project might be the way forward.

Thanks!
steven

On Thu, Apr 17, 2014 at 8:54 AM, Anthony Palomba <apalomba@austin.rr.com> wrote:
> Hey Steven,
>
> Will CSound NoteBook work with Chrome on iOS?
>
>
>
> Anthony
>
>
> On Thu, Apr 17, 2014 at 12:28 AM, Jim Aikin <midiguru23@sbcglobal.net>
> wrote:
>>
>> I was a little confused at first. Forrest, have you tried this?
>>
>> 1) Click Play.
>> 2) Select the entire instr code and click Evaluate.
>> 3) Select the entire orc code and click Evaluate.
>>
>> That works for me (in Chrome in Windows 7.) It's a bit counter-intuitive,
>> because clicking Play by itself does nothing. That just starts the Csound
>> engine -- it doesn't seem to actually compile and execute any code. That
>> seems to happen when you evaluate the code.
>>
>> If I'm correct in my analysis of this, perhaps "Play" is a confusing
>> label.
>> Perhaps it should say "Activate" or "Run." Just a thought.
>>
>>
>>
>> --
>> View this message in context:
>> http://csound.1045644.n5.nabble.com/Csound-Notebook-tp5734285p5734290.html
>> Sent from the Csound - General mailing list archive at Nabble.com.
>>
>>
>> Send bugs reports to
>>         https://github.com/csound/csound/issues
>> 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
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

It might be possible without too much trouble to use Csound's PNaCl build as a synthesis engine for Gibber.

Regards,

Mike

-----------------------------------------------------

Michael Gogins
Irreducible Productions
http://michaelgogins.tumblr.com
Michael dot Gogins at gmail dot com

On Thu, Apr 17, 2014 at 2:18 PM, Andres Cabrera <mantaraya36@gmail.com> wrote:

Thanks for the pointers.

I do know Gibber is open source and it is developed by Charlie Roberts here at MAT. Cool project to checkout if you haven't. It is slowly turning the editor into an interface (i.e. the editor shows where in a drum pattern you currently are, and has other nice usability features). It actually has two separate rendering engines, one using web audio, and the other using javescript for the DSP with some clever optimization techniques to improve performance.

http://charlie-roberts.com/gibber/info/

Overtone is also open source, and interestingly it uses the supercollider engine for audio and processing for visual. So it is more of a clojure front-end to both.
http://overtone.github.io/

Cheers,
Andrés

On Thu, Apr 17, 2014 at 11:08 AM, Michael Gogins <michael.gogins@gmail.com> wrote:

Have you seen the current issue of Computer Music Journal? It is all about live coding. There are two live encoding environments in the "Products of Interest" section, at least one of which is open source, I think probably both of them are actually.

Regards,

Mike

-----------------------------------------------------

Michael Gogins
Irreducible Productions
http://michaelgogins.tumblr.com
Michael dot Gogins at gmail dot com

On Thu, Apr 17, 2014 at 1:01 PM, Andres Cabrera <mantaraya36@gmail.com> wrote:

I'm thinking more of a format that is not meant to be executed directly with csound, but that can hold everything you would need for live-coding. I'm not entirely sure if that really makes sense though...

Cheers,
Andrés

On Thu, Apr 17, 2014 at 9:57 AM, Michael Gogins <michael.gogins@gmail.com> wrote:

Have you looked at the LuaJIT opcodes? They enable quite sophisticated algorithmic composition to be done by evaluating embedded Lua code in the orchestra header, to be run by the lua_exec opcode. This is actually the main way I work now. I use CsoundQt so I can fine-tune my instruments and levels with sliders, and I just write my pieces as Lua right in the orchestra header.

Oh, but I see you are speaking in the context of live coding. Oops, the orchestra header is only evaluated when Csound starts to run and then not again, is that not correct?

Is it possible to send a multi-line string from the sco to Csound? In that case a UDO could just evaluate any Lua code in that string. You could do live coding that way.

Regards,

Mike

-----------------------------------------------------

Michael Gogins
Irreducible Productions
http://michaelgogins.tumblr.com
Michael dot Gogins at gmail dot com

On Thu, Apr 17, 2014 at 12:47 PM, Andres Cabrera <mantaraya36@gmail.com> wrote:

Hi Steven,

This is great. It makes me wonder whether it's time to bundle all of the csound syntax into a new format, so you don't have to be jumping around between orchestra and score, but have a single format for this kind of live coding. It would be ideal if it was supported by csound itself, that way there are no divergences between different front ends.

For example, how about some syntax for score events within the orc section:

score

i 1 0 10
...

endsco

I first though of using some shorter character like:

{

}

But then it looked so different to the rest of the language and using a keyword makes it more readable.

Also I think this should go in the news section of the github webpage. We should start keeping that page in mind for announcements, so it's visible for external people how active Csound development is.

Cheers,
Andrés

On Thu, Apr 17, 2014 at 6:22 AM, Steven Yi <stevenyi@gmail.com> wrote:

Hi All,

Thanks for the feedback!  I think there's still a lot to do, but it
seems like a nice start and hopefully enough is there to start getting
some ideas on ways to improve it all.  I would love to see this grow
to be usable for education purposes, as well as general sound art
needs.

Anthony: I don't believe Chrome on iOS supports pNaCl at this time.
One of the things I'd like to see is adding support for both pNaCl and
Emscripten Csound builds.  The idea would be then to use pNaCl if
available, and fall back to Emscripten otherwise.  The Emscripten
build certainly needs a lot more attention, and in general there are
limitations just due to it using WebAudio.  On the other hand, it at
least does run on most mobile browsers as I think they're all
supporting WebAudio these days.  Ed and I were just chatting over
email about doing a new Emscripten Csound build with the newer
toolchain, though it looks like there might be some issues there.
Something to work through.

Also to note, I am pondering open sourcing the whole notebook server.
I am curious: are there members of the community who are Rails and/or
AngularJS developers who are interested to contribute to this project?
 I'd have to do some research on what's the best way to ensure no
private data (i.e. db passwords, server credentials, etc.) is checked
in.  (Looking at Figaro at the moment).  I don't know if I could
develop this alone and be able to move it forward at the pace I'd like
to see, so making it a community project might be the way forward.

Thanks!
steven

On Thu, Apr 17, 2014 at 8:54 AM, Anthony Palomba <apalomba@austin.rr.com> wrote:
> Hey Steven,
>
> Will CSound NoteBook work with Chrome on iOS?
>
>
>
> Anthony
>
>
> On Thu, Apr 17, 2014 at 12:28 AM, Jim Aikin <midiguru23@sbcglobal.net>
> wrote:
>>
>> I was a little confused at first. Forrest, have you tried this?
>>
>> 1) Click Play.
>> 2) Select the entire instr code and click Evaluate.
>> 3) Select the entire orc code and click Evaluate.
>>
>> That works for me (in Chrome in Windows 7.) It's a bit counter-intuitive,
>> because clicking Play by itself does nothing. That just starts the Csound
>> engine -- it doesn't seem to actually compile and execute any code. That
>> seems to happen when you evaluate the code.
>>
>> If I'm correct in my analysis of this, perhaps "Play" is a confusing
>> label.
>> Perhaps it should say "Activate" or "Run." Just a thought.
>>
>>
>>
>> --
>> View this message in context:
>> http://csound.1045644.n5.nabble.com/Csound-Notebook-tp5734285p5734290.html
>> Sent from the Csound - General mailing list archive at Nabble.com.
>>
>>
>> Send bugs reports to
>>         https://github.com/csound/csound/issues
>> 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
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

I have talked to Charlie about this, but he is not comfortable with a browser specific solution.

Cheers,
Andrés

On Thu, Apr 17, 2014 at 11:23 AM, Michael Gogins <michael.gogins@gmail.com> wrote:

It might be possible without too much trouble to use Csound's PNaCl build as a synthesis engine for Gibber.

Regards,

Mike

-----------------------------------------------------

Michael Gogins
Irreducible Productions
http://michaelgogins.tumblr.com
Michael dot Gogins at gmail dot com

On Thu, Apr 17, 2014 at 2:18 PM, Andres Cabrera <mantaraya36@gmail.com> wrote:

Thanks for the pointers.

I do know Gibber is open source and it is developed by Charlie Roberts here at MAT. Cool project to checkout if you haven't. It is slowly turning the editor into an interface (i.e. the editor shows where in a drum pattern you currently are, and has other nice usability features). It actually has two separate rendering engines, one using web audio, and the other using javescript for the DSP with some clever optimization techniques to improve performance.

http://charlie-roberts.com/gibber/info/

Overtone is also open source, and interestingly it uses the supercollider engine for audio and processing for visual. So it is more of a clojure front-end to both.
http://overtone.github.io/

Cheers,
Andrés

On Thu, Apr 17, 2014 at 11:08 AM, Michael Gogins <michael.gogins@gmail.com> wrote:

Have you seen the current issue of Computer Music Journal? It is all about live coding. There are two live encoding environments in the "Products of Interest" section, at least one of which is open source, I think probably both of them are actually.

Regards,

Mike

-----------------------------------------------------

Michael Gogins
Irreducible Productions
http://michaelgogins.tumblr.com
Michael dot Gogins at gmail dot com

On Thu, Apr 17, 2014 at 1:01 PM, Andres Cabrera <mantaraya36@gmail.com> wrote:

I'm thinking more of a format that is not meant to be executed directly with csound, but that can hold everything you would need for live-coding. I'm not entirely sure if that really makes sense though...

Cheers,
Andrés

On Thu, Apr 17, 2014 at 9:57 AM, Michael Gogins <michael.gogins@gmail.com> wrote:

Have you looked at the LuaJIT opcodes? They enable quite sophisticated algorithmic composition to be done by evaluating embedded Lua code in the orchestra header, to be run by the lua_exec opcode. This is actually the main way I work now. I use CsoundQt so I can fine-tune my instruments and levels with sliders, and I just write my pieces as Lua right in the orchestra header.

Oh, but I see you are speaking in the context of live coding. Oops, the orchestra header is only evaluated when Csound starts to run and then not again, is that not correct?

Is it possible to send a multi-line string from the sco to Csound? In that case a UDO could just evaluate any Lua code in that string. You could do live coding that way.

Regards,

Mike

-----------------------------------------------------

Michael Gogins
Irreducible Productions
http://michaelgogins.tumblr.com
Michael dot Gogins at gmail dot com

On Thu, Apr 17, 2014 at 12:47 PM, Andres Cabrera <mantaraya36@gmail.com> wrote:

Hi Steven,

This is great. It makes me wonder whether it's time to bundle all of the csound syntax into a new format, so you don't have to be jumping around between orchestra and score, but have a single format for this kind of live coding. It would be ideal if it was supported by csound itself, that way there are no divergences between different front ends.

For example, how about some syntax for score events within the orc section:

score

i 1 0 10
...

endsco

I first though of using some shorter character like:

{

}

But then it looked so different to the rest of the language and using a keyword makes it more readable.

Also I think this should go in the news section of the github webpage. We should start keeping that page in mind for announcements, so it's visible for external people how active Csound development is.

Cheers,
Andrés

On Thu, Apr 17, 2014 at 6:22 AM, Steven Yi <stevenyi@gmail.com> wrote:

Hi All,

Thanks for the feedback!  I think there's still a lot to do, but it
seems like a nice start and hopefully enough is there to start getting
some ideas on ways to improve it all.  I would love to see this grow
to be usable for education purposes, as well as general sound art
needs.

Anthony: I don't believe Chrome on iOS supports pNaCl at this time.
One of the things I'd like to see is adding support for both pNaCl and
Emscripten Csound builds.  The idea would be then to use pNaCl if
available, and fall back to Emscripten otherwise.  The Emscripten
build certainly needs a lot more attention, and in general there are
limitations just due to it using WebAudio.  On the other hand, it at
least does run on most mobile browsers as I think they're all
supporting WebAudio these days.  Ed and I were just chatting over
email about doing a new Emscripten Csound build with the newer
toolchain, though it looks like there might be some issues there.
Something to work through.

Also to note, I am pondering open sourcing the whole notebook server.
I am curious: are there members of the community who are Rails and/or
AngularJS developers who are interested to contribute to this project?
 I'd have to do some research on what's the best way to ensure no
private data (i.e. db passwords, server credentials, etc.) is checked
in.  (Looking at Figaro at the moment).  I don't know if I could
develop this alone and be able to move it forward at the pace I'd like
to see, so making it a community project might be the way forward.

Thanks!
steven

On Thu, Apr 17, 2014 at 8:54 AM, Anthony Palomba <apalomba@austin.rr.com> wrote:
> Hey Steven,
>
> Will CSound NoteBook work with Chrome on iOS?
>
>
>
> Anthony
>
>
> On Thu, Apr 17, 2014 at 12:28 AM, Jim Aikin <midiguru23@sbcglobal.net>
> wrote:
>>
>> I was a little confused at first. Forrest, have you tried this?
>>
>> 1) Click Play.
>> 2) Select the entire instr code and click Evaluate.
>> 3) Select the entire orc code and click Evaluate.
>>
>> That works for me (in Chrome in Windows 7.) It's a bit counter-intuitive,
>> because clicking Play by itself does nothing. That just starts the Csound
>> engine -- it doesn't seem to actually compile and execute any code. That
>> seems to happen when you evaluate the code.
>>
>> If I'm correct in my analysis of this, perhaps "Play" is a confusing
>> label.
>> Perhaps it should say "Activate" or "Run." Just a thought.
>>
>>
>>
>> --
>> View this message in context:
>> http://csound.1045644.n5.nabble.com/Csound-Notebook-tp5734285p5734290.html
>> Sent from the Csound - General mailing list archive at Nabble.com.
>>
>>
>> Send bugs reports to
>>         https://github.com/csound/csound/issues
>> 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
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"