csound api python documentation

[iain duncan]

Hi folks, been a long time since I did any csounding, and I'm wondering
where the current documentation for the csound api for python would be
living.

thanks!
Iain



Send bugs reports to this list.
To unsubscribe, send email sympa@... with body "unsubscribe csound"

[Michael Gogins-2]

If you build Csound yourself, just run doxygen in the root Csound
directory. Otherwise, it's in the Windows installers. Don't know about
Unix/Linux.

Regards,
Mike

On 10/19/09, Iain Duncan <iainduncan@...> wrote:

> Hi folks, been a long time since I did any csounding, and I'm wondering
> where the current documentation for the csound api for python would be
> living.
>
> thanks!
> Iain
>
>
>
> Send bugs reports to this list.
> To unsubscribe, send email sympa@... with body "unsubscribe
> csound"
>

--
Michael Gogins
Irreducible Productions
http://www.michael-gogins.com
Michael dot Gogins at gmail dot com


Send bugs reports to this list.
To unsubscribe, send email sympa@... with body "unsubscribe csound"

[iain duncan]

On Mon, 2009-10-19 at 00:55 -0400, Michael Gogins wrote:
> If you build Csound yourself, just run doxygen in the root Csound
> directory. Otherwise, it's in the Windows installers. Don't know about
> Unix/Linux.

Thanks, that worked. I guess that there is not 'python specific' docs
though, we just cross reference with the C/C++ docs and sort it out?

thanks for your help tonight Mike
Iain




Send bugs reports to this list.
To unsubscribe, send email sympa@... with body "unsubscribe csound"

[Michael Gogins-2]

That's right. It's pretty much a one to one mapping.

Regards,
Mike

On 10/19/09, Iain Duncan <iainduncan@...> wrote:

> On Mon, 2009-10-19 at 00:55 -0400, Michael Gogins wrote:
>> If you build Csound yourself, just run doxygen in the root Csound
>> directory. Otherwise, it's in the Windows installers. Don't know about
>> Unix/Linux.
>
> Thanks, that worked. I guess that there is not 'python specific' docs
> though, we just cross reference with the C/C++ docs and sort it out?
>
> thanks for your help tonight Mike
> Iain
>
>
>
>
> Send bugs reports to this list.
> To unsubscribe, send email sympa@... with body "unsubscribe
> csound"
>

--
Michael Gogins
Irreducible Productions
http://www.michael-gogins.com
Michael dot Gogins at gmail dot com


Send bugs reports to this list.
To unsubscribe, send email sympa@... with body "unsubscribe csound"

[Jacob Joaquin]

These docs need to be online somewhere. People need to be able to find
them either at sourceforge, csounds, or a search engine.  The API is
becoming more and more import as time goes on, and not having
documentation readily available is likely stopping a lot of people
from even trying it out.

Best,
Jake


On Sun, Oct 18, 2009 at 9:55 PM, Michael Gogins
<michael.gogins@...> wrote:

> If you build Csound yourself, just run doxygen in the root Csound
> directory. Otherwise, it's in the Windows installers. Don't know about
> Unix/Linux.
>
> Regards,
> Mike
>
> On 10/19/09, Iain Duncan <iainduncan@...> wrote:
>> Hi folks, been a long time since I did any csounding, and I'm wondering
>> where the current documentation for the csound api for python would be
>> living.
>>
>> thanks!
>> Iain
>>
>>
>>
>> Send bugs reports to this list.
>> To unsubscribe, send email sympa@... with body "unsubscribe
>> csound"
>>
>
>
> --
> Michael Gogins
> Irreducible Productions
> http://www.michael-gogins.com
> Michael dot Gogins at gmail dot com
>
>
> Send bugs reports to this list.
> To unsubscribe, send email sympa@... with body "unsubscribe csound"
>

Send bugs reports to this list.
To unsubscribe, send email sympa@... with body "unsubscribe csound"

[Victor Lazzarini]

yes, and for five years I have been thinking I ought to write an API
reference manual but never quite managed.

Victor
On 20 Oct 2009, at 15:03, Jacob Joaquin wrote:

> These docs need to be online somewhere. People need to be able to find
> them either at sourceforge, csounds, or a search engine.  The API is
> becoming more and more import as time goes on, and not having
> documentation readily available is likely stopping a lot of people
> from even trying it out.
>
> Best,
> Jake
>
>
> On Sun, Oct 18, 2009 at 9:55 PM, Michael Gogins
> <michael.gogins@...> wrote:
>> If you build Csound yourself, just run doxygen in the root Csound
>> directory. Otherwise, it's in the Windows installers. Don't know  
>> about
>> Unix/Linux.
>>
>> Regards,
>> Mike
>>
>> On 10/19/09, Iain Duncan <iainduncan@...> wrote:
>>> Hi folks, been a long time since I did any csounding, and I'm  
>>> wondering
>>> where the current documentation for the csound api for python  
>>> would be
>>> living.
>>>
>>> thanks!
>>> Iain
>>>
>>>
>>>
>>> Send bugs reports to this list.
>>> To unsubscribe, send email sympa@... with body  
>>> "unsubscribe
>>> csound"
>>>
>>
>>
>> --
>> Michael Gogins
>> Irreducible Productions
>> http://www.michael-gogins.com
>> Michael dot Gogins at gmail dot com
>>
>>
>> Send bugs reports to this list.
>> To unsubscribe, send email sympa@... with body  
>> "unsubscribe csound"
>>
>
>
> Send bugs reports to this list.
> To unsubscribe, send email sympa@... with body  
> "unsubscribe csound"

Send bugs reports to this list.
To unsubscribe, send email sympa@... with body "unsubscribe csound"

[iain duncan]

On Tue, 2009-10-20 at 07:03 -0700, Jacob Joaquin wrote:
> These docs need to be online somewhere. People need to be able to find
> them either at sourceforge, csounds, or a search engine.  The API is
> becoming more and more import as time goes on, and not having
> documentation readily available is likely stopping a lot of people
> from even trying it out.

I didn't want to complain too loudly given that I just reshowed my face
here, but I second that. I googled for Csound API docs, and the most
recent things I found were papers from three years ago. It's currently
*way* too hard to find api docs if the plan is to have the api adopted
to any degree by third parties.

Iain

>
> Best,
> Jake
>
>
> On Sun, Oct 18, 2009 at 9:55 PM, Michael Gogins
> <michael.gogins@...> wrote:
> > If you build Csound yourself, just run doxygen in the root Csound
> > directory. Otherwise, it's in the Windows installers. Don't know about
> > Unix/Linux.
> >
> > Regards,
> > Mike
> >
> > On 10/19/09, Iain Duncan <iainduncan@...> wrote:
> >> Hi folks, been a long time since I did any csounding, and I'm wondering
> >> where the current documentation for the csound api for python would be
> >> living.
> >>
> >> thanks!
> >> Iain
> >>
> >>
> >>
> >> Send bugs reports to this list.
> >> To unsubscribe, send email sympa@... with body "unsubscribe
> >> csound"
> >>
> >
> >
> > --
> > Michael Gogins
> > Irreducible Productions
> > http://www.michael-gogins.com
> > Michael dot Gogins at gmail dot com
> >
> >
> > Send bugs reports to this list.
> > To unsubscribe, send email sympa@... with body "unsubscribe csound"
> >
>
>
> Send bugs reports to this list.
> To unsubscribe, send email sympa@... with body "unsubscribe csound"

Send bugs reports to this list.
To unsubscribe, send email sympa@... with body "unsubscribe csound"

[iain duncan]

On Tue, 2009-10-20 at 16:15 +0100, Victor Lazzarini wrote:
> yes, and for five years I have been thinking I ought to write an API
> reference manual but never quite managed.

It seems like is perhaps a lot of scattered api knowledge. Does anyone
have suggestions for how to centralize recipes, docs, etc? A wiki site?

Iain

>
> Victor
> On 20 Oct 2009, at 15:03, Jacob Joaquin wrote:
>
> > These docs need to be online somewhere. People need to be able to find
> > them either at sourceforge, csounds, or a search engine.  The API is
> > becoming more and more import as time goes on, and not having
> > documentation readily available is likely stopping a lot of people
> > from even trying it out.
> >
> > Best,
> > Jake
> >
> >
> > On Sun, Oct 18, 2009 at 9:55 PM, Michael Gogins
> > <michael.gogins@...> wrote:
> >> If you build Csound yourself, just run doxygen in the root Csound
> >> directory. Otherwise, it's in the Windows installers. Don't know  
> >> about
> >> Unix/Linux.
> >>
> >> Regards,
> >> Mike
> >>
> >> On 10/19/09, Iain Duncan <iainduncan@...> wrote:
> >>> Hi folks, been a long time since I did any csounding, and I'm  
> >>> wondering
> >>> where the current documentation for the csound api for python  
> >>> would be
> >>> living.
> >>>
> >>> thanks!
> >>> Iain
> >>>
> >>>
> >>>
> >>> Send bugs reports to this list.
> >>> To unsubscribe, send email sympa@... with body  
> >>> "unsubscribe
> >>> csound"
> >>>
> >>
> >>
> >> --
> >> Michael Gogins
> >> Irreducible Productions
> >> http://www.michael-gogins.com
> >> Michael dot Gogins at gmail dot com
> >>
> >>
> >> Send bugs reports to this list.
> >> To unsubscribe, send email sympa@... with body  
> >> "unsubscribe csound"
> >>
> >
> >
> > Send bugs reports to this list.
> > To unsubscribe, send email sympa@... with body  
> > "unsubscribe csound"
>
>
>
> Send bugs reports to this list.
> To unsubscribe, send email sympa@... with body "unsubscribe csound"

Send bugs reports to this list.
To unsubscribe, send email sympa@... with body "unsubscribe csound"

[RoryWalsh]

I think a wiki for this would be great, lots of info gets posted
sporadically on this forum but it would be great to have a centralised
resource, could we put one up on the sourceforge page?


2009/10/20 Iain Duncan <iainduncan@...>:

> On Tue, 2009-10-20 at 16:15 +0100, Victor Lazzarini wrote:
>> yes, and for five years I have been thinking I ought to write an API
>> reference manual but never quite managed.
>
> It seems like is perhaps a lot of scattered api knowledge. Does anyone
> have suggestions for how to centralize recipes, docs, etc? A wiki site?
>
> Iain
>
>>
>> Victor
>> On 20 Oct 2009, at 15:03, Jacob Joaquin wrote:
>>
>> > These docs need to be online somewhere. People need to be able to find
>> > them either at sourceforge, csounds, or a search engine.  The API is
>> > becoming more and more import as time goes on, and not having
>> > documentation readily available is likely stopping a lot of people
>> > from even trying it out.
>> >
>> > Best,
>> > Jake
>> >
>> >
>> > On Sun, Oct 18, 2009 at 9:55 PM, Michael Gogins
>> > <michael.gogins@...> wrote:
>> >> If you build Csound yourself, just run doxygen in the root Csound
>> >> directory. Otherwise, it's in the Windows installers. Don't know
>> >> about
>> >> Unix/Linux.
>> >>
>> >> Regards,
>> >> Mike
>> >>
>> >> On 10/19/09, Iain Duncan <iainduncan@...> wrote:
>> >>> Hi folks, been a long time since I did any csounding, and I'm
>> >>> wondering
>> >>> where the current documentation for the csound api for python
>> >>> would be
>> >>> living.
>> >>>
>> >>> thanks!
>> >>> Iain
>> >>>
>> >>>
>> >>>
>> >>> Send bugs reports to this list.
>> >>> To unsubscribe, send email sympa@... with body
>> >>> "unsubscribe
>> >>> csound"
>> >>>
>> >>
>> >>
>> >> --
>> >> Michael Gogins
>> >> Irreducible Productions
>> >> http://www.michael-gogins.com
>> >> Michael dot Gogins at gmail dot com
>> >>
>> >>
>> >> Send bugs reports to this list.
>> >> To unsubscribe, send email sympa@... with body
>> >> "unsubscribe csound"
>> >>
>> >
>> >
>> > Send bugs reports to this list.
>> > To unsubscribe, send email sympa@... with body
>> > "unsubscribe csound"
>>
>>
>>
>> Send bugs reports to this list.
>> To unsubscribe, send email sympa@... with body "unsubscribe csound"
>
>
>
> Send bugs reports to this list.
> To unsubscribe, send email sympa@... with body "unsubscribe csound"
>

Send bugs reports to this list.
To unsubscribe, send email sympa@... with body "unsubscribe csound"

[Michael Gogins-2]

The API documents are included in the Windows installers. They could
easily be included in the Linux packages and put online.

Regards,
Mike

On 10/20/09, Iain Duncan <iainduncan@...> wrote:

> On Tue, 2009-10-20 at 07:03 -0700, Jacob Joaquin wrote:
>> These docs need to be online somewhere. People need to be able to find
>> them either at sourceforge, csounds, or a search engine.  The API is
>> becoming more and more import as time goes on, and not having
>> documentation readily available is likely stopping a lot of people
>> from even trying it out.
>
> I didn't want to complain too loudly given that I just reshowed my face
> here, but I second that. I googled for Csound API docs, and the most
> recent things I found were papers from three years ago. It's currently
> *way* too hard to find api docs if the plan is to have the api adopted
> to any degree by third parties.
>
> Iain
>
>>
>> Best,
>> Jake
>>
>>
>> On Sun, Oct 18, 2009 at 9:55 PM, Michael Gogins
>> <michael.gogins@...> wrote:
>> > If you build Csound yourself, just run doxygen in the root Csound
>> > directory. Otherwise, it's in the Windows installers. Don't know about
>> > Unix/Linux.
>> >
>> > Regards,
>> > Mike
>> >
>> > On 10/19/09, Iain Duncan <iainduncan@...> wrote:
>> >> Hi folks, been a long time since I did any csounding, and I'm wondering
>> >> where the current documentation for the csound api for python would be
>> >> living.
>> >>
>> >> thanks!
>> >> Iain
>> >>
>> >>
>> >>
>> >> Send bugs reports to this list.
>> >> To unsubscribe, send email sympa@... with body
>> >> "unsubscribe
>> >> csound"
>> >>
>> >
>> >
>> > --
>> > Michael Gogins
>> > Irreducible Productions
>> > http://www.michael-gogins.com
>> > Michael dot Gogins at gmail dot com
>> >
>> >
>> > Send bugs reports to this list.
>> > To unsubscribe, send email sympa@... with body "unsubscribe
>> > csound"
>> >
>>
>>
>> Send bugs reports to this list.
>> To unsubscribe, send email sympa@... with body "unsubscribe
>> csound"
>
>
>
> Send bugs reports to this list.
> To unsubscribe, send email sympa@... with body "unsubscribe
> csound"
>

--
Michael Gogins
Irreducible Productions
http://www.michael-gogins.com
Michael dot Gogins at gmail dot com


Send bugs reports to this list.
To unsubscribe, send email sympa@... with body "unsubscribe csound"

[Felipe Sateler]

The debian packages include them in libcsound64-doc.
I see that csounds.com has the (old?) pdf version of the manual, maybe
it should be replaced by the html versions?

On Tue, 2009-10-20 at 15:53 -0400, Michael Gogins wrote:

> The API documents are included in the Windows installers. They could
> easily be included in the Linux packages and put online.
>
> Regards,
> Mike
>
> On 10/20/09, Iain Duncan <iainduncan@...> wrote:
> > On Tue, 2009-10-20 at 07:03 -0700, Jacob Joaquin wrote:
> >> These docs need to be online somewhere. People need to be able to find
> >> them either at sourceforge, csounds, or a search engine.  The API is
> >> becoming more and more import as time goes on, and not having
> >> documentation readily available is likely stopping a lot of people
> >> from even trying it out.
> >
> > I didn't want to complain too loudly given that I just reshowed my face
> > here, but I second that. I googled for Csound API docs, and the most
> > recent things I found were papers from three years ago. It's currently
> > *way* too hard to find api docs if the plan is to have the api adopted
> > to any degree by third parties.
> >
> > Iain
> >
> >>
> >> Best,
> >> Jake
> >>
> >>
> >> On Sun, Oct 18, 2009 at 9:55 PM, Michael Gogins
> >> <michael.gogins@...> wrote:
> >> > If you build Csound yourself, just run doxygen in the root Csound
> >> > directory. Otherwise, it's in the Windows installers. Don't know about
> >> > Unix/Linux.
> >> >
> >> > Regards,
> >> > Mike
> >> >
> >> > On 10/19/09, Iain Duncan <iainduncan@...> wrote:
> >> >> Hi folks, been a long time since I did any csounding, and I'm wondering
> >> >> where the current documentation for the csound api for python would be
> >> >> living.
> >> >>
> >> >> thanks!
> >> >> Iain
> >> >>
> >> >>
> >> >>
> >> >> Send bugs reports to this list.
> >> >> To unsubscribe, send email sympa@... with body
> >> >> "unsubscribe
> >> >> csound"
> >> >>
> >> >
> >> >
> >> > --
> >> > Michael Gogins
> >> > Irreducible Productions
> >> > http://www.michael-gogins.com
> >> > Michael dot Gogins at gmail dot com
> >> >
> >> >
> >> > Send bugs reports to this list.
> >> > To unsubscribe, send email sympa@... with body "unsubscribe
> >> > csound"
> >> >
> >>
> >>
> >> Send bugs reports to this list.
> >> To unsubscribe, send email sympa@... with body "unsubscribe
> >> csound"
> >
> >
> >
> > Send bugs reports to this list.
> > To unsubscribe, send email sympa@... with body "unsubscribe
> > csound"
> >
>
>

--
Saludos,
Felipe Sateler

[iain duncan]

On Tue, 2009-10-20 at 15:53 -0400, Michael Gogins wrote:
> The API documents are included in the Windows installers. They could
> easily be included in the Linux packages and put online.
>

I'm not sure that would change adequately what happens, ( or rather
doesn't!) when one googles 'csound API', know what I mean? It's like a
hidden project. ;-)

Iain

> Regards,
> Mike
>
> On 10/20/09, Iain Duncan <iainduncan@...> wrote:
> > On Tue, 2009-10-20 at 07:03 -0700, Jacob Joaquin wrote:
> >> These docs need to be online somewhere. People need to be able to find
> >> them either at sourceforge, csounds, or a search engine.  The API is
> >> becoming more and more import as time goes on, and not having
> >> documentation readily available is likely stopping a lot of people
> >> from even trying it out.
> >
> > I didn't want to complain too loudly given that I just reshowed my face
> > here, but I second that. I googled for Csound API docs, and the most
> > recent things I found were papers from three years ago. It's currently
> > *way* too hard to find api docs if the plan is to have the api adopted
> > to any degree by third parties.
> >
> > Iain
> >
> >>
> >> Best,
> >> Jake
> >>
> >>
> >> On Sun, Oct 18, 2009 at 9:55 PM, Michael Gogins
> >> <michael.gogins@...> wrote:
> >> > If you build Csound yourself, just run doxygen in the root Csound
> >> > directory. Otherwise, it's in the Windows installers. Don't know about
> >> > Unix/Linux.
> >> >
> >> > Regards,
> >> > Mike
> >> >
> >> > On 10/19/09, Iain Duncan <iainduncan@...> wrote:
> >> >> Hi folks, been a long time since I did any csounding, and I'm wondering
> >> >> where the current documentation for the csound api for python would be
> >> >> living.
> >> >>
> >> >> thanks!
> >> >> Iain
> >> >>
> >> >>
> >> >>
> >> >> Send bugs reports to this list.
> >> >> To unsubscribe, send email sympa@... with body
> >> >> "unsubscribe
> >> >> csound"
> >> >>
> >> >
> >> >
> >> > --
> >> > Michael Gogins
> >> > Irreducible Productions
> >> > http://www.michael-gogins.com
> >> > Michael dot Gogins at gmail dot com
> >> >
> >> >
> >> > Send bugs reports to this list.
> >> > To unsubscribe, send email sympa@... with body "unsubscribe
> >> > csound"
> >> >
> >>
> >>
> >> Send bugs reports to this list.
> >> To unsubscribe, send email sympa@... with body "unsubscribe
> >> csound"
> >
> >
> >
> > Send bugs reports to this list.
> > To unsubscribe, send email sympa@... with body "unsubscribe
> > csound"
> >
>
>

Send bugs reports to this list.
To unsubscribe, send email sympa@... with body "unsubscribe csound"

[Jacob Joaquin]

I've never thought about it that way, but yeah, hidden project sounds
about right. The term API isn't even present in the table of contents
of the Csound manual.

Best,
Jake
---
The Csound Blog - http://csound.noisepages.com/



On Tue, Oct 20, 2009 at 6:24 PM, Iain Duncan <iainduncan@...> wrote:

> On Tue, 2009-10-20 at 15:53 -0400, Michael Gogins wrote:
>> The API documents are included in the Windows installers. They could
>> easily be included in the Linux packages and put online.
>>
>
> I'm not sure that would change adequately what happens, ( or rather
> doesn't!) when one googles 'csound API', know what I mean? It's like a
> hidden project. ;-)
>
> Iain
>
>
>> Regards,
>> Mike
>>
>> On 10/20/09, Iain Duncan <iainduncan@...> wrote:
>> > On Tue, 2009-10-20 at 07:03 -0700, Jacob Joaquin wrote:
>> >> These docs need to be online somewhere. People need to be able to find
>> >> them either at sourceforge, csounds, or a search engine.  The API is
>> >> becoming more and more import as time goes on, and not having
>> >> documentation readily available is likely stopping a lot of people
>> >> from even trying it out.
>> >
>> > I didn't want to complain too loudly given that I just reshowed my face
>> > here, but I second that. I googled for Csound API docs, and the most
>> > recent things I found were papers from three years ago. It's currently
>> > *way* too hard to find api docs if the plan is to have the api adopted
>> > to any degree by third parties.
>> >
>> > Iain
>> >
>> >>
>> >> Best,
>> >> Jake
>> >>
>> >>
>> >> On Sun, Oct 18, 2009 at 9:55 PM, Michael Gogins
>> >> <michael.gogins@...> wrote:
>> >> > If you build Csound yourself, just run doxygen in the root Csound
>> >> > directory. Otherwise, it's in the Windows installers. Don't know about
>> >> > Unix/Linux.
>> >> >
>> >> > Regards,
>> >> > Mike
>> >> >
>> >> > On 10/19/09, Iain Duncan <iainduncan@...> wrote:
>> >> >> Hi folks, been a long time since I did any csounding, and I'm wondering
>> >> >> where the current documentation for the csound api for python would be
>> >> >> living.
>> >> >>
>> >> >> thanks!
>> >> >> Iain
>> >> >>
>> >> >>
>> >> >>
>> >> >> Send bugs reports to this list.
>> >> >> To unsubscribe, send email sympa@... with body
>> >> >> "unsubscribe
>> >> >> csound"
>> >> >>
>> >> >
>> >> >
>> >> > --
>> >> > Michael Gogins
>> >> > Irreducible Productions
>> >> > http://www.michael-gogins.com
>> >> > Michael dot Gogins at gmail dot com
>> >> >
>> >> >
>> >> > Send bugs reports to this list.
>> >> > To unsubscribe, send email sympa@... with body "unsubscribe
>> >> > csound"
>> >> >
>> >>
>> >>
>> >> Send bugs reports to this list.
>> >> To unsubscribe, send email sympa@... with body "unsubscribe
>> >> csound"
>> >
>> >
>> >
>> > Send bugs reports to this list.
>> > To unsubscribe, send email sympa@... with body "unsubscribe
>> > csound"
>> >
>>
>>
>
>
>
> Send bugs reports to this list.
> To unsubscribe, send email sympa@... with body "unsubscribe csound"
>

Send bugs reports to this list.
To unsubscribe, send email sympa@... with body "unsubscribe csound"

[iain duncan]

On Tue, 2009-10-20 at 19:08 -0700, Jacob Joaquin wrote:
> I've never thought about it that way, but yeah, hidden project sounds
> about right. The term API isn't even present in the table of contents
> of the Csound manual.

Has anyone thought of using Sphinx? For python projects it makes
producing hand written docs much easier, and it's possible to include
docstests that run right while building the docs. And the generated html
is great.

I guess really what the API needs is a users guide, up online in some
format that is easily crawled.

Iain

>
> Best,
> Jake
> ---
> The Csound Blog - http://csound.noisepages.com/
>
>
>
> On Tue, Oct 20, 2009 at 6:24 PM, Iain Duncan <iainduncan@...> wrote:
> > On Tue, 2009-10-20 at 15:53 -0400, Michael Gogins wrote:
> >> The API documents are included in the Windows installers. They could
> >> easily be included in the Linux packages and put online.
> >>
> >
> > I'm not sure that would change adequately what happens, ( or rather
> > doesn't!) when one googles 'csound API', know what I mean? It's like a
> > hidden project. ;-)
> >
> > Iain
> >
> >
> >> Regards,
> >> Mike
> >>
> >> On 10/20/09, Iain Duncan <iainduncan@...> wrote:
> >> > On Tue, 2009-10-20 at 07:03 -0700, Jacob Joaquin wrote:
> >> >> These docs need to be online somewhere. People need to be able to find
> >> >> them either at sourceforge, csounds, or a search engine.  The API is
> >> >> becoming more and more import as time goes on, and not having
> >> >> documentation readily available is likely stopping a lot of people
> >> >> from even trying it out.
> >> >
> >> > I didn't want to complain too loudly given that I just reshowed my face
> >> > here, but I second that. I googled for Csound API docs, and the most
> >> > recent things I found were papers from three years ago. It's currently
> >> > *way* too hard to find api docs if the plan is to have the api adopted
> >> > to any degree by third parties.
> >> >
> >> > Iain
> >> >
> >> >>
> >> >> Best,
> >> >> Jake
> >> >>
> >> >>
> >> >> On Sun, Oct 18, 2009 at 9:55 PM, Michael Gogins
> >> >> <michael.gogins@...> wrote:
> >> >> > If you build Csound yourself, just run doxygen in the root Csound
> >> >> > directory. Otherwise, it's in the Windows installers. Don't know about
> >> >> > Unix/Linux.
> >> >> >
> >> >> > Regards,
> >> >> > Mike
> >> >> >
> >> >> > On 10/19/09, Iain Duncan <iainduncan@...> wrote:
> >> >> >> Hi folks, been a long time since I did any csounding, and I'm wondering
> >> >> >> where the current documentation for the csound api for python would be
> >> >> >> living.
> >> >> >>
> >> >> >> thanks!
> >> >> >> Iain
> >> >> >>
> >> >> >>
> >> >> >>
> >> >> >> Send bugs reports to this list.
> >> >> >> To unsubscribe, send email sympa@... with body
> >> >> >> "unsubscribe
> >> >> >> csound"
> >> >> >>
> >> >> >
> >> >> >
> >> >> > --
> >> >> > Michael Gogins
> >> >> > Irreducible Productions
> >> >> > http://www.michael-gogins.com
> >> >> > Michael dot Gogins at gmail dot com
> >> >> >
> >> >> >
> >> >> > Send bugs reports to this list.
> >> >> > To unsubscribe, send email sympa@... with body "unsubscribe
> >> >> > csound"
> >> >> >
> >> >>
> >> >>
> >> >> Send bugs reports to this list.
> >> >> To unsubscribe, send email sympa@... with body "unsubscribe
> >> >> csound"
> >> >
> >> >
> >> >
> >> > Send bugs reports to this list.
> >> > To unsubscribe, send email sympa@... with body "unsubscribe
> >> > csound"
> >> >
> >>
> >>
> >
> >
> >
> > Send bugs reports to this list.
> > To unsubscribe, send email sympa@... with body "unsubscribe csound"
> >
>
>
> Send bugs reports to this list.
> To unsubscribe, send email sympa@... with body "unsubscribe csound"

Send bugs reports to this list.
To unsubscribe, send email sympa@... with body "unsubscribe csound"

[john ffitch]

We tried to use the API in Java and the lack of documentation meant that
the project failed.
==John ffitch


Send bugs reports to this list.
To unsubscribe, send email sympa@... with body "unsubscribe csound"

[Victor Lazzarini]

For Java, I guess it's more like we don't have the know-how; if you were
doing the project with Python, you'd have plenty of help from this list,
even though the documentation is missing.

Apart from a little example, I never programmed anything with Java and
the API (or Java, full-stop). Steven Yi is the Java man in this list, but I
am
not sure how much he's done with the API.

But this is not to say that the missing API reference is not a problem. We
need to have a basic document for the C API, then for C++ and the other
wrapper languages.

Victor


----- Original Message -----
From: "jpff" <jpff@...>
To: <csound@...>
Cc: <csound@...>
Sent: Wednesday, October 21, 2009 7:23 AM
Subject: [Csnd] Re: Re: Re: csound api python documentation


> We tried to use the API in Java and the lack of documentation meant that
> the project failed.
> ==John ffitch
>
>
> Send bugs reports to this list.
> To unsubscribe, send email sympa@... with body "unsubscribe
> csound"



Send bugs reports to this list.
To unsubscribe, send email sympa@... with body "unsubscribe csound"

[Michael Gogins-2]

Yes, it should be replaced by the html.

Mkg

On Oct 20, 2009 6:43 PM, "Felipe Sateler" <fsateler@...> wrote:

The debian packages include them in libcsound64-doc.
I see that csounds.com has the (old?) pdf version of the manual, maybe
it should be replaced by the html versions?

On Tue, 2009-10-20 at 15:53 -0400, Michael Gogins wrote: > The API documents are included in the Wi...

Saludos,
Felipe Sateler

[Michael Gogins-2]

Putting it online, i.e. at csounds.com, would solve that problem.

Regards,
Mike

On 10/20/09, Iain Duncan <iainduncan@...> wrote:

> On Tue, 2009-10-20 at 15:53 -0400, Michael Gogins wrote:
>> The API documents are included in the Windows installers. They could
>> easily be included in the Linux packages and put online.
>>
>
> I'm not sure that would change adequately what happens, ( or rather
> doesn't!) when one googles 'csound API', know what I mean? It's like a
> hidden project. ;-)
>
> Iain
>
>
>> Regards,
>> Mike
>>
>> On 10/20/09, Iain Duncan <iainduncan@...> wrote:
>> > On Tue, 2009-10-20 at 07:03 -0700, Jacob Joaquin wrote:
>> >> These docs need to be online somewhere. People need to be able to find
>> >> them either at sourceforge, csounds, or a search engine.  The API is
>> >> becoming more and more import as time goes on, and not having
>> >> documentation readily available is likely stopping a lot of people
>> >> from even trying it out.
>> >
>> > I didn't want to complain too loudly given that I just reshowed my face
>> > here, but I second that. I googled for Csound API docs, and the most
>> > recent things I found were papers from three years ago. It's currently
>> > *way* too hard to find api docs if the plan is to have the api adopted
>> > to any degree by third parties.
>> >
>> > Iain
>> >
>> >>
>> >> Best,
>> >> Jake
>> >>
>> >>
>> >> On Sun, Oct 18, 2009 at 9:55 PM, Michael Gogins
>> >> <michael.gogins@...> wrote:
>> >> > If you build Csound yourself, just run doxygen in the root Csound
>> >> > directory. Otherwise, it's in the Windows installers. Don't know
>> >> > about
>> >> > Unix/Linux.
>> >> >
>> >> > Regards,
>> >> > Mike
>> >> >
>> >> > On 10/19/09, Iain Duncan <iainduncan@...> wrote:
>> >> >> Hi folks, been a long time since I did any csounding, and I'm
>> >> >> wondering
>> >> >> where the current documentation for the csound api for python would
>> >> >> be
>> >> >> living.
>> >> >>
>> >> >> thanks!
>> >> >> Iain
>> >> >>
>> >> >>
>> >> >>
>> >> >> Send bugs reports to this list.
>> >> >> To unsubscribe, send email sympa@... with body
>> >> >> "unsubscribe
>> >> >> csound"
>> >> >>
>> >> >
>> >> >
>> >> > --
>> >> > Michael Gogins
>> >> > Irreducible Productions
>> >> > http://www.michael-gogins.com
>> >> > Michael dot Gogins at gmail dot com
>> >> >
>> >> >
>> >> > Send bugs reports to this list.
>> >> > To unsubscribe, send email sympa@... with body
>> >> > "unsubscribe
>> >> > csound"
>> >> >
>> >>
>> >>
>> >> Send bugs reports to this list.
>> >> To unsubscribe, send email sympa@... with body
>> >> "unsubscribe
>> >> csound"
>> >
>> >
>> >
>> > Send bugs reports to this list.
>> > To unsubscribe, send email sympa@... with body "unsubscribe
>> > csound"
>> >
>>
>>
>
>
>
> Send bugs reports to this list.
> To unsubscribe, send email sympa@... with body "unsubscribe
> csound"
>

--
Michael Gogins
Irreducible Productions
http://www.michael-gogins.com
Michael dot Gogins at gmail dot com


Send bugs reports to this list.
To unsubscribe, send email sympa@... with body "unsubscribe csound"

[Dr. Richard Boulanger]

Happy to host the Csound API and examples/models of API in use @  
cSounds.com

Dr. B.


Dr. Richard Boulanger  -  rboulanger@...



On Oct 21, 2009, at 8:44 AM, Michael Gogins wrote:

> Putting it online, i.e. at csounds.com, would solve that problem.
>
> Regards,
> Mike
>
> On 10/20/09, Iain Duncan <iainduncan@...> wrote:
>> On Tue, 2009-10-20 at 15:53 -0400, Michael Gogins wrote:
>>> The API documents are included in the Windows installers. They could
>>> easily be included in the Linux packages and put online.
>>>
>>
>> I'm not sure that would change adequately what happens, ( or rather
>> doesn't!) when one googles 'csound API', know what I mean? It's  
>> like a
>> hidden project. ;-)
>>
>> Iain
>>
>>
>>> Regards,
>>> Mike
>>>
>>> On 10/20/09, Iain Duncan <iainduncan@...> wrote:
>>>> On Tue, 2009-10-20 at 07:03 -0700, Jacob Joaquin wrote:
>>>>> These docs need to be online somewhere. People need to be able  
>>>>> to find
>>>>> them either at sourceforge, csounds, or a search engine.  The  
>>>>> API is
>>>>> becoming more and more import as time goes on, and not having
>>>>> documentation readily available is likely stopping a lot of people
>>>>> from even trying it out.
>>>>
>>>> I didn't want to complain too loudly given that I just reshowed  
>>>> my face
>>>> here, but I second that. I googled for Csound API docs, and the  
>>>> most
>>>> recent things I found were papers from three years ago. It's  
>>>> currently
>>>> *way* too hard to find api docs if the plan is to have the api  
>>>> adopted
>>>> to any degree by third parties.
>>>>
>>>> Iain
>>>>
>>>>>
>>>>> Best,
>>>>> Jake
>>>>>
>>>>>
>>>>> On Sun, Oct 18, 2009 at 9:55 PM, Michael Gogins
>>>>> <michael.gogins@...> wrote:
>>>>>> If you build Csound yourself, just run doxygen in the root Csound
>>>>>> directory. Otherwise, it's in the Windows installers. Don't know
>>>>>> about
>>>>>> Unix/Linux.
>>>>>>
>>>>>> Regards,
>>>>>> Mike
>>>>>>
>>>>>> On 10/19/09, Iain Duncan <iainduncan@...> wrote:
>>>>>>> Hi folks, been a long time since I did any csounding, and I'm
>>>>>>> wondering
>>>>>>> where the current documentation for the csound api for python  
>>>>>>> would
>>>>>>> be
>>>>>>> living.
>>>>>>>
>>>>>>> thanks!
>>>>>>> Iain
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> Send bugs reports to this list.
>>>>>>> To unsubscribe, send email sympa@... with body
>>>>>>> "unsubscribe
>>>>>>> csound"
>>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Michael Gogins
>>>>>> Irreducible Productions
>>>>>> http://www.michael-gogins.com
>>>>>> Michael dot Gogins at gmail dot com
>>>>>>
>>>>>>
>>>>>> Send bugs reports to this list.
>>>>>> To unsubscribe, send email sympa@... with body
>>>>>> "unsubscribe
>>>>>> csound"
>>>>>>
>>>>>
>>>>>
>>>>> Send bugs reports to this list.
>>>>> To unsubscribe, send email sympa@... with body
>>>>> "unsubscribe
>>>>> csound"
>>>>
>>>>
>>>>
>>>> Send bugs reports to this list.
>>>> To unsubscribe, send email sympa@... with body  
>>>> "unsubscribe
>>>> csound"
>>>>
>>>
>>>
>>
>>
>>
>> Send bugs reports to this list.
>> To unsubscribe, send email sympa@... with body  
>> "unsubscribe
>> csound"
>>
>
>
> --
> Michael Gogins
> Irreducible Productions
> http://www.michael-gogins.com
> Michael dot Gogins at gmail dot com
>
>
> Send bugs reports to this list.
> To unsubscribe, send email sympa@... with body  
> "unsubscribe csound"

Send bugs reports to this list.
To unsubscribe, send email sympa@... with body "unsubscribe csound"

[Steven Yi]

I haven't had much time to do more with the API than I'm currently
doing, but it's been on my list of things to explore.  I've been
meaning to do a new test with JNA (the java equivalent of python's
ctypes) to directly use libcsound instead of using the SWIG-generated
bindings.  I did a test a year or two ago and it was very slow, but I
checked the project and it looks like a number of releases have come
out since then with improvements to speed.  If that's unsatisfactory
then I'll try to work with getting audio buffers from Csound and Java
and may modify the SWIG bindings if necessary.

On Wed, Oct 21, 2009 at 4:02 AM, victor <Victor.Lazzarini@...> wrote:

> For Java, I guess it's more like we don't have the know-how; if you were
> doing the project with Python, you'd have plenty of help from this list,
> even though the documentation is missing.
>
> Apart from a little example, I never programmed anything with Java and
> the API (or Java, full-stop). Steven Yi is the Java man in this list, but I
> am
> not sure how much he's done with the API.
>
> But this is not to say that the missing API reference is not a problem. We
> need to have a basic document for the C API, then for C++ and the other
> wrapper languages.
>
> Victor
>
>
> ----- Original Message ----- From: "jpff" <jpff@...>
> To: <csound@...>
> Cc: <csound@...>
> Sent: Wednesday, October 21, 2009 7:23 AM
> Subject: [Csnd] Re: Re: Re: csound api python documentation
>
>
>> We tried to use the API in Java and the lack of documentation meant that
>> the project failed.
>> ==John ffitch
>>
>>
>> Send bugs reports to this list.
>> To unsubscribe, send email sympa@... with body "unsubscribe
>> csound"
>
>
>
> Send bugs reports to this list.
> To unsubscribe, send email sympa@... with body "unsubscribe
> csound"
>

Send bugs reports to this list.
To unsubscribe, send email sympa@... with body "unsubscribe csound"