Ge, I am just entering the world of programming and OSC, though I've been a musician for a long time, and am familiar with MIDI. I am assembling a guitar and would like very much to operate a computer using OSC and skipping MIDI altogether (in fact I would consider my project a failure if I must resort to MIDI). Several programs in the subworld of music electric ring out... Csound, yours, supercollider, etc. Why is yours better than the rest? How is it different? Sorry for asking to be sold to, but I am a musician and not a programmer... I want to learn and need a place to start. How should I interface my guitar (from RMC piezo system) with my computer ( A brand new ripping machine) and with you software? Any data you can offer, as a teacher to a young student, would be greatly appreciated. This project, if successful, would mean the realization of a beautiful vision. THanks, Joshua Patriquin
hi
On 7/9/07, Joshua Patriquin
Why is yours better than the rest?
i am not on the chuck dev team, so i speak only for myself. in the open source audio world there's less an emphasis on 'better' in the way that microsoft may promote vista as 'better' [for microsoft shareholders mostly]. these projects are run by volunteers and usually advocacy [or 'advertising'] is the lowest priority [not always].
How is it different?
search the mailing list. you'll have to do this work yourself. but i think you should spend some time thinking about what you want and how you like to work first.
I want to learn and need a place to start.
1. download chuck 2. rtfm 3. produce audio 4. try to make it better [keep repeating steps 2-4] also, you can replace chuck with csound or pd for two differeing views into digital audio. and even though you say you are not a programmer, if you're going to use a computer to make music, it is very helpful to learn how it works [which means understanding something about programming].
This project, if successful, would mean the realization of a beautiful vision.
good luck! -- \js [ http://or8.net/~johns/ ]
On 7/10/07, Joshua Patriquin
Ge,
Hi, Joshua, sorry to answer a question not directed at me but Ge has been bussy and off the list lately (last we heard he was in Beijing).... I am just entering the world of programming and OSC, though I've been a
musician for a long time, and am familiar with MIDI.
I am assembling a guitar and would like very much to operate a computer using OSC and skipping MIDI altogether (in fact I would consider my project a failure if I must resort to MIDI).
Sounds very interestinmg and daring. Whatever you choose I'd love to hear about your project to build a OSC guitar. Several programs in the subworld of music electric ring out... Csound,
yours, supercollider, etc.
Why is yours better than the rest?
That's a excelent question. Personally I would never say ChucK is "better" then Csound or Supercollider. Csound is very old and has facilities for many things (nearly everything, realy), SC is very highly optimised and a far more mature then ChucK is. It eould be far easier, objectively speaking, to make a case ChucK is worse, it is for example young and experimental, it's not at all unlikely that you would encounter a bug or two (but those are definately on the way out and updates are quite frequent). ChucK people tend to hold the odd belief that hunting bugs together build comunity and that "experimental" equals "exciting". How is it different?
Ah, here we get to the fun stuff. I tried to learn Csound and tried to learn SC over the past years. I can still read most Csound programs but didn't find it's syntax that apealing i also wasn't too content with the lack of emphasis in realtime playing. SC I liked a lot conceptually but to read or write it wasn't that intuitive to me. this wasn't helped by me running Windows exclusively at the time and SC not fully suporting Windows at that time. ChucK, however, nearly instantly "clicked" with me. Back then there were no real tutorials beyond the examples and no manual yet so I started with editing the examples and before I knew it I was having lots of fun. I can't make any claims about the way anybody else functions I for me chucK was very easy to pick up and I find it very easy and convenient to prototy new instrument ideas ion ChucK very quickly. these days I code in ChucK a lot so it's to be expected that I'm experienced with it but I keep being pleasantly surprised just how quickly you can go from a idea to a working prototype. Sorry for asking to be sold to, but I am a musician and not a programmer...
I want to learn and need a place to start.
Well, in that case it's easy; I find ChucK is a excelent place to learn and a place to start. It's quitre conceivable that after starting on ChucK you'd find you'd like to also try something else, for example you might want to try SC at that point because SC is typically lighter on the cpu and your instrument might grow to need a lot of CPU at some stage. At that point, however, you'd already have done most of your prototyping in a language that I think is very suitable for this on account of bveing compact, readable and accessible. One of the aims of ChucK is in fact being a good place to learn and start. People who are far more knowledgable then I am can write papers on that after testing it in classrooms to novice programers and musicians, I can just say that I found that for me personally it works like a charm in that capacity. I also moderate the ChucK-forum where I'm continually pleasantly surprised to see it works for others as well; people who come in with no experience and in a few days will be developing their own little utility to do something usefull in their stdio or for their live setup. So; i can't guarantee anything, there is no substitute for getting your hands dirty but if we'd be betting i'd bet on ChucK being a good one to learn and start with. How should I interface my guitar (from RMC piezo system) with my computer (
A brand new ripping machine) and with you software?
If you are sure you want to go with OSC for the connection I'd grab one of those DSP development boards, one with a ethernet plug and definately one with a good community around it where you could borow chunks of code. That part would definately be more time-consuming then developing the ChucK code to turn the resultant OSC into sound but if you do pull it off it'd be very exciting. I'd say that's definately a advanced project and I think I'd recomend starting out with something more modest but related. Don't hesitate to ask more if you have speciffic questions but embedding guitar => OSC boards isn't my own field of expertise. Good luck, whatever you decide! Yours, Kas.
I still like RTcmix (http://rtcmix.org) but I'm old and weird. brad http://music.columbia.edu/~brad
Hi Joshua! Welcome and thanks for the post. Just adding a more points to the insightful posts by Kassen, John, and Brad. As Kassen mentioned, ChucK, while relatively young and immature as a language, can be (and has been) quite useful and fun to learn about sound/music synthesis, controller mapping, and much of computer music in general. As one develops more proficiency with ChucK (we believe a strength of ChucK is that it's fairly straightforward to "grok"), we hope the various features of the language (precise control over time, parallelism via "shreds", on-the-fly programming) will naturally present themselves as building blocks for making cool, interesting audio programs. Having said that, we also believe that it's a really great idea to try different languages and programming paradigms (e.g., also csound, supercollider, rtcmix, pd/max, etc.), for each has its strengths and limitations. Knowng the few major programming models will aid you in choosing the right tool(s) for the task at hand. As for your set up, we are very excited to hear about how things go! Once you are able to get OSC messages to the computer, you might check out the OSC chuck examples to see how to receive/send OSC messages. In the meantime, as John and Kassen said, play/break/ improve the examples, read resources, experiment, and post questions here or at the forum (http://electro-music.com/forum/forum-140.html). Perhaps most importantly, have fun with it! Happy ChucKing. Ge! On Jul 10, 2007, at 9:48 AM, Kassen wrote:
On 7/10/07, Joshua Patriquin
wrote: Ge, Hi, Joshua, sorry to answer a question not directed at me but Ge has been bussy and off the list lately (last we heard he was in Beijing)....
I am just entering the world of programming and OSC, though I've been a musician for a long time, and am familiar with MIDI.
I am assembling a guitar and would like very much to operate a computer using OSC and skipping MIDI altogether (in fact I would consider my project a failure if I must resort to MIDI).
Sounds very interestinmg and daring. Whatever you choose I'd love to hear about your project to build a OSC guitar.
Several programs in the subworld of music electric ring out... Csound, yours, supercollider, etc.
Why is yours better than the rest?
That's a excelent question. Personally I would never say ChucK is "better" then Csound or Supercollider. Csound is very old and has facilities for many things (nearly everything, realy), SC is very highly optimised and a far more mature then ChucK is. It eould be far easier, objectively speaking, to make a case ChucK is worse, it is for example young and experimental, it's not at all unlikely that you would encounter a bug or two (but those are definately on the way out and updates are quite frequent).
ChucK people tend to hold the odd belief that hunting bugs together build comunity and that "experimental" equals "exciting".
How is it different?
Ah, here we get to the fun stuff. I tried to learn Csound and tried to learn SC over the past years. I can still read most Csound programs but didn't find it's syntax that apealing i also wasn't too content with the lack of emphasis in realtime playing. SC I liked a lot conceptually but to read or write it wasn't that intuitive to me. this wasn't helped by me running Windows exclusively at the time and SC not fully suporting Windows at that time.
ChucK, however, nearly instantly "clicked" with me. Back then there were no real tutorials beyond the examples and no manual yet so I started with editing the examples and before I knew it I was having lots of fun. I can't make any claims about the way anybody else functions I for me chucK was very easy to pick up and I find it very easy and convenient to prototy new instrument ideas ion ChucK very quickly. these days I code in ChucK a lot so it's to be expected that I'm experienced with it but I keep being pleasantly surprised just how quickly you can go from a idea to a working prototype.
Sorry for asking to be sold to, but I am a musician and not a programmer... I want to learn and need a place to start.
Well, in that case it's easy; I find ChucK is a excelent place to learn and a place to start. It's quitre conceivable that after starting on ChucK you'd find you'd like to also try something else, for example you might want to try SC at that point because SC is typically lighter on the cpu and your instrument might grow to need a lot of CPU at some stage. At that point, however, you'd already have done most of your prototyping in a language that I think is very suitable for this on account of bveing compact, readable and accessible.
One of the aims of ChucK is in fact being a good place to learn and start. People who are far more knowledgable then I am can write papers on that after testing it in classrooms to novice programers and musicians, I can just say that I found that for me personally it works like a charm in that capacity. I also moderate the ChucK- forum where I'm continually pleasantly surprised to see it works for others as well; people who come in with no experience and in a few days will be developing their own little utility to do something usefull in their stdio or for their live setup.
So; i can't guarantee anything, there is no substitute for getting your hands dirty but if we'd be betting i'd bet on ChucK being a good one to learn and start with.
How should I interface my guitar (from RMC piezo system) with my computer ( A brand new ripping machine) and with you software?
If you are sure you want to go with OSC for the connection I'd grab one of those DSP development boards, one with a ethernet plug and definately one with a good community around it where you could borow chunks of code. That part would definately be more time- consuming then developing the ChucK code to turn the resultant OSC into sound but if you do pull it off it'd be very exciting.
I'd say that's definately a advanced project and I think I'd recomend starting out with something more modest but related.
Don't hesitate to ask more if you have speciffic questions but embedding guitar => OSC boards isn't my own field of expertise.
Good luck, whatever you decide!
Yours, Kas. _______________________________________________ chuck-users mailing list chuck-users@lists.cs.princeton.edu https://lists.cs.princeton.edu/mailman/listinfo/chuck-users
participants (5)
-
garton@columbia.edu
-
Ge Wang
-
john saylor
-
Joshua Patriquin
-
Kassen