Difference between revisions of "220a-fall-2007/chuck-lab1"

From CCRMA Wiki
Jump to: navigation, search
m (220a-fall2007/chuck-lab1 moved to 220a-fall-2007/chuck-lab1)
 
(12 intermediate revisions by 2 users not shown)
Line 3: Line 3:
 
= ChucK Lab #1: Hello ChucK and friends =
 
= 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!
+
This lab introduces running and programming in ChucK, several examples, and, perhaps most importantly, how to stop ChucK.  We are going to use ChucK on the Linux operating system, via the '''J'''ACK '''A'''udio '''C'''onnection '''K'''it.  however, it's possibly (and fairly easy) to also run ChucK (and friends) on MacOS X or Windows.  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').  Here we go; happy ChucKing!
  
we are going to use ChucK on the Linux operating system, via the '''J'''ACK '''A'''udio '''C'''onnection '''K'''it.  however, it's possibly (and fairly easy) to also run ChucK (and friends) on MacOS X or Windows.
 
# start JACK (see [[220a/start-jack|starting jack]])
 
# 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').
+
1. take the '''[[220a/miniAudicle-intro|miniAudicle intro tour]]'''
  
# start the miniAudicle via the following steps:
+
2. copy some files to your local directory.  in a terminal window, create a folder somewhere to hold the files, for example:
#* (make sure JACK is already started as instructed above)
+
#* open a terminal window
+
#* at the prompt type:
+
    '''miniAudicle &'''
+
  
(something like this):
+
    cd ~
 +
    mkdir ck-lab1
  
[[Image:Terminal-mA.png]]
+
go into the folder you just created, then copy the lab1 files over:
 +
 
 +
    cd ck-lab1
 +
    cp -r /usr/ccrma/web/html/courses/220a-fall-2007/ck/lab1/* .
 +
 
 +
4. in the miniAudicle, set current directory to your ck-lab1 in Edit/Preferences/Misc...
 +
 
 +
5. open these files in miniAudicle, play them, and play with them!  (try changing parameters, and get a sense of what they do!)
 +
 
 +
6. '''TBA''' component postponed. (move on to hw2!)

Latest revision as of 22:31, 4 January 2008

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. 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. 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'). Here we go; happy ChucKing!


1. take the miniAudicle intro tour

2. copy some files to your local directory. in a terminal window, create a folder somewhere to hold the files, for example:

   cd ~
   mkdir ck-lab1

go into the folder you just created, then copy the lab1 files over:

   cd ck-lab1
   cp -r /usr/ccrma/web/html/courses/220a-fall-2007/ck/lab1/* .
  

4. in the miniAudicle, set current directory to your ck-lab1 in Edit/Preferences/Misc...

5. open these files in miniAudicle, play them, and play with them! (try changing parameters, and get a sense of what they do!)

6. TBA component postponed. (move on to hw2!)