Re: [Cs-dev] materials needed for Cs5 tests
Date | 2005-02-25 18:17 |
From | "gogins@pipeline.com" |
Subject | Re: [Cs-dev] materials needed for Cs5 tests |
Thanks for your work, that's cool. You fixed the Koch example so I will contribute: (1) Loris analysis/resynthesis example. (2) CsoundVST as Python extension module example. (3) Python GUI controlling real-time performance (rudimentary example now in CVS). What is the status of Jack in Csound 5? Things on my "wish list" (may or may not personally get to them, not enough time if I continue to insist on composing which, thank God, I have been able to do lately)... these are just things that I'm pretty confident are technically feasible and would be cool, regardless of the fact that I don't have time to do more than one or two of them: OSC working. All current Perry Cook STK instruments as C++ plugin opcode(s). Improved performance and stability as VST plugin. Aeolus organ opcode -- this little thing is fantastic. Taosynth opcode with embedded scripts. Jack client opcodes (communicate with external synths from inside Csound performances). But perhaps can be done simply with PyJack. LISP binding directly into Common Music via Csound API (SWIG up S-expressions) Pampin's AST opcodes. ReWire interface (e.g. talk to Reason on Windows). Original Message: ----------------- From: Dave Phillips dlphilp@bright.net Date: Fri, 25 Feb 2005 12:20:42 -0500 To: csound-devel@lists.sourceforge.net Subject: Re: [Cs-dev] materials needed for Cs5 tests Richard Boulanger wrote: >This set of test instruments and topics will be a fantastic starting point >(and testing point) for all of us. Thanks so much for putting these >examples together. Can't wait to have the collection and begin testing with >them. (Of course, they will also serve as excellent tutorials too!) [snip] > >on 2/24/05 10:28 AM, gogins@pipeline.com at gogins@pipeline.com wrote: > > > >>Topics that should also be covered include: >> >>1. Loris analysis in Python / resynthesis using Loris opcodes. >> Looking forward to this. Btw, Istvan corrected cvanal's behavior, the convolve opcode kicks butt. Hetro/adsyn works, but pvanal/pvoc and lpanal/lpread do not. Perhaps libsndfile related stuff ? >>2. CsoundVST with Python algorithmic composition (I will contribute an example). >> As Michael knows, I combined his Koch generator with steven's fluidsynth opcodes and got a working example for this topic. Cool stuff, CsoundVST is impressive. >>3. Using CsoundVST as a Python extension module (I will contribute an example). >> Looking forward to this too. Michael, you got me interested in learning more about Python... just what I need... but there's that fat batch of Csound Python opcodes to check out... vita brevis, indeed... :) >>4. Does your SoundFont example use the Fluidsynth-based opcodes? If not, I can contribute an example. >> See above. >>5. VST plugin opcodes. >> I'm wondering if the libfst library could be worked into Csound5. Are you guys aware of it ? If not, it's a library for running VST/VSTi plugins in Linux. It requires software from the WINE project, but that's libfst's business, not Csound's. If the library can be built into Csound it would enable the use of VST/VSTi plugins for Linux users, provided the opcodes can be adapted, yes ? Best, dp ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ Csound-devel mailing list Csound-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/csound-devel -------------------------------------------------------------------- mail2web - Check your email from the web at http://mail2web.com/ . ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_ide95&alloc_id396&op=click _______________________________________________ Csound-devel mailing list Csound-devel@lists.sourceforge.net |
Date | 2005-02-25 19:04 |
From | Dave Phillips |
Subject | Re: [Cs-dev] materials needed for Cs5 tests |
gogins@pipeline.com wrote: >What is the status of Jack in Csound 5? > From my POV it's working nicely. No transport control, but maybe some of Gerard van Dongen's work can be incorporated for that ? Audio is fine, autoconnection works. I have a tutorial prepared for it already, not extensive though. Best, dp ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ Csound-devel mailing list Csound-devel@lists.sourceforge.net |
Date | 2005-02-26 02:01 |
From | "Richard Boulanger" |
Subject | Re: [Cs-dev] materials needed for Cs5 tests |
Totally into All of Michael's Extra List of thinkgs to get working - especially REWIRE and OSC. Dr. B. on 2/25/05 1:17 PM, gogins@pipeline.com at gogins@pipeline.com wrote: > Thanks for your work, that's cool. You fixed the Koch example so I will > contribute: > > (1) Loris analysis/resynthesis example. > > (2) CsoundVST as Python extension module example. > > (3) Python GUI controlling real-time performance (rudimentary example now > in CVS). > > What is the status of Jack in Csound 5? > > Things on my "wish list" (may or may not personally get to them, not enough > time if I continue to insist on composing which, thank God, I have been > able to do lately)... these are just things that I'm pretty confident are > technically feasible and would be cool, regardless of the fact that I don't > have time to do more than one or two of them: > > OSC working. > All current Perry Cook STK instruments as C++ plugin opcode(s). > Improved performance and stability as VST plugin. > Aeolus organ opcode -- this little thing is fantastic. > Taosynth opcode with embedded scripts. > Jack client opcodes (communicate with external synths from inside Csound > performances). But perhaps can be done simply with PyJack. > LISP binding directly into Common Music via Csound API (SWIG up > S-expressions) > Pampin's AST opcodes. > ReWire interface (e.g. talk to Reason on Windows). > > > > > Original Message: > ----------------- > From: Dave Phillips dlphilp@bright.net > Date: Fri, 25 Feb 2005 12:20:42 -0500 > To: csound-devel@lists.sourceforge.net > Subject: Re: [Cs-dev] materials needed for Cs5 tests > > > Richard Boulanger wrote: > >> This set of test instruments and topics will be a fantastic starting point >> (and testing point) for all of us. Thanks so much for putting these >> examples together. Can't wait to have the collection and begin testing > with >> them. (Of course, they will also serve as excellent tutorials too!) > [snip] >> >> on 2/24/05 10:28 AM, gogins@pipeline.com at gogins@pipeline.com wrote: >> >> >> >>> Topics that should also be covered include: >>> >>> 1. Loris analysis in Python / resynthesis using Loris opcodes. >>> > Looking forward to this. > > Btw, Istvan corrected cvanal's behavior, the convolve opcode kicks butt. > Hetro/adsyn works, but pvanal/pvoc and lpanal/lpread do not. Perhaps > libsndfile related stuff ? > >>> 2. CsoundVST with Python algorithmic composition (I will contribute an > example). >>> > As Michael knows, I combined his Koch generator with steven's fluidsynth > opcodes and got a working example for this topic. Cool stuff, CsoundVST > is impressive. > >>> 3. Using CsoundVST as a Python extension module (I will contribute an > example). >>> > Looking forward to this too. Michael, you got me interested in learning > more about Python... just what I need... but there's that fat batch of > Csound Python opcodes to check out... vita brevis, indeed... :) > >>> 4. Does your SoundFont example use the Fluidsynth-based opcodes? If not, > I can contribute an example. >>> > See above. > >>> 5. VST plugin opcodes. >>> > I'm wondering if the libfst library could be worked into Csound5. Are > you guys aware of it ? If not, it's a library for running VST/VSTi > plugins in Linux. It requires software from the WINE project, but that's > libfst's business, not Csound's. If the library can be built into Csound > it would enable the use of VST/VSTi plugins for Linux users, provided > the opcodes can be adapted, yes ? > > Best, > > dp > > > > > ------------------------------------------------------- > SF email is sponsored by - The IT Product Guide > Read honest & candid reviews on hundreds of IT Products from real users. > Discover which products truly live up to the hype. Start reading now. > http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click > _______________________________________________ > Csound-devel mailing list > Csound-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/csound-devel > > -------------------------------------------------------------------- > mail2web - Check your email from the web at > http://mail2web.com/ . > > > > > ------------------------------------------------------- > SF email is sponsored by - The IT Product Guide > Read honest & candid reviews on hundreds of IT Products from real users. > Discover which products truly live up to the hype. Start reading now. > http://ads.osdn.com/?ad_ide95&alloc_id396&op=click > _______________________________________________ > Csound-devel mailing list > Csound-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/csound-devel _______________________________________________________________________ + Dr. Richard Boulanger, Professor + Music Synthesis Department, Berklee College of Music + 1140 Boylston Street - Boston, MA 02215-3693 + Office Phone: (617) 747-2485 Office Fax: (617) 747-2564 + eMail: rboulanger@csounds.com or rboulanger@berklee.edu + WebPage: http://csounds.com/boulanger/ ________________________________________________________________________ + Almost Everything Csound @ http://csounds.com/ + The Csound Catalog with Audio @ http://csounds.com/catalog/ + The Csound Book @ http://csounds.com/book/ + The Csound Magazine @ http://csounds.com/ezine/ + CsoundForums @ http://csounds.com/phpBB2/ ________________________________________________________________________ ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ Csound-devel mailing list Csound-devel@lists.sourceforge.net |
Date | 2005-02-26 08:26 |
From | Anthony Kozar |
Subject | Re: [Cs-dev] materials needed for Cs5 tests |
This sounds pretty cool to me as I use Common Music with Csound (when I actually USE Csound instead of developing it ;) But, you might want to talk to Bill Schottstaedt and Rick Taube first. Bill's done a lot with various Lisps and their FFIs (foreign function interfaces). The details sound hairy and I believe that the various Lisps are inconsistent. And both Bill and Rick have really made a push towards porting CM/CLM/CMN to Guile/Scheme in the last couple of years. Scheme is cleaner and easier to learn. CM is really written in Scheme now, I think, with a compatibility layer implementing "Scheme in Lisp". Anthony On 2/25/05 1:17 PM, gogins@pipeline.com |