My existing html player allows the user to edit the csd example, but
does not save the edited version of the example.

In addition, most examples use mono but only stereo examples were
working, last time I checked. But this may now have changed because of
changes to the output opcodes. I will check.

I see no reason to maintain two versions of this thing. If you are
willing to maintain yours I am happy to remove mine.

Regards,
Mike

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


On Tue, Jan 24, 2017 at 11:39 AM, Ed Costello  wrote:
> Hi,
>
> I have started 2 projects which may be of interest. A web component for
> Csound that can play and edit .csd files (using either pnacl or emscripten),
> and a manual parser which converts, or will in theory convert, docbook xml
> opcode pages to html using Asciidoctor which includes the web component.
>
> I am aware that there is an online version of the manual which will also
> allow the playing of .csd files, but I thought I would give it a go as my
> idea was to have a text editor and the player engine embedded directly in
> the manual page.
>
> The csound web component player is here
> https://github.com/eddyc/csound-player/
>
> The manual to html project is here https://github.com/eddyc/csound-manual/
>
> I also have an example of a finished html manual page with the embedded csd
> player at
>
> https://eddyc.github.io/csound-manual/opcodes/areson.html
>
> there are a number of things unfinished here of course but I think it shows
> the potential of having such a player embedded directly in a manual page
> with an editor. I think another benefit of this approach is that the docbook
> xml files are converted to asciidoctor markup, which is very similar to
> markdown, and shows how it could be a lot simpler to make manual pages, and
> pages that are clearly legible in their source form inside of a text editor.
>
> Cheers

I went to your example page, and edited the example to output one
channel. It did not work. I assume you are using a more recent version
of the PNaCl or Emscripten build than my playable manual does.

I think the best fix here would be to change, not the manual page
code, but rather the JavaScript wrapper code.

Regards,
Mike

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


On Tue, Jan 24, 2017 at 11:58 AM, Michael Gogins
 wrote:
> My existing html player allows the user to edit the csd example, but
> does not save the edited version of the example.
>
> In addition, most examples use mono but only stereo examples were
> working, last time I checked. But this may now have changed because of
> changes to the output opcodes. I will check.
>
> I see no reason to maintain two versions of this thing. If you are
> willing to maintain yours I am happy to remove mine.
>
> Regards,
> Mike
>
> -----------------------------------------------------
> Michael Gogins
> Irreducible Productions
> http://michaelgogins.tumblr.com
> Michael dot Gogins at gmail dot com
>
>
> On Tue, Jan 24, 2017 at 11:39 AM, Ed Costello  wrote:
>> Hi,
>>
>> I have started 2 projects which may be of interest. A web component for
>> Csound that can play and edit .csd files (using either pnacl or emscripten),
>> and a manual parser which converts, or will in theory convert, docbook xml
>> opcode pages to html using Asciidoctor which includes the web component.
>>
>> I am aware that there is an online version of the manual which will also
>> allow the playing of .csd files, but I thought I would give it a go as my
>> idea was to have a text editor and the player engine embedded directly in
>> the manual page.
>>
>> The csound web component player is here
>> https://github.com/eddyc/csound-player/
>>
>> The manual to html project is here https://github.com/eddyc/csound-manual/
>>
>> I also have an example of a finished html manual page with the embedded csd
>> player at
>>
>> https://eddyc.github.io/csound-manual/opcodes/areson.html
>>
>> there are a number of things unfinished here of course but I think it shows
>> the potential of having such a player embedded directly in a manual page
>> with an editor. I think another benefit of this approach is that the docbook
>> xml files are converted to asciidoctor markup, which is very similar to
>> markdown, and shows how it could be a lot simpler to make manual pages, and
>> pages that are clearly legible in their source form inside of a text editor.
>>
>> Cheers

Yeah, 
I am using the latest release of both, I think though that the Pnacl version doesn’t allow single channel outputs?
Ed

> On 24 Jan 2017, at 17:04, Michael Gogins  wrote:
> 
> I went to your example page, and edited the example to output one
> channel. It did not work. I assume you are using a more recent version
> of the PNaCl or Emscripten build than my playable manual does.
> 
> I think the best fix here would be to change, not the manual page
> code, but rather the JavaScript wrapper code.
> 
> Regards,
> Mike
> 
> -----------------------------------------------------
> Michael Gogins
> Irreducible Productions
> http://michaelgogins.tumblr.com
> Michael dot Gogins at gmail dot com
> 
> 
> On Tue, Jan 24, 2017 at 11:58 AM, Michael Gogins
>  wrote:
>> My existing html player allows the user to edit the csd example, but
>> does not save the edited version of the example.
>> 
>> In addition, most examples use mono but only stereo examples were
>> working, last time I checked. But this may now have changed because of
>> changes to the output opcodes. I will check.
>> 
>> I see no reason to maintain two versions of this thing. If you are
>> willing to maintain yours I am happy to remove mine.
>> 
>> Regards,
>> Mike
>> 
>> -----------------------------------------------------
>> Michael Gogins
>> Irreducible Productions
>> http://michaelgogins.tumblr.com
>> Michael dot Gogins at gmail dot com
>> 
>> 
>> On Tue, Jan 24, 2017 at 11:39 AM, Ed Costello  wrote:
>>> Hi,
>>> 
>>> I have started 2 projects which may be of interest. A web component for
>>> Csound that can play and edit .csd files (using either pnacl or emscripten),
>>> and a manual parser which converts, or will in theory convert, docbook xml
>>> opcode pages to html using Asciidoctor which includes the web component.
>>> 
>>> I am aware that there is an online version of the manual which will also
>>> allow the playing of .csd files, but I thought I would give it a go as my
>>> idea was to have a text editor and the player engine embedded directly in
>>> the manual page.
>>> 
>>> The csound web component player is here
>>> https://github.com/eddyc/csound-player/
>>> 
>>> The manual to html project is here https://github.com/eddyc/csound-manual/
>>> 
>>> I also have an example of a finished html manual page with the embedded csd
>>> player at
>>> 
>>> https://eddyc.github.io/csound-manual/opcodes/areson.html
>>> 
>>> there are a number of things unfinished here of course but I think it shows
>>> the potential of having such a player embedded directly in a manual page
>>> with an editor. I think another benefit of this approach is that the docbook
>>> xml files are converted to asciidoctor markup, which is very similar to
>>> markdown, and shows how it could be a lot simpler to make manual pages, and
>>> pages that are clearly legible in their source form inside of a text editor.
>>> 
>>> Cheers

But the PNaCl code should be changed to always adapt to the host channel count.

Regards,
Mike

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


On Tue, Jan 24, 2017 at 12:17 PM, Ed Costello  wrote:
> Yeah,
> I am using the latest release of both, I think though that the Pnacl version doesn’t allow single channel outputs?
> Ed
>
>> On 24 Jan 2017, at 17:04, Michael Gogins  wrote:
>>
>> I went to your example page, and edited the example to output one
>> channel. It did not work. I assume you are using a more recent version
>> of the PNaCl or Emscripten build than my playable manual does.
>>
>> I think the best fix here would be to change, not the manual page
>> code, but rather the JavaScript wrapper code.
>>
>> Regards,
>> Mike
>>
>> -----------------------------------------------------
>> Michael Gogins
>> Irreducible Productions
>> http://michaelgogins.tumblr.com
>> Michael dot Gogins at gmail dot com
>>
>>
>> On Tue, Jan 24, 2017 at 11:58 AM, Michael Gogins
>>  wrote:
>>> My existing html player allows the user to edit the csd example, but
>>> does not save the edited version of the example.
>>>
>>> In addition, most examples use mono but only stereo examples were
>>> working, last time I checked. But this may now have changed because of
>>> changes to the output opcodes. I will check.
>>>
>>> I see no reason to maintain two versions of this thing. If you are
>>> willing to maintain yours I am happy to remove mine.
>>>
>>> Regards,
>>> Mike
>>>
>>> -----------------------------------------------------
>>> Michael Gogins
>>> Irreducible Productions
>>> http://michaelgogins.tumblr.com
>>> Michael dot Gogins at gmail dot com
>>>
>>>
>>> On Tue, Jan 24, 2017 at 11:39 AM, Ed Costello  wrote:
>>>> Hi,
>>>>
>>>> I have started 2 projects which may be of interest. A web component for
>>>> Csound that can play and edit .csd files (using either pnacl or emscripten),
>>>> and a manual parser which converts, or will in theory convert, docbook xml
>>>> opcode pages to html using Asciidoctor which includes the web component.
>>>>
>>>> I am aware that there is an online version of the manual which will also
>>>> allow the playing of .csd files, but I thought I would give it a go as my
>>>> idea was to have a text editor and the player engine embedded directly in
>>>> the manual page.
>>>>
>>>> The csound web component player is here
>>>> https://github.com/eddyc/csound-player/
>>>>
>>>> The manual to html project is here https://github.com/eddyc/csound-manual/
>>>>
>>>> I also have an example of a finished html manual page with the embedded csd
>>>> player at
>>>>
>>>> https://eddyc.github.io/csound-manual/opcodes/areson.html
>>>>
>>>> there are a number of things unfinished here of course but I think it shows
>>>> the potential of having such a player embedded directly in a manual page
>>>> with an editor. I think another benefit of this approach is that the docbook
>>>> xml files are converted to asciidoctor markup, which is very similar to
>>>> markdown, and shows how it could be a lot simpler to make manual pages, and
>>>> pages that are clearly legible in their source form inside of a text editor.
>>>>
>>>> Cheers

Afaik, channels are fixed to stereo by Pepper.

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

> On 24 Jan 2017, at 17:29, Michael Gogins  wrote:
> 
> But the PNaCl code should be changed to always adapt to the host channel count.
> 
> Regards,
> Mike
> 
> -----------------------------------------------------
> Michael Gogins
> Irreducible Productions
> http://michaelgogins.tumblr.com
> Michael dot Gogins at gmail dot com
> 
> 
>> On Tue, Jan 24, 2017 at 12:17 PM, Ed Costello  wrote:
>> Yeah,
>> I am using the latest release of both, I think though that the Pnacl version doesn’t allow single channel outputs?
>> Ed
>> 
>>> On 24 Jan 2017, at 17:04, Michael Gogins  wrote:
>>> 
>>> I went to your example page, and edited the example to output one
>>> channel. It did not work. I assume you are using a more recent version
>>> of the PNaCl or Emscripten build than my playable manual does.
>>> 
>>> I think the best fix here would be to change, not the manual page
>>> code, but rather the JavaScript wrapper code.
>>> 
>>> Regards,
>>> Mike
>>> 
>>> -----------------------------------------------------
>>> Michael Gogins
>>> Irreducible Productions
>>> http://michaelgogins.tumblr.com
>>> Michael dot Gogins at gmail dot com
>>> 
>>> 
>>> On Tue, Jan 24, 2017 at 11:58 AM, Michael Gogins
>>>  wrote:
>>>> My existing html player allows the user to edit the csd example, but
>>>> does not save the edited version of the example.
>>>> 
>>>> In addition, most examples use mono but only stereo examples were
>>>> working, last time I checked. But this may now have changed because of
>>>> changes to the output opcodes. I will check.
>>>> 
>>>> I see no reason to maintain two versions of this thing. If you are
>>>> willing to maintain yours I am happy to remove mine.
>>>> 
>>>> Regards,
>>>> Mike
>>>> 
>>>> -----------------------------------------------------
>>>> Michael Gogins
>>>> Irreducible Productions
>>>> http://michaelgogins.tumblr.com
>>>> Michael dot Gogins at gmail dot com
>>>> 
>>>> 
>>>>> On Tue, Jan 24, 2017 at 11:39 AM, Ed Costello  wrote:
>>>>> Hi,
>>>>> 
>>>>> I have started 2 projects which may be of interest. A web component for
>>>>> Csound that can play and edit .csd files (using either pnacl or emscripten),
>>>>> and a manual parser which converts, or will in theory convert, docbook xml
>>>>> opcode pages to html using Asciidoctor which includes the web component.
>>>>> 
>>>>> I am aware that there is an online version of the manual which will also
>>>>> allow the playing of .csd files, but I thought I would give it a go as my
>>>>> idea was to have a text editor and the player engine embedded directly in
>>>>> the manual page.
>>>>> 
>>>>> The csound web component player is here
>>>>> https://github.com/eddyc/csound-player/
>>>>> 
>>>>> The manual to html project is here https://github.com/eddyc/csound-manual/
>>>>> 
>>>>> I also have an example of a finished html manual page with the embedded csd
>>>>> player at
>>>>> 
>>>>> https://eddyc.github.io/csound-manual/opcodes/areson.html
>>>>> 
>>>>> there are a number of things unfinished here of course but I think it shows
>>>>> the potential of having such a player embedded directly in a manual page
>>>>> with an editor. I think another benefit of this approach is that the docbook
>>>>> xml files are converted to asciidoctor markup, which is very similar to
>>>>> markdown, and shows how it could be a lot simpler to make manual pages, and
>>>>> pages that are clearly legible in their source form inside of a text editor.
>>>>> 
>>>>> Cheers

Of course. So Csound should adapt to Pepper, that being the host --
that is what I said,

Regards,
Mike


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


On Tue, Jan 24, 2017 at 1:28 PM, Victor Lazzarini
 wrote:
> Afaik, channels are fixed to stereo by Pepper.
>
> Victor Lazzarini
> Dean of Arts, Celtic Studies, and Philosophy
> Maynooth University
> Ireland
>
>> On 24 Jan 2017, at 17:29, Michael Gogins  wrote:
>>
>> But the PNaCl code should be changed to always adapt to the host channel count.
>>
>> Regards,
>> Mike
>>
>> -----------------------------------------------------
>> Michael Gogins
>> Irreducible Productions
>> http://michaelgogins.tumblr.com
>> Michael dot Gogins at gmail dot com
>>
>>
>>> On Tue, Jan 24, 2017 at 12:17 PM, Ed Costello  wrote:
>>> Yeah,
>>> I am using the latest release of both, I think though that the Pnacl version doesn’t allow single channel outputs?
>>> Ed
>>>
>>>> On 24 Jan 2017, at 17:04, Michael Gogins  wrote:
>>>>
>>>> I went to your example page, and edited the example to output one
>>>> channel. It did not work. I assume you are using a more recent version
>>>> of the PNaCl or Emscripten build than my playable manual does.
>>>>
>>>> I think the best fix here would be to change, not the manual page
>>>> code, but rather the JavaScript wrapper code.
>>>>
>>>> Regards,
>>>> Mike
>>>>
>>>> -----------------------------------------------------
>>>> Michael Gogins
>>>> Irreducible Productions
>>>> http://michaelgogins.tumblr.com
>>>> Michael dot Gogins at gmail dot com
>>>>
>>>>
>>>> On Tue, Jan 24, 2017 at 11:58 AM, Michael Gogins
>>>>  wrote:
>>>>> My existing html player allows the user to edit the csd example, but
>>>>> does not save the edited version of the example.
>>>>>
>>>>> In addition, most examples use mono but only stereo examples were
>>>>> working, last time I checked. But this may now have changed because of
>>>>> changes to the output opcodes. I will check.
>>>>>
>>>>> I see no reason to maintain two versions of this thing. If you are
>>>>> willing to maintain yours I am happy to remove mine.
>>>>>
>>>>> Regards,
>>>>> Mike
>>>>>
>>>>> -----------------------------------------------------
>>>>> Michael Gogins
>>>>> Irreducible Productions
>>>>> http://michaelgogins.tumblr.com
>>>>> Michael dot Gogins at gmail dot com
>>>>>
>>>>>
>>>>>> On Tue, Jan 24, 2017 at 11:39 AM, Ed Costello  wrote:
>>>>>> Hi,
>>>>>>
>>>>>> I have started 2 projects which may be of interest. A web component for
>>>>>> Csound that can play and edit .csd files (using either pnacl or emscripten),
>>>>>> and a manual parser which converts, or will in theory convert, docbook xml
>>>>>> opcode pages to html using Asciidoctor which includes the web component.
>>>>>>
>>>>>> I am aware that there is an online version of the manual which will also
>>>>>> allow the playing of .csd files, but I thought I would give it a go as my
>>>>>> idea was to have a text editor and the player engine embedded directly in
>>>>>> the manual page.
>>>>>>
>>>>>> The csound web component player is here
>>>>>> https://github.com/eddyc/csound-player/
>>>>>>
>>>>>> The manual to html project is here https://github.com/eddyc/csound-manual/
>>>>>>
>>>>>> I also have an example of a finished html manual page with the embedded csd
>>>>>> player at
>>>>>>
>>>>>> https://eddyc.github.io/csound-manual/opcodes/areson.html
>>>>>>
>>>>>> there are a number of things unfinished here of course but I think it shows
>>>>>> the potential of having such a player embedded directly in a manual page
>>>>>> with an editor. I think another benefit of this approach is that the docbook
>>>>>> xml files are converted to asciidoctor markup, which is very similar to
>>>>>> markdown, and shows how it could be a lot simpler to make manual pages, and
>>>>>> pages that are clearly legible in their source form inside of a text editor.
>>>>>>
>>>>>> Cheers

that it does. Not sure what the question was.

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

> On 24 Jan 2017, at 18:43, Michael Gogins  wrote:
> 
> Of course. So Csound should adapt to Pepper, that being the host --
> that is what I said,
> 
> Regards,
> Mike
> 
> 
> -----------------------------------------------------
> Michael Gogins
> Irreducible Productions
> http://michaelgogins.tumblr.com
> Michael dot Gogins at gmail dot com
> 
> 
> On Tue, Jan 24, 2017 at 1:28 PM, Victor Lazzarini
>  wrote:
>> Afaik, channels are fixed to stereo by Pepper.
>> 
>> Victor Lazzarini
>> Dean of Arts, Celtic Studies, and Philosophy
>> Maynooth University
>> Ireland
>> 
>>> On 24 Jan 2017, at 17:29, Michael Gogins  wrote:
>>> 
>>> But the PNaCl code should be changed to always adapt to the host channel count.
>>> 
>>> Regards,
>>> Mike
>>> 
>>> -----------------------------------------------------
>>> Michael Gogins
>>> Irreducible Productions
>>> http://michaelgogins.tumblr.com
>>> Michael dot Gogins at gmail dot com
>>> 
>>> 
>>>> On Tue, Jan 24, 2017 at 12:17 PM, Ed Costello  wrote:
>>>> Yeah,
>>>> I am using the latest release of both, I think though that the Pnacl version doesn’t allow single channel outputs?
>>>> Ed
>>>> 
>>>>> On 24 Jan 2017, at 17:04, Michael Gogins  wrote:
>>>>> 
>>>>> I went to your example page, and edited the example to output one
>>>>> channel. It did not work. I assume you are using a more recent version
>>>>> of the PNaCl or Emscripten build than my playable manual does.
>>>>> 
>>>>> I think the best fix here would be to change, not the manual page
>>>>> code, but rather the JavaScript wrapper code.
>>>>> 
>>>>> Regards,
>>>>> Mike
>>>>> 
>>>>> -----------------------------------------------------
>>>>> Michael Gogins
>>>>> Irreducible Productions
>>>>> http://michaelgogins.tumblr.com
>>>>> Michael dot Gogins at gmail dot com
>>>>> 
>>>>> 
>>>>> On Tue, Jan 24, 2017 at 11:58 AM, Michael Gogins
>>>>>  wrote:
>>>>>> My existing html player allows the user to edit the csd example, but
>>>>>> does not save the edited version of the example.
>>>>>> 
>>>>>> In addition, most examples use mono but only stereo examples were
>>>>>> working, last time I checked. But this may now have changed because of
>>>>>> changes to the output opcodes. I will check.
>>>>>> 
>>>>>> I see no reason to maintain two versions of this thing. If you are
>>>>>> willing to maintain yours I am happy to remove mine.
>>>>>> 
>>>>>> Regards,
>>>>>> Mike
>>>>>> 
>>>>>> -----------------------------------------------------
>>>>>> Michael Gogins
>>>>>> Irreducible Productions
>>>>>> http://michaelgogins.tumblr.com
>>>>>> Michael dot Gogins at gmail dot com
>>>>>> 
>>>>>> 
>>>>>>> On Tue, Jan 24, 2017 at 11:39 AM, Ed Costello  wrote:
>>>>>>> Hi,
>>>>>>> 
>>>>>>> I have started 2 projects which may be of interest. A web component for
>>>>>>> Csound that can play and edit .csd files (using either pnacl or emscripten),
>>>>>>> and a manual parser which converts, or will in theory convert, docbook xml
>>>>>>> opcode pages to html using Asciidoctor which includes the web component.
>>>>>>> 
>>>>>>> I am aware that there is an online version of the manual which will also
>>>>>>> allow the playing of .csd files, but I thought I would give it a go as my
>>>>>>> idea was to have a text editor and the player engine embedded directly in
>>>>>>> the manual page.
>>>>>>> 
>>>>>>> The csound web component player is here
>>>>>>> https://github.com/eddyc/csound-player/
>>>>>>> 
>>>>>>> The manual to html project is here https://github.com/eddyc/csound-manual/
>>>>>>> 
>>>>>>> I also have an example of a finished html manual page with the embedded csd
>>>>>>> player at
>>>>>>> 
>>>>>>> https://eddyc.github.io/csound-manual/opcodes/areson.html
>>>>>>> 
>>>>>>> there are a number of things unfinished here of course but I think it shows
>>>>>>> the potential of having such a player embedded directly in a manual page
>>>>>>> with an editor. I think another benefit of this approach is that the docbook
>>>>>>> xml files are converted to asciidoctor markup, which is very similar to
>>>>>>> markdown, and shows how it could be a lot simpler to make manual pages, and
>>>>>>> pages that are clearly legible in their source form inside of a text editor.
>>>>>>> 
>>>>>>> Cheers

It does not. Did you try the example?

Go to https://eddyc.github.io/csound-manual/opcodes/areson.html and
edit the orc to use "nchnls = 1" instead of "nchnls  = 2" and "out
afil" instead of "outs afil, afil", then run it and see what happens.
It should work anyway.

Regards,
Mike

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


On Tue, Jan 24, 2017 at 3:14 PM, Victor Lazzarini
 wrote:
> that it does. Not sure what the question was.
>
> Victor Lazzarini
> Dean of Arts, Celtic Studies, and Philosophy
> Maynooth University
> Ireland
>
>> On 24 Jan 2017, at 18:43, Michael Gogins  wrote:
>>
>> Of course. So Csound should adapt to Pepper, that being the host --
>> that is what I said,
>>
>> Regards,
>> Mike
>>
>>
>> -----------------------------------------------------
>> Michael Gogins
>> Irreducible Productions
>> http://michaelgogins.tumblr.com
>> Michael dot Gogins at gmail dot com
>>
>>
>> On Tue, Jan 24, 2017 at 1:28 PM, Victor Lazzarini
>>  wrote:
>>> Afaik, channels are fixed to stereo by Pepper.
>>>
>>> Victor Lazzarini
>>> Dean of Arts, Celtic Studies, and Philosophy
>>> Maynooth University
>>> Ireland
>>>
>>>> On 24 Jan 2017, at 17:29, Michael Gogins  wrote:
>>>>
>>>> But the PNaCl code should be changed to always adapt to the host channel count.
>>>>
>>>> Regards,
>>>> Mike
>>>>
>>>> -----------------------------------------------------
>>>> Michael Gogins
>>>> Irreducible Productions
>>>> http://michaelgogins.tumblr.com
>>>> Michael dot Gogins at gmail dot com
>>>>
>>>>
>>>>> On Tue, Jan 24, 2017 at 12:17 PM, Ed Costello  wrote:
>>>>> Yeah,
>>>>> I am using the latest release of both, I think though that the Pnacl version doesn’t allow single channel outputs?
>>>>> Ed
>>>>>
>>>>>> On 24 Jan 2017, at 17:04, Michael Gogins  wrote:
>>>>>>
>>>>>> I went to your example page, and edited the example to output one
>>>>>> channel. It did not work. I assume you are using a more recent version
>>>>>> of the PNaCl or Emscripten build than my playable manual does.
>>>>>>
>>>>>> I think the best fix here would be to change, not the manual page
>>>>>> code, but rather the JavaScript wrapper code.
>>>>>>
>>>>>> Regards,
>>>>>> Mike
>>>>>>
>>>>>> -----------------------------------------------------
>>>>>> Michael Gogins
>>>>>> Irreducible Productions
>>>>>> http://michaelgogins.tumblr.com
>>>>>> Michael dot Gogins at gmail dot com
>>>>>>
>>>>>>
>>>>>> On Tue, Jan 24, 2017 at 11:58 AM, Michael Gogins
>>>>>>  wrote:
>>>>>>> My existing html player allows the user to edit the csd example, but
>>>>>>> does not save the edited version of the example.
>>>>>>>
>>>>>>> In addition, most examples use mono but only stereo examples were
>>>>>>> working, last time I checked. But this may now have changed because of
>>>>>>> changes to the output opcodes. I will check.
>>>>>>>
>>>>>>> I see no reason to maintain two versions of this thing. If you are
>>>>>>> willing to maintain yours I am happy to remove mine.
>>>>>>>
>>>>>>> Regards,
>>>>>>> Mike
>>>>>>>
>>>>>>> -----------------------------------------------------
>>>>>>> Michael Gogins
>>>>>>> Irreducible Productions
>>>>>>> http://michaelgogins.tumblr.com
>>>>>>> Michael dot Gogins at gmail dot com
>>>>>>>
>>>>>>>
>>>>>>>> On Tue, Jan 24, 2017 at 11:39 AM, Ed Costello  wrote:
>>>>>>>> Hi,
>>>>>>>>
>>>>>>>> I have started 2 projects which may be of interest. A web component for
>>>>>>>> Csound that can play and edit .csd files (using either pnacl or emscripten),
>>>>>>>> and a manual parser which converts, or will in theory convert, docbook xml
>>>>>>>> opcode pages to html using Asciidoctor which includes the web component.
>>>>>>>>
>>>>>>>> I am aware that there is an online version of the manual which will also
>>>>>>>> allow the playing of .csd files, but I thought I would give it a go as my
>>>>>>>> idea was to have a text editor and the player engine embedded directly in
>>>>>>>> the manual page.
>>>>>>>>
>>>>>>>> The csound web component player is here
>>>>>>>> https://github.com/eddyc/csound-player/
>>>>>>>>
>>>>>>>> The manual to html project is here https://github.com/eddyc/csound-manual/
>>>>>>>>
>>>>>>>> I also have an example of a finished html manual page with the embedded csd
>>>>>>>> player at
>>>>>>>>
>>>>>>>> https://eddyc.github.io/csound-manual/opcodes/areson.html
>>>>>>>>
>>>>>>>> there are a number of things unfinished here of course but I think it shows
>>>>>>>> the potential of having such a player embedded directly in a manual page
>>>>>>>> with an editor. I think another benefit of this approach is that the docbook
>>>>>>>> xml files are converted to asciidoctor markup, which is very similar to
>>>>>>>> markdown, and shows how it could be a lot simpler to make manual pages, and
>>>>>>>> pages that are clearly legible in their source form inside of a text editor.
>>>>>>>>
>>>>>>>> Cheers

I tried that and got 

Compiling CSD text...
Compiled.
Csound error: only stereo output is supported 

Ed

> On 24 Jan 2017, at 23:05, Michael Gogins  wrote:
> 
> It does not. Did you try the example?
> 
> Go to https://eddyc.github.io/csound-manual/opcodes/areson.html and
> edit the orc to use "nchnls = 1" instead of "nchnls  = 2" and "out
> afil" instead of "outs afil, afil", then run it and see what happens.
> It should work anyway.
> 
> Regards,
> Mike
> 
> -----------------------------------------------------
> Michael Gogins
> Irreducible Productions
> http://michaelgogins.tumblr.com
> Michael dot Gogins at gmail dot com
> 
> 
> On Tue, Jan 24, 2017 at 3:14 PM, Victor Lazzarini
>  wrote:
>> that it does. Not sure what the question was.
>> 
>> Victor Lazzarini
>> Dean of Arts, Celtic Studies, and Philosophy
>> Maynooth University
>> Ireland
>> 
>>> On 24 Jan 2017, at 18:43, Michael Gogins  wrote:
>>> 
>>> Of course. So Csound should adapt to Pepper, that being the host --
>>> that is what I said,
>>> 
>>> Regards,
>>> Mike
>>> 
>>> 
>>> -----------------------------------------------------
>>> Michael Gogins
>>> Irreducible Productions
>>> http://michaelgogins.tumblr.com
>>> Michael dot Gogins at gmail dot com
>>> 
>>> 
>>> On Tue, Jan 24, 2017 at 1:28 PM, Victor Lazzarini
>>>  wrote:
>>>> Afaik, channels are fixed to stereo by Pepper.
>>>> 
>>>> Victor Lazzarini
>>>> Dean of Arts, Celtic Studies, and Philosophy
>>>> Maynooth University
>>>> Ireland
>>>> 
>>>>> On 24 Jan 2017, at 17:29, Michael Gogins  wrote:
>>>>> 
>>>>> But the PNaCl code should be changed to always adapt to the host channel count.
>>>>> 
>>>>> Regards,
>>>>> Mike
>>>>> 
>>>>> -----------------------------------------------------
>>>>> Michael Gogins
>>>>> Irreducible Productions
>>>>> http://michaelgogins.tumblr.com
>>>>> Michael dot Gogins at gmail dot com
>>>>> 
>>>>> 
>>>>>> On Tue, Jan 24, 2017 at 12:17 PM, Ed Costello  wrote:
>>>>>> Yeah,
>>>>>> I am using the latest release of both, I think though that the Pnacl version doesn’t allow single channel outputs?
>>>>>> Ed
>>>>>> 
>>>>>>> On 24 Jan 2017, at 17:04, Michael Gogins  wrote:
>>>>>>> 
>>>>>>> I went to your example page, and edited the example to output one
>>>>>>> channel. It did not work. I assume you are using a more recent version
>>>>>>> of the PNaCl or Emscripten build than my playable manual does.
>>>>>>> 
>>>>>>> I think the best fix here would be to change, not the manual page
>>>>>>> code, but rather the JavaScript wrapper code.
>>>>>>> 
>>>>>>> Regards,
>>>>>>> Mike
>>>>>>> 
>>>>>>> -----------------------------------------------------
>>>>>>> Michael Gogins
>>>>>>> Irreducible Productions
>>>>>>> http://michaelgogins.tumblr.com
>>>>>>> Michael dot Gogins at gmail dot com
>>>>>>> 
>>>>>>> 
>>>>>>> On Tue, Jan 24, 2017 at 11:58 AM, Michael Gogins
>>>>>>>  wrote:
>>>>>>>> My existing html player allows the user to edit the csd example, but
>>>>>>>> does not save the edited version of the example.
>>>>>>>> 
>>>>>>>> In addition, most examples use mono but only stereo examples were
>>>>>>>> working, last time I checked. But this may now have changed because of
>>>>>>>> changes to the output opcodes. I will check.
>>>>>>>> 
>>>>>>>> I see no reason to maintain two versions of this thing. If you are
>>>>>>>> willing to maintain yours I am happy to remove mine.
>>>>>>>> 
>>>>>>>> Regards,
>>>>>>>> Mike
>>>>>>>> 
>>>>>>>> -----------------------------------------------------
>>>>>>>> Michael Gogins
>>>>>>>> Irreducible Productions
>>>>>>>> http://michaelgogins.tumblr.com
>>>>>>>> Michael dot Gogins at gmail dot com
>>>>>>>> 
>>>>>>>> 
>>>>>>>>> On Tue, Jan 24, 2017 at 11:39 AM, Ed Costello  wrote:
>>>>>>>>> Hi,
>>>>>>>>> 
>>>>>>>>> I have started 2 projects which may be of interest. A web component for
>>>>>>>>> Csound that can play and edit .csd files (using either pnacl or emscripten),
>>>>>>>>> and a manual parser which converts, or will in theory convert, docbook xml
>>>>>>>>> opcode pages to html using Asciidoctor which includes the web component.
>>>>>>>>> 
>>>>>>>>> I am aware that there is an online version of the manual which will also
>>>>>>>>> allow the playing of .csd files, but I thought I would give it a go as my
>>>>>>>>> idea was to have a text editor and the player engine embedded directly in
>>>>>>>>> the manual page.
>>>>>>>>> 
>>>>>>>>> The csound web component player is here
>>>>>>>>> https://github.com/eddyc/csound-player/
>>>>>>>>> 
>>>>>>>>> The manual to html project is here https://github.com/eddyc/csound-manual/
>>>>>>>>> 
>>>>>>>>> I also have an example of a finished html manual page with the embedded csd
>>>>>>>>> player at
>>>>>>>>> 
>>>>>>>>> https://eddyc.github.io/csound-manual/opcodes/areson.html
>>>>>>>>> 
>>>>>>>>> there are a number of things unfinished here of course but I think it shows
>>>>>>>>> the potential of having such a player embedded directly in a manual page
>>>>>>>>> with an editor. I think another benefit of this approach is that the docbook
>>>>>>>>> xml files are converted to asciidoctor markup, which is very similar to
>>>>>>>>> markdown, and shows how it could be a lot simpler to make manual pages, and
>>>>>>>>> pages that are clearly legible in their source form inside of a text editor.
>>>>>>>>> 
>>>>>>>>> Cheers

My remarks were a response to Victor's question.

Regards,
Mike

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


On Tue, Jan 24, 2017 at 6:42 PM, Ed Costello  wrote:
> I tried that and got
>
> Compiling CSD text...
> Compiled.
> Csound error: only stereo output is supported
>
> Ed
>
>> On 24 Jan 2017, at 23:05, Michael Gogins  wrote:
>>
>> It does not. Did you try the example?
>>
>> Go to https://eddyc.github.io/csound-manual/opcodes/areson.html and
>> edit the orc to use "nchnls = 1" instead of "nchnls  = 2" and "out
>> afil" instead of "outs afil, afil", then run it and see what happens.
>> It should work anyway.
>>
>> Regards,
>> Mike
>>
>> -----------------------------------------------------
>> Michael Gogins
>> Irreducible Productions
>> http://michaelgogins.tumblr.com
>> Michael dot Gogins at gmail dot com
>>
>>
>> On Tue, Jan 24, 2017 at 3:14 PM, Victor Lazzarini
>>  wrote:
>>> that it does. Not sure what the question was.
>>>
>>> Victor Lazzarini
>>> Dean of Arts, Celtic Studies, and Philosophy
>>> Maynooth University
>>> Ireland
>>>
>>>> On 24 Jan 2017, at 18:43, Michael Gogins  wrote:
>>>>
>>>> Of course. So Csound should adapt to Pepper, that being the host --
>>>> that is what I said,
>>>>
>>>> Regards,
>>>> Mike
>>>>
>>>>
>>>> -----------------------------------------------------
>>>> Michael Gogins
>>>> Irreducible Productions
>>>> http://michaelgogins.tumblr.com
>>>> Michael dot Gogins at gmail dot com
>>>>
>>>>
>>>> On Tue, Jan 24, 2017 at 1:28 PM, Victor Lazzarini
>>>>  wrote:
>>>>> Afaik, channels are fixed to stereo by Pepper.
>>>>>
>>>>> Victor Lazzarini
>>>>> Dean of Arts, Celtic Studies, and Philosophy
>>>>> Maynooth University
>>>>> Ireland
>>>>>
>>>>>> On 24 Jan 2017, at 17:29, Michael Gogins  wrote:
>>>>>>
>>>>>> But the PNaCl code should be changed to always adapt to the host channel count.
>>>>>>
>>>>>> Regards,
>>>>>> Mike
>>>>>>
>>>>>> -----------------------------------------------------
>>>>>> Michael Gogins
>>>>>> Irreducible Productions
>>>>>> http://michaelgogins.tumblr.com
>>>>>> Michael dot Gogins at gmail dot com
>>>>>>
>>>>>>
>>>>>>> On Tue, Jan 24, 2017 at 12:17 PM, Ed Costello  wrote:
>>>>>>> Yeah,
>>>>>>> I am using the latest release of both, I think though that the Pnacl version doesn’t allow single channel outputs?
>>>>>>> Ed
>>>>>>>
>>>>>>>> On 24 Jan 2017, at 17:04, Michael Gogins  wrote:
>>>>>>>>
>>>>>>>> I went to your example page, and edited the example to output one
>>>>>>>> channel. It did not work. I assume you are using a more recent version
>>>>>>>> of the PNaCl or Emscripten build than my playable manual does.
>>>>>>>>
>>>>>>>> I think the best fix here would be to change, not the manual page
>>>>>>>> code, but rather the JavaScript wrapper code.
>>>>>>>>
>>>>>>>> Regards,
>>>>>>>> Mike
>>>>>>>>
>>>>>>>> -----------------------------------------------------
>>>>>>>> Michael Gogins
>>>>>>>> Irreducible Productions
>>>>>>>> http://michaelgogins.tumblr.com
>>>>>>>> Michael dot Gogins at gmail dot com
>>>>>>>>
>>>>>>>>
>>>>>>>> On Tue, Jan 24, 2017 at 11:58 AM, Michael Gogins
>>>>>>>>  wrote:
>>>>>>>>> My existing html player allows the user to edit the csd example, but
>>>>>>>>> does not save the edited version of the example.
>>>>>>>>>
>>>>>>>>> In addition, most examples use mono but only stereo examples were
>>>>>>>>> working, last time I checked. But this may now have changed because of
>>>>>>>>> changes to the output opcodes. I will check.
>>>>>>>>>
>>>>>>>>> I see no reason to maintain two versions of this thing. If you are
>>>>>>>>> willing to maintain yours I am happy to remove mine.
>>>>>>>>>
>>>>>>>>> Regards,
>>>>>>>>> Mike
>>>>>>>>>
>>>>>>>>> -----------------------------------------------------
>>>>>>>>> Michael Gogins
>>>>>>>>> Irreducible Productions
>>>>>>>>> http://michaelgogins.tumblr.com
>>>>>>>>> Michael dot Gogins at gmail dot com
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>> On Tue, Jan 24, 2017 at 11:39 AM, Ed Costello  wrote:
>>>>>>>>>> Hi,
>>>>>>>>>>
>>>>>>>>>> I have started 2 projects which may be of interest. A web component for
>>>>>>>>>> Csound that can play and edit .csd files (using either pnacl or emscripten),
>>>>>>>>>> and a manual parser which converts, or will in theory convert, docbook xml
>>>>>>>>>> opcode pages to html using Asciidoctor which includes the web component.
>>>>>>>>>>
>>>>>>>>>> I am aware that there is an online version of the manual which will also
>>>>>>>>>> allow the playing of .csd files, but I thought I would give it a go as my
>>>>>>>>>> idea was to have a text editor and the player engine embedded directly in
>>>>>>>>>> the manual page.
>>>>>>>>>>
>>>>>>>>>> The csound web component player is here
>>>>>>>>>> https://github.com/eddyc/csound-player/
>>>>>>>>>>
>>>>>>>>>> The manual to html project is here https://github.com/eddyc/csound-manual/
>>>>>>>>>>
>>>>>>>>>> I also have an example of a finished html manual page with the embedded csd
>>>>>>>>>> player at
>>>>>>>>>>
>>>>>>>>>> https://eddyc.github.io/csound-manual/opcodes/areson.html
>>>>>>>>>>
>>>>>>>>>> there are a number of things unfinished here of course but I think it shows
>>>>>>>>>> the potential of having such a player embedded directly in a manual page
>>>>>>>>>> with an editor. I think another benefit of this approach is that the docbook
>>>>>>>>>> xml files are converted to asciidoctor markup, which is very similar to
>>>>>>>>>> markdown, and shows how it could be a lot simpler to make manual pages, and
>>>>>>>>>> pages that are clearly legible in their source form inside of a text editor.
>>>>>>>>>>
>>>>>>>>>> Cheers

yes, that is what I said. You can override nchnls using --nchnls=2

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

> On 24 Jan 2017, at 23:43, Ed Costello  wrote:
> 
> I tried that and got 
> 
> Compiling CSD text...
> Compiled.
> Csound error: only stereo output is supported 
> 
> Ed
> 
>> On 24 Jan 2017, at 23:05, Michael Gogins  wrote:
>> 
>> It does not. Did you try the example?
>> 
>> Go to https://eddyc.github.io/csound-manual/opcodes/areson.html and
>> edit the orc to use "nchnls = 1" instead of "nchnls  = 2" and "out
>> afil" instead of "outs afil, afil", then run it and see what happens.
>> It should work anyway.
>> 
>> Regards,
>> Mike
>> 
>> -----------------------------------------------------
>> Michael Gogins
>> Irreducible Productions
>> http://michaelgogins.tumblr.com
>> Michael dot Gogins at gmail dot com
>> 
>> 
>> On Tue, Jan 24, 2017 at 3:14 PM, Victor Lazzarini
>>  wrote:
>>> that it does. Not sure what the question was.
>>> 
>>> Victor Lazzarini
>>> Dean of Arts, Celtic Studies, and Philosophy
>>> Maynooth University
>>> Ireland
>>> 
>>>> On 24 Jan 2017, at 18:43, Michael Gogins  wrote:
>>>> 
>>>> Of course. So Csound should adapt to Pepper, that being the host --
>>>> that is what I said,
>>>> 
>>>> Regards,
>>>> Mike
>>>> 
>>>> 
>>>> -----------------------------------------------------
>>>> Michael Gogins
>>>> Irreducible Productions
>>>> http://michaelgogins.tumblr.com
>>>> Michael dot Gogins at gmail dot com
>>>> 
>>>> 
>>>> On Tue, Jan 24, 2017 at 1:28 PM, Victor Lazzarini
>>>>  wrote:
>>>>> Afaik, channels are fixed to stereo by Pepper.
>>>>> 
>>>>> Victor Lazzarini
>>>>> Dean of Arts, Celtic Studies, and Philosophy
>>>>> Maynooth University
>>>>> Ireland
>>>>> 
>>>>>> On 24 Jan 2017, at 17:29, Michael Gogins  wrote:
>>>>>> 
>>>>>> But the PNaCl code should be changed to always adapt to the host channel count.
>>>>>> 
>>>>>> Regards,
>>>>>> Mike
>>>>>> 
>>>>>> -----------------------------------------------------
>>>>>> Michael Gogins
>>>>>> Irreducible Productions
>>>>>> http://michaelgogins.tumblr.com
>>>>>> Michael dot Gogins at gmail dot com
>>>>>> 
>>>>>> 
>>>>>>> On Tue, Jan 24, 2017 at 12:17 PM, Ed Costello  wrote:
>>>>>>> Yeah,
>>>>>>> I am using the latest release of both, I think though that the Pnacl version doesn’t allow single channel outputs?
>>>>>>> Ed
>>>>>>> 
>>>>>>>> On 24 Jan 2017, at 17:04, Michael Gogins  wrote:
>>>>>>>> 
>>>>>>>> I went to your example page, and edited the example to output one
>>>>>>>> channel. It did not work. I assume you are using a more recent version
>>>>>>>> of the PNaCl or Emscripten build than my playable manual does.
>>>>>>>> 
>>>>>>>> I think the best fix here would be to change, not the manual page
>>>>>>>> code, but rather the JavaScript wrapper code.
>>>>>>>> 
>>>>>>>> Regards,
>>>>>>>> Mike
>>>>>>>> 
>>>>>>>> -----------------------------------------------------
>>>>>>>> Michael Gogins
>>>>>>>> Irreducible Productions
>>>>>>>> http://michaelgogins.tumblr.com
>>>>>>>> Michael dot Gogins at gmail dot com
>>>>>>>> 
>>>>>>>> 
>>>>>>>> On Tue, Jan 24, 2017 at 11:58 AM, Michael Gogins
>>>>>>>>  wrote:
>>>>>>>>> My existing html player allows the user to edit the csd example, but
>>>>>>>>> does not save the edited version of the example.
>>>>>>>>> 
>>>>>>>>> In addition, most examples use mono but only stereo examples were
>>>>>>>>> working, last time I checked. But this may now have changed because of
>>>>>>>>> changes to the output opcodes. I will check.
>>>>>>>>> 
>>>>>>>>> I see no reason to maintain two versions of this thing. If you are
>>>>>>>>> willing to maintain yours I am happy to remove mine.
>>>>>>>>> 
>>>>>>>>> Regards,
>>>>>>>>> Mike
>>>>>>>>> 
>>>>>>>>> -----------------------------------------------------
>>>>>>>>> Michael Gogins
>>>>>>>>> Irreducible Productions
>>>>>>>>> http://michaelgogins.tumblr.com
>>>>>>>>> Michael dot Gogins at gmail dot com
>>>>>>>>> 
>>>>>>>>> 
>>>>>>>>>> On Tue, Jan 24, 2017 at 11:39 AM, Ed Costello  wrote:
>>>>>>>>>> Hi,
>>>>>>>>>> 
>>>>>>>>>> I have started 2 projects which may be of interest. A web component for
>>>>>>>>>> Csound that can play and edit .csd files (using either pnacl or emscripten),
>>>>>>>>>> and a manual parser which converts, or will in theory convert, docbook xml
>>>>>>>>>> opcode pages to html using Asciidoctor which includes the web component.
>>>>>>>>>> 
>>>>>>>>>> I am aware that there is an online version of the manual which will also
>>>>>>>>>> allow the playing of .csd files, but I thought I would give it a go as my
>>>>>>>>>> idea was to have a text editor and the player engine embedded directly in
>>>>>>>>>> the manual page.
>>>>>>>>>> 
>>>>>>>>>> The csound web component player is here
>>>>>>>>>> https://github.com/eddyc/csound-player/
>>>>>>>>>> 
>>>>>>>>>> The manual to html project is here https://github.com/eddyc/csound-manual/
>>>>>>>>>> 
>>>>>>>>>> I also have an example of a finished html manual page with the embedded csd
>>>>>>>>>> player at
>>>>>>>>>> 
>>>>>>>>>> https://eddyc.github.io/csound-manual/opcodes/areson.html
>>>>>>>>>> 
>>>>>>>>>> there are a number of things unfinished here of course but I think it shows
>>>>>>>>>> the potential of having such a player embedded directly in a manual page
>>>>>>>>>> with an editor. I think another benefit of this approach is that the docbook
>>>>>>>>>> xml files are converted to asciidoctor markup, which is very similar to
>>>>>>>>>> markdown, and shows how it could be a lot simpler to make manual pages, and
>>>>>>>>>> pages that are clearly legible in their source form inside of a text editor.
>>>>>>>>>> 
>>>>>>>>>> Cheers

i would love to learn how this could be adapted to the csound floss 
manual, to play the examples via browser.

i tried your example page 
(https://eddyc.github.io/csound-manual/opcodes/areson.html) with firefox 
on debian, and got no complilation and no sound.  not sure i understood 
you right that it should work just from any browser?  or do i have to 
install your player first?

	joachim


On 24/01/17 17:39, Ed Costello wrote:
> Hi,
>
> I have started 2 projects which may be of interest. A web component for
> Csound that can play and edit .csd files (using either pnacl or
> emscripten), and a manual parser which converts, or will in theory
> convert, docbook xml opcode pages to html using Asciidoctor which
> includes the web component.
>
> I am aware that there is an online version of the manual which will also
> allow the playing of .csd files, but I thought I would give it a go as
> my idea was to have a text editor and the player engine embedded
> directly in the manual page.
>
> The csound web component player is
> here https://github.com/eddyc/csound-player/
>
> The manual to html project is here https://github.com/eddyc/csound-manual/
>
> I also have an example of a finished html manual page with the embedded
> csd player at
>
> https://eddyc.github.io/csound-manual/opcodes/areson.html
>
> there are a number of things unfinished here of course but I think it
> shows the potential of having such a player embedded directly in a
> manual page with an editor. I think another benefit of this approach is
> that the docbook xml files are converted to asciidoctor markup, which is
> very similar to markdown, and shows how it could be a lot simpler to
> make manual pages, and pages that are clearly legible in their source
> form inside of a text editor.
>
> Cheers

I tested it with firefox 50 in OSX and it worked fine, is there any error reported in the javascript console?
Ed

> On 27 Jan 2017, at 20:18, joachim heintz  wrote:
> 
> i would love to learn how this could be adapted to the csound floss manual, to play the examples via browser.
> 
> i tried your example page (https://eddyc.github.io/csound-manual/opcodes/areson.html) with firefox on debian, and got no complilation and no sound.  not sure i understood you right that it should work just from any browser?  or do i have to install your player first?
> 
> 	joachim
> 
> 
> On 24/01/17 17:39, Ed Costello wrote:
>> Hi,
>> 
>> I have started 2 projects which may be of interest. A web component for
>> Csound that can play and edit .csd files (using either pnacl or
>> emscripten), and a manual parser which converts, or will in theory
>> convert, docbook xml opcode pages to html using Asciidoctor which
>> includes the web component.
>> 
>> I am aware that there is an online version of the manual which will also
>> allow the playing of .csd files, but I thought I would give it a go as
>> my idea was to have a text editor and the player engine embedded
>> directly in the manual page.
>> 
>> The csound web component player is
>> here https://github.com/eddyc/csound-player/
>> 
>> The manual to html project is here https://github.com/eddyc/csound-manual/
>> 
>> I also have an example of a finished html manual page with the embedded
>> csd player at
>> 
>> https://eddyc.github.io/csound-manual/opcodes/areson.html
>> 
>> there are a number of things unfinished here of course but I think it
>> shows the potential of having such a player embedded directly in a
>> manual page with an editor. I think another benefit of this approach is
>> that the docbook xml files are converted to asciidoctor markup, which is
>> very similar to markdown, and shows how it could be a lot simpler to
>> make manual pages, and pages that are clearly legible in their source
>> form inside of a text editor.
>> 
>> Cheers

okay - i tried with chromium and it works.  firefox not (i checked about 
the ad blocker but there is nothing blocked): the console stays black.

what can i do to test it on an example for the floss manual?

thanks -
	joachim


On 27/01/17 21:28, Ed Costello wrote:
> I tested it with firefox 50 in OSX and it worked fine, is there any error reported in the javascript console?
> Ed
>
>> On 27 Jan 2017, at 20:18, joachim heintz  wrote:
>>
>> i would love to learn how this could be adapted to the csound floss manual, to play the examples via browser.
>>
>> i tried your example page (https://eddyc.github.io/csound-manual/opcodes/areson.html) with firefox on debian, and got no complilation and no sound.  not sure i understood you right that it should work just from any browser?  or do i have to install your player first?
>>
>> 	joachim
>>
>>
>> On 24/01/17 17:39, Ed Costello wrote:
>>> Hi,
>>>
>>> I have started 2 projects which may be of interest. A web component for
>>> Csound that can play and edit .csd files (using either pnacl or
>>> emscripten), and a manual parser which converts, or will in theory
>>> convert, docbook xml opcode pages to html using Asciidoctor which
>>> includes the web component.
>>>
>>> I am aware that there is an online version of the manual which will also
>>> allow the playing of .csd files, but I thought I would give it a go as
>>> my idea was to have a text editor and the player engine embedded
>>> directly in the manual page.
>>>
>>> The csound web component player is
>>> here https://github.com/eddyc/csound-player/
>>>
>>> The manual to html project is here https://github.com/eddyc/csound-manual/
>>>
>>> I also have an example of a finished html manual page with the embedded
>>> csd player at
>>>
>>> https://eddyc.github.io/csound-manual/opcodes/areson.html
>>>
>>> there are a number of things unfinished here of course but I think it
>>> shows the potential of having such a player embedded directly in a
>>> manual page with an editor. I think another benefit of this approach is
>>> that the docbook xml files are converted to asciidoctor markup, which is
>>> very similar to markdown, and shows how it could be a lot simpler to
>>> make manual pages, and pages that are clearly legible in their source
>>> form inside of a text editor.
>>>
>>> Cheers
>>> Ed

I just tried this on my iPhone and everything worked except that it could not find portaudio. I am impressed it did anything at all on an iPhone!

Regards,
Anders

> 27 jan. 2017 kl. 21:18 skrev joachim heintz :
> 
> i would love to learn how this could be adapted to the csound floss manual, to play the examples via browser.
> 
> i tried your example page (https://eddyc.github.io/csound-manual/opcodes/areson.html) with firefox on debian, and got no complilation and no sound.  not sure i understood you right that it should work just from any browser?  or do i have to install your player first?
> 
>    joachim
> 
> 
>> On 24/01/17 17:39, Ed Costello wrote:
>> Hi,
>> 
>> I have started 2 projects which may be of interest. A web component for
>> Csound that can play and edit .csd files (using either pnacl or
>> emscripten), and a manual parser which converts, or will in theory
>> convert, docbook xml opcode pages to html using Asciidoctor which
>> includes the web component.
>> 
>> I am aware that there is an online version of the manual which will also
>> allow the playing of .csd files, but I thought I would give it a go as
>> my idea was to have a text editor and the player engine embedded
>> directly in the manual page.
>> 
>> The csound web component player is
>> here https://github.com/eddyc/csound-player/
>> 
>> The manual to html project is here https://github.com/eddyc/csound-manual/
>> 
>> I also have an example of a finished html manual page with the embedded
>> csd player at
>> 
>> https://eddyc.github.io/csound-manual/opcodes/areson.html
>> 
>> there are a number of things unfinished here of course but I think it
>> shows the potential of having such a player embedded directly in a
>> manual page with an editor. I think another benefit of this approach is
>> that the docbook xml files are converted to asciidoctor markup, which is
>> very similar to markdown, and shows how it could be a lot simpler to
>> make manual pages, and pages that are clearly legible in their source
>> form inside of a text editor.
>> 
>> Cheers

It works over here: Ubuntu Studio 16.10 - Firefox 50.1.0

The first time it didn't work, so I cut and pasted the same text and it
started to work. Don't know if that makes sense.

Although it sounds fine, it still gives me this warning:  unknown
rtaudio module: 'PortAudio', using dummy module
rtaudio: dummy module enabled

Also there are two red Xs in line 1 and 2 of the editor with: expected
an identifier and instead saw '<'. Probably something to do with the
encoding of the browser.


On 27/01/17 17:52, joachim heintz wrote:
> okay - i tried with chromium and it works.  firefox not (i checked
> about the ad blocker but there is nothing blocked): the console stays
> black.
>
> what can i do to test it on an example for the floss manual?
>
> thanks -
>     joachim
>
>
> On 27/01/17 21:28, Ed Costello wrote:
>> I tested it with firefox 50 in OSX and it worked fine, is there any
>> error reported in the javascript console?
>> Ed
>>
>>> On 27 Jan 2017, at 20:18, joachim heintz  wrote:
>>>
>>> i would love to learn how this could be adapted to the csound floss
>>> manual, to play the examples via browser.
>>>
>>> i tried your example page
>>> (https://eddyc.github.io/csound-manual/opcodes/areson.html) with
>>> firefox on debian, and got no complilation and no sound.  not sure i
>>> understood you right that it should work just from any browser?  or
>>> do i have to install your player first?
>>>
>>>     joachim
>>>
>>>
>>> On 24/01/17 17:39, Ed Costello wrote:
>>>> Hi,
>>>>
>>>> I have started 2 projects which may be of interest. A web component
>>>> for
>>>> Csound that can play and edit .csd files (using either pnacl or
>>>> emscripten), and a manual parser which converts, or will in theory
>>>> convert, docbook xml opcode pages to html using Asciidoctor which
>>>> includes the web component.
>>>>
>>>> I am aware that there is an online version of the manual which will
>>>> also
>>>> allow the playing of .csd files, but I thought I would give it a go as
>>>> my idea was to have a text editor and the player engine embedded
>>>> directly in the manual page.
>>>>
>>>> The csound web component player is
>>>> here https://github.com/eddyc/csound-player/
>>>>
>>>> The manual to html project is here
>>>> https://github.com/eddyc/csound-manual/
>>>>
>>>> I also have an example of a finished html manual page with the
>>>> embedded
>>>> csd player at
>>>>
>>>> https://eddyc.github.io/csound-manual/opcodes/areson.html
>>>>
>>>> there are a number of things unfinished here of course but I think it
>>>> shows the potential of having such a player embedded directly in a
>>>> manual page with an editor. I think another benefit of this
>>>> approach is
>>>> that the docbook xml files are converted to asciidoctor markup,
>>>> which is
>>>> very similar to markdown, and shows how it could be a lot simpler to
>>>> make manual pages, and pages that are clearly legible in their source
>>>> form inside of a text editor.
>>>>
>>>> Cheers
>>>> Ed

I'm impressed by this in Ubuntu:

sample rate overrides: esr = 48000.0000, ekr = 187.5000, ksmps = 256.

How does it know the sample rate I'm using internally?


On 27/01/17 17:59, Anders Genell wrote:
> I just tried this on my iPhone and everything worked except that it could not find portaudio. I am impressed it did anything at all on an iPhone!
>
> Regards,
> Anders
>
>> 27 jan. 2017 kl. 21:18 skrev joachim heintz :
>>
>> i would love to learn how this could be adapted to the csound floss manual, to play the examples via browser.
>>
>> i tried your example page (https://eddyc.github.io/csound-manual/opcodes/areson.html) with firefox on debian, and got no complilation and no sound.  not sure i understood you right that it should work just from any browser?  or do i have to install your player first?
>>
>>    joachim
>>
>>
>>> On 24/01/17 17:39, Ed Costello wrote:
>>> Hi,
>>>
>>> I have started 2 projects which may be of interest. A web component for
>>> Csound that can play and edit .csd files (using either pnacl or
>>> emscripten), and a manual parser which converts, or will in theory
>>> convert, docbook xml opcode pages to html using Asciidoctor which
>>> includes the web component.
>>>
>>> I am aware that there is an online version of the manual which will also
>>> allow the playing of .csd files, but I thought I would give it a go as
>>> my idea was to have a text editor and the player engine embedded
>>> directly in the manual page.
>>>
>>> The csound web component player is
>>> here https://github.com/eddyc/csound-player/
>>>
>>> The manual to html project is here https://github.com/eddyc/csound-manual/
>>>
>>> I also have an example of a finished html manual page with the embedded
>>> csd player at
>>>
>>> https://eddyc.github.io/csound-manual/opcodes/areson.html
>>>
>>> there are a number of things unfinished here of course but I think it
>>> shows the potential of having such a player embedded directly in a
>>> manual page with an editor. I think another benefit of this approach is
>>> that the docbook xml files are converted to asciidoctor markup, which is
>>> very similar to markdown, and shows how it could be a lot simpler to
>>> make manual pages, and pages that are clearly legible in their source
>>> form inside of a text editor.
>>>
>>> Cheers

This worked for me, but there was a long load time for the first time
caching copies of the csound javascript/pnacl stuff (Nothing ran, I
reloaded and waited and things then ran).  If the case was indeed load
time, a pre-loader of some sort might be good to have.

On Fri, Jan 27, 2017 at 4:20 PM, Guillermo Senna  wrote:
> It works over here: Ubuntu Studio 16.10 - Firefox 50.1.0
>
> The first time it didn't work, so I cut and pasted the same text and it
> started to work. Don't know if that makes sense.
>
> Although it sounds fine, it still gives me this warning:  unknown
> rtaudio module: 'PortAudio', using dummy module [m
>  [mrtaudio: dummy module enabled
>
> Also there are two red Xs in line 1 and 2 of the editor with: expected
> an identifier and instead saw '<'. Probably something to do with the
> encoding of the browser.
>
>
> On 27/01/17 17:52, joachim heintz wrote:
>> okay - i tried with chromium and it works.  firefox not (i checked
>> about the ad blocker but there is nothing blocked): the console stays
>> black.
>>
>> what can i do to test it on an example for the floss manual?
>>
>> thanks -
>>     joachim
>>
>>
>> On 27/01/17 21:28, Ed Costello wrote:
>>> I tested it with firefox 50 in OSX and it worked fine, is there any
>>> error reported in the javascript console?
>>> Ed
>>>
>>>> On 27 Jan 2017, at 20:18, joachim heintz  wrote:
>>>>
>>>> i would love to learn how this could be adapted to the csound floss
>>>> manual, to play the examples via browser.
>>>>
>>>> i tried your example page
>>>> (https://eddyc.github.io/csound-manual/opcodes/areson.html) with
>>>> firefox on debian, and got no complilation and no sound.  not sure i
>>>> understood you right that it should work just from any browser?  or
>>>> do i have to install your player first?
>>>>
>>>>     joachim
>>>>
>>>>
>>>> On 24/01/17 17:39, Ed Costello wrote:
>>>>> Hi,
>>>>>
>>>>> I have started 2 projects which may be of interest. A web component
>>>>> for
>>>>> Csound that can play and edit .csd files (using either pnacl or
>>>>> emscripten), and a manual parser which converts, or will in theory
>>>>> convert, docbook xml opcode pages to html using Asciidoctor which
>>>>> includes the web component.
>>>>>
>>>>> I am aware that there is an online version of the manual which will
>>>>> also
>>>>> allow the playing of .csd files, but I thought I would give it a go as
>>>>> my idea was to have a text editor and the player engine embedded
>>>>> directly in the manual page.
>>>>>
>>>>> The csound web component player is
>>>>> here https://github.com/eddyc/csound-player/
>>>>>
>>>>> The manual to html project is here
>>>>> https://github.com/eddyc/csound-manual/
>>>>>
>>>>> I also have an example of a finished html manual page with the
>>>>> embedded
>>>>> csd player at
>>>>>
>>>>> https://eddyc.github.io/csound-manual/opcodes/areson.html
>>>>>
>>>>> there are a number of things unfinished here of course but I think it
>>>>> shows the potential of having such a player embedded directly in a
>>>>> manual page with an editor. I think another benefit of this
>>>>> approach is
>>>>> that the docbook xml files are converted to asciidoctor markup,
>>>>> which is
>>>>> very similar to markdown, and shows how it could be a lot simpler to
>>>>> make manual pages, and pages that are clearly legible in their source
>>>>> form inside of a text editor.
>>>>>
>>>>> Cheers
>>>>> Ed

So it wasn't the copy/paste thing but just time passing by. Can you see
the 2 red Xs in line 1 and 2 or is it just me?


On 27/01/17 19:14, Steven Yi wrote:
> This worked for me, but there was a long load time for the first time
> caching copies of the csound javascript/pnacl stuff (Nothing ran, I
> reloaded and waited and things then ran).  If the case was indeed load
> time, a pre-loader of some sort might be good to have.
>
> On Fri, Jan 27, 2017 at 4:20 PM, Guillermo Senna  wrote:
>> It works over here: Ubuntu Studio 16.10 - Firefox 50.1.0
>>
>> The first time it didn't work, so I cut and pasted the same text and it
>> started to work. Don't know if that makes sense.
>>
>> Although it sounds fine, it still gives me this warning:  unknown
>> rtaudio module: 'PortAudio', using dummy module [m
>>  [mrtaudio: dummy module enabled
>>
>> Also there are two red Xs in line 1 and 2 of the editor with: expected
>> an identifier and instead saw '<'. Probably something to do with the
>> encoding of the browser.
>>
>>
>> On 27/01/17 17:52, joachim heintz wrote:
>>> okay - i tried with chromium and it works.  firefox not (i checked
>>> about the ad blocker but there is nothing blocked): the console stays
>>> black.
>>>
>>> what can i do to test it on an example for the floss manual?
>>>
>>> thanks -
>>>     joachim
>>>
>>>
>>> On 27/01/17 21:28, Ed Costello wrote:
>>>> I tested it with firefox 50 in OSX and it worked fine, is there any
>>>> error reported in the javascript console?
>>>> Ed
>>>>
>>>>> On 27 Jan 2017, at 20:18, joachim heintz  wrote:
>>>>>
>>>>> i would love to learn how this could be adapted to the csound floss
>>>>> manual, to play the examples via browser.
>>>>>
>>>>> i tried your example page
>>>>> (https://eddyc.github.io/csound-manual/opcodes/areson.html) with
>>>>> firefox on debian, and got no complilation and no sound.  not sure i
>>>>> understood you right that it should work just from any browser?  or
>>>>> do i have to install your player first?
>>>>>
>>>>>     joachim
>>>>>
>>>>>
>>>>> On 24/01/17 17:39, Ed Costello wrote:
>>>>>> Hi,
>>>>>>
>>>>>> I have started 2 projects which may be of interest. A web component
>>>>>> for
>>>>>> Csound that can play and edit .csd files (using either pnacl or
>>>>>> emscripten), and a manual parser which converts, or will in theory
>>>>>> convert, docbook xml opcode pages to html using Asciidoctor which
>>>>>> includes the web component.
>>>>>>
>>>>>> I am aware that there is an online version of the manual which will
>>>>>> also
>>>>>> allow the playing of .csd files, but I thought I would give it a go as
>>>>>> my idea was to have a text editor and the player engine embedded
>>>>>> directly in the manual page.
>>>>>>
>>>>>> The csound web component player is
>>>>>> here https://github.com/eddyc/csound-player/
>>>>>>
>>>>>> The manual to html project is here
>>>>>> https://github.com/eddyc/csound-manual/
>>>>>>
>>>>>> I also have an example of a finished html manual page with the
>>>>>> embedded
>>>>>> csd player at
>>>>>>
>>>>>> https://eddyc.github.io/csound-manual/opcodes/areson.html
>>>>>>
>>>>>> there are a number of things unfinished here of course but I think it
>>>>>> shows the potential of having such a player embedded directly in a
>>>>>> manual page with an editor. I think another benefit of this
>>>>>> approach is
>>>>>> that the docbook xml files are converted to asciidoctor markup,
>>>>>> which is
>>>>>> very similar to markdown, and shows how it could be a lot simpler to
>>>>>> make manual pages, and pages that are clearly legible in their source
>>>>>> form inside of a text editor.
>>>>>>
>>>>>> Cheers

Hi,

I have started 2 projects which may be of interest. A web component for Csound that can play and edit .csd files (using either pnacl or emscripten), and a manual parser which converts, or will in theory convert, docbook xml opcode pages to html using Asciidoctor which includes the web component. 

I am aware that there is an online version of the manual which will also allow the playing of .csd files, but I thought I would give it a go as my idea was to have a text editor and the player engine embedded directly in the manual page.

The csound web component player is here https://github.com/eddyc/csound-player/

The manual to html project is here https://github.com/eddyc/csound-manual/

I also have an example of a finished html manual page with the embedded csd player at 

https://eddyc.github.io/csound-manual/opcodes/areson.html

there are a number of things unfinished here of course but I think it shows the potential of having such a player embedded directly in a manual page with an editor. I think another benefit of this approach is that the docbook xml files are converted to asciidoctor markup, which is very similar to markdown, and shows how it could be a lot simpler to make manual pages, and pages that are clearly legible in their source form inside of a text editor. 

Cheers

Ed