Hi I'm still quite new to chuck, but after going through the "Notes on Chuck for music" tutorial it struck me that a nice way to (over time) build a library of instruments that work in an interchangeable way would be to extend the StkInstrument. Instruments build this way should work like the StifKarp instrument used in the tutorial. I realize that this in some/most cases comes of fine grain control of the sound, but thinking about it that's the way I prefer thinking about instruments; encapsulated sound generating units. For instance I have over time build a library of over 100 midi-controlled realtime csound instruments that I use all the time. It this a recommended way of making instruments? Any documentation or examples on how to do this? How much slower would a userspace implementaion be compared to the buildin instruments? Would it be possible that such user defined instruments could make it into the language itself, and how much is involved in converting a userspace instrument into a build-in instrument? -- peace, love & harmony Atte http://www.atte.dk | quartet: http://www.anagrammer.dk http://www.atte.dk/gps | compositions: http://www.atte.dk/compositions
Atte André Jensen wrote:
and how much is involved in converting a userspace instrument into a build-in instrument?
Ok, I've discovered http://ccrma.stanford.edu/software/stk/, and feel a bit stupid. At least a part of my questions share the answer: "It's a lot hardet than you think, stupid...". Still, would it be possible (and what would it take) in chuck to inherit from StkInstrument and get the bennefits of streamlined instruments? -- peace, love & harmony Atte http://www.atte.dk | quartet: http://www.anagrammer.dk http://www.atte.dk/gps | compositions: http://www.atte.dk/compositions
Atte André Jensen wrote: Still, would it be possible (and what would it take) in chuck to inherit from StkInstrument and get the bennefits of streamlined instruments?
I thought there was going to be a somewhat documented more or less streamlined kit for including your own instruments in the ChucK source. Can't remember where I read that. That would probably mean DSP coding in C, I think. This was somewhere on the ToDo list but loads and loads of things are on that list (actually I think there are several lists). I think I read that poking around the Wiki. So; that would mean "probably" and "somewhere in the future", I think? I have a homebrew filter on the shelf that's realy inneficient in straight ChucK that I'd like to port myself but something tells me this isn't going so simple and cheerfull as ChucK itself... Hope that answers some of your question untill the chief mad scientist himself returns from France. Kas.
On 6/16/06, Perry R Cook
Yea, give Ge a break. He's on his honeymoon!!
Hey, Perry, you seem a bit older then the rest of us so hopefully wiser and more experienced too. Where does one find a partner willing to plan a honeymoon that fits with IRCAM events? I mean; I managed to find friends that can deal with being incomunicado for a few weeks because chucking binges but this seems to be the next level. Kas.
Dude, If IRCAM were in Detroit, I'm sure it would be hard to plan a romantic getaway. But Paris is Paris, so it's not too hard. Spain works well too (in my old experience). PRC On Fri, 16 Jun 2006, Kassen wrote:
On 6/16/06, Perry R Cook
wrote: Yea, give Ge a break. He's on his honeymoon!!
Hey, Perry, you seem a bit older then the rest of us so hopefully wiser and more experienced too. Where does one find a partner willing to plan a honeymoon that fits with IRCAM events?
I mean; I managed to find friends that can deal with being incomunicado for a few weeks because chucking binges but this seems to be the next level.
Kas. _______________________________________________ chuck-users mailing list chuck-users@lists.cs.princeton.edu https://lists.cs.princeton.edu/mailman/listinfo/chuck-users
uh, here is a synopsis in code... Girlfriend manman; manman $ wife + ge => Paris => Blois => Loire Valley => Rouen => Normandy => St. Michel => Bordeaux => Nimes => Arles => Avignon => Nice => Aix en Provence => Paris => New Jersey; 2::week => now;
On 6/16/06, Perry R Cook
wrote: Yea, give Ge a break. He's on his honeymoon!!
Hey, Perry, you seem a bit older then the rest of us so hopefully wiser and more experienced too. Where does one find a partner willing to plan a honeymoon that fits with IRCAM events?
I mean; I managed to find friends that can deal with being incomunicado for a few weeks because chucking binges but this seems to be the next level.
Kas. _______________________________________________ chuck-users mailing list chuck-users@lists.cs.princeton.edu https://lists.cs.princeton.edu/mailman/listinfo/chuck-users
_______________________________________________ chuck-users mailing list chuck-users@lists.cs.princeton.edu https://lists.cs.princeton.edu/mailman/listinfo/chuck-users
With regards to building your own unit generators, if you already have a C or C++ implementation of your instrument/filter/etc., its not too difficult to integrate that at compile-time into ChucK--there is a fairly straighforward mechanism for defining new ChucK classes and ugens, including fancy things like inheritance. Id say the only thing stopping users from implementing new compiled-in ugens right now is the lack of documentation. There is also a run-time plugin mechanism that exists in the source, but Im not positive that it is completely hooked-in and functional at the moment. Actually, getting that worked out is one of the things thats on the ChucK summer fun in the sun list. spencer On Jun 16, 2006, at 4:48 PM, Kassen wrote:
Atte André Jensen wrote: Still, would it be possible (and what would it take) in chuck to inherit from StkInstrument and get the bennefits of streamlined instruments?
I thought there was going to be a somewhat documented more or less streamlined kit for including your own instruments in the ChucK source. Can't remember where I read that. That would probably mean DSP coding in C, I think. This was somewhere on the ToDo list but loads and loads of things are on that list (actually I think there are several lists). I think I read that poking around the Wiki.
So; that would mean "probably" and "somewhere in the future", I think?
I have a homebrew filter on the shelf that's realy inneficient in straight ChucK that I'd like to port myself but something tells me this isn't going so simple and cheerfull as ChucK itself...
Hope that answers some of your question untill the chief mad scientist himself returns from France.
Kas. _______________________________________________ chuck-users mailing list chuck-users@lists.cs.princeton.edu https://lists.cs.princeton.edu/mailman/listinfo/chuck-users
On Fri, Jun 16, 2006 at 07:11:26PM -0400, Spencer Salazar wrote:
With regards to building your own unit generators, if you already have a C or C++ implementation of your instrument/filter/etc., its not too difficult to integrate that at compile-time into ChucK--there is a fairly straighforward mechanism for defining new ChucK classes and ugens, including fancy things like inheritance. Id say the only thing stopping users from implementing new compiled-in ugens right now is the lack of documentation.
Wow! I knew about the run-time plugin mechanism that's currently on hold, but I didn't know that there's a "not too difficult" way of compiling-in your own ugens. Anybody that knows how to do this and would be willing to write a short tutorial? Please... - ttg
participants (6)
-
Atte André Jensen
-
Ge Wang
-
Kassen
-
Perry R Cook
-
Spencer Salazar
-
Tyler Gillies