wow --- that's big!
i tried it and it works all flawlessly.
i wonder how we can include the documentation (manual pages) of the
installed plugins in a simple way.
cheers -
        joachim



On 09/05/2020 03:36, Eduardo Moguillansky wrote:
> Hi,
>
> here is a first attempt at a package manager for csound. I call it
> "risset".
>
> https://github.com/csound-plugins/risset
>
>
>     Installation
>
> 1) Install git and python3, if needed
>
> 2) At a terminal:
>
>      pip3 install risset
>
>
>     Quick Start
>
> # list all available plugins for your platform
> $ risset list
>
> * else  @ 0.2.0        | Miscellaneous plugins
> * poly  @ 0.2.0        | Run multiple copies of an opcode in parallel/series
> * klib  @ 0.2.0        | hashtable / pool / string cache plugins
> * jsfx  @ 0.2.0        | Jesusonics effects in csound  [installed: 0.2.0]
> * mverb  @ 1.3.7       | Artificial reverb based on a 2D waveguide mesh
> * rory  @ 0.2.0        | Opcodes to save/recall channels, triggers, etc
>
>
> # show information about a given plugin
> $ risset show mverb
>
> Plugin     : mverb
> Installed  : 1.3.7
> Author     : Michael Gogins
> Abstract   : Artificial reverb based on a 2D waveguide mesh
> Description:
>      Verb is a modified 5-by-5 2D waveguide mesh reverberator. It is highly
>      flexible and can generate ompelling and unique timbres ranging from
>      traditional spaces to infinite morphing spaces or the simulation of
>      metallic plates or cymbals. The plugin incorporates a 10-band parametric
>      equalizer for timbral control and delay randomization to create more
>      unusual effects.
> Platforms:
>      * linux: Ubuntu 18.04
> Opcodes:
>      MVerb
> Minimal csound version : 6.14
>
> # Install a plugin
> $ risset install mverb
>
>
>
>     Documentation
>
> Documentation to all available opcodes is autogenerated and lives at:
>
> https://github.com/csound-plugins/risset-data/tree/master/docs
>
> Csound mailing list Csound@listserv.heanet.ie
> <mailto:Csound@listserv.heanet.ie>
> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to
> https://github.com/csound/csound/issues Discussions of bugs and features
> can be posted here

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

wow --- that's big!
i tried it and it works all flawlessly.
i wonder how we can include the documentation (manual pages) of the
installed plugins in a simple way.
cheers -
        joachim



On 09/05/2020 03:36, Eduardo Moguillansky wrote:
> Hi,
>
> here is a first attempt at a package manager for csound. I call it
> "risset".
>
> https://github.com/csound-plugins/risset
>
>
>     Installation
>
> 1) Install git and python3, if needed
>
> 2) At a terminal:
>
>      pip3 install risset
>
>
>     Quick Start
>
> # list all available plugins for your platform
> $ risset list
>
> * else  @ 0.2.0        | Miscellaneous plugins
> * poly  @ 0.2.0        | Run multiple copies of an opcode in parallel/series
> * klib  @ 0.2.0        | hashtable / pool / string cache plugins
> * jsfx  @ 0.2.0        | Jesusonics effects in csound  [installed: 0.2.0]
> * mverb  @ 1.3.7       | Artificial reverb based on a 2D waveguide mesh
> * rory  @ 0.2.0        | Opcodes to save/recall channels, triggers, etc
>
>
> # show information about a given plugin
> $ risset show mverb
>
> Plugin     : mverb
> Installed  : 1.3.7
> Author     : Michael Gogins
> Abstract   : Artificial reverb based on a 2D waveguide mesh
> Description:
>      Verb is a modified 5-by-5 2D waveguide mesh reverberator. It is highly
>      flexible and can generate ompelling and unique timbres ranging from
>      traditional spaces to infinite morphing spaces or the simulation of
>      metallic plates or cymbals. The plugin incorporates a 10-band parametric
>      equalizer for timbral control and delay randomization to create more
>      unusual effects.
> Platforms:
>      * linux: Ubuntu 18.04
> Opcodes:
>      MVerb
> Minimal csound version : 6.14
>
> # Install a plugin
> $ risset install mverb
>
>
>
>     Documentation
>
> Documentation to all available opcodes is autogenerated and lives at:
>
> https://github.com/csound-plugins/risset-data/tree/master/docs
>
> Csound mailing list Csound@listserv.heanet.ie
> <mailto:Csound@listserv.heanet.ie>
> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to
> https://github.com/csound/csound/issues Discussions of bugs and features
> can be posted here

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

Hi,

here is a first attempt at a package manager for csound. I call it "risset".

https://github.com/csound-plugins/risset

Installation

1) Install git and python3, if needed

2) At a terminal:

    pip3 install risset

Quick Start

# list all available plugins for your platform
$ risset list

* else  @ 0.2.0        | Miscellaneous plugins  
* poly  @ 0.2.0        | Run multiple copies of an opcode in parallel/series  
* klib  @ 0.2.0        | hashtable / pool / string cache plugins  
* jsfx  @ 0.2.0        | Jesusonics effects in csound  [installed: 0.2.0]
* mverb  @ 1.3.7       | Artificial reverb based on a 2D waveguide mesh  
* rory  @ 0.2.0        | Opcodes to save/recall channels, triggers, etc 


# show information about a given plugin
$ risset show mverb

Plugin     : mverb
Installed  : 1.3.7
Author     : Michael Gogins
Abstract   : Artificial reverb based on a 2D waveguide mesh
Description:
    Verb is a modified 5-by-5 2D waveguide mesh reverberator. It is highly
    flexible and can generate ompelling and unique timbres ranging from
    traditional spaces to infinite morphing spaces or the simulation of
    metallic plates or cymbals. The plugin incorporates a 10-band parametric
    equalizer for timbral control and delay randomization to create more
    unusual effects.
Platforms: 
    * linux: Ubuntu 18.04
Opcodes:
    MVerb
Minimal csound version : 6.14

# Install a plugin
$ risset install mverb

Documentation

Documentation to all available opcodes is autogenerated and lives at:

https://github.com/csound-plugins/risset-data/tree/master/docs

Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

This is great to see, thanks!  I tested here on MacOS and it worked well. 

Some thoughts:

* I didn't see if there was support for ARM or ARM64 CPU type on Linux. Any thoughts on that?  (Thinking Raspberry Pi here)

* It would be liberating for users to be able to add their own repositories.  (Similar to apt sources.list)  I think it would remove a bottleneck for publishing new plugins.

* It would be nice to have this work with both CS6 and CS7 and future versions. I think that would have some ramifications on the plugin declaration among other things.

I haven't had much time to respond to other emails but I think the proposal for local OPCODE dir is also a very good idea.

On Fri, May 8, 2020 at 9:37 PM Eduardo Moguillansky <eduardo.moguillansky@gmail.com> wrote:

Hi,

here is a first attempt at a package manager for csound. I call it "risset".

https://github.com/csound-plugins/risset

Installation

1) Install git and python3, if needed

2) At a terminal:

    pip3 install risset

Quick Start

# list all available plugins for your platform
$ risset list

* else  @ 0.2.0        | Miscellaneous plugins  
* poly  @ 0.2.0        | Run multiple copies of an opcode in parallel/series  
* klib  @ 0.2.0        | hashtable / pool / string cache plugins  
* jsfx  @ 0.2.0        | Jesusonics effects in csound  [installed: 0.2.0]
* mverb  @ 1.3.7       | Artificial reverb based on a 2D waveguide mesh  
* rory  @ 0.2.0        | Opcodes to save/recall channels, triggers, etc 


# show information about a given plugin
$ risset show mverb

Plugin     : mverb
Installed  : 1.3.7
Author     : Michael Gogins
Abstract   : Artificial reverb based on a 2D waveguide mesh
Description:
    Verb is a modified 5-by-5 2D waveguide mesh reverberator. It is highly
    flexible and can generate ompelling and unique timbres ranging from
    traditional spaces to infinite morphing spaces or the simulation of
    metallic plates or cymbals. The plugin incorporates a 10-band parametric
    equalizer for timbral control and delay randomization to create more
    unusual effects.
Platforms: 
    * linux: Ubuntu 18.04
Opcodes:
    MVerb
Minimal csound version : 6.14

# Install a plugin
$ risset install mverb

Documentation

Documentation to all available opcodes is autogenerated and lives at:

https://github.com/csound-plugins/risset-data/tree/master/docs

Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

On 09.05.20 22:42, Steven Yi wrote:

This is great to see, thanks!  I tested here on MacOS and it worked well. 

Some thoughts:

* I didn't see if there was support for ARM or ARM64 CPU type on Linux. Any thoughts on that?  (Thinking Raspberry Pi here)

These could be added, of course. I don't have the hardware to test that though so contributions are welcome.

* It would be liberating for users to be able to add their own repositories.  (Similar to apt sources.list)  I think it would remove a bottleneck for publishing new plugins.

Publishing a plugin is just a PR appart. You need to fork the risset-data repository, add your plugin to the plugins.json and add the binaries for each of your supported platform. Then do a PR or ask to be given rights to the repository.

Keeping everything in one repository makes the design simpler. For example, documentation can be built much easier this way.

* It would be nice to have this work with both CS6 and CS7 and future versions. I think that would have some ramifications on the plugin declaration among other things.

This can be adapted once CS7 is a thing. At the moment the amount of external plugins is so small that such complexity / flexibility is not yet needed.

I haven't had much time to respond to other emails but I think the proposal for local OPCODE dir is also a very good idea.

This would make things much tidier in fact.

On Fri, May 8, 2020 at 9:37 PM Eduardo Moguillansky <eduardo.moguillansky@gmail.com> wrote:

Hi,

here is a first attempt at a package manager for csound. I call it "risset".

https://github.com/csound-plugins/risset

Installation

1) Install git and python3, if needed

2) At a terminal:

    pip3 install risset

Quick Start

# list all available plugins for your platform
$ risset list

* else  @ 0.2.0        | Miscellaneous plugins  
* poly  @ 0.2.0        | Run multiple copies of an opcode in parallel/series  
* klib  @ 0.2.0        | hashtable / pool / string cache plugins  
* jsfx  @ 0.2.0        | Jesusonics effects in csound  [installed: 0.2.0]
* mverb  @ 1.3.7       | Artificial reverb based on a 2D waveguide mesh  
* rory  @ 0.2.0        | Opcodes to save/recall channels, triggers, etc 


# show information about a given plugin
$ risset show mverb

Plugin     : mverb
Installed  : 1.3.7
Author     : Michael Gogins
Abstract   : Artificial reverb based on a 2D waveguide mesh
Description:
    Verb is a modified 5-by-5 2D waveguide mesh reverberator. It is highly
    flexible and can generate ompelling and unique timbres ranging from
    traditional spaces to infinite morphing spaces or the simulation of
    metallic plates or cymbals. The plugin incorporates a 10-band parametric
    equalizer for timbral control and delay randomization to create more
    unusual effects.
Platforms: 
    * linux: Ubuntu 18.04
Opcodes:
    MVerb
Minimal csound version : 6.14

# Install a plugin
$ risset install mverb

Documentation

Documentation to all available opcodes is autogenerated and lives at:

https://github.com/csound-plugins/risset-data/tree/master/docs

Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

maybe git submodules would be a solution for that. Instead of adding your plugin directly to the repo you can add your repo as submodule. Or just ask for commit rights.

On 10.05.20 00:07, Steven Yi wrote:

Publishing a PR is the bottleneck mentioned. I am imagining a scenario of testing plugins with non-dev users before they're final and not wanting to have to do PR's to iterate (nor feeling the pressure to have a dev version in git history).

On Sat, May 9, 2020 at 5:34 PM Eduardo Moguillansky <eduardo.moguillansky@gmail.com> wrote:

On 09.05.20 22:42, Steven Yi wrote:

This is great to see, thanks!  I tested here on MacOS and it worked well. 

Some thoughts:

* I didn't see if there was support for ARM or ARM64 CPU type on Linux. Any thoughts on that?  (Thinking Raspberry Pi here)

These could be added, of course. I don't have the hardware to test that though so contributions are welcome.

* It would be liberating for users to be able to add their own repositories.  (Similar to apt sources.list)  I think it would remove a bottleneck for publishing new plugins.

Publishing a plugin is just a PR appart. You need to fork the risset-data repository, add your plugin to the plugins.json and add the binaries for each of your supported platform. Then do a PR or ask to be given rights to the repository.

Keeping everything in one repository makes the design simpler. For example, documentation can be built much easier this way.

* It would be nice to have this work with both CS6 and CS7 and future versions. I think that would have some ramifications on the plugin declaration among other things.

This can be adapted once CS7 is a thing. At the moment the amount of external plugins is so small that such complexity / flexibility is not yet needed.

I haven't had much time to respond to other emails but I think the proposal for local OPCODE dir is also a very good idea.

This would make things much tidier in fact.

On Fri, May 8, 2020 at 9:37 PM Eduardo Moguillansky <eduardo.moguillansky@gmail.com> wrote:

Hi,

here is a first attempt at a package manager for csound. I call it "risset".

https://github.com/csound-plugins/risset

Installation

1) Install git and python3, if needed

2) At a terminal:

    pip3 install risset

Quick Start

# list all available plugins for your platform
$ risset list

* else  @ 0.2.0        | Miscellaneous plugins  
* poly  @ 0.2.0        | Run multiple copies of an opcode in parallel/series  
* klib  @ 0.2.0        | hashtable / pool / string cache plugins  
* jsfx  @ 0.2.0        | Jesusonics effects in csound  [installed: 0.2.0]
* mverb  @ 1.3.7       | Artificial reverb based on a 2D waveguide mesh  
* rory  @ 0.2.0        | Opcodes to save/recall channels, triggers, etc 


# show information about a given plugin
$ risset show mverb

Plugin     : mverb
Installed  : 1.3.7
Author     : Michael Gogins
Abstract   : Artificial reverb based on a 2D waveguide mesh
Description:
    Verb is a modified 5-by-5 2D waveguide mesh reverberator. It is highly
    flexible and can generate ompelling and unique timbres ranging from
    traditional spaces to infinite morphing spaces or the simulation of
    metallic plates or cymbals. The plugin incorporates a 10-band parametric
    equalizer for timbral control and delay randomization to create more
    unusual effects.
Platforms: 
    * linux: Ubuntu 18.04
Opcodes:
    MVerb
Minimal csound version : 6.14

# Install a plugin
$ risset install mverb

Documentation

Documentation to all available opcodes is autogenerated and lives at:

https://github.com/csound-plugins/risset-data/tree/master/docs

Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Hello Everyone.

I can't wait to explore and use this new utility - and be able to add plugins to Csound with "ease"

It is my hope that either:

ONE: it will be a simple thing for any and every MacUser (particularly non-developers) to someday be able to build from sources

(I followed the instructions, but still got many errors and some tips about what I needed to add to my .bash_profile)

(( Is it working?  Do I have the most recent developer build on my Mac?  Do I have only ONE version and the latest and most complete version of Csound running on my Mac?   Is HomeBrew the way to go?  ))

or

TWO: that the DMG will install everything, even plugins, or the directories that will let me add plugins or UDO or use ctcsound or 

the Csound API

or 

THREE:  that there is an uninstaller and clean installer so that we could remove ALL of the Csound dependencies and utilities and freshly install ONLY the latest versions (without having to purchase a new Mac or wipe our hard drives and reinstall the OS (which I have done in the past!)

(( As a sideNOTE: I did work until 5 am yesterday trying to get Jupyter Notebooks and ctcsound to work with Anaconda and Python 2.7 or 3.7 - but that's another email and long story.  I did get a lot of it to work eventually, but there is absolutely NO WAY that I would torture my students with that sort of PATH nightmare (( they would ALL drop the class and run to SuperCollider for sure. ))

(( PS - if you are reading this Steven Yi, you might like to know that your tkinter tutorial, the one that is supposed to put sliders up on the screen, so totally crashed my MacBook that it powered it DOWN !  Black screen !!! I have not seen this since 1986 or so.  WOW.  After three attempts and three blackouts, I didn't want to risk blowing all the fuses in here, so I just moved on.  ;-0. OK - please forgive this digression, let's get back to risset (whom, by the way, I miss very very much!)

And so..., I was super excited to read that risset worked and instantly and flawlessly on Mac OSX

Well.... it is 4:00 am and I have been working on this since 11 pm today. (taking a break from grading)

I have installed, uninstalled, brew-installed, installed from sources, reinstalled, removed, moved, added, included, symlinked and removed all sorts of things from my .bash_profile and .bashrc and from my machine itself

I hate to give up, but... this has been beating me up pretty badly

here is what I can report 

- in the risset manual it says that plugins are installed in:

macos: $HOME/Library/Application Support/csound6/plugins64




but there is no such directory on my system

- even after brew installing, brew installing from steven yi's instructions and site, and re-installing from the latest .dmg




It seems that everything is in... 




~/Library/Frameworks/CsoundLib64.framework/... 




But, I am not sure that there is a plugins folder in there?

- and so, I even tried creating a csound6 directory and plugins64 subdirectory in the Application Support folder (NOPE)




Below is my terminal output after installing and following the instructions

- NOTE: even though mverb is is the gogins folder it does not appear in the list, whereas the rory and ed's plugins do appear in the list.  

- NOTE:  I can not install anything

- NOTE:  I did try the --user option and did get a message that suggested how to fix my path by adding appropriate lines to my .bash_profile (which I did) (( I also was told about some things that I needed to add to my .bash_profile when I BrewInstalled Csound followng Steven Yi's instructions (which required many reinstall of broken utilities by the way)




Should it be this difficult?  Am I getting to old for this?  

How much hunting (and stack overflow) and trial and error (path + error message) must one endure to set up a Mac to be able to follow along with the great work that you are all doing?




Here is my .bash_profile ( I tossed everything out pretty much )




export PS1="db->  "

export DYLD_FRAMEWORK_PATH="$DYLD_FRAMEWORK_PATH:/usr/local/opt/csound/Frameworks"

export CLASSPATH="/usr/local/opt/csound/libexec/csnd6.jar:."

export OPCODE6DIR64="/Library/Frameworks/CsoundLib64.framework/Versions/6.0/Resources/Opcodes64:/Users/rboulanger/Library/Application Support/csound6/plugins64"




Here is what I get when I type in the commands from the risset manual and try to install a plug

db->  risset list

* else  @ 0.2.0        | Miscellaneous plugins  

* poly  @ 0.2.0        | Run multiple copies of an opcode in parallel/series  

* klib  @ 0.2.0        | hashtable / pool / string cache plugins  

* jsfx  @ 0.2.0        | Jesusonics effects in csound  

* rory  @ 0.2.0        | Opcodes to save/recall channels, triggers, etc  

db->  risset install else

Traceback (most recent call last):

  File "/usr/local/bin/risset", line 8, in <module>

    sys.exit(main())

  File "/usr/local/lib/python3.7/site-packages/risset.py", line 1284, in main

    ok = args.func(plugins_index, args)

  File "/usr/local/lib/python3.7/site-packages/risset.py", line 1139, in cmd_install

    error = plugins_index.install_plugin(plugin_definition, user=args.user)

  File "/usr/local/lib/python3.7/site-packages/risset.py", line 767, in install_plugin

    plugin_dll = self.get_plugin_dll(plugin)

  File "/usr/local/lib/python3.7/site-packages/risset.py", line 746, in get_plugin_dll

    path = resolve_path(binary_definition.url, Path(plugin.source).parent.as_posix())

AttributeError: 'Plugin' object has no attribute 'source'







_____________________________________________
Dr. Richard Boulanger
Professor of Electronic Production and Design
Professional Writing and Music Technology Division
Berklee College of Music

______________________________________________
OFFICE: 1126 Boylston St., Suite 201 (EPD), Suite 208 (Boulanger)

______________________________________________

President of Boulanger Labs - http://boulangerlabs.com
Author & Editor of The Csound Book - http://mitpress.mit.edu/books/csound-book
Author & Editor of The Audio Programming Book - http://mitpress.mit.edu/books/audio-programming-book
______________________________________________
about: http://www.boulangerlabs.com/#about
about: http://www.csounds.com/community/developers/dr-richard-boulanger/
music: http://www.csounds.com/community/developers/dr-richard-boulanger/dr-richard-boulanger-music/

______________________________________________
email: rboulanger@berklee.edu
facebook: https://www.facebook.com/richard.boulanger.58

On Sun, May 10, 2020 at 1:13 AM Steven Yi <stevenyi@gmail.com> wrote:

I'm not such a fan of submodules myself and I don't think it quite supports the use case. Additionally, supporting multiple repositories would also integrate with another thing we've talked about here which is the template git repo for opcode plugins. 

If an opcode plugin template repo has a plugins.json, and if the repo is pre-configured to work with Github Actions, it might be possible to have it setup for auto-compilation on multiple platforms.  Users could then clone the repo, develop a plugin, commit code, then the template project is setup to compile on multiple platforms and publish to the repo.  The repo could then be added to as a source to the sources.list for risset. 

Regardless, there's no pressing need to implement such a thing this moment but perhaps it's something to consider for the future.

On Sat, May 9, 2020 at 7:59 PM Eduardo Moguillansky <eduardo.moguillansky@gmail.com> wrote:

maybe git submodules would be a solution for that. Instead of adding your plugin directly to the repo you can add your repo as submodule. Or just ask for commit rights.

On 10.05.20 00:07, Steven Yi wrote:

Publishing a PR is the bottleneck mentioned. I am imagining a scenario of testing plugins with non-dev users before they're final and not wanting to have to do PR's to iterate (nor feeling the pressure to have a dev version in git history).

On Sat, May 9, 2020 at 5:34 PM Eduardo Moguillansky <eduardo.moguillansky@gmail.com> wrote:

On 09.05.20 22:42, Steven Yi wrote:

This is great to see, thanks!  I tested here on MacOS and it worked well. 

Some thoughts:

* I didn't see if there was support for ARM or ARM64 CPU type on Linux. Any thoughts on that?  (Thinking Raspberry Pi here)

These could be added, of course. I don't have the hardware to test that though so contributions are welcome.

* It would be liberating for users to be able to add their own repositories.  (Similar to apt sources.list)  I think it would remove a bottleneck for publishing new plugins.

Publishing a plugin is just a PR appart. You need to fork the risset-data repository, add your plugin to the plugins.json and add the binaries for each of your supported platform. Then do a PR or ask to be given rights to the repository.

Keeping everything in one repository makes the design simpler. For example, documentation can be built much easier this way.

* It would be nice to have this work with both CS6 and CS7 and future versions. I think that would have some ramifications on the plugin declaration among other things.

This can be adapted once CS7 is a thing. At the moment the amount of external plugins is so small that such complexity / flexibility is not yet needed.

I haven't had much time to respond to other emails but I think the proposal for local OPCODE dir is also a very good idea.

This would make things much tidier in fact.

On Fri, May 8, 2020 at 9:37 PM Eduardo Moguillansky <eduardo.moguillansky@gmail.com> wrote:

Hi,

here is a first attempt at a package manager for csound. I call it "risset".

https://github.com/csound-plugins/risset

Installation

1) Install git and python3, if needed

2) At a terminal:

    pip3 install risset

Quick Start

# list all available plugins for your platform
$ risset list

* else  @ 0.2.0        | Miscellaneous plugins  
* poly  @ 0.2.0        | Run multiple copies of an opcode in parallel/series  
* klib  @ 0.2.0        | hashtable / pool / string cache plugins  
* jsfx  @ 0.2.0        | Jesusonics effects in csound  [installed: 0.2.0]
* mverb  @ 1.3.7       | Artificial reverb based on a 2D waveguide mesh  
* rory  @ 0.2.0        | Opcodes to save/recall channels, triggers, etc 


# show information about a given plugin
$ risset show mverb

Plugin     : mverb
Installed  : 1.3.7
Author     : Michael Gogins
Abstract   : Artificial reverb based on a 2D waveguide mesh
Description:
    Verb is a modified 5-by-5 2D waveguide mesh reverberator. It is highly
    flexible and can generate ompelling and unique timbres ranging from
    traditional spaces to infinite morphing spaces or the simulation of
    metallic plates or cymbals. The plugin incorporates a 10-band parametric
    equalizer for timbral control and delay randomization to create more
    unusual effects.
Platforms: 
    * linux: Ubuntu 18.04
Opcodes:
    MVerb
Minimal csound version : 6.14

# Install a plugin
$ risset install mverb

Documentation

Documentation to all available opcodes is autogenerated and lives at:

https://github.com/csound-plugins/risset-data/tree/master/docs

Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Hello Everyone.

I can't wait to explore and use this new utility - and be able to add plugins to Csound with "ease"

It is my hope that either:

ONE: it will be a simple thing for any and every MacUser (particularly non-developers) to someday be able to build from sources

(I followed the instructions, but still got many errors and some tips about what I needed to add to my .bash_profile)

(( Is it working?  Do I have the most recent developer build on my Mac?  Do I have only ONE version and the latest and most complete version of Csound running on my Mac?   Is HomeBrew the way to go?  ))

or

TWO: that the DMG will install everything, even plugins, or the directories that will let me add plugins or UDO or use ctcsound or 

the Csound API

or 

THREE:  that there is an uninstaller and clean installer so that we could remove ALL of the Csound dependencies and utilities and freshly install ONLY the latest versions (without having to purchase a new Mac or wipe our hard drives and reinstall the OS (which I have done in the past!)

(( As a sideNOTE: I did work until 5 am yesterday trying to get Jupyter Notebooks and ctcsound to work with Anaconda and Python 2.7 or 3.7 - but that's another email and long story.  I did get a lot of it to work eventually, but there is absolutely NO WAY that I would torture my students with that sort of PATH nightmare (( they would ALL drop the class and run to SuperCollider for sure. ))

(( PS - if you are reading this Steven Yi, you might like to know that your tkinter tutorial, the one that is supposed to put sliders up on the screen, so totally crashed my MacBook that it powered it DOWN !  Black screen !!! I have not seen this since 1986 or so.  WOW.  After three attempts and three blackouts, I didn't want to risk blowing all the fuses in here, so I just moved on.  ;-0. OK - please forgive this digression, let's get back to risset (whom, by the way, I miss very very much!)

And so..., I was super excited to read that risset worked and instantly and flawlessly on Mac OSX

Well.... it is 4:00 am and I have been working on this since 11 pm today. (taking a break from grading)

I have installed, uninstalled, brew-installed, installed from sources, reinstalled, removed, moved, added, included, symlinked and removed all sorts of things from my .bash_profile and .bashrc and from my machine itself

I hate to give up, but... this has been beating me up pretty badly

here is what I can report 

- in the risset manual it says that plugins are installed in:

macos: $HOME/Library/Application Support/csound6/plugins64




but there is no such directory on my system

- even after brew installing, brew installing from steven yi's instructions and site, and re-installing from the latest .dmg




It seems that everything is in... 




~/Library/Frameworks/CsoundLib64.framework/... 




But, I am not sure that there is a plugins folder in there?

- and so, I even tried creating a csound6 directory and plugins64 subdirectory in the Application Support folder (NOPE)




Below is my terminal output after installing and following the instructions

- NOTE: even though mverb is is the gogins folder it does not appear in the list, whereas the rory and ed's plugins do appear in the list.  

- NOTE:  I can not install anything

- NOTE:  I did try the --user option and did get a message that suggested how to fix my path by adding appropriate lines to my .bash_profile (which I did) (( I also was told about some things that I needed to add to my .bash_profile when I BrewInstalled Csound followng Steven Yi's instructions (which required many reinstall of broken utilities by the way)




Should it be this difficult?  Am I getting to old for this?  

How much hunting (and stack overflow) and trial and error (path + error message) must one endure to set up a Mac to be able to follow along with the great work that you are all doing?




Here is my .bash_profile ( I tossed everything out pretty much )




export PS1="db->  "

export DYLD_FRAMEWORK_PATH="$DYLD_FRAMEWORK_PATH:/usr/local/opt/csound/Frameworks"

export CLASSPATH="/usr/local/opt/csound/libexec/csnd6.jar:."

export OPCODE6DIR64="/Library/Frameworks/CsoundLib64.framework/Versions/6.0/Resources/Opcodes64:/Users/rboulanger/Library/Application Support/csound6/plugins64"




Here is what I get when I type in the commands from the risset manual and try to install a plug

db->  risset list

* else  @ 0.2.0        | Miscellaneous plugins  

* poly  @ 0.2.0        | Run multiple copies of an opcode in parallel/series  

* klib  @ 0.2.0        | hashtable / pool / string cache plugins  

* jsfx  @ 0.2.0        | Jesusonics effects in csound  

* rory  @ 0.2.0        | Opcodes to save/recall channels, triggers, etc  

db->  risset install else

Traceback (most recent call last):

  File "/usr/local/bin/risset", line 8, in <module>

    sys.exit(main())

  File "/usr/local/lib/python3.7/site-packages/risset.py", line 1284, in main

    ok = args.func(plugins_index, args)

  File "/usr/local/lib/python3.7/site-packages/risset.py", line 1139, in cmd_install

    error = plugins_index.install_plugin(plugin_definition, user=args.user)

  File "/usr/local/lib/python3.7/site-packages/risset.py", line 767, in install_plugin

    plugin_dll = self.get_plugin_dll(plugin)

  File "/usr/local/lib/python3.7/site-packages/risset.py", line 746, in get_plugin_dll

    path = resolve_path(binary_definition.url, Path(plugin.source).parent.as_posix())

AttributeError: 'Plugin' object has no attribute 'source'







_____________________________________________
Dr. Richard Boulanger
Professor of Electronic Production and Design
Professional Writing and Music Technology Division
Berklee College of Music

______________________________________________
OFFICE: 1126 Boylston St., Suite 201 (EPD), Suite 208 (Boulanger)

______________________________________________

President of Boulanger Labs - http://boulangerlabs.com
Author & Editor of The Csound Book - http://mitpress.mit.edu/books/csound-book
Author & Editor of The Audio Programming Book - http://mitpress.mit.edu/books/audio-programming-book
______________________________________________
about: http://www.boulangerlabs.com/#about
about: http://www.csounds.com/community/developers/dr-richard-boulanger/
music: http://www.csounds.com/community/developers/dr-richard-boulanger/dr-richard-boulanger-music/

______________________________________________
email: rboulanger@berklee.edu
facebook: https://www.facebook.com/richard.boulanger.58

On Sun, May 10, 2020 at 1:13 AM Steven Yi <stevenyi@gmail.com> wrote:

I'm not such a fan of submodules myself and I don't think it quite supports the use case. Additionally, supporting multiple repositories would also integrate with another thing we've talked about here which is the template git repo for opcode plugins. 

If an opcode plugin template repo has a plugins.json, and if the repo is pre-configured to work with Github Actions, it might be possible to have it setup for auto-compilation on multiple platforms.  Users could then clone the repo, develop a plugin, commit code, then the template project is setup to compile on multiple platforms and publish to the repo.  The repo could then be added to as a source to the sources.list for risset. 

Regardless, there's no pressing need to implement such a thing this moment but perhaps it's something to consider for the future.

On Sat, May 9, 2020 at 7:59 PM Eduardo Moguillansky <eduardo.moguillansky@gmail.com> wrote:

maybe git submodules would be a solution for that. Instead of adding your plugin directly to the repo you can add your repo as submodule. Or just ask for commit rights.

On 10.05.20 00:07, Steven Yi wrote:

Publishing a PR is the bottleneck mentioned. I am imagining a scenario of testing plugins with non-dev users before they're final and not wanting to have to do PR's to iterate (nor feeling the pressure to have a dev version in git history).

On Sat, May 9, 2020 at 5:34 PM Eduardo Moguillansky <eduardo.moguillansky@gmail.com> wrote:

On 09.05.20 22:42, Steven Yi wrote:

This is great to see, thanks!  I tested here on MacOS and it worked well. 

Some thoughts:

* I didn't see if there was support for ARM or ARM64 CPU type on Linux. Any thoughts on that?  (Thinking Raspberry Pi here)

These could be added, of course. I don't have the hardware to test that though so contributions are welcome.

* It would be liberating for users to be able to add their own repositories.  (Similar to apt sources.list)  I think it would remove a bottleneck for publishing new plugins.

Publishing a plugin is just a PR appart. You need to fork the risset-data repository, add your plugin to the plugins.json and add the binaries for each of your supported platform. Then do a PR or ask to be given rights to the repository.

Keeping everything in one repository makes the design simpler. For example, documentation can be built much easier this way.

* It would be nice to have this work with both CS6 and CS7 and future versions. I think that would have some ramifications on the plugin declaration among other things.

This can be adapted once CS7 is a thing. At the moment the amount of external plugins is so small that such complexity / flexibility is not yet needed.

I haven't had much time to respond to other emails but I think the proposal for local OPCODE dir is also a very good idea.

This would make things much tidier in fact.

On Fri, May 8, 2020 at 9:37 PM Eduardo Moguillansky <eduardo.moguillansky@gmail.com> wrote:

Hi,

here is a first attempt at a package manager for csound. I call it "risset".

https://github.com/csound-plugins/risset

Installation

1) Install git and python3, if needed

2) At a terminal:

    pip3 install risset

Quick Start

# list all available plugins for your platform
$ risset list

* else  @ 0.2.0        | Miscellaneous plugins  
* poly  @ 0.2.0        | Run multiple copies of an opcode in parallel/series  
* klib  @ 0.2.0        | hashtable / pool / string cache plugins  
* jsfx  @ 0.2.0        | Jesusonics effects in csound  [installed: 0.2.0]
* mverb  @ 1.3.7       | Artificial reverb based on a 2D waveguide mesh  
* rory  @ 0.2.0        | Opcodes to save/recall channels, triggers, etc 


# show information about a given plugin
$ risset show mverb

Plugin     : mverb
Installed  : 1.3.7
Author     : Michael Gogins
Abstract   : Artificial reverb based on a 2D waveguide mesh
Description:
    Verb is a modified 5-by-5 2D waveguide mesh reverberator. It is highly
    flexible and can generate ompelling and unique timbres ranging from
    traditional spaces to infinite morphing spaces or the simulation of
    metallic plates or cymbals. The plugin incorporates a 10-band parametric
    equalizer for timbral control and delay randomization to create more
    unusual effects.
Platforms: 
    * linux: Ubuntu 18.04
Opcodes:
    MVerb
Minimal csound version : 6.14

# Install a plugin
$ risset install mverb

Documentation

Documentation to all available opcodes is autogenerated and lives at:

https://github.com/csound-plugins/risset-data/tree/master/docs

Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Steven, your tkinter code (I think) was adapted by Francois from your API collection into his excellent and comprehensive suite of ctcsound tutorials. He advises using Anaconda and Jupiter notebooks (like Joaquin did at the last ICSC) and once everything is all set and working (after about two hours of setup) it's a pretty great system.

To get risset to work I spent the next day uninstalling all of it... that took a few hours as well.

Thanks...

Brew install Csound seems to work and one can say Brew uninstall Csound too... 

But then... for some reason even after uninstalling there seems to be a Csound6.13 hanging around!

Installing with the .dmg seems to install simultaneously with a brew install and some let you use the python opcodes and some do not (I guess it's path issues and that there are many Csound bits and pieces everywhere.

Dr. Richard Boulanger

Professor

Electronic Production and Design

Berklee College of Music

On May 10, 2020, at 10:00 AM, Steven Yi <stevenyi@gmail.com> wrote:



I don't recall ever writing a csound tutorial with tkinter, so I'm not sure what this is referring to.

Regarding building on macOS, I'm not sure how that relates to risset, but the instructions for building on macOS certainly need to be updated. I wrote the instructions in BUILD.md years ago. I stopped using macOS for a few years and resumed using it last fall. 

Since that time, someone else has submitted the Csound formula to the main homebrew package repository:

https://formulae.brew.sh/formula/csound

I've now removed my old homebrew tap from github. I'm going to do a quick pass through the BUILD.md right now to remove references to that tap. I'm not sure if Victor is still using the dependencies/* scripts written a while ago but that's an alternative to using Homebrew-installed dependencies.  Perhaps we need another email thread here about building macOS.

On Sun, May 10, 2020 at 4:01 AM Dr. Richard Boulanger <rboulanger@berklee.edu> wrote:

Hello Everyone.

I can't wait to explore and use this new utility - and be able to add plugins to Csound with "ease"

It is my hope that either:

ONE: it will be a simple thing for any and every MacUser (particularly non-developers) to someday be able to build from sources

(I followed the instructions, but still got many errors and some tips about what I needed to add to my .bash_profile)

(( Is it working?  Do I have the most recent developer build on my Mac?  Do I have only ONE version and the latest and most complete version of Csound running on my Mac?   Is HomeBrew the way to go?  ))

or

TWO: that the DMG will install everything, even plugins, or the directories that will let me add plugins or UDO or use ctcsound or 

the Csound API

or 

THREE:  that there is an uninstaller and clean installer so that we could remove ALL of the Csound dependencies and utilities and freshly install ONLY the latest versions (without having to purchase a new Mac or wipe our hard drives and reinstall the OS (which I have done in the past!)

(( As a sideNOTE: I did work until 5 am yesterday trying to get Jupyter Notebooks and ctcsound to work with Anaconda and Python 2.7 or 3.7 - but that's another email and long story.  I did get a lot of it to work eventually, but there is absolutely NO WAY that I would torture my students with that sort of PATH nightmare (( they would ALL drop the class and run to SuperCollider for sure. ))

(( PS - if you are reading this Steven Yi, you might like to know that your tkinter tutorial, the one that is supposed to put sliders up on the screen, so totally crashed my MacBook that it powered it DOWN !  Black screen !!! I have not seen this since 1986 or so.  WOW.  After three attempts and three blackouts, I didn't want to risk blowing all the fuses in here, so I just moved on.  ;-0. OK - please forgive this digression, let's get back to risset (whom, by the way, I miss very very much!)

And so..., I was super excited to read that risset worked and instantly and flawlessly on Mac OSX

Well.... it is 4:00 am and I have been working on this since 11 pm today. (taking a break from grading)

I have installed, uninstalled, brew-installed, installed from sources, reinstalled, removed, moved, added, included, symlinked and removed all sorts of things from my .bash_profile and .bashrc and from my machine itself

I hate to give up, but... this has been beating me up pretty badly

here is what I can report 

- in the risset manual it says that plugins are installed in:

macos: $HOME/Library/Application Support/csound6/plugins64




but there is no such directory on my system

- even after brew installing, brew installing from steven yi's instructions and site, and re-installing from the latest .dmg




It seems that everything is in... 




~/Library/Frameworks/CsoundLib64.framework/... 




But, I am not sure that there is a plugins folder in there?

- and so, I even tried creating a csound6 directory and plugins64 subdirectory in the Application Support folder (NOPE)




Below is my terminal output after installing and following the instructions

- NOTE: even though mverb is is the gogins folder it does not appear in the list, whereas the rory and ed's plugins do appear in the list.  

- NOTE:  I can not install anything

- NOTE:  I did try the --user option and did get a message that suggested how to fix my path by adding appropriate lines to my .bash_profile (which I did) (( I also was told about some things that I needed to add to my .bash_profile when I BrewInstalled Csound followng Steven Yi's instructions (which required many reinstall of broken utilities by the way)




Should it be this difficult?  Am I getting to old for this?  

How much hunting (and stack overflow) and trial and error (path + error message) must one endure to set up a Mac to be able to follow along with the great work that you are all doing?




Here is my .bash_profile ( I tossed everything out pretty much )




export PS1="db->  "

export DYLD_FRAMEWORK_PATH="$DYLD_FRAMEWORK_PATH:/usr/local/opt/csound/Frameworks"

export CLASSPATH="/usr/local/opt/csound/libexec/csnd6.jar:."

export OPCODE6DIR64="/Library/Frameworks/CsoundLib64.framework/Versions/6.0/Resources/Opcodes64:/Users/rboulanger/Library/Application Support/csound6/plugins64"




Here is what I get when I type in the commands from the risset manual and try to install a plug

db->  risset list

* else  @ 0.2.0        | Miscellaneous plugins  

* poly  @ 0.2.0        | Run multiple copies of an opcode in parallel/series  

* klib  @ 0.2.0        | hashtable / pool / string cache plugins  

* jsfx  @ 0.2.0        | Jesusonics effects in csound  

* rory  @ 0.2.0        | Opcodes to save/recall channels, triggers, etc  

db->  risset install else

Traceback (most recent call last):

  File "/usr/local/bin/risset", line 8, in <module>

    sys.exit(main())

  File "/usr/local/lib/python3.7/site-packages/risset.py", line 1284, in main

    ok = args.func(plugins_index, args)

  File "/usr/local/lib/python3.7/site-packages/risset.py", line 1139, in cmd_install

    error = plugins_index.install_plugin(plugin_definition, user=args.user)

  File "/usr/local/lib/python3.7/site-packages/risset.py", line 767, in install_plugin

    plugin_dll = self.get_plugin_dll(plugin)

  File "/usr/local/lib/python3.7/site-packages/risset.py", line 746, in get_plugin_dll

    path = resolve_path(binary_definition.url, Path(plugin.source).parent.as_posix())

AttributeError: 'Plugin' object has no attribute 'source'







_____________________________________________
Dr. Richard Boulanger
Professor of Electronic Production and Design
Professional Writing and Music Technology Division
Berklee College of Music

______________________________________________
OFFICE: 1126 Boylston St., Suite 201 (EPD), Suite 208 (Boulanger)

______________________________________________

President of Boulanger Labs - http://boulangerlabs.com
Author & Editor of The Csound Book - http://mitpress.mit.edu/books/csound-book
Author & Editor of The Audio Programming Book - http://mitpress.mit.edu/books/audio-programming-book
______________________________________________
about: http://www.boulangerlabs.com/#about
about: http://www.csounds.com/community/developers/dr-richard-boulanger/
music: http://www.csounds.com/community/developers/dr-richard-boulanger/dr-richard-boulanger-music/

______________________________________________
email: rboulanger@berklee.edu
facebook: https://www.facebook.com/richard.boulanger.58

On Sun, May 10, 2020 at 1:13 AM Steven Yi <stevenyi@gmail.com> wrote:

I'm not such a fan of submodules myself and I don't think it quite supports the use case. Additionally, supporting multiple repositories would also integrate with another thing we've talked about here which is the template git repo for opcode plugins. 

If an opcode plugin template repo has a plugins.json, and if the repo is pre-configured to work with Github Actions, it might be possible to have it setup for auto-compilation on multiple platforms.  Users could then clone the repo, develop a plugin, commit code, then the template project is setup to compile on multiple platforms and publish to the repo.  The repo could then be added to as a source to the sources.list for risset. 

Regardless, there's no pressing need to implement such a thing this moment but perhaps it's something to consider for the future.

On Sat, May 9, 2020 at 7:59 PM Eduardo Moguillansky <eduardo.moguillansky@gmail.com> wrote:

maybe git submodules would be a solution for that. Instead of adding your plugin directly to the repo you can add your repo as submodule. Or just ask for commit rights.

On 10.05.20 00:07, Steven Yi wrote:

Publishing a PR is the bottleneck mentioned. I am imagining a scenario of testing plugins with non-dev users before they're final and not wanting to have to do PR's to iterate (nor feeling the pressure to have a dev version in git history).

On Sat, May 9, 2020 at 5:34 PM Eduardo Moguillansky <eduardo.moguillansky@gmail.com> wrote:

On 09.05.20 22:42, Steven Yi wrote:

This is great to see, thanks!  I tested here on MacOS and it worked well. 

Some thoughts:

* I didn't see if there was support for ARM or ARM64 CPU type on Linux. Any thoughts on that?  (Thinking Raspberry Pi here)

These could be added, of course. I don't have the hardware to test that though so contributions are welcome.

* It would be liberating for users to be able to add their own repositories.  (Similar to apt sources.list)  I think it would remove a bottleneck for publishing new plugins.

Publishing a plugin is just a PR appart. You need to fork the risset-data repository, add your plugin to the plugins.json and add the binaries for each of your supported platform. Then do a PR or ask to be given rights to the repository.

Keeping everything in one repository makes the design simpler. For example, documentation can be built much easier this way.

* It would be nice to have this work with both CS6 and CS7 and future versions. I think that would have some ramifications on the plugin declaration among other things.

This can be adapted once CS7 is a thing. At the moment the amount of external plugins is so small that such complexity / flexibility is not yet needed.

I haven't had much time to respond to other emails but I think the proposal for local OPCODE dir is also a very good idea.

This would make things much tidier in fact.

On Fri, May 8, 2020 at 9:37 PM Eduardo Moguillansky <eduardo.moguillansky@gmail.com> wrote:

Hi,

here is a first attempt at a package manager for csound. I call it "risset".

https://github.com/csound-plugins/risset

Installation

1) Install git and python3, if needed

2) At a terminal:

    pip3 install risset

Quick Start

# list all available plugins for your platform
$ risset list

* else  @ 0.2.0        | Miscellaneous plugins  
* poly  @ 0.2.0        | Run multiple copies of an opcode in parallel/series  
* klib  @ 0.2.0        | hashtable / pool / string cache plugins  
* jsfx  @ 0.2.0        | Jesusonics effects in csound  [installed: 0.2.0]
* mverb  @ 1.3.7       | Artificial reverb based on a 2D waveguide mesh  
* rory  @ 0.2.0        | Opcodes to save/recall channels, triggers, etc 


# show information about a given plugin
$ risset show mverb

Plugin     : mverb
Installed  : 1.3.7
Author     : Michael Gogins
Abstract   : Artificial reverb based on a 2D waveguide mesh
Description:
    Verb is a modified 5-by-5 2D waveguide mesh reverberator. It is highly
    flexible and can generate ompelling and unique timbres ranging from
    traditional spaces to infinite morphing spaces or the simulation of
    metallic plates or cymbals. The plugin incorporates a 10-band parametric
    equalizer for timbral control and delay randomization to create more
    unusual effects.
Platforms: 
    * linux: Ubuntu 18.04
Opcodes:
    MVerb
Minimal csound version : 6.14

# Install a plugin
$ risset install mverb

Documentation

Documentation to all available opcodes is autogenerated and lives at:

https://github.com/csound-plugins/risset-data/tree/master/docs

Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Steven,

the example is in Francois Pinot's ctcsound cookbook - example 8. The last two in that subset are "serious"

- anyone else have a problem with these - screen goes dark

Ctcsound API Examples

These examples are based on Steven Yi's Python "How to use the Csound API" files on https://github.com/csound/csoundAPI_examples

All of the examples assume having the ctcsound module imported which is the module containing the Python interface to the Csound API. This must be executed before the examples are run.

This adaptation of Steven's examples as a notebook using ctcsound has been written by Mitch Kaufman.

The previous examples all work GREAT... but then....

Example 11 - Graphical User Interfaces

This example demonstrates a minimal Graphical User Interface application. The setup of Csound and starting of the CsoundPerformanceThread is done in the global scripting space. Afterwards, a Tkinter GUI is created that has one button. The button's callback (the command action) routes to a function that just sends an event to Csound.

For this example, since there is no need to synchronize continous channel data changes with Csound, it is more efficient to use the CsoundPerformanceThread, as it is a native thread. We use the CsoundPerformanceThread's inputMessage() function to ensure that the message is processed in a thread-safe manner.

In [15]:

from tkinter import *
from random import randint, random

###############################
# Our Orchestra for our project

orc = """
sr=44100
ksmps=32
nchnls=2
0dbfs=1

instr 1 
kenv linsegr 0, .05, 1, .05, .9, .8, 0
aout vco2 p4 * kenv, p5
aout moogladder aout, 2000, p6
outs aout, aout
endin"""

#c = ctcsound.Csound()    # create an instance of Csound
c.setOption("-odac")  # Set option for Csound
c.setOption("-m7")  # Set option for Csound
c.compileOrc(orc)     # Compile Orchestra from String

c.start()             # When compiling from strings, this call is necessary before doing any performing

perfThread = ctcsound.CsoundPerformanceThread(c.csound())
perfThread.play()

class Application(Frame):

    def __init__(self,master=None):
        master.title("Csound API GUI Example")
        self.items = []
        self.notes = []
        Frame.__init__(self,master)
        self.pack()
        self.createUI()
        self.master.protocol("WM_DELETE_WINDOW", self.quit)

    def createUI(self):
        self.size = 600
        self.canvas = Canvas(self,height=self.size,width=self.size,bg="darkgray")
        self.canvas.pack()
        # create button and setup the playNote() callback
        self.button = Button(self.canvas, text='Play Note', command=self.playNote)    
        self.button.pack()

    def playNote(self):
        perfThread.inputMessage("i1 0 2 .5 400 .25")

    def quit(self):
        self.master.destroy()
        perfThread.stop()
        perfThread.join()


app = Application(Tk())
app.mainloop()
c.reset()

Example 12 - Graphical User Interfaces

This example demonstrates a slightly more advanced GUI example. It uses a slider to allow setting the value of the frequency that the notes initiated by the button will play at.

Note: the actual use of update() here is not thread-safe. In real-world usage, we would need to drive Csound from a loop calling PerformKsmps to ensure thread-safety. For this example, the updating generally works as there are few things demanding computation.

In [16]:

from tkinter import *
from random import randint, random

###############################

# Our Orchestra for our project
orc = """
sr=44100
ksmps=32
nchnls=2
0dbfs=1

gkpch chnexport "freq", 1

instr 1 
kpch port gkpch, 0.01, i(gkpch)
printk .5, gkpch
kenv linsegr 0, .05, 1, .05, .9, .8, 0
aout vco2 p4 * kenv, kpch
aout moogladder aout, 2000, .25 
outs aout, aout
endin"""

#c = ctcsound.Csound()    # create an instance of Csound
c.setOption("-odac")  # Set option for Csound
c.setOption("-m7")  # Set option for Csound
c.compileOrc(orc)     # Compile Orchestra from String

c.start()             # When compiling from strings, this call is necessary before doing any performing

perfThread = ctcsound.CsoundPerformanceThread(c.csound())
perfThread.play()


def createChannel(channelName):
    chn, _ = c.channelPtr(channelName,
    ctcsound.CSOUND_CONTROL_CHANNEL | ctcsound.CSOUND_INPUT_CHANNEL)
    return chn

class SliderWrapper(object):
    def __init__(self, csound, channelName, slider):
        self.slider = slider
        self.channel = createChannel(channelName)

    def update(self):
        self.channel[0] = self.slider.get()

class Application(Frame):

    def __init__(self,master=None):
        master.title("Csound API GUI Example")
        self.items = []
        self.notes = []
        Frame.__init__(self,master)
        self.pack()
        self.createUI()
        self.master.protocol("WM_DELETE_WINDOW", self.quit)

    def createUI(self):
        self.size = 600
        self.canvas = Canvas(self,height=self.size,width=self.size)
        self.canvas.pack()
        self.button = Button(self.canvas, text='Play Note', command=self.playNote)    
        self.button.pack()
        self.freqSlider = Scale(self.canvas,from_=80.0, to=600.0,command=self.setFreq,label="Freq")
        self.freqSlider.pack()
        self.freqUpdater = SliderWrapper(c, "freq", self.freqSlider)

    def playNote(self):
        perfThread.inputMessage("i1 0 2 .3")

    def setFreq(self, val):
        print(val)
        self.freqUpdater.update()

    def quit(self):
        self.master.destroy()
        perfThread.stop()
        perfThread.join()


app = Application(Tk())
app.mainloop()
c.stop
del c

_____________________________________________
Dr. Richard Boulanger
Professor of Electronic Production and Design
Professional Writing and Music Technology Division
Berklee College of Music

______________________________________________
OFFICE: 1126 Boylston St., Suite 201 (EPD), Suite 208 (Boulanger)

______________________________________________

President of Boulanger Labs - http://boulangerlabs.com
Author & Editor of The Csound Book - http://mitpress.mit.edu/books/csound-book
Author & Editor of The Audio Programming Book - http://mitpress.mit.edu/books/audio-programming-book
______________________________________________
about: http://www.boulangerlabs.com/#about
about: http://www.csounds.com/community/developers/dr-richard-boulanger/
music: http://www.csounds.com/community/developers/dr-richard-boulanger/dr-richard-boulanger-music/

______________________________________________
email: rboulanger@berklee.edu
facebook: https://www.facebook.com/richard.boulanger.58

On Sun, May 10, 2020 at 11:02 AM Dr. Richard Boulanger <rboulanger@berklee.edu> wrote:

Steven, your tkinter code (I think) was adapted by Francois from your API collection into his excellent and comprehensive suite of ctcsound tutorials. He advises using Anaconda and Jupiter notebooks (like Joaquin did at the last ICSC) and once everything is all set and working (after about two hours of setup) it's a pretty great system.

To get risset to work I spent the next day uninstalling all of it... that took a few hours as well.

Thanks...

Brew install Csound seems to work and one can say Brew uninstall Csound too... 

But then... for some reason even after uninstalling there seems to be a Csound6.13 hanging around!

Installing with the .dmg seems to install simultaneously with a brew install and some let you use the python opcodes and some do not (I guess it's path issues and that there are many Csound bits and pieces everywhere.

Dr. Richard Boulanger

Professor

Electronic Production and Design

Berklee College of Music

On May 10, 2020, at 10:00 AM, Steven Yi <stevenyi@gmail.com> wrote:



I don't recall ever writing a csound tutorial with tkinter, so I'm not sure what this is referring to.

Regarding building on macOS, I'm not sure how that relates to risset, but the instructions for building on macOS certainly need to be updated. I wrote the instructions in BUILD.md years ago. I stopped using macOS for a few years and resumed using it last fall. 

Since that time, someone else has submitted the Csound formula to the main homebrew package repository:

https://formulae.brew.sh/formula/csound

I've now removed my old homebrew tap from github. I'm going to do a quick pass through the BUILD.md right now to remove references to that tap. I'm not sure if Victor is still using the dependencies/* scripts written a while ago but that's an alternative to using Homebrew-installed dependencies.  Perhaps we need another email thread here about building macOS.

On Sun, May 10, 2020 at 4:01 AM Dr. Richard Boulanger <rboulanger@berklee.edu> wrote:

Hello Everyone.

I can't wait to explore and use this new utility - and be able to add plugins to Csound with "ease"

It is my hope that either:

ONE: it will be a simple thing for any and every MacUser (particularly non-developers) to someday be able to build from sources

(I followed the instructions, but still got many errors and some tips about what I needed to add to my .bash_profile)

(( Is it working?  Do I have the most recent developer build on my Mac?  Do I have only ONE version and the latest and most complete version of Csound running on my Mac?   Is HomeBrew the way to go?  ))

or

TWO: that the DMG will install everything, even plugins, or the directories that will let me add plugins or UDO or use ctcsound or 

the Csound API

or 

THREE:  that there is an uninstaller and clean installer so that we could remove ALL of the Csound dependencies and utilities and freshly install ONLY the latest versions (without having to purchase a new Mac or wipe our hard drives and reinstall the OS (which I have done in the past!)

(( As a sideNOTE: I did work until 5 am yesterday trying to get Jupyter Notebooks and ctcsound to work with Anaconda and Python 2.7 or 3.7 - but that's another email and long story.  I did get a lot of it to work eventually, but there is absolutely NO WAY that I would torture my students with that sort of PATH nightmare (( they would ALL drop the class and run to SuperCollider for sure. ))

(( PS - if you are reading this Steven Yi, you might like to know that your tkinter tutorial, the one that is supposed to put sliders up on the screen, so totally crashed my MacBook that it powered it DOWN !  Black screen !!! I have not seen this since 1986 or so.  WOW.  After three attempts and three blackouts, I didn't want to risk blowing all the fuses in here, so I just moved on.  ;-0. OK - please forgive this digression, let's get back to risset (whom, by the way, I miss very very much!)

And so..., I was super excited to read that risset worked and instantly and flawlessly on Mac OSX

Well.... it is 4:00 am and I have been working on this since 11 pm today. (taking a break from grading)

I have installed, uninstalled, brew-installed, installed from sources, reinstalled, removed, moved, added, included, symlinked and removed all sorts of things from my .bash_profile and .bashrc and from my machine itself

I hate to give up, but... this has been beating me up pretty badly

here is what I can report 

- in the risset manual it says that plugins are installed in:

macos: $HOME/Library/Application Support/csound6/plugins64




but there is no such directory on my system

- even after brew installing, brew installing from steven yi's instructions and site, and re-installing from the latest .dmg




It seems that everything is in... 




~/Library/Frameworks/CsoundLib64.framework/... 




But, I am not sure that there is a plugins folder in there?

- and so, I even tried creating a csound6 directory and plugins64 subdirectory in the Application Support folder (NOPE)




Below is my terminal output after installing and following the instructions

- NOTE: even though mverb is is the gogins folder it does not appear in the list, whereas the rory and ed's plugins do appear in the list.  

- NOTE:  I can not install anything

- NOTE:  I did try the --user option and did get a message that suggested how to fix my path by adding appropriate lines to my .bash_profile (which I did) (( I also was told about some things that I needed to add to my .bash_profile when I BrewInstalled Csound followng Steven Yi's instructions (which required many reinstall of broken utilities by the way)




Should it be this difficult?  Am I getting to old for this?  

How much hunting (and stack overflow) and trial and error (path + error message) must one endure to set up a Mac to be able to follow along with the great work that you are all doing?




Here is my .bash_profile ( I tossed everything out pretty much )




export PS1="db->  "

export DYLD_FRAMEWORK_PATH="$DYLD_FRAMEWORK_PATH:/usr/local/opt/csound/Frameworks"

export CLASSPATH="/usr/local/opt/csound/libexec/csnd6.jar:."

export OPCODE6DIR64="/Library/Frameworks/CsoundLib64.framework/Versions/6.0/Resources/Opcodes64:/Users/rboulanger/Library/Application Support/csound6/plugins64"




Here is what I get when I type in the commands from the risset manual and try to install a plug

db->  risset list

* else  @ 0.2.0        | Miscellaneous plugins  

* poly  @ 0.2.0        | Run multiple copies of an opcode in parallel/series  

* klib  @ 0.2.0        | hashtable / pool / string cache plugins  

* jsfx  @ 0.2.0        | Jesusonics effects in csound  

* rory  @ 0.2.0        | Opcodes to save/recall channels, triggers, etc  

db->  risset install else

Traceback (most recent call last):

  File "/usr/local/bin/risset", line 8, in <module>

    sys.exit(main())

  File "/usr/local/lib/python3.7/site-packages/risset.py", line 1284, in main

    ok = args.func(plugins_index, args)

  File "/usr/local/lib/python3.7/site-packages/risset.py", line 1139, in cmd_install

    error = plugins_index.install_plugin(plugin_definition, user=args.user)

  File "/usr/local/lib/python3.7/site-packages/risset.py", line 767, in install_plugin

    plugin_dll = self.get_plugin_dll(plugin)

  File "/usr/local/lib/python3.7/site-packages/risset.py", line 746, in get_plugin_dll

    path = resolve_path(binary_definition.url, Path(plugin.source).parent.as_posix())

AttributeError: 'Plugin' object has no attribute 'source'







_____________________________________________
Dr. Richard Boulanger
Professor of Electronic Production and Design
Professional Writing and Music Technology Division
Berklee College of Music

______________________________________________
OFFICE: 1126 Boylston St., Suite 201 (EPD), Suite 208 (Boulanger)

______________________________________________

President of Boulanger Labs - http://boulangerlabs.com
Author & Editor of The Csound Book - http://mitpress.mit.edu/books/csound-book
Author & Editor of The Audio Programming Book - http://mitpress.mit.edu/books/audio-programming-book
______________________________________________
about: http://www.boulangerlabs.com/#about
about: http://www.csounds.com/community/developers/dr-richard-boulanger/
music: http://www.csounds.com/community/developers/dr-richard-boulanger/dr-richard-boulanger-music/

______________________________________________
email: rboulanger@berklee.edu
facebook: https://www.facebook.com/richard.boulanger.58

On Sun, May 10, 2020 at 1:13 AM Steven Yi <stevenyi@gmail.com> wrote:

I'm not such a fan of submodules myself and I don't think it quite supports the use case. Additionally, supporting multiple repositories would also integrate with another thing we've talked about here which is the template git repo for opcode plugins. 

If an opcode plugin template repo has a plugins.json, and if the repo is pre-configured to work with Github Actions, it might be possible to have it setup for auto-compilation on multiple platforms.  Users could then clone the repo, develop a plugin, commit code, then the template project is setup to compile on multiple platforms and publish to the repo.  The repo could then be added to as a source to the sources.list for risset. 

Regardless, there's no pressing need to implement such a thing this moment but perhaps it's something to consider for the future.

On Sat, May 9, 2020 at 7:59 PM Eduardo Moguillansky <eduardo.moguillansky@gmail.com> wrote:

maybe git submodules would be a solution for that. Instead of adding your plugin directly to the repo you can add your repo as submodule. Or just ask for commit rights.

On 10.05.20 00:07, Steven Yi wrote:

Publishing a PR is the bottleneck mentioned. I am imagining a scenario of testing plugins with non-dev users before they're final and not wanting to have to do PR's to iterate (nor feeling the pressure to have a dev version in git history).

On Sat, May 9, 2020 at 5:34 PM Eduardo Moguillansky <eduardo.moguillansky@gmail.com> wrote:

On 09.05.20 22:42, Steven Yi wrote:

This is great to see, thanks!  I tested here on MacOS and it worked well. 

Some thoughts:

* I didn't see if there was support for ARM or ARM64 CPU type on Linux. Any thoughts on that?  (Thinking Raspberry Pi here)

These could be added, of course. I don't have the hardware to test that though so contributions are welcome.

* It would be liberating for users to be able to add their own repositories.  (Similar to apt sources.list)  I think it would remove a bottleneck for publishing new plugins.

Publishing a plugin is just a PR appart. You need to fork the risset-data repository, add your plugin to the plugins.json and add the binaries for each of your supported platform. Then do a PR or ask to be given rights to the repository.

Keeping everything in one repository makes the design simpler. For example, documentation can be built much easier this way.

* It would be nice to have this work with both CS6 and CS7 and future versions. I think that would have some ramifications on the plugin declaration among other things.

This can be adapted once CS7 is a thing. At the moment the amount of external plugins is so small that such complexity / flexibility is not yet needed.

I haven't had much time to respond to other emails but I think the proposal for local OPCODE dir is also a very good idea.

This would make things much tidier in fact.

On Fri, May 8, 2020 at 9:37 PM Eduardo Moguillansky <eduardo.moguillansky@gmail.com> wrote:

Hi,

here is a first attempt at a package manager for csound. I call it "risset".

https://github.com/csound-plugins/risset

Installation

1) Install git and python3, if needed

2) At a terminal:

    pip3 install risset

Quick Start

# list all available plugins for your platform
$ risset list

* else  @ 0.2.0        | Miscellaneous plugins  
* poly  @ 0.2.0        | Run multiple copies of an opcode in parallel/series  
* klib  @ 0.2.0        | hashtable / pool / string cache plugins  
* jsfx  @ 0.2.0        | Jesusonics effects in csound  [installed: 0.2.0]
* mverb  @ 1.3.7       | Artificial reverb based on a 2D waveguide mesh  
* rory  @ 0.2.0        | Opcodes to save/recall channels, triggers, etc 


# show information about a given plugin
$ risset show mverb

Plugin     : mverb
Installed  : 1.3.7
Author     : Michael Gogins
Abstract   : Artificial reverb based on a 2D waveguide mesh
Description:
    Verb is a modified 5-by-5 2D waveguide mesh reverberator. It is highly
    flexible and can generate ompelling and unique timbres ranging from
    traditional spaces to infinite morphing spaces or the simulation of
    metallic plates or cymbals. The plugin incorporates a 10-band parametric
    equalizer for timbral control and delay randomization to create more
    unusual effects.
Platforms: 
    * linux: Ubuntu 18.04
Opcodes:
    MVerb
Minimal csound version : 6.14

# Install a plugin
$ risset install mverb

Documentation

Documentation to all available opcodes is autogenerated and lives at:

https://github.com/csound-plugins/risset-data/tree/master/docs

Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Hi,

here is a first attempt at a package manager for csound. I call it "risset".

https://github.com/csound-plugins/risset

Installation

1) Install git and python3, if needed

2) At a terminal:

    pip3 install risset

Quick Start

# list all available plugins for your platform
$ risset list

* else  @ 0.2.0        | Miscellaneous plugins  
* poly  @ 0.2.0        | Run multiple copies of an opcode in parallel/series  
* klib  @ 0.2.0        | hashtable / pool / string cache plugins  
* jsfx  @ 0.2.0        | Jesusonics effects in csound  [installed: 0.2.0]
* mverb  @ 1.3.7       | Artificial reverb based on a 2D waveguide mesh  
* rory  @ 0.2.0        | Opcodes to save/recall channels, triggers, etc 


# show information about a given plugin
$ risset show mverb

Plugin     : mverb
Installed  : 1.3.7
Author     : Michael Gogins
Abstract   : Artificial reverb based on a 2D waveguide mesh
Description:
    Verb is a modified 5-by-5 2D waveguide mesh reverberator. It is highly
    flexible and can generate ompelling and unique timbres ranging from
    traditional spaces to infinite morphing spaces or the simulation of
    metallic plates or cymbals. The plugin incorporates a 10-band parametric
    equalizer for timbral control and delay randomization to create more
    unusual effects.
Platforms: 
    * linux: Ubuntu 18.04
Opcodes:
    MVerb
Minimal csound version : 6.14

# Install a plugin
$ risset install mverb

Documentation

Documentation to all available opcodes is autogenerated and lives at:

https://github.com/csound-plugins/risset-data/tree/master/docs

Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

These two examples work fine for me on Ubuntu Linux 18.04, running without a notebook, i.e. as standalone Python scripts.

I had to make the following changes:

-- Install the "python-tk" system package.

-- Change "from tkinter import *" to "from Tkinter import *".

-- Add "import ctcsound".

-- Uncomment this line: "#c = ctcsound.Csound()    # create an instance of Csound"

-- Change "-odac" to "-odac:plughw:1,0" in order to use ALSA.

Regards,

Mike

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

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

On Sun, May 10, 2020 at 11:24 AM Dr. Richard Boulanger <rboulanger@berklee.edu> wrote:

Steven,

the example is in Francois Pinot's ctcsound cookbook - example 8. The last two in that subset are "serious"

- anyone else have a problem with these - screen goes dark

Ctcsound API Examples

These examples are based on Steven Yi's Python "How to use the Csound API" files on https://github.com/csound/csoundAPI_examples

All of the examples assume having the ctcsound module imported which is the module containing the Python interface to the Csound API. This must be executed before the examples are run.

This adaptation of Steven's examples as a notebook using ctcsound has been written by Mitch Kaufman.

The previous examples all work GREAT... but then....

Example 11 - Graphical User Interfaces

This example demonstrates a minimal Graphical User Interface application. The setup of Csound and starting of the CsoundPerformanceThread is done in the global scripting space. Afterwards, a Tkinter GUI is created that has one button. The button's callback (the command action) routes to a function that just sends an event to Csound.

For this example, since there is no need to synchronize continous channel data changes with Csound, it is more efficient to use the CsoundPerformanceThread, as it is a native thread. We use the CsoundPerformanceThread's inputMessage() function to ensure that the message is processed in a thread-safe manner.

In [15]:

from tkinter import *
from random import randint, random

###############################
# Our Orchestra for our project

orc = """
sr=44100
ksmps=32
nchnls=2
0dbfs=1

instr 1 
kenv linsegr 0, .05, 1, .05, .9, .8, 0
aout vco2 p4 * kenv, p5
aout moogladder aout, 2000, p6
outs aout, aout
endin"""

#c = ctcsound.Csound()    # create an instance of Csound
c.setOption("-odac")  # Set option for Csound
c.setOption("-m7")  # Set option for Csound
c.compileOrc(orc)     # Compile Orchestra from String

c.start()             # When compiling from strings, this call is necessary before doing any performing

perfThread = ctcsound.CsoundPerformanceThread(c.csound())
perfThread.play()

class Application(Frame):

    def __init__(self,master=None):
        master.title("Csound API GUI Example")
        self.items = []
        self.notes = []
        Frame.__init__(self,master)
        self.pack()
        self.createUI()
        self.master.protocol("WM_DELETE_WINDOW", self.quit)

    def createUI(self):
        self.size = 600
        self.canvas = Canvas(self,height=self.size,width=self.size,bg="darkgray")
        self.canvas.pack()
        # create button and setup the playNote() callback
        self.button = Button(self.canvas, text='Play Note', command=self.playNote)    
        self.button.pack()

    def playNote(self):
        perfThread.inputMessage("i1 0 2 .5 400 .25")

    def quit(self):
        self.master.destroy()
        perfThread.stop()
        perfThread.join()


app = Application(Tk())
app.mainloop()
c.reset()

Example 12 - Graphical User Interfaces

This example demonstrates a slightly more advanced GUI example. It uses a slider to allow setting the value of the frequency that the notes initiated by the button will play at.

Note: the actual use of update() here is not thread-safe. In real-world usage, we would need to drive Csound from a loop calling PerformKsmps to ensure thread-safety. For this example, the updating generally works as there are few things demanding computation.

In [16]:

from tkinter import *
from random import randint, random

###############################

# Our Orchestra for our project
orc = """
sr=44100
ksmps=32
nchnls=2
0dbfs=1

gkpch chnexport "freq", 1

instr 1 
kpch port gkpch, 0.01, i(gkpch)
printk .5, gkpch
kenv linsegr 0, .05, 1, .05, .9, .8, 0
aout vco2 p4 * kenv, kpch
aout moogladder aout, 2000, .25 
outs aout, aout
endin"""

#c = ctcsound.Csound()    # create an instance of Csound
c.setOption("-odac")  # Set option for Csound
c.setOption("-m7")  # Set option for Csound
c.compileOrc(orc)     # Compile Orchestra from String

c.start()             # When compiling from strings, this call is necessary before doing any performing

perfThread = ctcsound.CsoundPerformanceThread(c.csound())
perfThread.play()


def createChannel(channelName):
    chn, _ = c.channelPtr(channelName,
    ctcsound.CSOUND_CONTROL_CHANNEL | ctcsound.CSOUND_INPUT_CHANNEL)
    return chn

class SliderWrapper(object):
    def __init__(self, csound, channelName, slider):
        self.slider = slider
        self.channel = createChannel(channelName)

    def update(self):
        self.channel[0] = self.slider.get()

class Application(Frame):

    def __init__(self,master=None):
        master.title("Csound API GUI Example")
        self.items = []
        self.notes = []
        Frame.__init__(self,master)
        self.pack()
        self.createUI()
        self.master.protocol("WM_DELETE_WINDOW", self.quit)

    def createUI(self):
        self.size = 600
        self.canvas = Canvas(self,height=self.size,width=self.size)
        self.canvas.pack()
        self.button = Button(self.canvas, text='Play Note', command=self.playNote)    
        self.button.pack()
        self.freqSlider = Scale(self.canvas,from_=80.0, to=600.0,command=self.setFreq,label="Freq")
        self.freqSlider.pack()
        self.freqUpdater = SliderWrapper(c, "freq", self.freqSlider)

    def playNote(self):
        perfThread.inputMessage("i1 0 2 .3")

    def setFreq(self, val):
        print(val)
        self.freqUpdater.update()

    def quit(self):
        self.master.destroy()
        perfThread.stop()
        perfThread.join()


app = Application(Tk())
app.mainloop()
c.stop
del c

_____________________________________________
Dr. Richard Boulanger
Professor of Electronic Production and Design
Professional Writing and Music Technology Division
Berklee College of Music

______________________________________________
OFFICE: 1126 Boylston St., Suite 201 (EPD), Suite 208 (Boulanger)

______________________________________________

President of Boulanger Labs - http://boulangerlabs.com
Author & Editor of The Csound Book - http://mitpress.mit.edu/books/csound-book
Author & Editor of The Audio Programming Book - http://mitpress.mit.edu/books/audio-programming-book
______________________________________________
about: http://www.boulangerlabs.com/#about
about: http://www.csounds.com/community/developers/dr-richard-boulanger/
music: http://www.csounds.com/community/developers/dr-richard-boulanger/dr-richard-boulanger-music/

______________________________________________
email: rboulanger@berklee.edu
facebook: https://www.facebook.com/richard.boulanger.58

On Sun, May 10, 2020 at 11:02 AM Dr. Richard Boulanger <rboulanger@berklee.edu> wrote:

Steven, your tkinter code (I think) was adapted by Francois from your API collection into his excellent and comprehensive suite of ctcsound tutorials. He advises using Anaconda and Jupiter notebooks (like Joaquin did at the last ICSC) and once everything is all set and working (after about two hours of setup) it's a pretty great system.

To get risset to work I spent the next day uninstalling all of it... that took a few hours as well.

Thanks...

Brew install Csound seems to work and one can say Brew uninstall Csound too... 

But then... for some reason even after uninstalling there seems to be a Csound6.13 hanging around!

Installing with the .dmg seems to install simultaneously with a brew install and some let you use the python opcodes and some do not (I guess it's path issues and that there are many Csound bits and pieces everywhere.

Dr. Richard Boulanger

Professor

Electronic Production and Design

Berklee College of Music

On May 10, 2020, at 10:00 AM, Steven Yi <stevenyi@gmail.com> wrote:



I don't recall ever writing a csound tutorial with tkinter, so I'm not sure what this is referring to.

Regarding building on macOS, I'm not sure how that relates to risset, but the instructions for building on macOS certainly need to be updated. I wrote the instructions in BUILD.md years ago. I stopped using macOS for a few years and resumed using it last fall. 

Since that time, someone else has submitted the Csound formula to the main homebrew package repository:

https://formulae.brew.sh/formula/csound

I've now removed my old homebrew tap from github. I'm going to do a quick pass through the BUILD.md right now to remove references to that tap. I'm not sure if Victor is still using the dependencies/* scripts written a while ago but that's an alternative to using Homebrew-installed dependencies.  Perhaps we need another email thread here about building macOS.

On Sun, May 10, 2020 at 4:01 AM Dr. Richard Boulanger <rboulanger@berklee.edu> wrote:

Hello Everyone.

I can't wait to explore and use this new utility - and be able to add plugins to Csound with "ease"

It is my hope that either:

ONE: it will be a simple thing for any and every MacUser (particularly non-developers) to someday be able to build from sources

(I followed the instructions, but still got many errors and some tips about what I needed to add to my .bash_profile)

(( Is it working?  Do I have the most recent developer build on my Mac?  Do I have only ONE version and the latest and most complete version of Csound running on my Mac?   Is HomeBrew the way to go?  ))

or

TWO: that the DMG will install everything, even plugins, or the directories that will let me add plugins or UDO or use ctcsound or 

the Csound API

or 

THREE:  that there is an uninstaller and clean installer so that we could remove ALL of the Csound dependencies and utilities and freshly install ONLY the latest versions (without having to purchase a new Mac or wipe our hard drives and reinstall the OS (which I have done in the past!)

(( As a sideNOTE: I did work until 5 am yesterday trying to get Jupyter Notebooks and ctcsound to work with Anaconda and Python 2.7 or 3.7 - but that's another email and long story.  I did get a lot of it to work eventually, but there is absolutely NO WAY that I would torture my students with that sort of PATH nightmare (( they would ALL drop the class and run to SuperCollider for sure. ))

(( PS - if you are reading this Steven Yi, you might like to know that your tkinter tutorial, the one that is supposed to put sliders up on the screen, so totally crashed my MacBook that it powered it DOWN !  Black screen !!! I have not seen this since 1986 or so.  WOW.  After three attempts and three blackouts, I didn't want to risk blowing all the fuses in here, so I just moved on.  ;-0. OK - please forgive this digression, let's get back to risset (whom, by the way, I miss very very much!)

And so..., I was super excited to read that risset worked and instantly and flawlessly on Mac OSX

Well.... it is 4:00 am and I have been working on this since 11 pm today. (taking a break from grading)

I have installed, uninstalled, brew-installed, installed from sources, reinstalled, removed, moved, added, included, symlinked and removed all sorts of things from my .bash_profile and .bashrc and from my machine itself

I hate to give up, but... this has been beating me up pretty badly

here is what I can report 

- in the risset manual it says that plugins are installed in:

macos: $HOME/Library/Application Support/csound6/plugins64




but there is no such directory on my system

- even after brew installing, brew installing from steven yi's instructions and site, and re-installing from the latest .dmg




It seems that everything is in... 




~/Library/Frameworks/CsoundLib64.framework/... 




But, I am not sure that there is a plugins folder in there?

- and so, I even tried creating a csound6 directory and plugins64 subdirectory in the Application Support folder (NOPE)




Below is my terminal output after installing and following the instructions

- NOTE: even though mverb is is the gogins folder it does not appear in the list, whereas the rory and ed's plugins do appear in the list.  

- NOTE:  I can not install anything

- NOTE:  I did try the --user option and did get a message that suggested how to fix my path by adding appropriate lines to my .bash_profile (which I did) (( I also was told about some things that I needed to add to my .bash_profile when I BrewInstalled Csound followng Steven Yi's instructions (which required many reinstall of broken utilities by the way)




Should it be this difficult?  Am I getting to old for this?  

How much hunting (and stack overflow) and trial and error (path + error message) must one endure to set up a Mac to be able to follow along with the great work that you are all doing?




Here is my .bash_profile ( I tossed everything out pretty much )




export PS1="db->  "

export DYLD_FRAMEWORK_PATH="$DYLD_FRAMEWORK_PATH:/usr/local/opt/csound/Frameworks"

export CLASSPATH="/usr/local/opt/csound/libexec/csnd6.jar:."

export OPCODE6DIR64="/Library/Frameworks/CsoundLib64.framework/Versions/6.0/Resources/Opcodes64:/Users/rboulanger/Library/Application Support/csound6/plugins64"




Here is what I get when I type in the commands from the risset manual and try to install a plug

db->  risset list

* else  @ 0.2.0        | Miscellaneous plugins  

* poly  @ 0.2.0        | Run multiple copies of an opcode in parallel/series  

* klib  @ 0.2.0        | hashtable / pool / string cache plugins  

* jsfx  @ 0.2.0        | Jesusonics effects in csound  

* rory  @ 0.2.0        | Opcodes to save/recall channels, triggers, etc  

db->  risset install else

Traceback (most recent call last):

  File "/usr/local/bin/risset", line 8, in <module>

    sys.exit(main())

  File "/usr/local/lib/python3.7/site-packages/risset.py", line 1284, in main

    ok = args.func(plugins_index, args)

  File "/usr/local/lib/python3.7/site-packages/risset.py", line 1139, in cmd_install

    error = plugins_index.install_plugin(plugin_definition, user=args.user)

  File "/usr/local/lib/python3.7/site-packages/risset.py", line 767, in install_plugin

    plugin_dll = self.get_plugin_dll(plugin)

  File "/usr/local/lib/python3.7/site-packages/risset.py", line 746, in get_plugin_dll

    path = resolve_path(binary_definition.url, Path(plugin.source).parent.as_posix())

AttributeError: 'Plugin' object has no attribute 'source'







_____________________________________________
Dr. Richard Boulanger
Professor of Electronic Production and Design
Professional Writing and Music Technology Division
Berklee College of Music

______________________________________________
OFFICE: 1126 Boylston St., Suite 201 (EPD), Suite 208 (Boulanger)

______________________________________________

President of Boulanger Labs - http://boulangerlabs.com
Author & Editor of The Csound Book - http://mitpress.mit.edu/books/csound-book
Author & Editor of The Audio Programming Book - http://mitpress.mit.edu/books/audio-programming-book
______________________________________________
about: http://www.boulangerlabs.com/#about
about: http://www.csounds.com/community/developers/dr-richard-boulanger/
music: http://www.csounds.com/community/developers/dr-richard-boulanger/dr-richard-boulanger-music/

______________________________________________
email: rboulanger@berklee.edu
facebook: https://www.facebook.com/richard.boulanger.58

On Sun, May 10, 2020 at 1:13 AM Steven Yi <stevenyi@gmail.com> wrote:

I'm not such a fan of submodules myself and I don't think it quite supports the use case. Additionally, supporting multiple repositories would also integrate with another thing we've talked about here which is the template git repo for opcode plugins. 

If an opcode plugin template repo has a plugins.json, and if the repo is pre-configured to work with Github Actions, it might be possible to have it setup for auto-compilation on multiple platforms.  Users could then clone the repo, develop a plugin, commit code, then the template project is setup to compile on multiple platforms and publish to the repo.  The repo could then be added to as a source to the sources.list for risset. 

Regardless, there's no pressing need to implement such a thing this moment but perhaps it's something to consider for the future.

On Sat, May 9, 2020 at 7:59 PM Eduardo Moguillansky <eduardo.moguillansky@gmail.com> wrote:

maybe git submodules would be a solution for that. Instead of adding your plugin directly to the repo you can add your repo as submodule. Or just ask for commit rights.

On 10.05.20 00:07, Steven Yi wrote:

Publishing a PR is the bottleneck mentioned. I am imagining a scenario of testing plugins with non-dev users before they're final and not wanting to have to do PR's to iterate (nor feeling the pressure to have a dev version in git history).

On Sat, May 9, 2020 at 5:34 PM Eduardo Moguillansky <eduardo.moguillansky@gmail.com> wrote:

On 09.05.20 22:42, Steven Yi wrote:

This is great to see, thanks!  I tested here on MacOS and it worked well. 

Some thoughts:

* I didn't see if there was support for ARM or ARM64 CPU type on Linux. Any thoughts on that?  (Thinking Raspberry Pi here)

These could be added, of course. I don't have the hardware to test that though so contributions are welcome.

* It would be liberating for users to be able to add their own repositories.  (Similar to apt sources.list)  I think it would remove a bottleneck for publishing new plugins.

Publishing a plugin is just a PR appart. You need to fork the risset-data repository, add your plugin to the plugins.json and add the binaries for each of your supported platform. Then do a PR or ask to be given rights to the repository.

Keeping everything in one repository makes the design simpler. For example, documentation can be built much easier this way.

* It would be nice to have this work with both CS6 and CS7 and future versions. I think that would have some ramifications on the plugin declaration among other things.

This can be adapted once CS7 is a thing. At the moment the amount of external plugins is so small that such complexity / flexibility is not yet needed.

I haven't had much time to respond to other emails but I think the proposal for local OPCODE dir is also a very good idea.

This would make things much tidier in fact.

On Fri, May 8, 2020 at 9:37 PM Eduardo Moguillansky <eduardo.moguillansky@gmail.com> wrote:

Hi,

here is a first attempt at a package manager for csound. I call it "risset".

https://github.com/csound-plugins/risset

Installation

1) Install git and python3, if needed

2) At a terminal:

    pip3 install risset

Quick Start

# list all available plugins for your platform
$ risset list

* else  @ 0.2.0        | Miscellaneous plugins  
* poly  @ 0.2.0        | Run multiple copies of an opcode in parallel/series  
* klib  @ 0.2.0        | hashtable / pool / string cache plugins  
* jsfx  @ 0.2.0        | Jesusonics effects in csound  [installed: 0.2.0]
* mverb  @ 1.3.7       | Artificial reverb based on a 2D waveguide mesh  
* rory  @ 0.2.0        | Opcodes to save/recall channels, triggers, etc 


# show information about a given plugin
$ risset show mverb

Plugin     : mverb
Installed  : 1.3.7
Author     : Michael Gogins
Abstract   : Artificial reverb based on a 2D waveguide mesh
Description:
    Verb is a modified 5-by-5 2D waveguide mesh reverberator. It is highly
    flexible and can generate ompelling and unique timbres ranging from
    traditional spaces to infinite morphing spaces or the simulation of
    metallic plates or cymbals. The plugin incorporates a 10-band parametric
    equalizer for timbral control and delay randomization to create more
    unusual effects.
Platforms: 
    * linux: Ubuntu 18.04
Opcodes:
    MVerb
Minimal csound version : 6.14

# Install a plugin
$ risset install mverb

Documentation

Documentation to all available opcodes is autogenerated and lives at:

https://github.com/csound-plugins/risset-data/tree/master/docs

Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here