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

OSC pattern matching
by dparson 26 Jul '13

26 Jul '13

It's been a while, so apologies in advance if this topic has come up lately. Last time that I wrote an OSC receiver in ChucK, the code had to match the incoming address pattern verbatim. There was no way to apply pattern matching, e.g., a regular expression, to match the incoming string. Also, I don't think that there was a way to match a prefix of the incoming string, after which one could in theory write one's own pattern matcher on the remainder of the incoming string. Little time for that, anyway. Is it (still) necessary to match the incoming OSC pattern string, literally, in its entirety? My solution last time was to spork a separate shred to match each incoming literal string in its entirety. That approach does not fully solve the problem at hand. Thanks. Dale (Acoustic Interloper)

2 1

How to read from standard input
by Rich Caloggero 10 Jul '13

10 Jul '13

Is there a way to do this? -- Rich

1 0

One more question - how to get state of shift key when receiving a keyboard event
by Rich Caloggero 10 Jul '13

10 Jul '13

The system sends integer 224 prefixing an extended key, but modifiers like shift and alt don’t seem to trigger this. thanx very much for all your help here. The FileIO stuff works great! -- Rich

1 1

Writing non-audio data to files
by Rich Caloggero 09 Jul '13

09 Jul '13

I found references to FIleIO class circa 2008, but seems none are implemented. .3-1.2 has chout <= float <= int <= string ... and same for cherr but how to go to file instead of console? Guess I could just redirect on command line, but kinda kludgy. -- Rich

2 1

Online Manual
by Rich Caloggero 08 Jul '13

08 Jul '13

http://booki.flossmanuals.net/chuck/_full/ Is this manual current / being actively updated? If so, then there is a problem throughout with how characters are represented. It seems that perhaps the text may have been extracted from some graphical design program because some character combinations "(the characters “f” followed by “i” in this example) are replaced by a single weird character. When seen visually this may look like the two-character sequence “fi”, but to a screen reader or to anything else that processes text, this looks like a weird unpronouncible mess. My screen reader reads the word “file” in this example as: [character 64257[le The stuff in brackets is what the screen reader says when it encounters the weird character. Hope this can be fixed. Reading the manual in its current state is much less fun than it could be. Thanx for a great language and community. -- Rich %>chuck moe.ckIn this case, ChucK will run whatever is in moe.ck. You can replace moe.ck with the name of another ChucK ﬁle. If this script is a just a loop that never ends then we need to stop ChucK eventually. Simply press CTRL-C (hold control and press c). This is the ”kill process” hotkey in the terminal. Some ﬁrst things to try is to test the concurrency (running multiple ChucK ﬁles in parallel) are moe, larry, and curly. First, run them each individually ( run chuck on moe.ck, larry.ck, or

1 0