Difference between revisions of "220a-fall-2007/chuck-lab1"
| Line 11: | Line 11: | ||
2. copying files | 2. copying files | ||
| − | + | there are several ways to run ChucK (e.g., via command line, Audicle, miniAudicle). for this lab, we will primarily use the miniAudicle ([http://audicle.cs.princeton.edu/mini/ homepage]), a development environment for ChucK that includes the ChucK engine (i.e., it's all you need to starting ChucKin'). | |
| + | |||
| + | 3. start the miniAudicle via the following steps: | ||
| + | ** (make sure JACK is already started as instructed above) | ||
| + | ** open a terminal window | ||
| + | ** at the prompt type: '''miniAudicle &''' | ||
Revision as of 20:29, 3 October 2007
http://chuck.cs.princeton.edu/doc/images/chuck_logo2.jpg
ChucK Lab #1: Hello ChucK and friends
This lab introduces running and programming in ChucK, several examples, and, perhaps most importantly, how to stop ChucK. Here we go; happy ChucKing!
0. we are going to use ChucK on the Linux operating system, via the JACK Audio Connection Kit. however, it's possibly (and fairly easy) to also run ChucK (and friends) on MacOS X or Windows.
1. start JACK (see starting jack)
2. copying files
there are several ways to run ChucK (e.g., via command line, Audicle, miniAudicle). for this lab, we will primarily use the miniAudicle (homepage), a development environment for ChucK that includes the ChucK engine (i.e., it's all you need to starting ChucKin').
3. start the miniAudicle via the following steps:
- (make sure JACK is already started as instructed above)
- open a terminal window
- at the prompt type: miniAudicle &
