- chuck-users - lists.cs.princeton.edu

vista and addressing soundcards (RTAudio?)
by Kassen 19 Dec '09

19 Dec '09

Fellow ChucKists, Are there any known issues addressing the Vista sound system? There was a post about this here; http://electro-music.com/forum/viewtopic.php?t=38812 and it strikes me that the results of --probe come up with rather unrealistic sample rates for the available outputs. Does this relate to any known issues? I do think that our version of RTAusdio predates Vista's changes to the Windows sound system but I find it a bit hard to imagine that they changed the hooks *that* badly. Any Vista experts who could shed some light on this? Kas.

1 0

--callback&--blocking (RTAudio?)
by Kassen 18 Dec '09

18 Dec '09

Fellow ChucKists, Dear Gary, I'm currently working on extending the manual section on the comandline flags for starting the VM and ran into --callback and --blocking. While mentioned in the online docs (which I'm basing my text on with some additional notes) these flags aren't explained in any depth beyond them being related to buffering. I suspect they relate to the interaction between RTAudio and the host-system/ soundcard but the way in which they do so isn't at all clear. Is there a place where more info could be found? Yours, Kas.

2 2

Documentation Sprint
by Adam Tindale 17 Dec '09

17 Dec '09

Hi All, We have finished our documentation sprint and I'd like to sum up a bit. Sorry for the thread going a bit nuts, it was necessary to get organized. Thanks for your patience. We have migrated the documentation to FLOSS manuals. You can see the results of the day here: http://en.flossmanuals.net/ChucK/Introduction We had a few very active people working very hard today. I'd like to thank Tomasz, Kas, Scott, and Michael. They did a great job. The good news is that we were able to port all of the docs over. We have a few things that need some touch ups but it is complete. We have added some new sections to the docs about user submitted libraries. We have fixed many small typos, errors, and errata. We have also initiated four more people into the documentation system so that I can get some ongoing help. The bad news is also plentiful. The current web style cannot be changed. We require deeper access to the css files in order to make our documentation clear. The PDF output provided by FLOSS manuals is insufficient. We have established a relationship with the founder and main dev of FLOSS manuals who is excited to help us. We have also created a number of new bugs in their system. Truly ChucKian. I plan to spend the next month in contact with the FLOSS manual dev list to figure out our issues. In January I will organize another sprint to integrate the solutions we develop across the whole manual. Basically, we are making a tradeoff: greater user contribution for lesser control of layout and formatting. I hope to work with the ChucK team to migrate our web documentation to FLOSS manuals as we centralized to that system. We made it a lot farther than I hoped today. We were able to develop new documentation and not just rehash the old stuff with a new skin. This is a major win for the community and I invite you to sign up for an account and help us to continue building the documentation. --art

3 3

Scale
by Hans Aberg 16 Dec '09

16 Dec '09

I've updated scale.ck - it now contains close to 50 measured gamelan pelog and slendro tunings, plus a few others, available here: http://www.math.su.se/~haberg/tuning_systems/ Hans

1 0

Integer divisions
by Hans Aberg 15 Dec '09

15 Dec '09

I find the integer divisions C rule is problematic when working with intervals. Suppose I have [8/7, 7/6, 7/6, 8/7] and implement it as [Interval.r(8/7), Interval.r(7/6), Interval.r(7/6), Interval.r(8/7)] Then this is the same as: [Interval.r(0), Interval.r(0), Interval.r(0), Interval.r(0)] One has to add ".0" one of the numerator/denominator: [Interval.r(8.0/7), Interval.r(7.0/6), Interval.r(7.0/6), Interval.r(8.0/7)], One possible rule might be converting 32-bit int to 64-bit floats, and then only back to int when needed. The question if it then affects some ChucK legacy code. Hans

6 14

banshee
by David Loberg Code 15 Dec '09

15 Dec '09

Any suggestions on how to create a scraped string effect in ChucK? (like in Henry Cowell's Banshee) http://upload.wikimedia.org/wikipedia/en/f/f0/Cowell-The_Banshee.ogg thanks david David Loberg Code School of Music Western Michigan University Kalamazoo, MI 49008 code(a)wmich.edu

2 1

mini shortcuts mistery
by Kassen 14 Dec '09

14 Dec '09

Fellow ChucKists, dear Spencer. For me the mini on Linux, using the Gnome desktop, has lately been acting up. Shortcuts like ctrl-c, ctrl-v, ctrl-x stop working after a while, so do the ones for adding and replacing shreds. Strangely ctrl-d *does* work in this state. No other programs have shown this behaviour and it's not consistent; they disappear after a while and so far I haven't seen them return. I think only the latest version does this. I'd like to document under what conditions this happens but it's quite inconsistent. Yours, Kas.

1 0

pitch tracking in ChucK
by Robert Poor 12 Dec '09

12 Dec '09

I need a low-latency pitch tracker for real-time performance work -- has anyone implemented one in ChucK? I'm ready to write one if need be -- it would be fun to start playing with the UAna objects -- but I don't feel the need to replicate work already done. Thanks in advance. - Rob

4 8

Mixed Object Lists and Hierarchy
by mike clemow 12 Dec '09

12 Dec '09

Hi list, Why can't I make an array of a parent type with objects of a single type, which is a child of the parent? class Foo { int foo; } class Bar extends Foo { int bar; } class Spam extends Foo { int spam; } Bar bara, barb, barc; Spam spama, spamb, spamc; Foo fooa, foob, fooc; [ bara, barb, barc ] @=> Bar bars[]; // okay [ bara, spamb, fooc ] @=> Foo foos[]; // mixed children okay [ bara, barb, barc ] @=> Foo morefoos[]; // incompatible types for assignment? best, Mike -- http://michaelclemow.com http://semiotech.org

3 5

Cloning
by Hans Aberg 11 Dec '09

11 Dec '09

ChucK does not have cloning for reference object, right? That is, the semantic equivalent of an this explicit copy-constructor pseudocode: class A {...} A a0; ... new A(a0) @=> A a1; That is, instead of merely setting a1 to the same reference as that of a0, create a new independent copy, and set its references to that of a0 (shallow copy). It is a problem in the program I wrote, scale.ck: if modifying tuning data, one actually manipulates the data of the original tuning loaded into memory. This is cool, but if I want to be able to reload the original data, I will have to write my own cloning operator. The difference is illustrated in the code below. First I make a shallow copy of a to b, which means that I can change b without changing a. Then I set a reference of a to b, after which changing b also changes a. Hans ---- clone.ck ---- class A { string s; } A a; "a" @=> a.s; A b; "b" @=> b.s; chout <= "a.s = " <= a.s <= ", b.s = " <= b.s <= ".\n"; "c" @=> b.s; chout <= "\"c\" @=> b.s; a = " <= a.s <= ", b = " <= b.s <= ".\n"; a.s @=> b.s; chout <= "a.s @=> b.s; a.s = " <= a.s <= ", b.s = " <= b.s <= ".\n"; "d" @=> b.s; chout <= "\"d\" @=> b.s; a.s = " <= a.s <= ", b.s = " <= b.s <= ".\n"; a @=> b; chout <= "a @=> b; a.s = " <= a.s <= ", b.s = " <= b.s <= ".\n"; "e" @=> b.s; chout <= "\"e\" @=> b.s; a.s = " <= a.s <= ", b.s = " <= b.s <= ".\n"; ---- run ---- $ chuck clone.ck a.s = a, b.s = b. "c" @=> b.s; a = a, b = c. a.s @=> b.s; a.s = a, b.s = a. "d" @=> b.s; a.s = a, b.s = d. a @=> b; a.s = a, b.s = a. "e" @=> b.s; a.s = e, b.s = e. --------

3 4