[Csnd] csound plugins repository
Date | 2019-03-13 13:13 |
From | Eduardo Moguillansky |
Subject | [Csnd] csound plugins repository |
Hi. I created a repository with a collection of new plugins for csound: https://github.com/gesellkammer/csound-plugins The most relevant contribution are two plugins "poly" and "polyseq" which allow to control multiple instances of an opcode either in parallel (to make complex banks of oscillators, to control complex spatialization, etc) or in series (to generate filter banks, parametric eqs, etc). https://github.com/gesellkammer/csound-plugins/wiki/poly These are very easy to install provided you have a compiler and cmake installed. At this stage there are no prebuilt binaries, but the build script should work for all platforms. I would very much welcome testing and contributions to this collection. best, Eduardo Moguillansky 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 |
Date | 2019-03-13 13:35 |
From | Tarmo Johannes |
Subject | Re: [Csnd] csound plugins repository |
Thanks, this seems super useful!
Building on openSuse Linux results with:
[ 50%] Building C object src/poly/CMakeFiles/poly.dir/src/poly.c.o
Is the arrays.h a system header file or somehow not present in git?
greetings, tarmo
On Wednesday, March 13, 2019 3:13:18 PM EET you wrote: > Hi. I created a repository with a collection of new plugins for csound: > > https://github.com/gesellkammer/csound-plugins > > The most relevant contribution are two plugins "poly" and "polyseq" > which allow to control multiple instances of an opcode either in > parallel (to make complex banks of oscillators, to control complex > spatialization, etc) or in series (to generate filter banks, parametric > eqs, etc). > > https://github.com/gesellkammer/csound-plugins/wiki/poly > > These are very easy to install provided you have a compiler and cmake > installed. At this stage there are no prebuilt binaries, but the build > script should work for all platforms. > > I would very much welcome testing and contributions to this collection. > > best, > > Eduardo Moguillansky > > 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
|
Date | 2019-03-13 13:41 |
From | Eduardo Moguillansky |
Subject | Re: [Csnd] csound plugins repository |
arrays.h is part of include files csound installs in your system. arrays.h should be in /usr/local/include/csound (at least this is the case if you installed from source). On Mi, Mar 13, 2019 at 2:35 PM, Tarmo Johannes |
Date | 2019-03-13 13:50 |
From | Tarmo Johannes |
Subject | Re: [Csnd] csound plugins repository |
Hi, Stange, yes I build Csound myself, updated now from git/develop branch but no arrays.h I could find arrays.c in Csound source Opcodes directory but no arrays.h also in source code. Maybe bad search... Where is it? tarmo On Wednesday, March 13, 2019 3:41:42 PM EET you wrote: > /usr/local/include/csound 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 |
Date | 2019-03-13 14:03 |
From | Eduardo Moguillansky |
Subject | Re: [Csnd] csound plugins repository |
All files in the folder "include" should have been copied to /usr/local/include/csound when you installed. arrays.h is there since 6.11 if I remember correctly. This is the file I am referring to: https://github.com/csound/csound/blob/develop/include/arrays.h On Mi, Mar 13, 2019 at 2:50 PM, Tarmo Johannes |
Date | 2019-03-13 14:40 |
From | Tarmo Johannes |
Subject | Re: [Csnd] csound plugins repository |
Thanks,
something strange in my rspository, the file was missing. For did a clean clone of Csound code, reinstalled Csound. Now the array.h is there but next problem is:
[ 50%] Building C object src/klib/CMakeFiles/klib.dir/src/klib.c.o /home/em/dev/c/ukstring.h
Can you please update git with actual file?
thanks, tarmo
On Wednesday, March 13, 2019 4:03:05 PM EET you wrote: > All files in the folder "include" should have been copied to > /usr/local/include/csound when you installed. arrays.h is there since > 6.11 if I remember correctly. This is the file I am referring to: > https://github.com/csound/csound/blob/develop/include/arrays.h > > > > On Mi, Mar 13, 2019 at 2:50 PM, Tarmo Johannes <trmjhnns@GMAIL.COM> > > wrote: > > Hi, > > > > Stange, yes I build Csound myself, updated now from git/develop > > branch but no > > arrays.h I could find arrays.c in Csound source Opcodes directory but > > no > > arrays.h also in source code. Maybe bad search... Where is it? > > > > tarmo > > > > On Wednesday, March 13, 2019 3:41:42 PM EET you wrote: > >> /usr/local/include/csound > > > > 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
|
Date | 2019-03-13 15:54 |
From | Eduardo Moguillansky |
Subject | Re: [Csnd] csound plugins repository |
sorry, I thought git would follow links. On Mi, Mar 13, 2019 at 3:40 PM, Tarmo Johannes |
Date | 2019-03-14 08:54 |
From | Eduardo Moguillansky |
Subject | Re: [Csnd] csound plugins repository |
Tarmo, could you get it to compile in the end? On Mi, Mar 13, 2019 at 4:54 PM, Eduardo Moguillansky |
Date | 2019-03-14 09:24 |
From | Rory Walsh |
Subject | Re: [Csnd] csound plugins repository |
Thanks for posting these Eduardo. I see you have some scripts for generating documentation, does it output in a format/style that can slot straight into the Csound reference manual? On Thu, 14 Mar 2019 at 08:54, Eduardo Moguillansky <eduardo.moguillansky@gmail.com> wrote: Tarmo, could you get it to compile in the end? |
Date | 2019-03-14 17:44 |
From | Tarmo Johannes |
Subject | Re: [Csnd] csound plugins repository |
Hi, I got now chance to try it again. Worked like charm - no problems with building. I tested the poly opcode from examples and wrote a simple code of my own, works very well. I find it truly useful in many situations, thanks a lot! I find it should be part of next release. tarmo On Thursday, March 14, 2019 10:54:08 AM EET you wrote: > Tarmo, could you get it to compile in the end? > > On Mi, Mar 13, 2019 at 4:54 PM, Eduardo Moguillansky > > |
Date | 2019-03-14 21:53 |
From | "Dr. Richard Boulanger" |
Subject | Re: [Csnd] csound plugins repository |
YES. Let's make this a part of the next release - with manPage and example.csd. - Thanks so much for developing Eduardo!! -dB _____________________________________________ 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 Thu, Mar 14, 2019 at 1:44 PM Tarmo Johannes <trmjhnns@gmail.com> wrote: Hi, |
Date | 2019-03-14 22:56 |
From | Eduardo Moguillansky |
Subject | Re: [Csnd] csound plugins repository |
I would rather see a parallel distribution of plugins outside the packaged releases (supercollider has a similar split between the main distribution and the sc3-plugins project). For a software so attached to backwards compatibility, it is highly desirable to only allow new code which is thoroughly tested and has shown to be used and useful. I think that the opposite direction is desirable: to strip csound down to a minimum of opcodes, deprecating unused and unsupported ones and moving problematic opcodes (like the python opcodes, the lua opcodes, etc.) outside of the main distrubution. This repository could in fact be used for that. On Do, Mar 14, 2019 at 10:53 PM, "Dr. Richard Boulanger" |
Date | 2019-03-15 11:37 |
From | "Dr. Richard Boulanger" |
Subject | Re: [Csnd] csound plugins repository |
In Csound 7, will it be as easy to add "plug-ins" as it is to add a VST or AU plugin on a commercial app/daw. - in the commercial case, you drop the plugin, in a particular format, in a locally defined "plug-ins" folder and it just runs as part of the app. - it shows up in a DSP menu, or a PLUGINS menu. That would be ideal. Having to recompile Csound in order to add a specific set of plugins is not "typical" or "convenient" or the current industry "standard". It makes sense for plug-ins to be outside the main or core Csound releaae, but, they should be super easy to add/include. if they are not easy to add, then I would suggest/recommend/hope that (if they work) they would be part of the current release. -dB _____________________________________________ 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 Thu, Mar 14, 2019 at 6:56 PM Eduardo Moguillansky <eduardo.moguillansky@gmail.com> wrote: I would rather see a parallel distribution of plugins outside the |
Date | 2019-03-15 12:31 |
From | Eduardo Moguillansky |
Subject | Re: [Csnd] csound plugins repository |
On 14.03.19 10:24, Rory Walsh wrote:
It is possible to generate nice looking html with syntax
highlighting for the examples, similar to what is rendered in the
github wiki. Some adaptation could be done to use the manual's
css. It is even possible to generate docbook from the markdown man
pages here, so with some manual modifications it would be possible
to integrate it to the reference manual. I would rather invest
time in the opposite, converting the manual to a friendlier format
(the current manual is, for example, not searchable from the html
view itself, you need to grep the sources directly if you need to
search something more than the short description of an opcode).
|
Date | 2019-03-15 14:16 |
From | Rory Walsh |
Subject | Re: [Csnd] csound plugins repository |
I agree about the current format of the manual. Perhaps something else to add to the list for Csound7. On Fri, 15 Mar 2019 at 12:31, Eduardo Moguillansky <eduardo.moguillansky@gmail.com> wrote:
|
Date | 2019-03-15 17:08 |
From | john |
Subject | Re: [Csnd] csound plugins repository |
The manual has no one in charge, so asking for improvements or any modification is unlikely to happen unless 9a) trivial and (b) I or SCS have spare time. On Fri, 15 Mar 2019, Rory Walsh wrote: > I agree about the current format of the manual. Perhaps something else to add > to the list for Csound7. > > On Fri, 15 Mar 2019 at 12:31, Eduardo Moguillansky > |
Date | 2019-03-15 17:34 |
From | joachim heintz |
Subject | Re: [Csnd] csound plugins repository |
i totally agree. in the same way as the 1500+ opcodes are a strength of csound, they are a jungle for anyone who wants to learn csound. some can be done by tutorials and recommendations, but it needs some re-ordering in the way you mention. joachim On 14/03/19 23:56, Eduardo Moguillansky wrote: > I would rather see a parallel distribution of plugins outside the > packaged releases (supercollider has a similar split between the main > distribution and the sc3-plugins project). For a software so attached to > backwards compatibility, it is highly desirable to only allow new code > which is thoroughly tested and has shown to be used and useful. I think > that the opposite direction is desirable: to strip csound down to a > minimum of opcodes, deprecating unused and unsupported ones and moving > problematic opcodes (like the python opcodes, the lua opcodes, etc.) > outside of the main distrubution. This repository could in fact be used > for that. > > > > On Do, Mar 14, 2019 at 10:53 PM, "Dr. Richard Boulanger" > |
Date | 2019-03-15 17:55 |
From | Steven Yi |
Subject | Re: [Csnd] csound plugins repository |
After ICSC 2017, we discussed having: 1. Core Csound (libcsound, commandline executables, internal opcodes) 2. External Plugin repos 3. Distribution(s) (the installer, which would be built using core, external, and other things like CsoundQt) 4. Package Manager: can grab and install plugins from external repos (see deken for pd, quarks for SC3) So far, only some opcodes were moved out from core to external plugins, and the installer is still built within core's repo, and there was some investigatory work with QT's package manager system via Guillermo. Ed had looked at a cspm package manager built using node.js that could package opcode libs as well as executables. I had done an older cspm exploration years ago written in python that didn't get uptake. Rory also did explorations into an external repo that could auto-build the opcode plugin via CI (Travis, Appveyor) and generate artifacts for users. (Rory: Perhaps an opportunity to explore Azure Pipelines for this?) Not much progress elsewhere. I'd love to see all of the above happen. IMO, the current system has made entry into csound development/maintenance too high for all but the most stoic of user/developers. It should be *easy* to casually add a native extension to Csound for desktop systems. Here I'd prefer option for centralized external repo (as Eduardo mentioned) as well as option to add repos. This would allow for complete independence for 3rd parties to extend the system by saying "I have a new opcode lib at this repo, add this source repo to cspm, then call 'cspm install mynewopcodelib." For Mobile and Web, similar organization should be looked into. This requires working out a good dynamic loading system workflow for both of those systems. Those are the primary open ecosystem issues I see. Much of this can be worked on in parallel to CS7, though some parts may best be done in coordination as CS7 development. Question now: any volunteers? The simplest might be the one Eduardo mentioned, the externals repo. We can add a repo to the csound organization for this. Ideally it would develop off of Rory's work and have CI driven builds for platforms. (This would not be a replacement for Rory's work, as that would still be necessary and useful for those wanting to create standalone external opcodes.) I'd be happy to contribute work towards getting a CMake system worked out as well as look at CI builds, but I don't have bandwidth to lead maintenance of it. Other projects need volunteers for leads and contributors. On Fri, Mar 15, 2019 at 7:37 AM Dr. Richard Boulanger <rboulanger@berklee.edu> wrote:
|
Date | 2019-03-15 18:43 |
From | Francois PINOT |
Subject | Re: [Csnd] csound plugins repository |
Within each release of Csound, there's a single html file version of the manual (https://github.com/csound/csound/releases/download/6.12.2/Csound6.12.2_manual_html_single.zip). François Le ven. 15 mars 2019 à 13:31, Eduardo Moguillansky <eduardo.moguillansky@gmail.com> a écrit :
|
Date | 2019-03-16 00:35 |
From | Guillermo Senna |
Subject | Re: [Csnd] csound plugins repository |
Regarding the Qt Installer Framework, I had it working for Win and MacOs (awful time spent on that since I use and prefer Linux) using Travis and AppVeyor to upload the binaries to bintray.com. I'll see if I can fork the Csound repo, put everything together and then make a pull request before I have to start my PhD in September. Cheers. On 15/3/19 14:55, Steven Yi wrote: > After ICSC 2017, we discussed having: > > 1. Core Csound (libcsound, commandline executables, internal opcodes) > 2. External Plugin repos > 3. Distribution(s) (the installer, which would be built using core, > external, and other things like CsoundQt) > 4. Package Manager: can grab and install plugins from external repos (see > deken for pd, quarks for SC3) > > So far, only some opcodes were moved out from core to external plugins, and > the installer is still built within core's repo, and there was some > investigatory work with QT's package manager system via Guillermo. Ed had > looked at a cspm package manager built using node.js that could package > opcode libs as well as executables. I had done an older cspm exploration > years ago written in python that didn't get uptake. Rory also did > explorations into an external repo that could auto-build the opcode plugin > via CI (Travis, Appveyor) and generate artifacts for users. (Rory: Perhaps > an opportunity to explore Azure Pipelines for this?) Not much progress > elsewhere. > > I'd love to see all of the above happen. IMO, the current system has made > entry into csound development/maintenance too high for all but the most > stoic of user/developers. It should be *easy* to casually add a native > extension to Csound for desktop systems. Here I'd prefer option for > centralized external repo (as Eduardo mentioned) as well as option to add > repos. This would allow for complete independence for 3rd parties to > extend the system by saying "I have a new opcode lib at this repo, add this > source repo to cspm, then call 'cspm install mynewopcodelib." > > For Mobile and Web, similar organization should be looked into. This > requires working out a good dynamic loading system workflow for both of > those systems. > > Those are the primary open ecosystem issues I see. Much of this can be > worked on in parallel to CS7, though some parts may best be done in > coordination as CS7 development. > > Question now: any volunteers? The simplest might be the one Eduardo > mentioned, the externals repo. We can add a repo to the csound > organization for this. Ideally it would develop off of Rory's work and have > CI driven builds for platforms. (This would not be a replacement for > Rory's work, as that would still be necessary and useful for those wanting > to create standalone external opcodes.) I'd be happy to contribute work > towards getting a CMake system worked out as well as look at CI builds, but > I don't have bandwidth to lead maintenance of it. Other projects need > volunteers for leads and contributors. > > On Fri, Mar 15, 2019 at 7:37 AM Dr. Richard Boulanger < > rboulanger@berklee.edu> wrote: > >> In Csound 7, will it be as easy to add "plug-ins" as it is to add a VST or >> AU plugin on a commercial app/daw. >> - in the commercial case, you drop the plugin, in a particular format, in >> a locally defined "plug-ins" folder and it just runs as part of the app. >> - it shows up in a DSP menu, or a PLUGINS menu. That would be ideal. >> Having to recompile Csound in order to add a specific set of plugins is not >> "typical" or "convenient" or the current industry "standard". >> >> It makes sense for plug-ins to be outside the main or core Csound releaae, >> but, they should be super easy to add/include. >> >> if they are not easy to add, then I would suggest/recommend/hope that (if >> they work) they would be part of the current release. >> >> -dB >> _____________________________________________ >> *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 Thu, Mar 14, 2019 at 6:56 PM Eduardo Moguillansky < >> eduardo.moguillansky@gmail.com> wrote: >> >>> I would rather see a parallel distribution of plugins outside the >>> packaged releases (supercollider has a similar split between the main >>> distribution and the sc3-plugins project). For a software so attached >>> to backwards compatibility, it is highly desirable to only allow new >>> code which is thoroughly tested and has shown to be used and useful. I >>> think that the opposite direction is desirable: to strip csound down to >>> a minimum of opcodes, deprecating unused and unsupported ones and >>> moving problematic opcodes (like the python opcodes, the lua opcodes, >>> etc.) outside of the main distrubution. This repository could in fact >>> be used for that. >>> >>> >>> >>> On Do, Mar 14, 2019 at 10:53 PM, "Dr. Richard Boulanger" >>> |
Date | 2019-03-16 10:00 |
From | joachim heintz |
Subject | Re: [Csnd] csound plugins repository |
awesome! j On 16/03/19 01:35, Guillermo Senna wrote: > Regarding the Qt Installer Framework, I had it working for Win and MacOs > (awful time spent on that since I use and prefer Linux) using Travis and > AppVeyor to upload the binaries to bintray.com. > > I'll see if I can fork the Csound repo, put everything together and then > make a pull request before I have to start my PhD in September. > > Cheers. > > > On 15/3/19 14:55, Steven Yi wrote: >> After ICSC 2017, we discussed having: >> >> 1. Core Csound (libcsound, commandline executables, internal opcodes) >> 2. External Plugin repos >> 3. Distribution(s) (the installer, which would be built using core, >> external, and other things like CsoundQt) >> 4. Package Manager: can grab and install plugins from external repos (see >> deken for pd, quarks for SC3) >> >> So far, only some opcodes were moved out from core to external plugins, and >> the installer is still built within core's repo, and there was some >> investigatory work with QT's package manager system via Guillermo. Ed had >> looked at a cspm package manager built using node.js that could package >> opcode libs as well as executables. I had done an older cspm exploration >> years ago written in python that didn't get uptake. Rory also did >> explorations into an external repo that could auto-build the opcode plugin >> via CI (Travis, Appveyor) and generate artifacts for users. (Rory: Perhaps >> an opportunity to explore Azure Pipelines for this?) Not much progress >> elsewhere. >> >> I'd love to see all of the above happen. IMO, the current system has made >> entry into csound development/maintenance too high for all but the most >> stoic of user/developers. It should be *easy* to casually add a native >> extension to Csound for desktop systems. Here I'd prefer option for >> centralized external repo (as Eduardo mentioned) as well as option to add >> repos. This would allow for complete independence for 3rd parties to >> extend the system by saying "I have a new opcode lib at this repo, add this >> source repo to cspm, then call 'cspm install mynewopcodelib." >> >> For Mobile and Web, similar organization should be looked into. This >> requires working out a good dynamic loading system workflow for both of >> those systems. >> >> Those are the primary open ecosystem issues I see. Much of this can be >> worked on in parallel to CS7, though some parts may best be done in >> coordination as CS7 development. >> >> Question now: any volunteers? The simplest might be the one Eduardo >> mentioned, the externals repo. We can add a repo to the csound >> organization for this. Ideally it would develop off of Rory's work and have >> CI driven builds for platforms. (This would not be a replacement for >> Rory's work, as that would still be necessary and useful for those wanting >> to create standalone external opcodes.) I'd be happy to contribute work >> towards getting a CMake system worked out as well as look at CI builds, but >> I don't have bandwidth to lead maintenance of it. Other projects need >> volunteers for leads and contributors. >> >> On Fri, Mar 15, 2019 at 7:37 AM Dr. Richard Boulanger < >> rboulanger@berklee.edu> wrote: >> >>> In Csound 7, will it be as easy to add "plug-ins" as it is to add a VST or >>> AU plugin on a commercial app/daw. >>> - in the commercial case, you drop the plugin, in a particular format, in >>> a locally defined "plug-ins" folder and it just runs as part of the app. >>> - it shows up in a DSP menu, or a PLUGINS menu. That would be ideal. >>> Having to recompile Csound in order to add a specific set of plugins is not >>> "typical" or "convenient" or the current industry "standard". >>> >>> It makes sense for plug-ins to be outside the main or core Csound releaae, >>> but, they should be super easy to add/include. >>> >>> if they are not easy to add, then I would suggest/recommend/hope that (if >>> they work) they would be part of the current release. >>> >>> -dB >>> _____________________________________________ >>> *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 Thu, Mar 14, 2019 at 6:56 PM Eduardo Moguillansky < >>> eduardo.moguillansky@gmail.com> wrote: >>> >>>> I would rather see a parallel distribution of plugins outside the >>>> packaged releases (supercollider has a similar split between the main >>>> distribution and the sc3-plugins project). For a software so attached >>>> to backwards compatibility, it is highly desirable to only allow new >>>> code which is thoroughly tested and has shown to be used and useful. I >>>> think that the opposite direction is desirable: to strip csound down to >>>> a minimum of opcodes, deprecating unused and unsupported ones and >>>> moving problematic opcodes (like the python opcodes, the lua opcodes, >>>> etc.) outside of the main distrubution. This repository could in fact >>>> be used for that. >>>> >>>> >>>> >>>> On Do, Mar 14, 2019 at 10:53 PM, "Dr. Richard Boulanger" >>>> |
Date | 2019-03-17 16:26 |
From | Oscar Pablo Di Liscia |
Subject | Re: [Csnd] csound plugins repository |
I'm triying to build the binary for Windows10 and I could not find also the arrays.h file. I performed a complete search in the complete sources and in the folder where Csound is installed without any result. Maybe the file changed to aops.h? Any help on this? Best Pablo El mié., 13 mar. 2019 a las 10:13, Eduardo Moguillansky ( |
Date | 2019-03-17 16:41 |
From | Eduardo Moguillansky |
Subject | Re: [Csnd] csound plugins repository |
In csound >= 6.11 (or maybe earlier?) arrays.h is copied together with all other include files present in the "include" folder in the csound source tree. https://github.com/csound/csound/blob/develop/include/arrays.h Tarmo reported a similar problem, which was solved by doing a clean clone of the github repo. Maybe you can try that? On So, Mar 17, 2019 at 5:26 PM, Oscar Pablo Di Liscia |
Date | 2019-03-17 16:47 |
From | Oscar Pablo Di Liscia |
Subject | Re: [Csnd] csound plugins repository |
Yes, I will try clonning again, many thanks. El dom., 17 mar. 2019 a las 13:41, Eduardo Moguillansky ( |
Date | 2019-03-18 00:08 |
From | Oscar Pablo Di Liscia |
Subject | Re: [Csnd] csound plugins repository |
Hello Eduardo. I did a fresh clone and updated my Csound version. That fixed the dependencies problem I had. Then, I adapted the build command from your build-linux.sh making the changes needed for folders and compiler instructions as follows: gcc -O2 -shared -o "c:/Program Files/Csound6_x64/plugins64/poly.dll" poly.c -DUSE_DOUBLE -I"c:/Program Files/Csound6_x64/include/csound" However, I tried to build poly with the following results: \csound-plugins\src\poly\src>gcc -O2 -shared -o "c:/Program Files/Csound6_x64/plugins64/poly.dll" poly.c -DUSE_DOUBLE -I"c:/Program Files/Csound6_x64/include/csound" poly.c: In function 'poly1_init': poly.c:560:17: error: 'CSOUND {aka struct CSOUND_}' has no member named 'find_opcode_new' opc = csound->find_opcode_new(csound, p->opcode_name->data, opc_outsig, opc_insig); ^~ poly.c: In function 'polyseq_init': poly.c:794:25: error: 'CSOUND {aka struct CSOUND_}' has no member named 'find_opcode_new' OENTRY *opc = csound->find_opcode_new(csound, p->opcode_name->data, Any help on this? I'm using this version of gcc under Windows 10. Using built-in specs. COLLECT_GCC=gcc COLLECT_LTO_WRAPPER=C:/Program\ Files/mingw-w64/x86_64-7.1.0-posix-seh-rt_v5-rev2/mingw64/bin/../libexec/gcc/x86_64-w64-mingw32/7.1.0/lto-wrapper.exe Target: x86_64-w64-mingw32 Configured with: ../../../src/gcc-7.1.0/configure --host=x86_64-w64-mingw32 --build=x86_64-w64-mingw32 --target=x86_64-w64-mingw32 --prefix=/mingw64 --with-sysroot=/c/mingw710/x86_64-710-posix-seh-rt_v5-rev2/mingw64 --enable-shared --enable-static --disable-multilib --enable-languages=c,c++,fortran,lto --enable-libstdcxx-time=yes --enable-threads=posix --enable-libgomp --enable-libatomic --enable-lto --enable-graphite --enable-checking=release --enable-fully-dynamic-string --enable-version-specific-runtime-libs --enable-libstdcxx-filesystem-ts=yes --disable-libstdcxx-pch --disable-libstdcxx-debug --enable-bootstrap --disable-rpath --disable-win32-registry --disable-nls --disable-werror --disable-symvers --with-gnu-as --with-gnu-ld --with-arch=nocona --with-tune=core2 --with-libiconv --with-system-zlib --with-gmp=/c/mingw710/prerequisites/x86_64-w64-mingw32-static --with-mpfr=/c/mingw710/prerequisites/x86_64-w64-mingw32-static --with-mpc=/c/mingw710/prerequisites/x86_64-w64-mingw32-static --with-isl=/c/mingw710/prerequisites/x86_64-w64-mingw32-static --with-pkgversion='x86_64-posix-seh-rev2, Built by MinGW-W64 project' --with-bugurl=https://sourceforge.net/projects/mingw-w64 CFLAGS='-O2 -pipe -fno-ident -I/c/mingw710/x86_64-710-posix-seh-rt_v5-rev2/mingw64/opt/include -I/c/mingw710/prerequisites/x86_64-zlib-static/include -I/c/mingw710/prerequisites/x86_64-w64-mingw32-static/include' CXXFLAGS='-O2 -pipe -fno-ident -I/c/mingw710/x86_64-710-posix-seh-rt_v5-rev2/mingw64/opt/include -I/c/mingw710/prerequisites/x86_64-zlib-static/include -I/c/mingw710/prerequisites/x86_64-w64-mingw32-static/include' CPPFLAGS=' -I/c/mingw710/x86_64-710-posix-seh-rt_v5-rev2/mingw64/opt/include -I/c/mingw710/prerequisites/x86_64-zlib-static/include -I/c/mingw710/prerequisites/x86_64-w64-mingw32-static/include' LDFLAGS='-pipe -fno-ident -L/c/mingw710/x86_64-710-posix-seh-rt_v5-rev2/mingw64/opt/lib -L/c/mingw710/prerequisites/x86_64-zlib-static/lib -L/c/mingw710/prerequisites/x86_64-w64-mingw32-static/lib ' Thread model: posix gcc version 7.1.0 (x86_64-posix-seh-rev2, Built by MinGW-W64 project) El dom., 17 mar. 2019 a las 13:47, Oscar Pablo Di Liscia ( |
Date | 2019-03-18 07:15 |
From | Eduardo Moguillansky |
Subject | Re: [Csnd] csound plugins repository |
Regarding the build system, the whole repository can be built with cmake, which should do a decent job at finding dependencies, include files, etc. (the build_linux.sh file is there just for testing). The build instructions are the same as with csound (in fact, the cmake file is a strippped down version of csound's own cmake script, plus some added functionality). See https://github.com/gesellkammer/csound-plugins#installation But the error you are getting is because poly needs the latest version of csound from the "develop" branch in github (the function "find_opcode_new" was exposed recently, see https://github.com/csound/csound/commit/7e95870915f079fb4b7fd68cbc2e894a258d69bb) On Mo, Mar 18, 2019 at 1:08 AM, Oscar Pablo Di Liscia |
Date | 2019-03-18 07:24 |
From | Tarmo Johannes |
Subject | Re: [Csnd] csound plugins repository |
Another thing (I don't know so much about builing on Windows) - you probably cannot mix different compilers. Csound is built with Visual Studio msvc compiler and in the end using gcc for building plugin would result most likely also linking errors. tarmo Kontakt Eduardo Moguillansky (<eduardo.moguillansky@gmail.com>) kirjutas kuupäeval E, 18. märts 2019 kell 09:15: Regarding the build system, the whole repository can be built with |
Date | 2019-03-18 08:58 |
From | Michael Gogins |
Subject | Re: [Csnd] csound plugins repository |
The MSVC and gcc compilers can be mixed for C language bindings such as in csound.h, and they can be mixed in header-file-only C++ language bindings such as csound.hpp. The compilers cannot be mixed if precompiled C++ code from one compiler needs to be linked with C++ code from another compiler. I haven't used plugin.h myself, but looking at it, it looks like a header-file-only system that might well work for you. Victor, is that the case? Regards, Mike ----------------------------------------------------- Michael Gogins Irreducible Productions http://michaelgogins.tumblr.com Michael dot Gogins at gmail dot com On Mon, Mar 18, 2019 at 6:25 PM Tarmo Johannes |
Date | 2019-03-20 21:39 |
From | Oscar Pablo Di Liscia |
Subject | Re: [Csnd] csound plugins repository |
Many thanks Eduardo. I cloned the sources folder you pointed to me https://github.com/csound/csound/commit/7e95870915f079fb4b7fd68cbc2e894a258d69bb) And after that I could build poly.dll without problems. I've tried the simplest example you gave in poly.csd: (I only changed the sumarray opcode, because it seems not to be available in the version of Csound I have, and changed the frequency values) opcode test, a, k kfreq xin aout oscili 0.1, kfreq xout aout endop instr 3 ; test udo kfreqs[] fillarray 440, 880 aA[] poly 2, "test", kfreqs a0 = aA[0]+ aA[1] out a0 endin But got a Segmentation violation. Now, I'm using the latest pre-built (to my knowledge) Csound Windows version, which is: --Csound version 6.12 beta (double samples) Oct 24 2018 [commit: 037becccce26dc9ebc37198a75877e817431d978] libsndfile-1.0.29pre1 It is possible that the Segmentation violation is due to the fact that I have to build Csound from the lattest version you pointed to me, and from which I used the dependencies to build your plugin? Sorry for so many questions, I could try to build and use your code under Linux, which seems to be less painful, but I think is important to be able to build and use it under Windows as well. Best Pablo El lun., 18 mar. 2019 a las 4:15, Eduardo Moguillansky ( |
Date | 2019-03-20 21:58 |
From | Eduardo Moguillansky |
Subject | Re: [Csnd] csound plugins repository |
The code works fine, you are running poly with an UDO, which does not work, so it is supposed to fail. Try the example in the manual but comment out instr 3 in the score. On Mi, Mar 20, 2019 at 10:39 PM, Oscar Pablo Di Liscia |
Date | 2019-03-20 23:22 |
From | John ff |
Subject | Re: [Csnd] csound plugins repository |
What other opcodes can not be in a Udo?
Sent from TypeApp
On 20 Mar 2019, at 21:59, Eduardo Moguillansky <eduardo.moguillansky@gmail.com> wrote: The code works fine, you are running poly with an UDO, which does not |
Date | 2019-03-20 23:31 |
From | Eduardo Moguillansky |
Subject | Re: [Csnd] csound plugins repository |
With that I meant that poly, at the moment, works only with built in opcodes and not user defined ones, so the fact that using an udo fails is correct behaviour. https://csound-plugins.github.io/csound-plugins/opcodes/poly/ On Do, Mar 21, 2019 at 12:22 AM, John ff |
Date | 2019-03-22 17:39 |
From | Oscar Pablo Di Liscia |
Subject | Re: [Csnd] csound plugins repository |
Hi Eduardo. I've tried this example you gave in the manual. |
Date | 2019-03-22 17:41 |
From | Eduardo Moguillansky |
Subject | Re: [Csnd] csound plugins repository |
What version of csound are you using? On Fr, Mar 22, 2019 at 6:39 PM, Oscar Pablo Di Liscia |
Date | 2019-03-22 17:52 |
From | Oscar Pablo Di Liscia |
Subject | Re: [Csnd] csound plugins repository |
Eduardo: I'm using this one that is (to my knowledge) the latest pre compiled for Windows 64 bits that is available. --Csound version 6.12 beta (double samples) Oct 24 2018 [commit: 037becccce26dc9ebc37198a75877e817431d978] libsndfile-1.0.29pre1 El vie., 22 mar. 2019 a las 14:41, Eduardo Moguillansky ( |
Date | 2019-03-22 18:12 |
From | Eduardo Moguillansky |
Subject | Re: [Csnd] csound plugins repository |
The plugins need latest csound from the develop branch, since poly relies on functionality which was not exposed for plugins until some weeks ago. Maybe someone can help you build it for windows? It would be great to confirm that these work for windows also. On Fr, Mar 22, 2019 at 6:52 PM, Oscar Pablo Di Liscia |
Date | 2019-03-22 18:38 |
From | Oscar Pablo Di Liscia |
Subject | Re: [Csnd] csound plugins repository |
Yes, that was what I guess. I'll try to build by myself, but if somebody is reading this thread, any help shall be very welcome. Many thanks again. Pablo El viernes, 22 de marzo de 2019, Eduardo Moguillansky <eduardo.moguillansky@gmail.com> escribió: The plugins need latest csound from the develop branch, since poly relies on functionality which was not exposed for plugins until some weeks ago. Maybe someone can help you build it for windows? It would be great to confirm that these work for windows also. -- Dr. Oscar Pablo Di Liscia Profesor Titular Director Programa de Investigación "Sistemas Temporales y Síntesis Espacial en el Arte Sonoro" http://stseas.web.unq.edu.ar/ Director Colección Editorial "Música y Ciencia" Escuela Universitaria de Artes Universidad Nacional de Quilmes Argentina 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 |
Date | 2019-03-22 19:39 |
From | Guillermo Senna |
Subject | Re: [Csnd] csound plugins repository |
Hi Pablo, I don't use Windows, but wouldn't an AppVeyor artifact come in handy in your case? https://ci.appveyor.com/project/csound/csound/build/artifacts Cheers. On 22/3/19 15:38, Oscar Pablo Di Liscia wrote: > Yes, that was what I guess. > I'll try to build by myself, but if somebody is reading this thread, any > help shall be very welcome. > Many thanks again. > Pablo > > El viernes, 22 de marzo de 2019, Eduardo Moguillansky < > eduardo.moguillansky@gmail.com> escribió: > >> The plugins need latest csound from the develop branch, since poly relies >> on functionality which was not exposed for plugins until some weeks ago. >> Maybe someone can help you build it for windows? It would be great to >> confirm that these work for windows also. >> >> On Fr, Mar 22, 2019 at 6:52 PM, Oscar Pablo Di Liscia < >> oscarpablodiliscia@GMAIL.COM> wrote: >> >>> Eduardo: I'm using this one that is (to my knowledge) the latest pre >>> compiled for Windows 64 bits that is available. >>> --Csound version 6.12 beta (double samples) Oct 24 2018 >>> [commit: 037becccce26dc9ebc37198a75877e817431d978] >>> libsndfile-1.0.29pre1 >>> >>> El vie., 22 mar. 2019 a las 14:41, Eduardo Moguillansky >>> ( |
Date | 2019-03-22 21:12 |
From | Oscar Pablo Di Liscia |
Subject | Re: [Csnd] csound plugins repository |
Many thanks Guillermo, ill try this. El vie., 22 mar. 2019 a las 16:39, Guillermo Senna ( |
Date | 2019-03-22 21:26 |
From | Oscar Pablo Di Liscia |
Subject | Re: [Csnd] csound plugins repository |
OK, I've used the --Csound version 6.13 beta (double samples) Mar 22 2019 [commit: d527a6178c3e8afa65b11bf15165a69fe952d891] libsndfile-1.0.29pre1 And poly as I compiled it on Windows, works fine, at least running the example in the manual. Many thanks for your help Eduardo and Guillermo. This is a great Opcode Eduardo, i will keep testing it. Best Pablo El vie., 22 mar. 2019 a las 18:12, Oscar Pablo Di Liscia ( |