|
I've just received my first advance copy of Csound Power! Published by Course Technology and available through the usual retail outlets, this book will have little or nothing for power users, but my hope is that newcomers will find it useful.
Thanks again to Andres, Steven, and many other individuals for their technical help while I was writing this book. --Jim Aikin |
|
Hello Jim I have received mine about a week ago, and i live in Athens-Greece. :) :) Congratulations are in order! On small complaint though: where is the source code? Panos On Feb 20, 2012, at 10:19 PM, Jim Aikin wrote: > I've just received my first advance copy of Csound Power! Published by Course > Technology and available through the usual retail outlets, this book will > have little or nothing for power users, but my hope is that newcomers will > find it useful. > > Thanks again to Andres, Steven, and many other individuals for their > technical help while I was writing this book. > > --Jim Aikin > > -- > View this message in context: http://csound.1045644.n5.nabble.com/Csound-Power-Book-Is-Out-tp5500160p5500160.html > Sent from the Csound - General mailing list archive at Nabble.com. > > > Send bugs reports to the Sourceforge bug tracker > https://sourceforge.net/tracker/?group_id=81968&atid=564599 > Discussions of bugs and features can be posted here > To unsubscribe, send email [hidden email] with body "unsubscribe csound" > Send bugs reports to the Sourceforge bug tracker https://sourceforge.net/tracker/?group_id=81968&atid=564599 Discussions of bugs and features can be posted here To unsubscribe, send email [hidden email] with body "unsubscribe csound" |
|
> I have received mine about a week ago, and i live in Athens-Greece. :) :)
> Congratulations are in order! > One small complaint though: where is the source code? Please accept my apologies on that point! One of the reasons I kept the examples short was so I wouldn't have to prepare a bunch of source code files. Also, my feeling is that people learn more by typing the code themselves than by using copy-and-paste. The projects in Chapter 3 could be assembled into source code files, but as I was testing the code in the book I kept revising my CsoundQt files, so I'm not sure I even _have_ complete source code on those projects. That said, I would have prepared source code files for a website if Course Technology had a budget item for that. They didn't. For my previous book for them, "Picture Yourself Playing Cello," I had to acquire 95% of the photos (at no cost to Course Technology), prepare all of the music notation examples myself in Sibelius (no budget for that, either), and shoot the video for the DVD myself (no budget for a video shoot -- I did it all with my MacBook Pro). So when the Csound book rolled around ... not to whine or anything, but I just plain wasn't in the mood to do any extra work beyond the actual writing. I did end up redoing the index, because it was a mess -- and by golly, they paid me for doing it! But at this point, the book is what it is. There are lots and lots of examples of Csound code available online for free download, so I don't feel that I'm depriving anyone of musically useful code. I'm happy that Course Technology published the book at all! It was a little outside the mainstream for them, but they went for it. I hope it will help some people get started with Csound. |
|
Congratulations! I'm eager to get my hands on a copy.
All the best, Colman
On Mon, Feb 20, 2012 at 7:45 PM, Jim Aikin <[hidden email]> wrote:
Colman O'Reilly | [hidden email] | www.colmanoreilly.com
|
|
Looks great Jim. I had no idea it was already out!
On 20 February 2012 19:13, Colman O'Reilly <[hidden email]> wrote: > Congratulations! I'm eager to get my hands on a copy. > > All the best, > Colman > > > On Mon, Feb 20, 2012 at 7:45 PM, Jim Aikin <[hidden email]> wrote: >> >> > I have received mine about a week ago, and i live in Athens-Greece. :) >> > :) >> > Congratulations are in order! >> > One small complaint though: where is the source code? >> >> Please accept my apologies on that point! >> >> One of the reasons I kept the examples short was so I wouldn't have to >> prepare a bunch of source code files. Also, my feeling is that people >> learn >> more by typing the code themselves than by using copy-and-paste. The >> projects in Chapter 3 could be assembled into source code files, but as I >> was testing the code in the book I kept revising my CsoundQt files, so I'm >> not sure I even _have_ complete source code on those projects. >> >> That said, I would have prepared source code files for a website if Course >> Technology had a budget item for that. They didn't. For my previous book >> for >> them, "Picture Yourself Playing Cello," I had to acquire 95% of the photos >> (at no cost to Course Technology), prepare all of the music notation >> examples myself in Sibelius (no budget for that, either), and shoot the >> video for the DVD myself (no budget for a video shoot -- I did it all with >> my MacBook Pro). >> >> So when the Csound book rolled around ... not to whine or anything, but I >> just plain wasn't in the mood to do any extra work beyond the actual >> writing. I did end up redoing the index, because it was a mess -- and by >> golly, they paid me for doing it! >> >> But at this point, the book is what it is. There are lots and lots of >> examples of Csound code available online for free download, so I don't >> feel >> that I'm depriving anyone of musically useful code. >> >> I'm happy that Course Technology published the book at all! It was a >> little >> outside the mainstream for them, but they went for it. I hope it will help >> some people get started with Csound. >> >> -- >> View this message in context: >> http://csound.1045644.n5.nabble.com/Csound-Power-Book-Is-Out-tp5500160p5500731.html >> Sent from the Csound - General mailing list archive at Nabble.com. >> >> >> Send bugs reports to the Sourceforge bug tracker >> https://sourceforge.net/tracker/?group_id=81968&atid=564599 >> Discussions of bugs and features can be posted here >> To unsubscribe, send email [hidden email] with body "unsubscribe >> csound" >> > > > > -- > Colman O'Reilly | [hidden email] | www.colmanoreilly.com > > > Send bugs reports to the Sourceforge bug tracker https://sourceforge.net/tracker/?group_id=81968&atid=564599 Discussions of bugs and features can be posted here To unsubscribe, send email [hidden email] with body "unsubscribe csound" |
|
In reply to this post by Jim Aikin
A hearty congratulations Jim! I've long enjoyed and appreciated your
writing, whether it was in magazines, books, the Csound Journal, and other formats. I think this is great to have as a resource and hope new users turn to it when they come to Csound. Bravo! steven On Mon, Feb 20, 2012 at 8:19 PM, Jim Aikin <[hidden email]> wrote: > I've just received my first advance copy of Csound Power! Published by Course > Technology and available through the usual retail outlets, this book will > have little or nothing for power users, but my hope is that newcomers will > find it useful. > > Thanks again to Andres, Steven, and many other individuals for their > technical help while I was writing this book. > > --Jim Aikin > > -- > View this message in context: http://csound.1045644.n5.nabble.com/Csound-Power-Book-Is-Out-tp5500160p5500160.html > Sent from the Csound - General mailing list archive at Nabble.com. > > > Send bugs reports to the Sourceforge bug tracker > https://sourceforge.net/tracker/?group_id=81968&atid=564599 > Discussions of bugs and features can be posted here > To unsubscribe, send email [hidden email] with body "unsubscribe csound" > Send bugs reports to the Sourceforge bug tracker https://sourceforge.net/tracker/?group_id=81968&atid=564599 Discussions of bugs and features can be posted here To unsubscribe, send email [hidden email] with body "unsubscribe csound" |
|
Hi,
Great to hear Jim, congratulations! The book is very well laid out, looks beautiful! I think it'll be interesting to see how it reaches a group of people that might not otherwise be exposed to Csound. Cheers, Andrés On Tue, Feb 21, 2012 at 1:37 PM, Steven Yi <[hidden email]> wrote: A hearty congratulations Jim! I've long enjoyed and appreciated your |
|
In reply to this post by Jim Aikin
I've had my copy for a week or so...excellent book. A much
needed addition to the csound collection. I especially appreciate the sections about setting up csound and csoundqt. Cleared up several issues for me. Thanks, Jim Bob Foose On 13:59, Jim Aikin wrote: > I've just received my first advance copy of Csound Power! Published by Course > Technology and available through the usual retail outlets, this book will > have little or nothing for power users, but my hope is that newcomers will > find it useful. > > Thanks again to Andres, Steven, and many other individuals for their > technical help while I was writing this book. > > --Jim Aikin > > -- > View this message in context: http://csound.1045644.n5.nabble.com/Csound-Power-Book-Is-Out-tp5500160p5500160.html > Sent from the Csound - General mailing list archive at Nabble.com. > Send bugs reports to the Sourceforge bug tracker https://sourceforge.net/tracker/?group_id=81968&atid=564599 Discussions of bugs and features can be posted here To unsubscribe, send email [hidden email] with body "unsubscribe csound" |
|
Just got a copy of the book today and worked up to the Sound Design Project. I'm really enjoying it! Thanks Jim
On Tue, Feb 21, 2012 at 6:37 PM, Robert or Gretchen Foose <[hidden email]> wrote: I've had my copy for a week or so...excellent book. A much needed addition to the csound collection. I especially appreciate the sections about setting up csound and csoundqt. Cleared up several issues for me. Thanks, Jim |
|
In reply to this post by Jim Aikin
Greetings,
Got my copy of the book today, spent the afternoon perusing. Definitely recommended. Clearly written, enthusiastic prose, published in a nice readable format, very comfortable on these olden eyes. Excellent work, Jim ! The community owes you a beverage or two. :) Best, dp Send bugs reports to the Sourceforge bug tracker https://sourceforge.net/tracker/?group_id=81968&atid=564599 Discussions of bugs and features can be posted here To unsubscribe, send email [hidden email] with body "unsubscribe csound" |
|
For those of you on the music-dsp list, not sure if you are following but there is an interesting thread which has moved on to discuss the merits or lack of them of Csound. Ross Bencina in particular seems to be very critical, almost on a messianic level. Some of the responses appeared to me to be a bit ott.
Anyway, interesting read... Victor Send bugs reports to the Sourceforge bug tracker https://sourceforge.net/tracker/?group_id=81968&atid=564599 Discussions of bugs and features can be posted here To unsubscribe, send email [hidden email] with body "unsubscribe csound" |
|
link? :-}
On Mon, Feb 27, 2012 at 1:32 PM, Victor <[hidden email]> wrote: For those of you on the music-dsp list, not sure if you are following but there is an interesting thread which has moved on to discuss the merits or lack of them of Csound. Ross Bencina in particular seems to be very critical, almost on a messianic level. Some of the responses appeared to me to be a bit ott. --------------------------------------------------- Nick Suda ¦ [hidden email] Renton, WA ¦ (425) 941-0093 http://www.nicksuda.com ---------------------------------------------------
-- |
|
|
I think it's a case of either you "getting" csound or not. Different people are looking for different things in their tools. For instance, I've tried a few different things, but I keep coming back to csound. Neither tool is better or worse in a qualitative sense.
Jen
On Mon, Feb 27, 2012 at 4:42 PM, Victor <[hidden email]> wrote:
|
|
In reply to this post by Victor Lazzarini
I haven't been on the music-dsp mailing list in many years,
interesting to check in on that thread. I don't understand this: If you can't synchronously execute a procedural algorithm at the exact sample location of every zero crossing in an arbitrary input signal then there is a problem with your synthesis language. You can do sample by sample processing with vaget/vaset opcodes to read/write samples from/to an asig. Code written using those opcodes ends up looking very similar to code found in C/C++ versions of code I've seen, where a k-rate for-loop with an a-sig being the same as a for-loop iterating over a float[] or double[]. It also doesn't require ksmps=1 or setksmps 1. steven On Mon, Feb 27, 2012 at 9:42 PM, Victor <[hidden email]> wrote: > http://music.columbia.edu/pipermail/music-dsp/2012-February/070337.html > > > > On 27 Feb 2012, at 21:37, Nick Suda <[hidden email]> wrote: > > link? :-} > > On Mon, Feb 27, 2012 at 1:32 PM, Victor <[hidden email]> wrote: >> >> For those of you on the music-dsp list, not sure if you are following but >> there is an interesting thread which has moved on to discuss the merits or >> lack of them of Csound. Ross Bencina in particular seems to be very >> critical, almost on a messianic level. Some of the responses appeared to me >> to be a bit ott. >> >> Anyway, interesting read... >> >> Victor >> >> Send bugs reports to the Sourceforge bug tracker >> https://sourceforge.net/tracker/?group_id=81968&atid=564599 >> Discussions of bugs and features can be posted here >> To unsubscribe, send email [hidden email] with body "unsubscribe >> csound" >> > > > > -- > --------------------------------------------------- > Nick Suda ¦ [hidden email] > Renton, WA ¦ (425) 941-0093 > http://www.nicksuda.com > --------------------------------------------------- > -- > Send bugs reports to the Sourceforge bug tracker https://sourceforge.net/tracker/?group_id=81968&atid=564599 Discussions of bugs and features can be posted here To unsubscribe, send email [hidden email] with body "unsubscribe csound" |
|
In reply to this post by Jennifer Doering
I haven't read as far in as to find anything Ross has said yet that could be characterized as messianic or dogmatic, but this ensuing conversation is positively riveting. Thank you for bringing it to this list's attention!
On Mon, Feb 27, 2012 at 2:17 PM, Jennifer Doering <[hidden email]> wrote: I think it's a case of either you "getting" csound or not. Different people are looking for different things in their tools. For instance, I've tried a few different things, but I keep coming back to csound. Neither tool is better or worse in a qualitative sense. --------------------------------------------------- Nick Suda ¦ [hidden email] Renton, WA ¦ (425) 941-0093 http://www.nicksuda.com ---------------------------------------------------
-- |
|
In reply to this post by Jennifer Doering
+1
Am 27.02.2012 23:17, schrieb Jennifer Doering: > I think it's a case of either you "getting" csound or not. Different > people are looking for different things in their tools. For instance, > I've tried a few different things, but I keep coming back to csound. > Neither tool is better or worse in a qualitative sense. > > Jen > > On Mon, Feb 27, 2012 at 4:42 PM, Victor <[hidden email] > <mailto:[hidden email]>> wrote: > > http://music.columbia.edu/pipermail/music-dsp/2012-February/070337.html > > > > On 27 Feb 2012, at 21:37, Nick Suda <[hidden email] > <mailto:[hidden email]>> wrote: > >> link? :-} >> >> On Mon, Feb 27, 2012 at 1:32 PM, Victor <[hidden email] >> <mailto:[hidden email]>> wrote: >> >> For those of you on the music-dsp list, not sure if you are >> following but there is an interesting thread which has moved >> on to discuss the merits or lack of them of Csound. Ross >> Bencina in particular seems to be very critical, almost on a >> messianic level. Some of the responses appeared to me to be a >> bit ott. >> >> Anyway, interesting read... >> >> Victor >> >> Send bugs reports to the Sourceforge bug tracker >> >> https://sourceforge.net/tracker/?group_id=81968&atid=564599 >> <https://sourceforge.net/tracker/?group_id=81968&atid=564599> >> Discussions of bugs and features can be posted here >> To unsubscribe, send email [hidden email] >> <mailto:[hidden email]> with body "unsubscribe csound" >> >> >> >> >> -- >> --------------------------------------------------- >> Nick Suda ¦ [hidden email] <mailto:[hidden email]> >> Renton, WA ¦ (425) 941-0093 >> http://www.nicksuda.com <http://www.nicksuda.com/> >> --------------------------------------------------- >> -- >> > Send bugs reports to the Sourceforge bug tracker https://sourceforge.net/tracker/?group_id=81968&atid=564599 Discussions of bugs and features can be posted here To unsubscribe, send email [hidden email] with body "unsubscribe csound" |
|
In reply to this post by Steven Yi
Sure, but there is nothing wrong with using setksmps 1 on an UDO, to do sample by sample processing.
On 27 Feb 2012, at 22:22, Steven Yi <[hidden email]> wrote: > I haven't been on the music-dsp mailing list in many years, > interesting to check in on that thread. I don't understand this: > > If you can't synchronously execute a procedural algorithm at the exact > sample location of every zero crossing in an arbitrary input signal then > there is a problem with your synthesis language. > > You can do sample by sample processing with vaget/vaset opcodes to > read/write samples from/to an asig. Code written using those opcodes > ends up looking very similar to code found in C/C++ versions of code > I've seen, where a k-rate for-loop with an a-sig being the same as a > for-loop iterating over a float[] or double[]. It also doesn't require > ksmps=1 or setksmps 1. > > > steven > > > On Mon, Feb 27, 2012 at 9:42 PM, Victor <[hidden email]> wrote: >> http://music.columbia.edu/pipermail/music-dsp/2012-February/070337.html >> >> >> >> On 27 Feb 2012, at 21:37, Nick Suda <[hidden email]> wrote: >> >> link? :-} >> >> On Mon, Feb 27, 2012 at 1:32 PM, Victor <[hidden email]> wrote: >>> >>> For those of you on the music-dsp list, not sure if you are following but >>> there is an interesting thread which has moved on to discuss the merits or >>> lack of them of Csound. Ross Bencina in particular seems to be very >>> critical, almost on a messianic level. Some of the responses appeared to me >>> to be a bit ott. >>> >>> Anyway, interesting read... >>> >>> Victor >>> >>> Send bugs reports to the Sourceforge bug tracker >>> https://sourceforge.net/tracker/?group_id=81968&atid=564599 >>> Discussions of bugs and features can be posted here >>> To unsubscribe, send email [hidden email] with body "unsubscribe >>> csound" >>> >> >> >> >> -- >> --------------------------------------------------- >> Nick Suda ¦ [hidden email] >> Renton, WA ¦ (425) 941-0093 >> http://www.nicksuda.com >> --------------------------------------------------- >> -- >> > > > Send bugs reports to the Sourceforge bug tracker > https://sourceforge.net/tracker/?group_id=81968&atid=564599 > Discussions of bugs and features can be posted here > To unsubscribe, send email [hidden email] with body "unsubscribe csound" > Send bugs reports to the Sourceforge bug tracker https://sourceforge.net/tracker/?group_id=81968&atid=564599 Discussions of bugs and features can be posted here To unsubscribe, send email [hidden email] with body "unsubscribe csound" |
|
In reply to this post by Nick Suda
Well this probably supports my point: My basic contention is that it is an insurmountable shortcoming and obstacle to future human creative progress for any environment that employs this restrictive DSL-like paradigm [csound's] for creative expression in the domain of computer music (as previously described). This is what I mean by "flaw". brackets are mine.
|
|
hello fellow regressives
/rimshot an anonymous member of music-dsp wrote: >> My basic contention is that it is an insurmountable shortcoming and >> obstacle to future human creative progress for any environment that >> employs this restrictive DSL-like paradigm [csound's] for creative >> expression in the domain of computer music (as previously described). >> This is what I mean by "flaw". i think this is demonstratively false. humans have made creative progress even in the most restrictive environments [for instance, japanese internment (concentration) camps (poetry on the walls)- or even more archetypal, the nazi concentration camps (messaien's quator)]. i'm not saying there aren't any other ways to do computer music that might be more intutive, or efficient, or ... but to say that csound blocks creative progress shows the speakers limited conception of both the creative process and the human spirit. i'd say the speaker is more interested in making grand sweeping statements, and boosting his or her 'brand' [so to speak]; than saying something significant about creativity. especially in the arts, "progress" is a sticky issue; regardless, every day people do creative stuff with csound- some may be categorized as "progressive," some may be categorized as "regressive," some may be categorized as "masturbatory," and so on. but the wheel keeps turning. all it takes is one of those people to do something that might be seen as progressive [in an artistic content (which is extremely broad)] to show that the speaker was premature in his or her pronouncement. and i think i did that last week ... /rimshot -- http://or8.net/~johns "yeah yeah yeah" -beatles Send bugs reports to the Sourceforge bug tracker https://sourceforge.net/tracker/?group_id=81968&atid=564599 Discussions of bugs and features can be posted here To unsubscribe, send email [hidden email] with body "unsubscribe csound" |
| Powered by Nabble | See how NAML generates this page |
