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

infinitely stuck
by Kassen 19 Sep '08

19 Sep '08

Dear ChucKists, Another day, another novel and exciting way to get the whole VM stuck; Wurely w => dac; 1.0 / 0 => w.freq; 1 => w.noteOn; second => now; At a frequency of infinity (which admittedly is a bit silly but it happened by accident...) Wurley (and probably the other FM instruments as well, I imagine) gets completely stuck and takes 100% CPU time. This is quite understandable but what's not so nice is that this gets the whole VM stuck as well. Watchdog will offer to stop the shred (in the Mini) but fails... so that forces us to quit the whole thing the hard way. I think LiSa can cause a similar situation if we request a lot of voices very quickly, say one every few ms, and she runs out of voices (I'm not yet certain about the exact conditions there). Generally it seems like watchdog is unable to remidy the situation if it's a UGen and not a shred that gets stuck. I'm not sure how we should deal with this. Perhaps there could be some way to get watchdog to interupt UGens, or perhaps we should sanitise UGen function calls. I'm not sure, for example, whether there is a perceived need for fm electrical pianos to accept frequencies above the nequist... It probably can't be avoided that some things will get suck under some conditions but I would like to have some safeguards against this taking down the whole VM, where possible. Yours, Kas.

2 2

UGen v.s. code in timing; very tricky
by Kassen 19 Sep '08

19 Sep '08

Dear list. Suppose we have a SinOsc named "s", connected to the dac, that has been playing for some arbitrary amount of time at a arbitrary frequency. Suppose we'd like to disconnect this from the dac while minimising the "click". One thing to try would be this; (1 - s.phase() )::s.period() => now; //strong timing to the rescue! s =< dac; Quite ChucKian, I thought, however this still clicks a bit. Some clickery is to be expected as not all frequencies will have a period that can be expressed in a integer number of samp's but this seemed like a bit much. On a whim I tried; (1 - s.phase() )::s.period() + samp => now; s =< dac; This clicks less and when I print the s.last(), the value is on -average- lower in magnitude. I then tried lining up the shred's timing with the UGen graph's; samp - (now % samp) => now; //yes; that's quite anal (1 - s.phase() )::s.period() => now; s =< dac; This doesn't affect matters quite as much as simply adding a samp to the time advanced; waiting a extra sample generally seems (to me) to decrease the magnitude of the s.last() right before we disconnect it. This would lead us to ask; "where does this samp come from?". I'm a bit at loss here, does anybody have any insights? Yours, Kas.

4 7

determining the type of an Object in code
by mike clemow 17 Sep '08

17 Sep '08

Hi list, Is there a way to determine an object's type programmatically? Cheers, Mike -- http://semiotech.org http://semiotech.org/michael

8 27

Double ChucK cleanup (bug)
by Kassen 16 Sep '08

16 Sep '08

Fellow ChucKists, With the return of "double chucking" (making more then one connection between two UGens or a UGen and the dac) something seems to have gone wrong; SinOsc s=> dac; second=> now; s=> dac; second=> now; If this is run in a VM set to loop or a MiniAudicle with it's version of ChucK replaced with the latest greatest only a single connection will be cleaned up as the shred exits, meaning "s" will stay connected to the dac and as "s" is never garbage collected this means a beep. This also means there is no way at all to get rid of this beep (short of stopping the whole VM) as there is no way at all to reach the namespace "s" is/was in. I'm adding this to the WiKi as a bug. Yours, Kas.

3 5

what is Gluck?
by lucas samaruga 15 Sep '08

15 Sep '08

Hola a todos I have two questions. Somebody knows what is about Gluck (Ogl api)? Is something like fluxus or is for a GUI use within audicle? BTW: Fluxus like ChucK is a great project!!! www.pawfal.org BTW2: An unified language approach would be surely better, (a time based approach) *1. Inventor: I think it can be good for your multimedia projects (fluxus can manage and RECORD OSC events). Cheers Lucas *1 PS: Ok, I'm musician, I have my preferences.

6 11

setting static data at construction (bug)
by Kassen 11 Sep '08

11 Sep '08

Fellow ChucKists, I believe this to be a bug; ------------------------------------------------------- class foo { 3 => static int bar; } <<<foo.bar>>>; ---------------------------------------- For float, int and dur making members static prevents them being set to a default value at construction, instead they are defaulting to 0 (or 0::ms). I ran into this with dur, where it's obviously dangerous to make this mistake. Of course these constructs would (probably?) mean that initialising any instance of such a class would mean resetting the value for all instancesbut I'm dealing with classes that exclusively have static members and not intending to make any specific instances of them. Clearly this is easy to get around but I still feel it's a bug. Yours, Kas.

5 13

ProcessPP + STK = ChucK on steroids?
by Stephen Sinclair 11 Sep '08

11 Sep '08

This was posted on the LAD mailing list: http://tapas.affenbande.org/wordpress/?page_id=91 It's a "livecoding" environment for making music with C++. I bet if you combined it with STK you could get something like ChucK. :) (but, *shudder*, C++... can't stand it more and more these days) Steve

2 2

Re: [chuck-users] emacs, and other editors for chuck
by ynohtna 10 Sep '08

10 Sep '08

Yay, lots of Emacs users! I'm currently, in my spare time, looking into integrating Emacs with ChucK to streamline (live) coding and experimentation. I have recently prototyped an Emacs minor mode that supports real-time text-mode sequencing (sending arbitrary OSC messages via realtime modified Emacs Lisp code) and have been hacking Emacs on and off since the early 90s. So, if anyone wants to express their needs for such a thing I'd be happy to consider converting them into implementable features. No promises, though, as my daylight job often consumes all my computer-centric energy. So far, I have determined a wish list including syntax highlighting, "intellisense" style completion, mode-line representation of ChucK's status, automatic shred/spork replacement, and minibuffer display of micro-documentation for classes/functions/syntax under the point. Any other input is welcome. Anthony. (Sometimes short bearded, often stubbled, no sandals)

4 3

library additions
by Kassen 10 Sep '08

10 Sep '08

I added a section on MIDI and a link to Bruce Murphy's MIDI sender code. I'd prefer to have that code on the WIKI as well and perhaps merge it with Antimon/Stefan's work on MIDI clock out as that fills the largest hole there (see http://electro-music.com/forum/viewtopic.php?p=161799#161799 ), but it's not my code. Yours, Kas.

1 0

emacs, and other editors for chuck
by Stephen Sinclair 09 Sep '08

09 Sep '08

On Tue, Sep 9, 2008 at 10:29 AM, Kassen <signal.automatique(a)gmail.com> wrote: > Stephen Sinclair; > >> I don't use it (emacs ftw!) > > Would you have the time to share some of your thoughts on the advantages of > emacs for ChucKing? I looked at it but it's quite a daunting editor and I'd > like to know a bit about the potential gains before investing time in it. Hm, let's see. _mainly_ I use emacs because i'm used to it. I use it for coding, and my fingers know the shortcuts, and it just works for me. I've tried to get used to vim, for example, and just can't seem to do it. This goes for any editor, of course: use what you know, and what you like. I'm not on any mission to make people use specific software, I can't only make recommendations. However, there are some virtues, I think that deserve mention. (Some of these will of course be available in other programs.) One, is that emacs has "windows". You can drop a shell into one window, an editor into another, and a status window into a third. You can split the screen in any desireable way. Two, is that I have F6 configured for "compile", which gives me a one-liner shell command, and F7 for "recompile", which just repeats whatever the last compile command was. This is insanely useful for chucking, because you can hit F6 and tell chuck to load your script, and then take note of which shred ID it got, and use the '=' command to replace it the next time. Then just edit and keep hitting F7. On top of that, emacs has really good search & replace and regexp support. (I use the former more than the latter.) Which I have configured to Ctrl-A on my keyboard so that's a really fast thing to do. Then I can switch between files by hitting Ctrl-B and typing the first few letters of the file name and then Tab (if i've loaded it already) or load or create a new file with Ctrl-F. The filename completion rocks. Lastly, it's completely programmable with lisp. So if I wanted I could probably make it way more intelligently communicate with ChucK, interpreting its error messages among other things. But I don't have the patience for that. :) One thing that I sorely miss is the ability to automatically track which shred IDs get assigned to which files, for when I want to remove or replace a shred. However I think this is also partly the fault of ChucK which can't be bothered to tell me this information in a useful way, since it doesn't differentiate between files and sporks. But I'd love to be able to remove or replace a shred by *name* instead of by some number that I have to look way back in the buffer to find. (But of course Ctrl-S-S "search" is pretty quick for this.) All in all I don't have to take my hand off the keyboard, which is particularly nice. As for it being a daunting editor, I really only use a handful of commands, though of course it's capable of much more. > >> >> but I just tried to compile it quickly and >> it failed, so I can't help directly. > > Hmmm. I found the Mini quite easy to compile, at least since there is a > clear list of all that you need for it, on top of ChucK's dependencies. Yeah I don't know why it didn't work. But I haven't taken the time to figure it out. Probably something small. > I just wish it would have a more intelligent "replace" function for shreds > then always replacing the last one that was run. It's nice and simple, I > like that. There are hotkeys for running code though not enough for editing > it. emacs will solve all of those issues, I'm sure but that would go at the > expense of the simplicity? I'd love to program some emacs lisp, or some other mechanism, to track which shreds have been loaded. Something that would give super-quick keyboard access to remove or replace specific shreds. Perhaps Tab completion would be good for this. By the way, with all this talk about emacs, I should really specify, honestly, that I really only have a very short beard. And no, I don't wear sandles. ;-) cheers, Steve

3 3