https://ccrma.stanford.edu/mediawiki/api.php?action=feedcontributions&user=Craffel&feedformat=atomCCRMA Wiki - User contributions [en]2024-03-29T08:32:43ZUser contributionsMediaWiki 1.24.1https://ccrma.stanford.edu/mediawiki/index.php?title=220c-spring-2010&diff=9971220c-spring-20102010-05-18T18:14:04Z<p>Craffel: </p>
<hr />
<div>[[Category:Courses]]<br />
= [https://ccrma.stanford.edu/courses/220c/ <b>Music 220c</b>] - Research Seminar in Computer-Generated Music =<br />
<br />
== [http://ccrma.stanford.edu/wiki/220c-spring-2010/about <b>About the Class</b>] ==<br />
<br />
<br />
==Use the Space Below to Link to Your Project Pages/Wikis==<br />
Short blurbs and links to project pages:<br />
<br />
* <b>Bjoern Erlach</b> - w/ J. Abel. inter-sampling artifact calibration, acoustic modeling<br />
* <b>Charlie Forkish</b> - Produce a stage show. Develop a system that will take inputs from each player (of about five), and visualize each input to [http://www.youtube.com/watch?v=Bh7bYNAHXxw <b>a freakin' LASER BEAM(!)</b>] — using freq. analysis/tracking, envelope tracking, timbre tracking, etc...<br />
* [https://ccrma.stanford.edu/~hanaboy/220c/ <b>Stephen Henderson</b>] - Alzheimer's helped by medial prefrontal cortex? helped by music?<br />
* <b>Grahame Lesh</b> - Live Video Recording/Editing of a band based on their output.<br />
* [http://ccrma.stanford.edu/~tymaue/220c/ <b>Tyler Maue</b>] - Lüp-It: One-man band loop generator.<br />
* [https://ccrma.stanford.edu/~lmelvin/220c/ <b>Linden Melvin</b>] - Live Sound Synthesis to make a Soundscape<br />
* <b>Dohi Moon</b> - Electronic Music + Animation (String Quartet)<br />
* [https://ccrma.stanford.edu/~craffel/sound/echo <b>Colin Raffel</b>] - Getting Rain Barrels - Live sampling, wireless miking — group music making.<br />
* [https://ccrma.stanford.edu/~mrepper/220c/ <b>Michael Repper</b>] - Bending Music, Spectrograms for Donald Barra's new book, "Shaping Music" <br />
* [https://ccrma.stanford.edu/wiki/Shep421 <b>Adam Shepperd</b>] - Composition for infrasonics. Creation of very low frequency driver using tactile transducers and found satellite dish.<br />
* [https://ccrma.stanford.edu/~isyiwang/220c/ <b>Isaac Wang</b>] - Expansion of 220B project - sonifying twitter updates - Something generative/automated that also sounds good, put interface on server so that people can "tweet" from anywhere. Collaborative.<br />
* <b>Jacob Wittenberg</b> - divine players choices (maybe in Jazz?) with MIDI info, formulate algorythms based on choices made by performers - learn the probabilities for different things (Machine learning) so that one can play a duet with oneself. The computer "knows" one's style. <br />
*[https://ccrma.stanford.edu/~xiangzh/Site/Site/220C.html <b>Xiang Zhang</b>] - w/ J. Abel. 3d modeling, acoustic modeling <br />
<br />
~<br />
<br />
==CONCERT PLANNING==<br />
<br />
<b>Thurs. May 27, 2010</b><br />
<br />
Sound-check SAME DAY.<br />
<b>sound-check order:</b><br />
<br />
*Isaac 3:30pm<br />
*Tyler 4pm<br />
*Jacob 4:30pm<br />
*Linden 5pm<br />
*Graham 5:30pm<br />
<br />
<i>outside</i><br />
<br />
*Adam 6pm<br />
*Colin 6:30pm<br />
<br />
<br />
<b>CONCERT order:</b><br />
*Melvin<br />
*Wittenberg<br />
*Maue<br />
*Bjoern<br />
*Wang<br />
*Graham<br />
<br />
<i>outside</i><br />
<br />
*Adam<br />
*Colin<br />
<br />
<br />
Backyard reqs.<br />
*risers<br />
*screen<br />
*PA<br />
*stage<br />
<br />
===Rehearsal Times:===<br />
*Linden - M 6-7:30, T 6:30-8, W 12-1:30<br />
*Jacob - M 4:15-6, T 10-11<br />
*Tyler - M 7:30-9, W 2:30-4, R 12-1<br />
*Colin - M 3-4, T 5-6:30, W 1:30-2:30<br />
*Adam - W 4-5<br />
*Bjoern - T 9-10<br />
*Isaac - T 8-9, W 5-6,<br />
*Grahame - T 11-12, W 11-12<br />
<br />
[[Image:Rehearse220c_03.jpg]]<br />
<br />
<br />
----<br />
Email [mailto:cc@ccrma.stanford.edu Chris] ~ <br />
Email [mailto:mpberger@ccrma.stanford.edu Michael]</div>Craffelhttps://ccrma.stanford.edu/mediawiki/index.php?title=220c-spring-2010&diff=9970220c-spring-20102010-05-18T18:12:53Z<p>Craffel: </p>
<hr />
<div>[[Category:Courses]]<br />
= [https://ccrma.stanford.edu/courses/220c/ <b>Music 220c</b>] - Research Seminar in Computer-Generated Music =<br />
<br />
== [http://ccrma.stanford.edu/wiki/220c-spring-2010/about <b>About the Class</b>] ==<br />
<br />
<br />
==Use the Space Below to Link to Your Project Pages/Wikis==<br />
Short blurbs and links to project pages:<br />
<br />
* <b>Bjoern Erlach</b> - w/ J. Abel. inter-sampling artifact calibration, acoustic modeling<br />
* <b>Charlie Forkish</b> - Produce a stage show. Develop a system that will take inputs from each player (of about five), and visualize each input to [http://www.youtube.com/watch?v=Bh7bYNAHXxw <b>a freakin' LASER BEAM(!)</b>] — using freq. analysis/tracking, envelope tracking, timbre tracking, etc...<br />
* [https://ccrma.stanford.edu/~hanaboy/220c/ <b>Stephen Henderson</b>] - Alzheimer's helped by medial prefrontal cortex? helped by music?<br />
* <b>Grahame Lesh</b> - Live Video Recording/Editing of a band based on their output.<br />
* [http://ccrma.stanford.edu/~tymaue/220c/ <b>Tyler Maue</b>] - Lüp-It: One-man band loop generator.<br />
* [https://ccrma.stanford.edu/~lmelvin/220c/ <b>Linden Melvin</b>] - Live Sound Synthesis to make a Soundscape<br />
* <b>Dohi Moon</b> - Electronic Music + Animation (String Quartet)<br />
* [https://ccrma.stanford.edu/~craffel/music/echo <b>Colin Raffel</b>] - Getting Rain Barrels - Live sampling, wireless miking — group music making.<br />
* [https://ccrma.stanford.edu/~mrepper/220c/ <b>Michael Repper</b>] - Bending Music, Spectrograms for Donald Barra's new book, "Shaping Music" <br />
* [https://ccrma.stanford.edu/wiki/Shep421 <b>Adam Shepperd</b>] - Composition for infrasonics. Creation of very low frequency driver using tactile transducers and found satellite dish.<br />
* [https://ccrma.stanford.edu/~isyiwang/220c/ <b>Isaac Wang</b>] - Expansion of 220B project - sonifying twitter updates - Something generative/automated that also sounds good, put interface on server so that people can "tweet" from anywhere. Collaborative.<br />
* <b>Jacob Wittenberg</b> - divine players choices (maybe in Jazz?) with MIDI info, formulate algorythms based on choices made by performers - learn the probabilities for different things (Machine learning) so that one can play a duet with oneself. The computer "knows" one's style. <br />
*[https://ccrma.stanford.edu/~xiangzh/Site/Site/220C.html <b>Xiang Zhang</b>] - w/ J. Abel. 3d modeling, acoustic modeling <br />
<br />
~<br />
<br />
==CONCERT PLANNING==<br />
<br />
<b>Thurs. May 27, 2010</b><br />
<br />
Sound-check SAME DAY.<br />
<b>sound-check order:</b><br />
<br />
*Isaac 3:30pm<br />
*Tyler 4pm<br />
*Jacob 4:30pm<br />
*Linden 5pm<br />
*Graham 5:30pm<br />
<br />
<i>outside</i><br />
<br />
*Adam 6pm<br />
*Colin 6:30pm<br />
<br />
<br />
<b>CONCERT order:</b><br />
*Melvin<br />
*Wittenberg<br />
*Maue<br />
*Bjoern<br />
*Wang<br />
*Graham<br />
<br />
<i>outside</i><br />
<br />
*Adam<br />
*Colin<br />
<br />
<br />
Backyard reqs.<br />
*risers<br />
*screen<br />
*PA<br />
*stage<br />
<br />
===Rehearsal Times:===<br />
*Linden - M 6-7:30, T 6:30-8, W 12-1:30<br />
*Jacob - M 4:15-6, T 10-11<br />
*Tyler - M 7:30-9, W 2:30-4, R 12-1<br />
*Colin - M 3-4, T 5-6:30, W 1:30-2:30<br />
*Adam - W 4-5<br />
*Bjoern - T 9-10<br />
*Isaac - T 8-9, W 5-6,<br />
*Grahame - T 11-12, W 11-12<br />
<br />
[[Image:Rehearse220c_03.jpg]]<br />
<br />
<br />
----<br />
Email [mailto:cc@ccrma.stanford.edu Chris] ~ <br />
Email [mailto:mpberger@ccrma.stanford.edu Michael]</div>Craffelhttps://ccrma.stanford.edu/mediawiki/index.php?title=Tralala&diff=9706Tralala2010-04-01T18:29:25Z<p>Craffel: Created page with 'Don't create me'</p>
<hr />
<div>Don't create me</div>Craffelhttps://ccrma.stanford.edu/mediawiki/index.php?title=MakerFaireTech&diff=9693MakerFaireTech2010-03-31T18:57:44Z<p>Craffel: </p>
<hr />
<div>=='''Adam Somers'''==<br />
<br />
''Can you present Saturday morning? Yes''<br />
<br />
''Can you present Saturday afternoon? Yes''<br />
<br />
''Can you present Sunday morning? Yes''<br />
<br />
''Can you present Sunday afternoon? Yes''<br />
<br />
<br />
''Will you be using a CCRMA workstation computer? No"<br />
<br />
''Will you be using your own laptop? No''<br />
<br />
''What will your audio outputs be? Stereo quarter inch. ”''<br />
<br />
''Can your audio be played with headphones? Yes''<br />
<br />
''If not, how loud will your work be? Depends on speaker setup''<br />
<br />
''Will you need more space than a regular workstation? no''<br />
<br />
''Any other needs or requests we should know about?''<br />
<br />
''Do you have any interest in giving a short lecture or performance if there is a stage in the computer music corner?''<br />
<br />
=='''Colin Raffel'''==<br />
''Can you present Saturday morning? (Yes, No, I'd prefer not)''<br />
Yes<br />
<br />
''Can you present Saturday afternoon? (Yes, No, I'd prefer not)''<br />
Yes<br />
<br />
''Can you present Sunday morning? (Yes, No, I'd prefer not)''<br />
Yes<br />
<br />
''Can you present Sunday afternoon? (Yes, No, I'd prefer not)''<br />
Yes<br />
<br />
''Will you be using a CCRMA workstation computer?<br />
No<br />
<br />
''Will you be using your own laptop?''<br />
Yes<br />
<br />
''What will your audio outputs be? (Ie. 4 1/4” or stereo 1/8” or headphones etc.)''<br />
Stereo 1/8" Headphones<br />
<br />
''Can your audio be played with headphones?''<br />
Yes<br />
<br />
''If not, how loud will your work be?''<br />
--<br />
<br />
''Will you need more space than a regular workstation''<br />
Enough for a laptop and two ~12"x12" controllers<br />
<br />
''Any other needs or requests we should know about?''<br />
No<br />
<br />
''Do you have any interest in giving a short lecture or performance if there is a stage in the computer music corner?'<br />
Yes<br />
<br />
<br />
<br />
=='''Uri Nieto'''==<br />
''Can you present Saturday morning? (Yes, No, I'd prefer not)''<br />
<br />
''Can you present Saturday afternoon? (Yes, No, I'd prefer not)''<br />
<br />
''Can you present Sunday morning? (Yes, No, I'd prefer not)''<br />
<br />
''Can you present Sunday afternoon? (Yes, No, I'd prefer not)''<br />
<br />
<br />
''Will you be using a CCRMA workstation computer?<br />
<br />
''Will you be using your own laptop?''<br />
<br />
''What will your audio outputs be? (Ie. 4 1/4” or stereo 1/8” or headphones etc.)''<br />
<br />
''Can your audio be played with headphones?''<br />
<br />
''If not, how loud will your work be?''<br />
<br />
''Will you need more space than a regular workstation''<br />
<br />
''Any other needs or requests we should know about?''<br />
<br />
''Do you have any interest in giving a short lecture or performance if there is a stage in the computer music corner?'<br />
<br />
<br />
<br />
<br />
=='''Ed Berdahl'''==<br />
''Can you present Saturday morning? Yes''<br />
<br />
''Can you present Saturday afternoon? Yes''<br />
<br />
''Can you present Sunday morning? Yes''<br />
<br />
''Can you present Sunday afternoon? Yes''<br />
<br />
<br />
''Will you be using a CCRMA workstation computer? No''<br />
<br />
''Will you be using your own laptop? Yes''<br />
<br />
''What will your audio outputs be? None (acoustic project)''<br />
<br />
''Can your audio be played with headphones? N/A''<br />
<br />
''If not, how loud will your work be? Probably shaker sound level''<br />
<br />
''Will you need more space than a regular workstation No''<br />
<br />
''Any other needs or requests we should know about? No''<br />
<br />
''Do you have any interest in giving a short lecture or performance if there is a stage in the computer music corner? Happy to give a lecture w/ short demo at the end!'<br />
<br />
=='''Michael Berger'''==<br />
<br />
<b>GRIP MAESTRO</b><br />
<br />
''Can you present Saturday morning?'' <b>(Yes)</b><br />
<br />
''Can you present Saturday afternoon?'' <b>(Yes)</b><br />
<br />
''Can you present Sunday morning?'' <b>(Yes)</b><br />
<br />
''Can you present Sunday afternoon?'' <b>(Yes)</b><br />
<br />
<br />
''Will you be using a CCRMA workstation computer? <b>No, but I would love to use some portable stereo speakers.</b><br />
<br />
''Will you be using your own laptop?'' <b>Yes.</b><br />
<br />
''What will your audio outputs be?'' <b>MiniStereo plug (i.e. for headphones, or computer speakers)</b><br />
<br />
''Can your audio be played with headphones?'' <b>Yes.</b><br />
<br />
''If not, how loud will your work be?'' <b>Just above conversation level.</b><br />
<br />
''Will you need more space than a regular workstation'' <b>No.</b><br />
<br />
''Any other needs or requests we should know about?'' <b>No.</b><br />
<br />
''Do you have any interest in giving a short lecture or performance if there is a stage in the computer music corner?'' <b>Sure, 3-5 min.</b><br />
<br />
=='''Nando'''==<br />
''Can you present Saturday morning? (Yes, No, I'd prefer not)''<br />
<br />
''Can you present Saturday afternoon? (Yes, No, I'd prefer not)''<br />
<br />
''Can you present Sunday morning? (Yes, No, I'd prefer not)''<br />
<br />
''Can you present Sunday afternoon? (Yes, No, I'd prefer not)''<br />
<br />
<br />
''Will you be using a CCRMA workstation computer?<br />
<br />
''Will you be using your own laptop?''<br />
<br />
''What will your audio outputs be? (Ie. 4 1/4” or stereo 1/8” or headphones etc.)''<br />
<br />
''Can your audio be played with headphones?''<br />
<br />
''If not, how loud will your work be?''<br />
<br />
''Will you need more space than a regular workstation''<br />
<br />
''Any other needs or requests we should know about?''<br />
<br />
''Do you have any interest in giving a short lecture or performance if there is a stage in the computer music corner?'<br />
<br />
<br />
<br />
<br />
=='''Carr Wilkerson'''==<br />
''Can you present Saturday morning? (Yes, No, I'd prefer not)''<br />
<br />
''Can you present Saturday afternoon? (Yes, No, I'd prefer not)''<br />
<br />
''Can you present Sunday morning? (Yes, No, I'd prefer not)''<br />
<br />
''Can you present Sunday afternoon? (Yes, No, I'd prefer not)''<br />
<br />
<br />
''Will you be using a CCRMA workstation computer?<br />
<br />
''Will you be using your own laptop?''<br />
<br />
''What will your audio outputs be? (Ie. 4 1/4” or stereo 1/8” or headphones etc.)''<br />
<br />
''Can your audio be played with headphones?''<br />
<br />
''If not, how loud will your work be?''<br />
<br />
''Will you need more space than a regular workstation''<br />
<br />
''Any other needs or requests we should know about?''<br />
<br />
''Do you have any interest in giving a short lecture or performance if there is a stage in the computer music corner?'<br />
<br />
<br />
<br />
<br />
=='''Jason Sadural'''==<br />
''Can you present Saturday morning? (Yes, No, I'd prefer not)''<br />
<br />
''Can you present Saturday afternoon? (Yes, No, I'd prefer not)''<br />
<br />
''Can you present Sunday morning? (Yes, No, I'd prefer not)''<br />
<br />
''Can you present Sunday afternoon? (Yes, No, I'd prefer not)''<br />
<br />
<br />
''Will you be using a CCRMA workstation computer?<br />
<br />
''Will you be using your own laptop?''<br />
<br />
''What will your audio outputs be? (Ie. 4 1/4” or stereo 1/8” or headphones etc.)''<br />
<br />
''Can your audio be played with headphones?''<br />
<br />
''If not, how loud will your work be?''<br />
<br />
''Will you need more space than a regular workstation''<br />
<br />
''Any other needs or requests we should know about?''<br />
<br />
''Do you have any interest in giving a short lecture or performance if there is a stage in the computer music corner?'<br />
<br />
<br />
=='''Sasha Leitman'''==<br />
''Can you present Saturday morning? (Yes, No, I'd prefer not)''<br />
<br />
''Can you present Saturday afternoon? (Yes, No, I'd prefer not)''<br />
<br />
''Can you present Sunday morning? (Yes, No, I'd prefer not)''<br />
<br />
''Can you present Sunday afternoon? (Yes, No, I'd prefer not)''<br />
<br />
<br />
''Will you be using a CCRMA workstation computer?<br />
<br />
''Will you be using your own laptop?''<br />
<br />
''What will your audio outputs be? (Ie. 4 1/4” or stereo 1/8” or headphones etc.)''<br />
<br />
''Can your audio be played with headphones?''<br />
<br />
''If not, how loud will your work be?''<br />
<br />
''Will you need more space than a regular workstation''<br />
<br />
''Any other needs or requests we should know about?''<br />
<br />
''Do you have any interest in giving a short lecture or performance if there is a stage in the computer music corner?'<br />
<br />
<br />
<br />
=='''Javier Sanchez'''==<br />
''Can you present Saturday morning? (Yes, No, I'd prefer not)'' YES<br />
<br />
''Can you present Saturday afternoon? (Yes, No, I'd prefer not)'' YES<br />
<br />
''Can you present Sunday morning? (Yes, No, I'd prefer not)'' NO<br />
<br />
''Can you present Sunday afternoon? (Yes, No, I'd prefer not)'' NO<br />
<br />
<br />
''Will you be using a CCRMA workstation computer? NO<br />
<br />
''Will you be using your own laptop?'' YES<br />
<br />
''What will your audio outputs be? (Ie. 4 1/4” or stereo 1/8” or headphones etc.)'' Headphones - Stereo 1/8''<br />
<br />
''Can your audio be played with headphones?'' YES<br />
<br />
''If not, how loud will your work be?'' <br />
<br />
''Will you need more space than a regular workstation'' NO<br />
<br />
''Any other needs or requests we should know about?'' NO<br />
<br />
''Do you have any interest in giving a short lecture or performance if there is a stage in the computer music corner?' YES !!!<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
'''Just ignore this part'''<br />
<br />
<br />
FOR PERFORMANCES:<br />
I can do short improvisations of about 3-6 minutes if requested.<br />
<br />
What is the length of your piece?<br />
3-6 minutes<br />
<br />
What will your audio outputs be? (Ie. 4 [WINDOWS-1252?]1/4” or stereo [WINDOWS-1252?]1/8” etc)<br />
my computer outputs mini-stereo<br />
<br />
Will you be projecting video?<br />
NO.<br />
<br />
FOR LECTURES:<br />
<br />
What will your audio outputs be? (Ie. 4 [WINDOWS-1252?]1/4” or stereo [WINDOWS-1252?]1/8” etc)<br />
<br />
Will you be projecting video?</div>Craffelhttps://ccrma.stanford.edu/mediawiki/index.php?title=MakerFaireTech&diff=9688MakerFaireTech2010-03-31T18:43:08Z<p>Craffel: </p>
<hr />
<div>=='''Adam Sommers'''==<br />
<br />
''Can you present Saturday morning? (Yes, No, I'd prefer not)''<br />
<br />
''Can you present Saturday afternoon? (Yes, No, I'd prefer not)''<br />
<br />
''Can you present Sunday morning? (Yes, No, I'd prefer not)''<br />
<br />
''Can you present Sunday afternoon? (Yes, No, I'd prefer not)''<br />
<br />
<br />
''Will you be using a CCRMA workstation computer?<br />
<br />
''Will you be using your own laptop?''<br />
<br />
''What will your audio outputs be? (Ie. 4 1/4” or stereo 1/8” or headphones etc.)''<br />
<br />
''Can your audio be played with headphones?''<br />
<br />
''If not, how loud will your work be?''<br />
<br />
''Will you need more space than a regular workstation''<br />
<br />
''Any other needs or requests we should know about?''<br />
<br />
''Do you have any interest in giving a short lecture or performance if there is a stage in the computer music corner?''<br />
<br />
<br />
<br />
<br />
=='''Colin Raffel'''==<br />
''Can you present Saturday morning? (Yes, No, I'd prefer not)''<br />
Yes<br />
''Can you present Saturday afternoon? (Yes, No, I'd prefer not)''<br />
Yes<br />
''Can you present Sunday morning? (Yes, No, I'd prefer not)''<br />
Yes<br />
''Can you present Sunday afternoon? (Yes, No, I'd prefer not)''<br />
Yes<br />
<br />
''Will you be using a CCRMA workstation computer?<br />
No<br />
''Will you be using your own laptop?''<br />
Yes<br />
''What will your audio outputs be? (Ie. 4 1/4” or stereo 1/8” or headphones etc.)''<br />
Stereo 1/8" Headphones<br />
''Can your audio be played with headphones?''<br />
Yes<br />
''If not, how loud will your work be?''<br />
--<br />
''Will you need more space than a regular workstation''<br />
Enough for a laptop and two ~12"x12" controllers<br />
''Any other needs or requests we should know about?''<br />
No<br />
''Do you have any interest in giving a short lecture or performance if there is a stage in the computer music corner?'<br />
Yes<br />
<br />
<br />
<br />
=='''Uri Nieto'''==<br />
''Can you present Saturday morning? (Yes, No, I'd prefer not)''<br />
<br />
''Can you present Saturday afternoon? (Yes, No, I'd prefer not)''<br />
<br />
''Can you present Sunday morning? (Yes, No, I'd prefer not)''<br />
<br />
''Can you present Sunday afternoon? (Yes, No, I'd prefer not)''<br />
<br />
<br />
''Will you be using a CCRMA workstation computer?<br />
<br />
''Will you be using your own laptop?''<br />
<br />
''What will your audio outputs be? (Ie. 4 1/4” or stereo 1/8” or headphones etc.)''<br />
<br />
''Can your audio be played with headphones?''<br />
<br />
''If not, how loud will your work be?''<br />
<br />
''Will you need more space than a regular workstation''<br />
<br />
''Any other needs or requests we should know about?''<br />
<br />
''Do you have any interest in giving a short lecture or performance if there is a stage in the computer music corner?'<br />
<br />
<br />
<br />
<br />
=='''Ed Berdahl'''==<br />
''Can you present Saturday morning? Yes''<br />
<br />
''Can you present Saturday afternoon? Yes''<br />
<br />
''Can you present Sunday morning? Yes''<br />
<br />
''Can you present Sunday afternoon? Yes''<br />
<br />
<br />
''Will you be using a CCRMA workstation computer? No''<br />
<br />
''Will you be using your own laptop? Yes''<br />
<br />
''What will your audio outputs be? None (acoustic project)''<br />
<br />
''Can your audio be played with headphones? N/A''<br />
<br />
''If not, how loud will your work be? Probably shaker sound level''<br />
<br />
''Will you need more space than a regular workstation No''<br />
<br />
''Any other needs or requests we should know about? No''<br />
<br />
''Do you have any interest in giving a short lecture or performance if there is a stage in the computer music corner? Happy to give a lecture w/ short demo at the end!'<br />
<br />
=='''Michael Berger'''==<br />
''Can you present Saturday morning? (Yes, No, I'd prefer not)''<br />
<br />
''Can you present Saturday afternoon? (Yes, No, I'd prefer not)''<br />
<br />
''Can you present Sunday morning? (Yes, No, I'd prefer not)''<br />
<br />
''Can you present Sunday afternoon? (Yes, No, I'd prefer not)''<br />
<br />
<br />
''Will you be using a CCRMA workstation computer?<br />
<br />
''Will you be using your own laptop?''<br />
<br />
''What will your audio outputs be? (Ie. 4 1/4” or stereo 1/8” or headphones etc.)''<br />
<br />
''Can your audio be played with headphones?''<br />
<br />
''If not, how loud will your work be?''<br />
<br />
''Will you need more space than a regular workstation''<br />
<br />
''Any other needs or requests we should know about?''<br />
<br />
''Do you have any interest in giving a short lecture or performance if there is a stage in the computer music corner?'<br />
<br />
<br />
<br />
<br />
=='''Nando'''==<br />
''Can you present Saturday morning? (Yes, No, I'd prefer not)''<br />
<br />
''Can you present Saturday afternoon? (Yes, No, I'd prefer not)''<br />
<br />
''Can you present Sunday morning? (Yes, No, I'd prefer not)''<br />
<br />
''Can you present Sunday afternoon? (Yes, No, I'd prefer not)''<br />
<br />
<br />
''Will you be using a CCRMA workstation computer?<br />
<br />
''Will you be using your own laptop?''<br />
<br />
''What will your audio outputs be? (Ie. 4 1/4” or stereo 1/8” or headphones etc.)''<br />
<br />
''Can your audio be played with headphones?''<br />
<br />
''If not, how loud will your work be?''<br />
<br />
''Will you need more space than a regular workstation''<br />
<br />
''Any other needs or requests we should know about?''<br />
<br />
''Do you have any interest in giving a short lecture or performance if there is a stage in the computer music corner?'<br />
<br />
<br />
<br />
<br />
=='''Carr Wilkerson'''==<br />
''Can you present Saturday morning? (Yes, No, I'd prefer not)''<br />
<br />
''Can you present Saturday afternoon? (Yes, No, I'd prefer not)''<br />
<br />
''Can you present Sunday morning? (Yes, No, I'd prefer not)''<br />
<br />
''Can you present Sunday afternoon? (Yes, No, I'd prefer not)''<br />
<br />
<br />
''Will you be using a CCRMA workstation computer?<br />
<br />
''Will you be using your own laptop?''<br />
<br />
''What will your audio outputs be? (Ie. 4 1/4” or stereo 1/8” or headphones etc.)''<br />
<br />
''Can your audio be played with headphones?''<br />
<br />
''If not, how loud will your work be?''<br />
<br />
''Will you need more space than a regular workstation''<br />
<br />
''Any other needs or requests we should know about?''<br />
<br />
''Do you have any interest in giving a short lecture or performance if there is a stage in the computer music corner?'<br />
<br />
<br />
<br />
<br />
=='''Jason Sadural'''==<br />
''Can you present Saturday morning? (Yes, No, I'd prefer not)''<br />
<br />
''Can you present Saturday afternoon? (Yes, No, I'd prefer not)''<br />
<br />
''Can you present Sunday morning? (Yes, No, I'd prefer not)''<br />
<br />
''Can you present Sunday afternoon? (Yes, No, I'd prefer not)''<br />
<br />
<br />
''Will you be using a CCRMA workstation computer?<br />
<br />
''Will you be using your own laptop?''<br />
<br />
''What will your audio outputs be? (Ie. 4 1/4” or stereo 1/8” or headphones etc.)''<br />
<br />
''Can your audio be played with headphones?''<br />
<br />
''If not, how loud will your work be?''<br />
<br />
''Will you need more space than a regular workstation''<br />
<br />
''Any other needs or requests we should know about?''<br />
<br />
''Do you have any interest in giving a short lecture or performance if there is a stage in the computer music corner?'<br />
<br />
<br />
=='''Sasha Leitman'''==<br />
''Can you present Saturday morning? (Yes, No, I'd prefer not)''<br />
<br />
''Can you present Saturday afternoon? (Yes, No, I'd prefer not)''<br />
<br />
''Can you present Sunday morning? (Yes, No, I'd prefer not)''<br />
<br />
''Can you present Sunday afternoon? (Yes, No, I'd prefer not)''<br />
<br />
<br />
''Will you be using a CCRMA workstation computer?<br />
<br />
''Will you be using your own laptop?''<br />
<br />
''What will your audio outputs be? (Ie. 4 1/4” or stereo 1/8” or headphones etc.)''<br />
<br />
''Can your audio be played with headphones?''<br />
<br />
''If not, how loud will your work be?''<br />
<br />
''Will you need more space than a regular workstation''<br />
<br />
''Any other needs or requests we should know about?''<br />
<br />
''Do you have any interest in giving a short lecture or performance if there is a stage in the computer music corner?'<br />
<br />
<br />
<br />
=='''Javier Sanchez'''==<br />
''Can you present Saturday morning? (Yes, No, I'd prefer not)'' YES<br />
<br />
''Can you present Saturday afternoon? (Yes, No, I'd prefer not)'' YES<br />
<br />
''Can you present Sunday morning? (Yes, No, I'd prefer not)'' NO<br />
<br />
''Can you present Sunday afternoon? (Yes, No, I'd prefer not)'' NO<br />
<br />
<br />
''Will you be using a CCRMA workstation computer? NO<br />
<br />
''Will you be using your own laptop?'' YES<br />
<br />
''What will your audio outputs be? (Ie. 4 1/4” or stereo 1/8” or headphones etc.)'' Headphones - Stereo 1/8''<br />
<br />
''Can your audio be played with headphones?'' YES<br />
<br />
''If not, how loud will your work be?'' <br />
<br />
''Will you need more space than a regular workstation'' NO<br />
<br />
''Any other needs or requests we should know about?'' NO<br />
<br />
''Do you have any interest in giving a short lecture or performance if there is a stage in the computer music corner?' YES !!!<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
'''Just ignore this part'''<br />
<br />
<br />
FOR PERFORMANCES:<br />
I can do short improvisations of about 3-6 minutes if requested.<br />
<br />
What is the length of your piece?<br />
3-6 minutes<br />
<br />
What will your audio outputs be? (Ie. 4 [WINDOWS-1252?]1/4” or stereo [WINDOWS-1252?]1/8” etc)<br />
my computer outputs mini-stereo<br />
<br />
Will you be projecting video?<br />
NO.<br />
<br />
FOR LECTURES:<br />
<br />
What will your audio outputs be? (Ie. 4 [WINDOWS-1252?]1/4” or stereo [WINDOWS-1252?]1/8” etc)<br />
<br />
Will you be projecting video?</div>Craffelhttps://ccrma.stanford.edu/mediawiki/index.php?title=Useful_approximations&diff=9644Useful approximations2010-03-30T23:30:48Z<p>Craffel: </p>
<hr />
<div>This is an attempt to keep track of the various numbers and approximations that are good to have in your hip-pocket when studying audio and music.<br />
<br />
== Physics ==<br />
* Sound travels roughly 1 foot every millisecond.<br />
* Typical t60 for a small, house-sized room is .5 seconds, for a larger room (eg, classroom) it's about 1 second.<br />
* A 20 Hz signal has a period of 50 milliseconds ( .05 seconds), a 20,000 Hz signal has a period of 50 microseconds ( .00005 seconds)<br />
<br />
== Perception ==<br />
* Humans can usually hear from about 20 Hz to 20,000 Hz (20 kHz)<br />
* Perception of "loudness" for different frequencies is (very) roughly flat from about 100 Hz to 10 kHz, for most decibel levels. Pitches sound much less loud outside of this range.<br />
* A quarter of a decibel change in intensity is the threshold of perception.<br />
<br />
== Digital Audio ==<br />
* About 6 dB of Signal to Noise Ratio is gained per bit when quantizing continuous values.<br />
* In order to avoid aliasing, the sampling frequency must be two times that of the highest frequency present in the signal.<br />
* 44100 Hz = .00002675737 seconds between samples, 48000 Hz = .000020833333 seconds between samples</div>Craffelhttps://ccrma.stanford.edu/mediawiki/index.php?title=220b-winter-2010&diff=9619220b-winter-20102010-03-16T23:44:19Z<p>Craffel: </p>
<hr />
<div>= 220b: Compositional Algorithms (Wiki) =<br />
<br />
== Final Project Presentations ==<br />
The 220b Final presentations will take a concert format on Thursday evening, March 18 at 7:00 PM in the CCRMA stage.<br />
<br />
Rehearsals will be held all day Wednesday and Thursday in 30 min. slots for each group or individual presenting. <br />
<br />
Additionally, at 5:00 PM on Thursday, a tech run-through will be held to set the final changes for each piece.<br />
<br />
Each group is required to sign up for a 30 min rehearsal slot as well as come to the Tech run-through to make sure all final settings are correct. If you cannot make the final Tech run through due to a final exam conflict, make sure you contact Ge and Rob before Thursday.<br />
<br />
Please sign up for a slot below:<br />
<br />
== Scheduled Final Project Dress Rehearsal Times ==<br />
* Wednesday + Thursday, March 17/18, 2009 { 12:00 - 5:00 }<br />
* Sound check will take place in <b>30 MINUTE</b> CHUNKS.<br />
* Please have your equipment in the room [[by that time]].<br />
* Please give us that the following information:<br />
<br />
* <b>N:</b> Your name<br />
* <b>D:</b> Description of the performance.<br />
* <b>E:</b> What equipment will you use? If you need us to provide it put it in <b>bold</b><br />
* <b>C:</b> Channels?<br />
<br />
Wednesday 3/17:<br />
<br />
<b>12:00-----------------------------------</b> <br />
* N: Xiang Zhang <br />
* D: Paper Generated Sound Music. Live should with MIDI kb controled SndBuf. <br />
* E: Midi Keyboad and Dynamic Microphone. Better could be provided one dynamic microphone and one DI box<br />
* C: Two channel output, one channel input (to my computer, so it's fine)<br />
<br />
<b>12:30-----------------------------------</b><br />
* N: Isaac Wang<br />
* D: Sonification of Tweets<br />
* E: laptop and projector <br />
* C: 2 channel output <br />
<br />
<br />
<b>1:00-----------------------------------</b><br />
* N: Ben Roth<br />
* D: Simon<br />
* E: My laptop and <b>your projector</b><br />
* C: A million<br />
<br />
<br />
<b>1:30-----------------------------------</b><br />
* N:<br />
* D:<br />
* E: <br />
* C: <br />
<br />
<br />
<b>2:00-----------------------------------</b><br />
* N:<br />
* D:<br />
* E: <br />
* C: <br />
<br />
<b>2:30-----------------------------------</b><br />
* N:<br />
* D:<br />
* E: <br />
* C: <br />
<br />
<b>3:00-----------------------------------</b><br />
* N:<br />
* D:<br />
* E: <br />
* C: <br />
<br />
<b>3:30-----------------------------------</b><br />
* N:<br />
* D:<br />
* E: <br />
* C: <br />
<br />
<b>4:00-----------------------------------</b><br />
* N: Linden Melvin<br />
* D: I will be using pre-recorded sounds to make a soundscape for the audience to enjoy. I will be using a Trigger Finger and on-the-fly programming in ChucK. <br />
* E: I already have the Trigger Finger and my computer so I think I am good to go.<br />
* C: Stereo<br />
<br />
<b>4:30-----------------------------------</b><br />
* N: Adam Somers<br />
* D: Laptop Performance<br />
* E: Laptop, Touchboard, Audio Interface<br />
* C: 4<br />
<br />
Thursday 3/18:<br />
<br />
<b>12:00-----------------------------------</b><br />
* N: Jacob Wittenberg<br />
* D: Man v. Machine: Jazz Piano (interpretive) with a MIDI keyboard that controls bass lines and drumbeats and other sounds. Additionally, chucK code randomly shoots out bleeps and bloops. Basically, the point is to take something relatively tonal and set it slightly offphase (you may notice slight non-syncing noises with the bass and beats, etc.). This is intentional, as it's supposed to illustrate the imperfections and differences between human and machine noises.<br />
* E: my laptop, a midi-USB controller keyboard, and a '''Grand Piano'''<br />
* C: Just 2. I just need to plug in my computer to the speakers, and I'm good to go. <br />
<br />
<b>12:30-----------------------------------</b><br />
* N:<br />
* D:<br />
* E: <br />
* C: <br />
<br />
<br />
<b>1:00-----------------------------------</b><br />
* N:<br />
* D:<br />
* E: <br />
* C: <br />
<br />
<br />
<b>1:30-----------------------------------</b><br />
* N:<br />
* D:<br />
* E: <br />
* C: <br />
<br />
<br />
<b>2:00-----------------------------------</b><br />
* N: Blair Bohannan<br />
* D: Sonified EEG<br />
* E: 2 laptops, <b>projector</b><br />
* C: 2<br />
<br />
<b>2:30-----------------------------------</b><br />
* N:<br />
* D:<br />
* E: <br />
* C: <br />
<br />
<b>3:00-----------------------------------</b><br />
* N:<br />
* D:<br />
* E: <br />
* C: <br />
<br />
<b>3:30-----------------------------------</b><br />
* N: Colin Raffel<br />
* D: Flute and computer<br />
* E: Flute, monome, ooscc, x-station, usb audio interface, <b>mic stand</b><br />
* C: NBC, ABC, CBS, Comedy Central, Nickelodeon (and stereo audio)<br />
<br />
<br />
<b>4:00-----------------------------------</b><br />
* N: Charlie Forkish + Uri Nieto<br />
* D: Song with Chuck Generated Music controlled by two voice inputs<br />
* E: We have our own audio interface and mics. In theory we just need the mixing table and the speakers<br />
* C: The more speakers the better (and the louder the better). However, we won't use more than two channels in theory.<br />
<br />
<b>4:30-----------------------------------</b><br />
* N: Adam Sheppard, Bjorn Erlach<br />
* D: We will present a performance paradox that is present in computer music.<br />
* E: Laptop, CCRMA computers, projector, sound reinforcement.<br />
* C: It is a two channel piece, but I agree with the group above, the louder the better.<br />
<br />
<br />
<br />
<br />
<br />
* see [http://ccrma.stanford.edu/courses/220b-winter-2010 course homepage]<br />
* rest is coming in winter 2010!<br />
<br />
== assignments ==<br />
* [[220b-winter-2010/hw0|homework #0: computation (an)aesthetics]]<br />
* [[220b-winter-2010/hw1|homework #1: timbre-scapes]]</div>Craffelhttps://ccrma.stanford.edu/mediawiki/index.php?title=220b-winter-2010&diff=9618220b-winter-20102010-03-16T23:43:59Z<p>Craffel: </p>
<hr />
<div>= 220b: Compositional Algorithms (Wiki) =<br />
<br />
== Final Project Presentations ==<br />
The 220b Final presentations will take a concert format on Thursday evening, March 18 at 7:00 PM in the CCRMA stage.<br />
<br />
Rehearsals will be held all day Wednesday and Thursday in 30 min. slots for each group or individual presenting. <br />
<br />
Additionally, at 5:00 PM on Thursday, a tech run-through will be held to set the final changes for each piece.<br />
<br />
Each group is required to sign up for a 30 min rehearsal slot as well as come to the Tech run-through to make sure all final settings are correct. If you cannot make the final Tech run through due to a final exam conflict, make sure you contact Ge and Rob before Thursday.<br />
<br />
Please sign up for a slot below:<br />
<br />
== Scheduled Final Project Dress Rehearsal Times ==<br />
* Wednesday + Thursday, March 17/18, 2009 { 12:00 - 5:00 }<br />
* Sound check will take place in <b>30 MINUTE</b> CHUNKS.<br />
* Please have your equipment in the room [[by that time]].<br />
* Please give us that the following information:<br />
<br />
* <b>N:</b> Your name<br />
* <b>D:</b> Description of the performance.<br />
* <b>E:</b> What equipment will you use? If you need us to provide it put it in <b>bold</b><br />
* <b>C:</b> Channels?<br />
<br />
Wednesday 3/17:<br />
<br />
<b>12:00-----------------------------------</b> <br />
* N: Xiang Zhang <br />
* D: Paper Generated Sound Music. Live should with MIDI kb controled SndBuf. <br />
* E: Midi Keyboad and Dynamic Microphone. Better could be provided one dynamic microphone and one DI box<br />
* C: Two channel output, one channel input (to my computer, so it's fine)<br />
<br />
<b>12:30-----------------------------------</b><br />
* N: Isaac Wang<br />
* D: Sonification of Tweets<br />
* E: laptop and projector <br />
* C: 2 channel output <br />
<br />
<br />
<b>1:00-----------------------------------</b><br />
* N: Ben Roth<br />
* D: Simon<br />
* E: My laptop and <b>your projector</b><br />
* C: A million<br />
<br />
<br />
<b>1:30-----------------------------------</b><br />
* N:<br />
* D:<br />
* E: <br />
* C: <br />
<br />
<br />
<b>2:00-----------------------------------</b><br />
* N:<br />
* D:<br />
* E: <br />
* C: <br />
<br />
<b>2:30-----------------------------------</b><br />
* N:<br />
* D:<br />
* E: <br />
* C: <br />
<br />
<b>3:00-----------------------------------</b><br />
* N:<br />
* D:<br />
* E: <br />
* C: <br />
<br />
<b>3:30-----------------------------------</b><br />
* N:<br />
* D:<br />
* E: <br />
* C: <br />
<br />
<b>4:00-----------------------------------</b><br />
* N: Linden Melvin<br />
* D: I will be using pre-recorded sounds to make a soundscape for the audience to enjoy. I will be using a Trigger Finger and on-the-fly programming in ChucK. <br />
* E: I already have the Trigger Finger and my computer so I think I am good to go.<br />
* C: Stereo<br />
<br />
<b>4:30-----------------------------------</b><br />
* N: Adam Somers<br />
* D: Laptop Performance<br />
* E: Laptop, Touchboard, Audio Interface<br />
* C: 4<br />
<br />
Thursday 3/18:<br />
<br />
<b>12:00-----------------------------------</b><br />
* N: Jacob Wittenberg<br />
* D: Man v. Machine: Jazz Piano (interpretive) with a MIDI keyboard that controls bass lines and drumbeats and other sounds. Additionally, chucK code randomly shoots out bleeps and bloops. Basically, the point is to take something relatively tonal and set it slightly offphase (you may notice slight non-syncing noises with the bass and beats, etc.). This is intentional, as it's supposed to illustrate the imperfections and differences between human and machine noises.<br />
* E: my laptop, a midi-USB controller keyboard, and a '''Grand Piano'''<br />
* C: Just 2. I just need to plug in my computer to the speakers, and I'm good to go. <br />
<br />
<b>12:30-----------------------------------</b><br />
* N:<br />
* D:<br />
* E: <br />
* C: <br />
<br />
<br />
<b>1:00-----------------------------------</b><br />
* N:<br />
* D:<br />
* E: <br />
* C: <br />
<br />
<br />
<b>1:30-----------------------------------</b><br />
* N:<br />
* D:<br />
* E: <br />
* C: <br />
<br />
<br />
<b>2:00-----------------------------------</b><br />
* N: Blair Bohannan<br />
* D: Sonified EEG<br />
* E: 2 laptops, <b>projector</b><br />
* C: 2<br />
<br />
<b>2:30-----------------------------------</b><br />
* N:<br />
* D:<br />
* E: <br />
* C: <br />
<br />
<b>3:00-----------------------------------</b><br />
* N:<br />
* D:<br />
* E: <br />
* C: <br />
<br />
<b>3:30-----------------------------------</b><br />
* N: Colin Raffel<br />
* D: Flute and computer<br />
* E: Flute, monome, ooscc, x-station, usb audio interface, [b]mic stand[/b]<br />
* C: NBC, ABC, CBS, Comedy Central, Nickelodeon (and stereo audio)<br />
<br />
<br />
<b>4:00-----------------------------------</b><br />
* N: Charlie Forkish + Uri Nieto<br />
* D: Song with Chuck Generated Music controlled by two voice inputs<br />
* E: We have our own audio interface and mics. In theory we just need the mixing table and the speakers<br />
* C: The more speakers the better (and the louder the better). However, we won't use more than two channels in theory.<br />
<br />
<b>4:30-----------------------------------</b><br />
* N: Adam Sheppard, Bjorn Erlach<br />
* D: We will present a performance paradox that is present in computer music.<br />
* E: Laptop, CCRMA computers, projector, sound reinforcement.<br />
* C: It is a two channel piece, but I agree with the group above, the louder the better.<br />
<br />
<br />
<br />
<br />
<br />
* see [http://ccrma.stanford.edu/courses/220b-winter-2010 course homepage]<br />
* rest is coming in winter 2010!<br />
<br />
== assignments ==<br />
* [[220b-winter-2010/hw0|homework #0: computation (an)aesthetics]]<br />
* [[220b-winter-2010/hw1|homework #1: timbre-scapes]]</div>Craffelhttps://ccrma.stanford.edu/mediawiki/index.php?title=220b-winter-2010&diff=9616220b-winter-20102010-03-16T05:10:26Z<p>Craffel: </p>
<hr />
<div>= 220b: Compositional Algorithms (Wiki) =<br />
<br />
== Final Project Presentations ==<br />
The 220b Final presentations will take a concert format on Thursday evening, March 18 at 7:00 PM in the CCRMA stage.<br />
<br />
Rehearsals will be held all day Wednesday and Thursday in 30 min. slots for each group or individual presenting. <br />
<br />
Additionally, at 5:00 PM on Thursday, a tech run-through will be held to set the final changes for each piece.<br />
<br />
Each group is required to sign up for a 30 min rehearsal slot as well as come to the Tech run-through to make sure all final settings are correct. If you cannot make the final Tech run through due to a final exam conflict, make sure you contact Ge and Rob before Thursday.<br />
<br />
Please sign up for a slot below:<br />
<br />
== Scheduled Final Project Dress Rehearsal Times ==<br />
* Wednesday + Thursday, March 17/18, 2009 { 12:00 - 5:00 }<br />
* Sound check will take place in <b>30 MINUTE</b> CHUNKS.<br />
* Please have your equipment in the room [[by that time]].<br />
* Please give us that the following information:<br />
<br />
* <b>N:</b> Your name<br />
* <b>D:</b> Description of the performance.<br />
* <b>E:</b> What equipment will you use? If you need us to provide it put it in <b>bold</b><br />
* <b>C:</b> Channels?<br />
<br />
Wednesday 3/17:<br />
<br />
<b>12:00-----------------------------------</b> <br />
* N: Xiang Zhang <br />
* D: Paper Generated Sound Music. Live should with MIDI kb controled SndBuf. <br />
* E: Midi Keyboad and Dynamic Microphone. Better could be provided one dynamic microphone and one DI box<br />
* C: Two channel output, one channel input (to my computer, so it's fine)<br />
<br />
<b>12:30-----------------------------------</b><br />
* N: Isaac Wang<br />
* D: Sonification of Tweets<br />
* E: laptop and projector <br />
* C: 2 channel output <br />
<br />
<br />
<b>1:00-----------------------------------</b><br />
* N: Ben Roth<br />
* D: The computer and I will improvise a song together by playing a game similar to Simon.<br />
* E: My laptop and <b>your projector</b><br />
* C: A million<br />
<br />
<br />
<b>1:30-----------------------------------</b><br />
* N:<br />
* D:<br />
* E: <br />
* C: <br />
<br />
<br />
<b>2:00-----------------------------------</b><br />
* N:<br />
* D:<br />
* E: <br />
* C: <br />
<br />
<b>2:30-----------------------------------</b><br />
* N:<br />
* D:<br />
* E: <br />
* C: <br />
<br />
<b>3:00-----------------------------------</b><br />
* N: Colin Raffel<br />
* D: Flute and computer<br />
* E: Flute, monome, ooscc, x-station, usb audio interface, [b]mic stand[/b]<br />
* C: NBC, ABC, CBS, Comedy Central, Nickelodeon (and stereo audio)<br />
<br />
<b>3:30-----------------------------------</b><br />
* N:<br />
* D:<br />
* E: <br />
* C: <br />
<br />
<b>4:00-----------------------------------</b><br />
* N: Linden Melvin<br />
* D: I will be using pre-recorded sounds to make a soundscape for the audience to enjoy. I will be using a Trigger Finger and on-the-fly programming in ChucK. <br />
* E: I already have the Trigger Finger and my computer so I think I am good to go.<br />
* C: Stereo<br />
<br />
<b>4:30-----------------------------------</b><br />
* N: Adam Somers<br />
* D: Laptop Performance<br />
* E: Laptop, Touchboard, Audio Interface<br />
* C: 4<br />
<br />
Thursday 3/18:<br />
<br />
<b>12:00-----------------------------------</b><br />
* N: Jacob Wittenberg<br />
* D: Man v. Machine: Jazz Piano (interpretive) with a MIDI keyboard that controls bass lines and drumbeats and other sounds. Additionally, chucK code randomly shoots out bleeps and bloops. Basically, the point is to take something relatively tonal and set it slightly offphase (you may notice slight non-syncing noises with the bass and beats, etc.). This is intentional, as it's supposed to illustrate the imperfections and differences between human and machine noises.<br />
* E: my laptop, a midi-USB controller keyboard, and a '''Grand Piano'''<br />
* C: Just 2. I just need to plug in my computer to the speakers, and I'm good to go. <br />
<br />
<b>12:30-----------------------------------</b><br />
* N:<br />
* D:<br />
* E: <br />
* C: <br />
<br />
<br />
<b>1:00-----------------------------------</b><br />
* N:<br />
* D:<br />
* E: <br />
* C: <br />
<br />
<br />
<b>1:30-----------------------------------</b><br />
* N:<br />
* D:<br />
* E: <br />
* C: <br />
<br />
<br />
<b>2:00-----------------------------------</b><br />
* N: Blair Bohannan<br />
* D: Sonified EEG<br />
* E: 2 laptops, <b>projector</b><br />
* C: 2<br />
<br />
<b>2:30-----------------------------------</b><br />
* N:<br />
* D:<br />
* E: <br />
* C: <br />
<br />
<b>3:00-----------------------------------</b><br />
* N:<br />
* D:<br />
* E: <br />
* C: <br />
<br />
<b>3:30-----------------------------------</b><br />
* N:<br />
* D:<br />
* E: <br />
* C: <br />
<br />
<b>4:00-----------------------------------</b><br />
* N: Charlie Forkish + Uri Nieto<br />
* D: Song with Chuck Generated Music controlled by two voice inputs<br />
* E: We have our own audio interface and mics. In theory we just need the mixing table and the speakers<br />
* C: The more speakers the better (and the louder the better). However, we won't use more than two channels in theory.<br />
<br />
<b>4:30-----------------------------------</b><br />
* N: Adam Sheppard, Bjorn Erlach<br />
* D: We will present a performance paradox that is present in computer music.<br />
* E: Laptop, CCRMA computers, projector, sound reinforcement.<br />
* C: It is a two channel piece, but I agree with the group above, the louder the better.<br />
<br />
<br />
<br />
<br />
<br />
* see [http://ccrma.stanford.edu/courses/220b-winter-2010 course homepage]<br />
* rest is coming in winter 2010!<br />
<br />
== assignments ==<br />
* [[220b-winter-2010/hw0|homework #0: computation (an)aesthetics]]<br />
* [[220b-winter-2010/hw1|homework #1: timbre-scapes]]</div>Craffelhttps://ccrma.stanford.edu/mediawiki/index.php?title=Useful_approximations&diff=9555Useful approximations2010-02-03T00:41:37Z<p>Craffel: </p>
<hr />
<div>This is an attempt to keep track of the various numbers and approximations that are good to have in your hip-pocket when studying audio and music.<br />
<br />
== Physics ==<br />
* Sound travels roughly 1 foot every millisecond.<br />
* Typical t60 for a small, house-sized room is .5 seconds, for a larger room (eg, classroom) it's about 1 second.<br />
* A 20 Hz signal has a period of 50 milliseconds ( .05 seconds), a 20,000 Hz signal has a period of 50 microseconds ( .00005 seconds)<br />
<br />
== Perception ==<br />
* Humans can usually hear from about 20 Hz to 20,000 Hz (20 kHz)<br />
* Perception of "loudness" for different frequencies is (very) roughly flat from about 100 Hz to 10 kHz, for most decibel levels. Pitches sound much less loud outside of this range.<br />
<br />
== Digital Audio ==<br />
* About 6 dB of Signal to Noise Ratio is gained per bit when quantizing continuous values.<br />
* In order to avoid aliasing, the sampling frequency must be two times that of the highest frequency present in the signal.<br />
* 44100 Hz = .00002675737 seconds between samples, 48000 Hz = .000020833333 seconds between samples</div>Craffelhttps://ccrma.stanford.edu/mediawiki/index.php?title=Useful_approximations&diff=9554Useful approximations2010-02-03T00:41:09Z<p>Craffel: </p>
<hr />
<div>This is an attempt to keep track of the various numbers and approximations that are good to have in your hip-pocket when studying audio and music.<br />
<br />
== Physics ==<br />
* Sound travels roughly 1 foot every millisecond.<br />
* Typical t60 for a small, house-sized room is .5 seconds, for a larger room (eg, classroom) it's about 1 second.<br />
* A 20 Hz signal has a period of 50 milliseconds ( .05 seconds), a 20,000 Hz signal has a period of 50 microseconds ( .00005 seconds)<br />
<br />
== Perception ==<br />
* Humans can usually hear from about 20 Hz to 20,000 Hz (20 kHz)<br />
* Perception of "loudness" for different frequencies is (very) roughly flat from about 100 Hz to 10 kHz, for most decibel levels. Pitches sound much less loud outside of this range.<br />
<br />
== Digital Audio ==<br />
* About 6 dB of Signal to Noise Ratio is gained per bit when quantizing continuous values.<br />
* In order to avoid aliasing, the sampling frequency must be two times that of the highest frequency present in the signal.<br />
* 44100 Hz = .00002675737 seconds between samples, 48000 Hz = .000020833333 seconds per sample</div>Craffelhttps://ccrma.stanford.edu/mediawiki/index.php?title=Useful_approximations&diff=9553Useful approximations2010-02-03T00:36:38Z<p>Craffel: </p>
<hr />
<div>This is an attempt to keep track of the various numbers and approximations that are good to have in your hip-pocket when studying audio and music.<br />
<br />
== Physics ==<br />
* Sound travels roughly 1 foot every millisecond.<br />
* Typical t60 for a small, house-sized room is .5 seconds, for a larger room (eg, classroom) it's about 1 second.<br />
<br />
== Perception ==<br />
* Humans can usually hear from about 20 Hz to 20,000 Hz (20 kHz)<br />
* Perception of "loudness" for different frequencies is (very) roughly flat from about 100 Hz to 10 kHz, for most decibel levels. Pitches sound much less loud outside of this range.<br />
<br />
== Digital Audio ==<br />
* About 6 dB of Signal to Noise Ratio is gained per bit when quantizing continuous values.<br />
* In order to avoid aliasing, the sampling frequency must be two times that of the highest frequency present in the signal.</div>Craffelhttps://ccrma.stanford.edu/mediawiki/index.php?title=Useful_approximations&diff=9552Useful approximations2010-02-03T00:36:09Z<p>Craffel: Created page with 'This is an attempt to keep track of the various numbers and approximations that are good to have in your hip-pocket when studying audio and music. == Physics == * Sound travels …'</p>
<hr />
<div>This is an attempt to keep track of the various numbers and approximations that are good to have in your hip-pocket when studying audio and music.<br />
<br />
== Physics ==<br />
* Sound travels roughly 1 foot every millisecond<br />
<br />
== Perception ==<br />
* Humans can usually hear from about 20 Hz to 20,000 Hz (20 kHz)<br />
* Perception of "loudness" for different frequencies is (very) roughly flat from about 100 Hz to 10 kHz, for most decibel levels. Pitches sound much less loud outside of this range.<br />
<br />
== Digital Audio ==<br />
* About 6 dB of Signal to Noise Ratio is gained per bit when quantizing continuous values.<br />
* In order to avoid aliasing, the sampling frequency must be two times that of the highest frequency present in the signal.</div>Craffelhttps://ccrma.stanford.edu/mediawiki/index.php?title=Listening_Room_ChucK_tutorial&diff=9363Listening Room ChucK tutorial2009-12-04T20:22:26Z<p>Craffel: </p>
<hr />
<div>''Note - this tutorial doesn't use Jack, and there could be a cleaner way to do this with fewer steps, but it works and is fairly easy to do''<br />
<br />
0) Log in to the linux box which is NOT the openmixer box (there should be two monitor/keyboard/mouse combos you can use to do this, one in the middle of the room and one in the corner). You can tell that it's not the openmixer computer because there is no sticker on the monitor which says "OPENMIXER WORKSTATION: DO NOT LOGIN!" on it.<br />
<br />
1) Download the MiniAudicle for Linux [http://audicle.cs.princeton.edu/mini/linux/ here].<br />
<br />
2) Unzip the archive, cd to the unzipped directory in Terminal, and type make linux-alsa<br />
<br />
3) Now go into the unzipped directory, and you'll find the MiniAudicle app inside of the wxw folder. Open it.<br />
<br />
4) Open HDSPMixer - click on "Applications" at the top left, then go to "Sound and Video", then find and click on HDSPMixer.<br />
<br />
5) Run this example code: (copy and paste it, hit "add shred")<br />
<br />
ModalBar sin;<br />
<br />
8 => sin.preset;<br />
<br />
Gain g[16];<br />
<br />
.1 => float delay;<br />
<br />
for (0 => int i; i < 16; i++)<br />
{<br />
sin => g[i];<br />
0 => g[i].gain;<br />
g[i] => dac.chan(i);<br />
}<br />
<br />
while(true)<br />
{<br />
for (0 => int i; i < 16; i++)<br />
{<br />
Std.mtof(60+2*i) => sin.freq;<br />
sin.noteOn(1);<br />
.8=> g[i].gain;<br />
if(i == 0) { 0 => g[15].gain; }<br />
else { 0 => g[i-1].gain; }<br />
delay::second => now;<br />
0 => g[i].gain;<br />
delay::second => now;<br />
sin.noteOff(0);<br />
}<br />
}<br />
<br />
6) Now in HDSPMixer, you should see the level meters registering a signal. It should look like this: (if it doesn't, get help!)<br />
<br />
[[File:hdsptest.png]]<br />
<br />
7) On the fader box, hit "Linux" then "Preset". The fader box is the one that looks like this:<br />
<br />
[[File:BCF2000_top.jpg]]<br />
<br />
You should hear sound now, with notes cascading around the room. If you don't, try restarting the openmixer box: it's the bigger computer which is connected to the monitor which says "OPENMIXER WORKSTATION: DO NOT LOGIN!". Find the computer and press "reset" on the front panel. If you still don't get sound. hit "Zero" then "Linux" on the fader box, then turn up the leftmost fader. Now, on the knob box, turn up the third knob down in the leftmost column (if you think of the knob box as a 8x4 matrix, this is in location 3, 1). You should be hearing sound now out of one of the speakers. If you aren't, something is awry, and find help!<br />
<br />
8) If you are experiencing popping and clicking, try entering cpufreq-selector -g performance into a terminal window. (Thanks Jason Sadural for this)<br />
<br />
9) If you notice that channels are "pairing", that is, if you change the pan value on one channel and it changes the pan value on another channel too, try resetting the openmixer computer. (Thanks Jason for this too)<br />
<br />
10) Rule of thumb: When in doubt, try restarting the openmixer computer first. Then, seek help!</div>Craffelhttps://ccrma.stanford.edu/mediawiki/index.php?title=Listening_Room_ChucK_tutorial&diff=9362Listening Room ChucK tutorial2009-12-04T20:21:55Z<p>Craffel: </p>
<hr />
<div>''Note - this tutorial doesn't use Jack, and there could be a cleaner way to do this with fewer steps, but it works and is fairly easy to do''<br />
<br />
0) Log in to the linux box which is NOT the openmixer box (there should be two monitor/keyboard/mouse combos you can use to do this, one in the middle of the room and one in the corner). You can tell that it's not the openmixer computer because there is no sticker on the monitor which says "OPENMIXER WORKSTATION: DO NOT LOGIN!" on it.<br />
<br />
1) Download the MiniAudicle for Linux [http://audicle.cs.princeton.edu/mini/linux/ here].<br />
<br />
2) Unzip the archive, cd to the unzipped directory in Terminal, and type make linux-alsa<br />
<br />
3) Now go into the unzipped directory, and you'll find the MiniAudicle app inside of the wxw folder. Open it.<br />
<br />
4) Open HDSPMixer - click on "Applications" at the top left, then go to "Sound and Video", then find and click on HDSPMixer.<br />
<br />
5) Run this example code: (copy and paste it, hit "add shred")<br />
<br />
ModalBar sin;<br />
<br />
8 => sin.preset;<br />
<br />
Gain g[16];<br />
<br />
.1 => float delay;<br />
<br />
for (0 => int i; i < 16; i++)<br />
{<br />
sin => g[i];<br />
0 => g[i].gain;<br />
g[i] => dac.chan(i);<br />
}<br />
<br />
while(true)<br />
{<br />
for (0 => int i; i < 16; i++)<br />
{<br />
Std.mtof(60+2*i) => sin.freq;<br />
sin.noteOn(1);<br />
.8=> g[i].gain;<br />
if(i == 0) { 0 => g[15].gain; }<br />
else { 0 => g[i-1].gain; }<br />
delay::second => now;<br />
0 => g[i].gain;<br />
delay::second => now;<br />
sin.noteOff(0);<br />
}<br />
}<br />
<br />
6) Now in HDSPMixer, you should see the level meters registering a signal. It should look like this: (if it doesn't, get help!)<br />
<br />
[[File:hdsptest.png]]<br />
<br />
7) On the fader box, hit "Linux" then "Preset". The fader box is the one that looks like this:<br />
<br />
[[File:BCF2000-top.jpg]]<br />
<br />
You should hear sound now, with notes cascading around the room. If you don't, try restarting the openmixer box: it's the bigger computer which is connected to the monitor which says "OPENMIXER WORKSTATION: DO NOT LOGIN!". Find the computer and press "reset" on the front panel. If you still don't get sound. hit "Zero" then "Linux" on the fader box, then turn up the leftmost fader. Now, on the knob box, turn up the third knob down in the leftmost column (if you think of the knob box as a 8x4 matrix, this is in location 3, 1). You should be hearing sound now out of one of the speakers. If you aren't, something is awry, and find help!<br />
<br />
8) If you are experiencing popping and clicking, try entering cpufreq-selector -g performance into a terminal window. (Thanks Jason Sadural for this)<br />
<br />
9) If you notice that channels are "pairing", that is, if you change the pan value on one channel and it changes the pan value on another channel too, try resetting the openmixer computer. (Thanks Jason for this too)<br />
<br />
10) Rule of thumb: When in doubt, try restarting the openmixer computer first. Then, seek help!</div>Craffelhttps://ccrma.stanford.edu/mediawiki/index.php?title=File:BCF2000_top.jpg&diff=9361File:BCF2000 top.jpg2009-12-04T20:21:35Z<p>Craffel: Behringer BCF2000 fader box</p>
<hr />
<div>Behringer BCF2000 fader box</div>Craffelhttps://ccrma.stanford.edu/mediawiki/index.php?title=Listening_Room_ChucK_tutorial&diff=9360Listening Room ChucK tutorial2009-12-03T22:56:15Z<p>Craffel: </p>
<hr />
<div>''Note - this tutorial doesn't use Jack, and there could be a cleaner way to do this with fewer steps, but it works and is fairly easy to do''<br />
<br />
0) Log in to the linux box which is NOT the openmixer box (there should be two monitor/keyboard/mouse combos you can use to do this, one in the middle of the room and one in the corner). You can tell that it's not the openmixer computer because there is no sticker on the monitor which says "OPENMIXER WORKSTATION: DO NOT LOGIN!" on it.<br />
<br />
1) Download the MiniAudicle for Linux [http://audicle.cs.princeton.edu/mini/linux/ here].<br />
<br />
2) Unzip the archive, cd to the unzipped directory in Terminal, and type make linux-alsa<br />
<br />
3) Now go into the unzipped directory, and you'll find the MiniAudicle app inside of the wxw folder. Open it.<br />
<br />
4) Open HDSPMixer - click on "Applications" at the top left, then go to "Sound and Video", then find and click on HDSPMixer.<br />
<br />
5) Run this example code: (copy and paste it, hit "add shred")<br />
<br />
ModalBar sin;<br />
<br />
8 => sin.preset;<br />
<br />
Gain g[16];<br />
<br />
.1 => float delay;<br />
<br />
for (0 => int i; i < 16; i++)<br />
{<br />
sin => g[i];<br />
0 => g[i].gain;<br />
g[i] => dac.chan(i);<br />
}<br />
<br />
while(true)<br />
{<br />
for (0 => int i; i < 16; i++)<br />
{<br />
Std.mtof(60+2*i) => sin.freq;<br />
sin.noteOn(1);<br />
.8=> g[i].gain;<br />
if(i == 0) { 0 => g[15].gain; }<br />
else { 0 => g[i-1].gain; }<br />
delay::second => now;<br />
0 => g[i].gain;<br />
delay::second => now;<br />
sin.noteOff(0);<br />
}<br />
}<br />
<br />
6) Now in HDSPMixer, you should see the level meters registering a signal. It should look like this: (if it doesn't, get help!)<br />
<br />
[[File:hdsptest.png]]<br />
<br />
7) On the fader box, hit "Preset". You should hear sound now, with notes cascading around the room. If you don't, try restarting the openmixer box: it's the bigger computer which is connected to the monitor which says "OPENMIXER WORKSTATION: DO NOT LOGIN!". Find the computer and press "reset" on the front panel. If you still don't get sound. hit "Zero" then "Linux" on the fader box, then turn up the leftmost fader. Now, on the knob box, turn up the third knob down in the leftmost column (if you think of the knob box as a 8x4 matrix, this is in location 3, 1). You should be hearing sound now out of one of the speakers. If you aren't, something is awry, and find help!<br />
<br />
8) If you are experiencing popping and clicking, try entering cpufreq-selector -g performance into a terminal window. (Thanks Jason Sadural for this)<br />
<br />
9) If you notice that channels are "pairing", that is, if you change the pan value on one channel and it changes the pan value on another channel too, try resetting the openmixer computer. (Thanks Jason for this too)<br />
<br />
10) Rule of thumb: When in doubt, try restarting the openmixer computer first. Then, seek help!</div>Craffelhttps://ccrma.stanford.edu/mediawiki/index.php?title=Listening_Room_Specs&diff=9359Listening Room Specs2009-12-03T22:54:25Z<p>Craffel: </p>
<hr />
<div>== Welcome to the Pit Page ==<br />
written by Jason Sadural (jsadural@ccrma.stanford.edu)<br />
comments and suggestions always welcomed<br />
<br />
This page discusses the room dimensions as well as the the process of calibrating the spherical VBAP configuration. It will also discuss the equipment and software used to operate sound as well as how to configure and save settings for your personal needs. If you move any speaker in the room you will be personally responsible to recalculate and recalibrate speaker configuration (in other words "DON"T DO IT!!!").In the future we hope to update this page with a new wave field synthesis installation. In 2008 we will be implementing a new system formally titled Openmixer.<br />
<br />
For a "complete idiot's guide" to getting sound out of the listening room using ChucK/miniaudicle: [[Listening Room ChucK tutorial]]<br />
<br />
<br />
<br />
# Room Dimensions<br />
#* 277inches x 292 inches x 86 inches(height)<br />
# There exists a heptagon in the center with 3 steps downwards to a cage in the middle<br />
#* Height of each step = 5.5 inches<br />
#* Length of step = 11.75 inches<br />
#* Length of side of Heptagon at top = 84 inches (same as top)<br />
#* Depth of indentation in ceiling = 15 inches<br />
#* Length of side of Heptagon at cage(bottom) = 63 inches<br />
#* Depth to bottom of cage = 41 inches<br />
#* Closest point of Heptagon to wall = 51 inches<br />
# Equipment and software<br />
#* Samsung 17 inch monitor<br />
#* Linux box<br />
#* RME Hammerfall DSP Digiface<br />
#* Tascam TDIF-1/ADAT interface format converter<br />
#* Tascam DM-3200<br />
#* 5.1 DVD player<br />
#* 8 Mackie HR824<br />
#* 8 Mackie HR624<br />
#* AKG C-414 Mic/Stand/adapter<br />
#* ALSA HDSP<br />
#* Jack <br />
# Before beginning, create your own project by clicking "alt-Project" and cursor down to "store as." Name your project using the Dial and the enter key. After doing so, follow instructions and store at the end of calibration. Please use current calculations of speaker configuration instead of repositioning speakers. <br />
# Current speaker configuration<br />
#* speakers 1 is on channel 1 assigned to output 7, speaker congiguration is coutner-clockwise starting at 0 degrees<br />
#* speakers are in octagonal setup with speakers 92 inches apart<br />
#* Distance to sweetspot from each horizontal speaker is 120.205 inches<br />
#* Verticle speakers distance will be termed in counterclockwise order PhiU1(upper1 azimuth), ThetaU1(upper1 angle), ru1(upper1 distance) and so on(all in degrees). <br />
#* Speaker 1 horizontal = 120.205 <br />
#* ThetaU1 = 46.123 ; PhiU1 = 34.582; rU1 = 88.8147<br />
#* ThetaU2 = 134.578; PhiU2 = 35.213; rU2 = 87.2017<br />
#* ThetaU3 = 225.119; PhiU3 = 29.898; rU3 = 90.2783<br />
#* ThetaU4 = 328.552; PhiU4 = 31.448; rU4 = 91.3406<br />
#* ThetaD1 = 46.429 ; PhiD1 = -61.214; rD1 = 95.1767<br />
#* ThetaD2 = 135.557; PhiD2 = -60.980; rD2 = 95.6595<br />
#* ThetaD3 = 235.089; PhiD3 = -43.200; rD3 = 89.9286 (Possible Error)<br />
#* ThetaD4 = 317.181; PhiD4 = -55.781; rD4 = 98.3265<br />
# Speaker Positioning : In calibration of the speakers, I used a T-square, laser Line tool, Wire, tape measure, and Protractor. I made sure that the sweet spot would be intuitive upon placing the seat into the center of the Pit.<br />
#* Use obvious methods to align horizontal speakers in an octagon at a arbitrary distance measured from the center of cage. <br />
#* Measure 3 distances from each verticle(above/below) speaker to 3 different horizontal speakers <br />
#* Use [http://en.wikipedia.org/wiki/Trilateration trilateral] calculation to solve xyz position in space<br />
#* Use octagon properties to perform coordinate transformation in order to find position from sweet spot(center of octagon)<br />
#* PD patch in which calculates intersecting spheres located through ccrma-gate at /jsadura/trilateration <br />
# Speaker Calibration<br />
#* settings: Acoustic Space "B"half; Low Freq 37Hz; High Freq 0Hz; Power Mode ON<br />
#* Make sure all bus and gain settings are equal on mixer<br />
#* Adjust gain on speaker and use Pink noise to calibrate equal SPL levels at the sweet spot one at a time<br />
# Time Delay<br />
#* Calculate distance to verticle speakers (R) from trilateration page and find the difference in distance to horizontal speakers<br />
#* At a 44.1kHz sample rate, divide distance in inches by 0.3 to calculate samples of delay<br />
#* on Tascam DM-3200 mixer select "Module" on top right and move cursor down to Delay <br />
#* Hold [http://en.wiktionary.org/wiki/shift#Verb shiFt] while turning third knob for smaller increments of delay in samples.<br />
<br />
== Photo of the Listening Room: without speakers ==<br />
<br />
[[Image:Listeningroom.jpg]]<br />
<br />
<br />
[[Category:CCRMA User Guide]]</div>Craffelhttps://ccrma.stanford.edu/mediawiki/index.php?title=Listening_Room_ChucK_tutorial&diff=9358Listening Room ChucK tutorial2009-12-03T22:52:16Z<p>Craffel: </p>
<hr />
<div>''Note - this tutorial doesn't use Jack, and there could be a cleaner way to do this with fewer steps, but it works and is fairly easy to do''<br />
<br />
1) Download the MiniAudicle for Linux [http://audicle.cs.princeton.edu/mini/linux/ here].<br />
<br />
2) Unzip the archive, cd to the unzipped directory in Terminal, and type make linux-alsa<br />
<br />
3) Now go into the unzipped directory, and you'll find the MiniAudicle app inside of the wxw folder. Open it.<br />
<br />
4) Open HDSPMixer - click on "Applications" at the top left, then go to "Sound and Video", then find and click on HDSPMixer.<br />
<br />
5) Run this example code: (copy and paste it, hit "add shred")<br />
<br />
ModalBar sin;<br />
<br />
8 => sin.preset;<br />
<br />
Gain g[16];<br />
<br />
.1 => float delay;<br />
<br />
for (0 => int i; i < 16; i++)<br />
{<br />
sin => g[i];<br />
0 => g[i].gain;<br />
g[i] => dac.chan(i);<br />
}<br />
<br />
while(true)<br />
{<br />
for (0 => int i; i < 16; i++)<br />
{<br />
Std.mtof(60+2*i) => sin.freq;<br />
sin.noteOn(1);<br />
.8=> g[i].gain;<br />
if(i == 0) { 0 => g[15].gain; }<br />
else { 0 => g[i-1].gain; }<br />
delay::second => now;<br />
0 => g[i].gain;<br />
delay::second => now;<br />
sin.noteOff(0);<br />
}<br />
}<br />
<br />
6) Now in HDSPMixer, you should see the level meters registering a signal. It should look like this: (if it doesn't, get help!)<br />
<br />
[[File:hdsptest.png]]<br />
<br />
7) On the fader box, hit "Preset". You should hear sound now, with notes cascading around the room. If you don't, try restarting the openmixer box: it's the bigger computer which is connected to the monitor which says "OPENMIXER WORKSTATION: DO NOT LOGIN!". Find the computer and press "reset" on the front panel. If you still don't get sound. hit "Zero" then "Linux" on the fader box, then turn up the leftmost fader. Now, on the knob box, turn up the third knob down in the leftmost column (if you think of the knob box as a 8x4 matrix, this is in location 3, 1). You should be hearing sound now out of one of the speakers. If you aren't, something is awry, and find help!<br />
<br />
8) If you are experiencing popping and clicking, try entering cpufreq-selector -g performance into a terminal window. (Thanks Jason Sadural for this)<br />
<br />
9) If you notice that channels are "pairing", that is, if you change the pan value on one channel and it changes the pan value on another channel too, try resetting the openmixer computer. (Thanks Jason for this too)<br />
<br />
10) Rule of thumb: When in doubt, try restarting the openmixer computer first. Then, seek help!</div>Craffelhttps://ccrma.stanford.edu/mediawiki/index.php?title=Listening_Room_ChucK_tutorial&diff=9357Listening Room ChucK tutorial2009-12-03T22:51:38Z<p>Craffel: </p>
<hr />
<div>''Note - this tutorial doesn't use Jack, and there could be a cleaner way to do this with fewer steps, but it works and is fairly easy to do''<br />
<br />
1) Download the MiniAudicle for Linux [http://audicle.cs.princeton.edu/mini/linux/ here].<br />
<br />
2) Unzip the archive, cd to the unzipped directory in Terminal, and type make linux-alsa<br />
<br />
3) Now go into the unzipped directory, and you'll find the MiniAudicle app inside of the wxw folder. Open it.<br />
<br />
4) Open HDSPMixer - click on "Applications" at the top left, then go to "Sound and Video", then find and click on HDSPMixer.<br />
<br />
5) Run this example code: (copy and paste it, hit "add shred")<br />
<br />
ModalBar sin;<br />
<br />
8 => sin.preset;<br />
<br />
Gain g[16];<br />
<br />
.1 => float delay;<br />
<br />
for (0 => int i; i < 16; i++)<br />
{<br />
sin => g[i];<br />
0 => g[i].gain;<br />
g[i] => dac.chan(i);<br />
}<br />
<br />
while(true)<br />
{<br />
for (0 => int i; i < 16; i++)<br />
{<br />
Std.mtof(60+2*i) => sin.freq;<br />
sin.noteOn(1);<br />
.8=> g[i].gain;<br />
if(i == 0) { 0 => g[15].gain; }<br />
else { 0 => g[i-1].gain; }<br />
delay::second => now;<br />
0 => g[i].gain;<br />
delay::second => now;<br />
sin.noteOff(0);<br />
}<br />
}<br />
<br />
6) Now in HDSPMixer, you should see the level meters registering a signal. It should look like this:<br />
<br />
[[File:hdsptest.png]]<br />
<br />
7) On the fader box, hit "Preset". You should hear sound now, with notes cascading around the room. If you don't, try restarting the openmixer box: it's the bigger computer which is connected to the monitor which says "OPENMIXER WORKSTATION: DO NOT LOGIN!". Find the computer and press "reset" on the front panel. If you still don't get sound. hit "Zero" then "Linux" on the fader box, then turn up the leftmost fader. Now, on the knob box, turn up the third knob down in the leftmost column (if you think of the knob box as a 8x4 matrix, this is in location 3, 1). You should be hearing sound now out of one of the speakers. If you aren't, something is awry, and find help!<br />
<br />
8) If you are experiencing popping and clicking, try entering cpufreq-selector -g performance into a terminal window. (Thanks Jason Sadural for this)<br />
<br />
9) If you notice that channels are "pairing", that is, if you change the pan value on one channel and it changes the pan value on another channel too, try resetting the openmixer computer. (Thanks Jason for this too)<br />
<br />
10) Rule of thumb: When in doubt, try restarting the openmixer computer first. Then, seek help!</div>Craffelhttps://ccrma.stanford.edu/mediawiki/index.php?title=File:Hdsptest.png&diff=9356File:Hdsptest.png2009-12-03T22:50:49Z<p>Craffel: What the screen should look like for chuck test in the listening room</p>
<hr />
<div>What the screen should look like for chuck test in the listening room</div>Craffelhttps://ccrma.stanford.edu/mediawiki/index.php?title=Listening_Room_ChucK_tutorial&diff=9355Listening Room ChucK tutorial2009-12-03T22:49:53Z<p>Craffel: </p>
<hr />
<div>''Note - this tutorial doesn't use Jack, and there could be a cleaner way to do this with fewer steps, but it works and is fairly easy to do''<br />
<br />
1) Download the MiniAudicle for Linux [http://audicle.cs.princeton.edu/mini/linux/ here].<br />
<br />
2) Unzip the archive, cd to the unzipped directory in Terminal, and type make linux-alsa<br />
<br />
3) Now go into the unzipped directory, and you'll find the MiniAudicle app inside of the wxw folder. Open it.<br />
<br />
4) Open HDSPMixer - click on "Applications" at the top left, then go to "Sound and Video", then find and click on HDSPMixer.<br />
<br />
5) Run this example code: (copy and paste it, hit "add shred")<br />
<br />
ModalBar sin;<br />
<br />
8 => sin.preset;<br />
<br />
Gain g[16];<br />
<br />
.1 => float delay;<br />
<br />
for (0 => int i; i < 16; i++)<br />
{<br />
sin => g[i];<br />
0 => g[i].gain;<br />
g[i] => dac.chan(i);<br />
}<br />
<br />
while(true)<br />
{<br />
for (0 => int i; i < 16; i++)<br />
{<br />
Std.mtof(60+2*i) => sin.freq;<br />
sin.noteOn(1);<br />
.8=> g[i].gain;<br />
if(i == 0) { 0 => g[15].gain; }<br />
else { 0 => g[i-1].gain; }<br />
delay::second => now;<br />
0 => g[i].gain;<br />
delay::second => now;<br />
sin.noteOff(0);<br />
}<br />
}<br />
<br />
6) Now in HDSPMixer, you should see the level meters registering a signal. It should look like this:<br />
<br />
[[File:Example.jpg]]<br />
<br />
7) On the fader box, hit "Preset". You should hear sound now, with notes cascading around the room. If you don't, try restarting the openmixer box: it's the bigger computer which is connected to the monitor which says "OPENMIXER WORKSTATION: DO NOT LOGIN!". Find the computer and press "reset" on the front panel. If you still don't get sound. hit "Zero" then "Linux" on the fader box, then turn up the leftmost fader. Now, on the knob box, turn up the third knob down in the leftmost column (if you think of the knob box as a 8x4 matrix, this is in location 3, 1). You should be hearing sound now out of one of the speakers. If you aren't, something is awry, and find help!<br />
<br />
8) If you are experiencing popping and clicking, try entering cpufreq-selector -g performance into a terminal window. (Thanks Jason Sadural for this)<br />
<br />
9) If you notice that channels are "pairing", that is, if you change the pan value on one channel and it changes the pan value on another channel too, try resetting the openmixer computer. (Thanks Jason for this too)<br />
<br />
10) Rule of thumb: When in doubt, try restarting the openmixer computer first. Then, seek help!</div>Craffelhttps://ccrma.stanford.edu/mediawiki/index.php?title=Listening_Room_ChucK_tutorial&diff=9354Listening Room ChucK tutorial2009-12-03T22:46:02Z<p>Craffel: </p>
<hr />
<div>''Note - this tutorial doesn't use Jack, and there could be a cleaner way to do this with fewer steps, but it works and is fairly easy to do''<br />
<br />
1) Download the MiniAudicle for Linux [http://audicle.cs.princeton.edu/mini/linux/ here].<br />
<br />
2) Unzip the archive, cd to the unzipped directory in Terminal, and type make linux-alsa<br />
<br />
3) Now go into the unzipped directory, and you'll find the MiniAudicle app inside of the wxw folder. Open it.<br />
<br />
4) Open HDSPMixer - click on "Applications" at the top left, then go to "Sound and Video", then find and click on HDSPMixer.<br />
<br />
5) Run this example code: (copy and paste it, hit "add shred")<br />
<br />
ModalBar sin;<br />
<br />
8 => sin.preset;<br />
<br />
Gain g[16];<br />
<br />
.1 => float delay;<br />
<br />
for (0 => int i; i < 16; i++)<br />
{<br />
sin => g[i];<br />
0 => g[i].gain;<br />
g[i] => dac.chan(i);<br />
}<br />
<br />
while(true)<br />
{<br />
for (0 => int i; i < 16; i++)<br />
{<br />
Std.mtof(60+2*i) => sin.freq;<br />
sin.noteOn(1);<br />
.8=> g[i].gain;<br />
if(i == 0) { 0 => g[15].gain; }<br />
else { 0 => g[i-1].gain; }<br />
delay::second => now;<br />
0 => g[i].gain;<br />
delay::second => now;<br />
sin.noteOff(0);<br />
}<br />
}<br />
<br />
6) Now in HDSPMixer, you should see the level meters registering a signal. It should move across<br />
<br />
7) On the fader box, hit "Preset". You should hear sound now, with notes cascading around the room. If you don't, try restarting the openmixer box: it's the bigger computer which is connected to the monitor which says "OPENMIXER WORKSTATION: DO NOT LOGIN!". Find the computer and press "reset" on the front panel. If you still don't get sound. hit "Zero" then "Linux" on the fader box, then turn up the leftmost fader. Now, on the knob box, turn up the third knob down in the leftmost column (if you think of the knob box as a 8x4 matrix, this is in location 3, 1). You should be hearing sound now out of one of the speakers. If you aren't, something is awry, and find help!<br />
<br />
8) If you are experiencing popping and clicking, try entering cpufreq-selector -g performance into a terminal window. (Thanks Jason Sadural for this)<br />
<br />
9) If you notice that channels are "pairing", that is, if you change the pan value on one channel and it changes the pan value on another channel too, try resetting the openmixer computer. (Thanks Jason for this too)<br />
<br />
10) Rule of thumb: When in doubt, try restarting the openmixer computer first. Then, seek help!</div>Craffelhttps://ccrma.stanford.edu/mediawiki/index.php?title=Listening_Room_ChucK_tutorial&diff=9353Listening Room ChucK tutorial2009-12-03T22:45:24Z<p>Craffel: </p>
<hr />
<div>1) Download the MiniAudicle for Linux [http://audicle.cs.princeton.edu/mini/linux/ here] (note - this may not be necessary, but it certainly works, at least).<br />
<br />
2) Unzip the archive, cd to the unzipped directory in Terminal, and type make linux-alsa<br />
<br />
3) Now go into the unzipped directory, and you'll find the MiniAudicle app inside of the wxw folder. Open it.<br />
<br />
4) Open HDSPMixer - click on "Applications" at the top left, then go to "Sound and Video", then find and click on HDSPMixer.<br />
<br />
5) Run this example code: (copy and paste it, hit "add shred")<br />
<br />
ModalBar sin;<br />
<br />
8 => sin.preset;<br />
<br />
Gain g[16];<br />
<br />
.1 => float delay;<br />
<br />
for (0 => int i; i < 16; i++)<br />
{<br />
sin => g[i];<br />
0 => g[i].gain;<br />
g[i] => dac.chan(i);<br />
}<br />
<br />
while(true)<br />
{<br />
for (0 => int i; i < 16; i++)<br />
{<br />
Std.mtof(60+2*i) => sin.freq;<br />
sin.noteOn(1);<br />
.8=> g[i].gain;<br />
if(i == 0) { 0 => g[15].gain; }<br />
else { 0 => g[i-1].gain; }<br />
delay::second => now;<br />
0 => g[i].gain;<br />
delay::second => now;<br />
sin.noteOff(0);<br />
}<br />
}<br />
<br />
6) Now in HDSPMixer, you should see the level meters registering a signal. It should move across<br />
<br />
7) On the fader box, hit "Preset". You should hear sound now, with notes cascading around the room. If you don't, try restarting the openmixer box: it's the bigger computer which is connected to the monitor which says "OPENMIXER WORKSTATION: DO NOT LOGIN!". Find the computer and press "reset" on the front panel. If you still don't get sound. hit "Zero" then "Linux" on the fader box, then turn up the leftmost fader. Now, on the knob box, turn up the third knob down in the leftmost column (if you think of the knob box as a 8x4 matrix, this is in location 3, 1). You should be hearing sound now out of one of the speakers. If you aren't, something is awry, and find help!<br />
<br />
8) If you are experiencing popping and clicking, try entering cpufreq-selector -g performance into a terminal window. (Thanks Jason Sadural for this)<br />
<br />
9) If you notice that channels are "pairing", that is, if you change the pan value on one channel and it changes the pan value on another channel too, try resetting the openmixer computer. (Thanks Jason for this too)<br />
<br />
10) Rule of thumb: When in doubt, try restarting the openmixer computer first. Then, seek help!</div>Craffelhttps://ccrma.stanford.edu/mediawiki/index.php?title=Listening_Room_ChucK_tutorial&diff=9352Listening Room ChucK tutorial2009-12-03T22:44:51Z<p>Craffel: </p>
<hr />
<div>1) Download the MiniAudicle for Linux [http://audicle.cs.princeton.edu/mini/linux/ here] (note - this may not be necessary, but it certainly works, at least).<br />
<br />
2) Unzip the archive, cd to the unzipped directory in Terminal, and type make linux-alsa<br />
<br />
3) Now go into the unzipped directory, and you'll find the MiniAudicle app inside of the wxw folder. Open it.<br />
<br />
4) Open HDSPMixer - click on "Applications" at the top left, then go to "Sound and Video", then find and click on HDSPMixer.<br />
<br />
5) Run this example code: (copy and paste it, hit "add shred")<br />
<br />
ModalBar sin;<br />
<br />
8 => sin.preset;<br />
<br />
Gain g[16];<br />
<br />
.1 => float delay;<br />
<br />
for (0 => int i; i < 16; i++)<br />
{<br />
sin => g[i];<br />
0 => g[i].gain;<br />
g[i] => dac.chan(i);<br />
}<br />
<br />
while(true)<br />
{<br />
for (0 => int i; i < 16; i++)<br />
{<br />
Std.mtof(60+2*i) => sin.freq;<br />
sin.noteOn(1);<br />
.8=> g[i].gain;<br />
if(i == 0) { 0 => g[15].gain; }<br />
else { 0 => g[i-1].gain; }<br />
delay::second => now;<br />
0 => g[i].gain;<br />
delay::second => now;<br />
sin.noteOff(0);<br />
}<br />
}<br />
<br />
6) Now in HDSPMixer, you should see the level meters registering a signal. It should move across<br />
<br />
7) On the fader box, hit "Preset". You should hear sound now, with notes cascading around the room. If you don't, try restarting the openmixer box: it's the bigger computer which is connected to the monitor which says "OPENMIXER WORKSTATION: DO NOT LOGIN!". Find the computer and press "reset" on the front panel. If you still don't get sound. hit "Zero" then "Linux" on the fader box, then turn up the leftmost fader. Now, on the knob box, turn up the third knob down in the leftmost column (if you think of the knob box as a 8x4 matrix, this is in location 3, 1). You should be hearing sound now out of one of the speakers. If you aren't, something is awry, and find help!<br />
<br />
8) If you are experiencing popping and clicking, try entering cpufreq-selector -g performance into a terminal window. (Thanks Jason Sadural for this)<br />
<br />
9) If you notice that channels are "pairing", that is, if you change the pan value on one channel and it changes the pan value on another channel too, try resetting the openmixer computer. (Thanks Jason for this too)<br />
<br />
10) Rule of thumb: When in doubt, try restarting the openmixer computer first.</div>Craffelhttps://ccrma.stanford.edu/mediawiki/index.php?title=Listening_Room_ChucK_tutorial&diff=9351Listening Room ChucK tutorial2009-12-03T22:43:39Z<p>Craffel: </p>
<hr />
<div>1) Download the MiniAudicle for Linux [http://audicle.cs.princeton.edu/mini/linux/ here] (note - this may not be necessary, but it certainly works, at least).<br />
<br />
2) Unzip the archive, cd to the unzipped directory in Terminal, and type make linux-alsa<br />
<br />
3) Now go into the unzipped directory, and you'll find the MiniAudicle app inside of the wxw folder. Open it.<br />
<br />
4) Open HDSPMixer - click on "Applications" at the top left, then go to "Sound and Video", then find and click on HDSPMixer.<br />
<br />
5) Run this example code: (copy and paste it, hit "add shred")<br />
<br />
ModalBar sin;<br />
<br />
8 => sin.preset;<br />
<br />
Gain g[16];<br />
<br />
.15 => float delay;<br />
<br />
for (0 => int i; i < 16; i++)<br />
{<br />
sin => g[i];<br />
0 => g[i].gain;<br />
g[i] => dac.chan(i);<br />
}<br />
<br />
while(true)<br />
{<br />
for (0 => int i; i < 16; i++)<br />
{<br />
Std.mtof(40+2*i) => sin.freq;<br />
sin.noteOn(1);<br />
.8=> g[i].gain;<br />
if(i == 0) { 0 => g[15].gain; }<br />
else { 0 => g[i-1].gain; }<br />
delay::second => now;<br />
0 => g[i].gain;<br />
delay::second => now;<br />
sin.noteOff(0);<br />
}<br />
}<br />
<br />
6) Now in HDSPMixer, you should see the level meters registering a signal.<br />
<br />
7) On the fader box, hit "Preset". You should hear sound now, with notes cascading around the room. If you don't, try restarting the openmixer box: it's the bigger computer which is connected to the monitor which says "OPENMIXER WORKSTATION: DO NOT LOGIN!". Find the computer and press "reset" on the front panel. If you still don't get sound. hit "Zero" then "Linux" on the fader box, then turn up the leftmost fader. Now, on the knob box, turn up the third knob down in the leftmost column (if you think of the knob box as a 8x4 matrix, this is in location 3, 1). You should be hearing sound now out of one of the speakers. If you aren't, something is awry, and find help!<br />
<br />
8) If you are experiencing popping and clicking, try entering cpufreq-selector -g performance into a terminal window. (Thanks Jason Sadural for this)<br />
<br />
9) If you notice that channels are "pairing", that is, if you change the pan value on one channel and it changes the pan value on another channel too, try resetting the openmixer computer. (Thanks Jason for this too)<br />
<br />
10) Rule of thumb: When in doubt, try restarting the openmixer computer first.</div>Craffelhttps://ccrma.stanford.edu/mediawiki/index.php?title=Listening_Room_ChucK_tutorial&diff=9350Listening Room ChucK tutorial2009-12-03T22:43:23Z<p>Craffel: </p>
<hr />
<div>1) Download the MiniAudicle for Linux: [http://audicle.cs.princeton.edu/mini/linux/] (note - this may not be necessary, but it certainly works, at least).<br />
<br />
2) Unzip the archive, cd to the unzipped directory in Terminal, and type make linux-alsa<br />
<br />
3) Now go into the unzipped directory, and you'll find the MiniAudicle app inside of the wxw folder. Open it.<br />
<br />
4) Open HDSPMixer - click on "Applications" at the top left, then go to "Sound and Video", then find and click on HDSPMixer.<br />
<br />
5) Run this example code: (copy and paste it, hit "add shred")<br />
<br />
ModalBar sin;<br />
<br />
8 => sin.preset;<br />
<br />
Gain g[16];<br />
<br />
.15 => float delay;<br />
<br />
for (0 => int i; i < 16; i++)<br />
{<br />
sin => g[i];<br />
0 => g[i].gain;<br />
g[i] => dac.chan(i);<br />
}<br />
<br />
while(true)<br />
{<br />
for (0 => int i; i < 16; i++)<br />
{<br />
Std.mtof(40+2*i) => sin.freq;<br />
sin.noteOn(1);<br />
.8=> g[i].gain;<br />
if(i == 0) { 0 => g[15].gain; }<br />
else { 0 => g[i-1].gain; }<br />
delay::second => now;<br />
0 => g[i].gain;<br />
delay::second => now;<br />
sin.noteOff(0);<br />
}<br />
}<br />
<br />
6) Now in HDSPMixer, you should see the level meters registering a signal.<br />
<br />
7) On the fader box, hit "Preset". You should hear sound now, with notes cascading around the room. If you don't, try restarting the openmixer box: it's the bigger computer which is connected to the monitor which says "OPENMIXER WORKSTATION: DO NOT LOGIN!". Find the computer and press "reset" on the front panel. If you still don't get sound. hit "Zero" then "Linux" on the fader box, then turn up the leftmost fader. Now, on the knob box, turn up the third knob down in the leftmost column (if you think of the knob box as a 8x4 matrix, this is in location 3, 1). You should be hearing sound now out of one of the speakers. If you aren't, something is awry, and find help!<br />
<br />
8) If you are experiencing popping and clicking, try entering cpufreq-selector -g performance into a terminal window. (Thanks Jason Sadural for this)<br />
<br />
9) If you notice that channels are "pairing", that is, if you change the pan value on one channel and it changes the pan value on another channel too, try resetting the openmixer computer. (Thanks Jason for this too)<br />
<br />
10) Rule of thumb: When in doubt, try restarting the openmixer computer first.</div>Craffelhttps://ccrma.stanford.edu/mediawiki/index.php?title=Listening_Room_ChucK_tutorial&diff=9349Listening Room ChucK tutorial2009-12-03T22:42:34Z<p>Craffel: </p>
<hr />
<div>1) Download the MiniAudicle for Linux: [http://audicle.cs.princeton.edu/mini/linux/] (note - this may not be necessary, but it certainly works, at least).<br />
<br />
2) Unzip the archive, cd to the unzipped directory in Terminal, and type make linux-alsa<br />
<br />
3) Now go into the unzipped directory, and you'll find the MiniAudicle app inside of the wxw folder. Open it.<br />
<br />
4) Open hDSP Mixer.<br />
<br />
5) Run this example code: (copy and paste it, hit "add shred")<br />
<br />
ModalBar sin;<br />
<br />
8 => sin.preset;<br />
<br />
Gain g[16];<br />
<br />
.15 => float delay;<br />
<br />
for (0 => int i; i < 16; i++)<br />
{<br />
sin => g[i];<br />
0 => g[i].gain;<br />
g[i] => dac.chan(i);<br />
}<br />
<br />
while(true)<br />
{<br />
for (0 => int i; i < 16; i++)<br />
{<br />
Std.mtof(40+2*i) => sin.freq;<br />
sin.noteOn(1);<br />
.8=> g[i].gain;<br />
if(i == 0) { 0 => g[15].gain; }<br />
else { 0 => g[i-1].gain; }<br />
delay::second => now;<br />
0 => g[i].gain;<br />
delay::second => now;<br />
sin.noteOff(0);<br />
}<br />
}<br />
<br />
6) Now in HDSPMixer, you should see the level meters registering a signal.<br />
<br />
7) On the fader box, hit "Preset". You should hear sound now, with notes cascading around the room. If you don't, try restarting the openmixer box: it's the bigger computer which is connected to the monitor which says "OPENMIXER WORKSTATION: DO NOT LOGIN!". Find the computer and press "reset" on the front panel. If you still don't get sound. hit "Zero" then "Linux" on the fader box, then turn up the leftmost fader. Now, on the knob box, turn up the third knob down in the leftmost column (if you think of the knob box as a 8x4 matrix, this is in location 3, 1). You should be hearing sound now out of one of the speakers. If you aren't, something is awry, and find help!<br />
<br />
8) If you are experiencing popping and clicking, try entering cpufreq-selector -g performance into a terminal window. (Thanks Jason Sadural for this)<br />
<br />
9) If you notice that channels are "pairing", that is, if you change the pan value on one channel and it changes the pan value on another channel too, try resetting the openmixer computer. (Thanks Jason for this too)<br />
<br />
10) Rule of thumb: When in doubt, try restarting the openmixer computer first.</div>Craffelhttps://ccrma.stanford.edu/mediawiki/index.php?title=Listening_Room_ChucK_tutorial&diff=9348Listening Room ChucK tutorial2009-12-03T22:42:22Z<p>Craffel: </p>
<hr />
<div>1) Download the MiniAudicle for Linux: [http://audicle.cs.princeton.edu/mini/linux/] (note - this may not be necessary, but it certainly works, at least).<br />
<br />
2) Unzip the archive, cd to the unzipped directory in Terminal, and type make linux-alsa<br />
<br />
3) Now go into the unzipped directory, and you'll find the MiniAudicle app inside of the wxw folder. Open it.<br />
<br />
4) Open hDSP Mixer.<br />
<br />
5) Run this example code: (copy and paste it, hit "add shred")<br />
<br />
ModalBar sin;<br />
<br />
8 => sin.preset;<br />
<br />
Gain g[16];<br />
<br />
.15 => float delay;<br />
<br />
for (0 => int i; i < 16; i++)<br />
{<br />
sin => g[i];<br />
0 => g[i].gain;<br />
g[i] => dac.chan(i);<br />
}<br />
<br />
while(true)<br />
{<br />
for (0 => int i; i < 16; i++)<br />
{<br />
Std.mtof(40+2*i) => sin.freq;<br />
sin.noteOn(1);<br />
.8=> g[i].gain;<br />
if(i == 0) { 0 => g[15].gain; }<br />
else { 0 => g[i-1].gain; }<br />
delay::second => now;<br />
0 => g[i].gain;<br />
delay::second => now;<br />
sin.noteOff(0);<br />
}<br />
}<br />
<br />
6) Now in HDSPMixer, you should see the level meters registering a signal.<br />
<br />
7) On the fader box, hit "Preset". You should hear sound now, with notes cascading around the room. If you don't, try restarting the openmixer box: it's the bigger computer which is connected to the monitor which says "OPENMIXER WORKSTATION: DO NOT LOGIN!". Find the computer and press "reset" on the front panel. If you still don't get sound. hit "Zero" then "Linux" on the fader box, then turn up the leftmost fader. Now, on the knob box, turn up the third knob down in the leftmost column (if you think of the knob box as a 8x4 matrix, this is in location 3, 1). You should be hearing sound now out of one of the speakers. If you aren't, something is awry, and find help!<br />
<br />
8) If you are experiencing popping and clicking, try entering cpufreq-selector -g performance into a terminal window. (Thanks Jason Sadural for this)<br />
<br />
9) If you notice that channels are "pairing", that is, if you change the pan value on one channel and it changes the pan value on another channel too, try resetting the openmixer computer. (Thanks Jason for this too)<br />
<br />
10) Rule of thumb: When in doubt, try restarting the openmixer computer first.</div>Craffelhttps://ccrma.stanford.edu/mediawiki/index.php?title=Listening_Room_ChucK_tutorial&diff=9347Listening Room ChucK tutorial2009-12-03T22:41:31Z<p>Craffel: Created page with '1) Download the MiniAudicle for Linux: [http://audicle.cs.princeton.edu/mini/linux/] (note - this may not be necessary, but it certainly works, at least). 2) Unzip the archive,…'</p>
<hr />
<div>1) Download the MiniAudicle for Linux: [http://audicle.cs.princeton.edu/mini/linux/] (note - this may not be necessary, but it certainly works, at least).<br />
<br />
2) Unzip the archive, cd to the unzipped directory in Terminal, and type make linux-alsa<br />
<br />
3) Now go into the unzipped directory, and you'll find the MiniAudicle app inside of the wxw folder. Open it.<br />
<br />
4) Open hDSP Mixer.<br />
<br />
5) Run this example code: (copy and paste it, hit "add shred")<br />
<br />
ModalBar sin;<br />
<br />
8 => sin.preset;<br />
<br />
Gain g[16];<br />
<br />
.15 => float delay;<br />
<br />
for (0 => int i; i < 16; i++)<br />
{<br />
sin => g[i];<br />
0 => g[i].gain;<br />
g[i] => dac.chan(i);<br />
}<br />
<br />
while(true)<br />
{<br />
for (0 => int i; i < 16; i++)<br />
{<br />
Std.mtof(40+2*i) => sin.freq;<br />
sin.noteOn(1);<br />
.8=> g[i].gain;<br />
if(i == 0) { 0 => g[15].gain; }<br />
else { 0 => g[i-1].gain; }<br />
delay::second => now;<br />
0 => g[i].gain;<br />
delay::second => now;<br />
sin.noteOff(0);<br />
}<br />
}<br />
<br />
6) Now in HDSPMixer, you should see the level meters registering a signal.<br />
<br />
7) On the fader box, hit "Preset". You should hear sound now, with notes cascading around the room. If you don't, try restarting the openmixer box: it's the bigger computer which is connected to the monitor which says "OPENMIXER WORKSTATION: DO NOT LOGIN!". Find the computer and press "reset" on the front panel. If you still don't get sound. hit "Zero" then "Linux" on the fader box, then turn up the leftmost fader. Now, on the knob box, turn up the third knob down in the leftmost column (if you think of the knob box as a 8x4 matrix, this is in location 3, 1). You should be hearing sound now out of one of the speakers. If you aren't, something is awry, and find help!<br />
<br />
8) If you are experiencing popping and clicking, try entering cpufreq-selector -g performance into a terminal window. (Thanks Jason Sadural for this)<br />
<br />
9) If you notice that channels are "pairing", that is, if you change the pan value on one channel and it changes the pan value on another channel too, try resetting the openmixer computer. (Thanks Jason for this too)<br />
<br />
10) Rule of thumb: When in doubt, try restarting the openmixer computer first.</div>Craffelhttps://ccrma.stanford.edu/mediawiki/index.php?title=Listening_Room_Specs&diff=9346Listening Room Specs2009-12-03T22:29:22Z<p>Craffel: </p>
<hr />
<div>== Welcome to the Pit Page ==<br />
written by Jason Sadural (jsadural@ccrma.stanford.edu)<br />
comments and suggestions always welcomed<br />
<br />
This page discusses the room dimensions as well as the the process of calibrating the spherical VBAP configuration. It will also discuss the equipment and software used to operate sound as well as how to configure and save settings for your personal needs. If you move any speaker in the room you will be personally responsible to recalculate and recalibrate speaker configuration (in other words "DON"T DO IT!!!").In the future we hope to update this page with a new wave field synthesis installation. In 2008 we will be implementing a new system formally titled Openmixer.<br />
<br />
For a "complete idiots guide" to getting sound out of the listening room using ChucK/miniaudicle: [[Listening Room ChucK tutorial]]<br />
<br />
<br />
<br />
# Room Dimensions<br />
#* 277inches x 292 inches x 86 inches(height)<br />
# There exists a heptagon in the center with 3 steps downwards to a cage in the middle<br />
#* Height of each step = 5.5 inches<br />
#* Length of step = 11.75 inches<br />
#* Length of side of Heptagon at top = 84 inches (same as top)<br />
#* Depth of indentation in ceiling = 15 inches<br />
#* Length of side of Heptagon at cage(bottom) = 63 inches<br />
#* Depth to bottom of cage = 41 inches<br />
#* Closest point of Heptagon to wall = 51 inches<br />
# Equipment and software<br />
#* Samsung 17 inch monitor<br />
#* Linux box<br />
#* RME Hammerfall DSP Digiface<br />
#* Tascam TDIF-1/ADAT interface format converter<br />
#* Tascam DM-3200<br />
#* 5.1 DVD player<br />
#* 8 Mackie HR824<br />
#* 8 Mackie HR624<br />
#* AKG C-414 Mic/Stand/adapter<br />
#* ALSA HDSP<br />
#* Jack <br />
# Before beginning, create your own project by clicking "alt-Project" and cursor down to "store as." Name your project using the Dial and the enter key. After doing so, follow instructions and store at the end of calibration. Please use current calculations of speaker configuration instead of repositioning speakers. <br />
# Current speaker configuration<br />
#* speakers 1 is on channel 1 assigned to output 7, speaker congiguration is coutner-clockwise starting at 0 degrees<br />
#* speakers are in octagonal setup with speakers 92 inches apart<br />
#* Distance to sweetspot from each horizontal speaker is 120.205 inches<br />
#* Verticle speakers distance will be termed in counterclockwise order PhiU1(upper1 azimuth), ThetaU1(upper1 angle), ru1(upper1 distance) and so on(all in degrees). <br />
#* Speaker 1 horizontal = 120.205 <br />
#* ThetaU1 = 46.123 ; PhiU1 = 34.582; rU1 = 88.8147<br />
#* ThetaU2 = 134.578; PhiU2 = 35.213; rU2 = 87.2017<br />
#* ThetaU3 = 225.119; PhiU3 = 29.898; rU3 = 90.2783<br />
#* ThetaU4 = 328.552; PhiU4 = 31.448; rU4 = 91.3406<br />
#* ThetaD1 = 46.429 ; PhiD1 = -61.214; rD1 = 95.1767<br />
#* ThetaD2 = 135.557; PhiD2 = -60.980; rD2 = 95.6595<br />
#* ThetaD3 = 235.089; PhiD3 = -43.200; rD3 = 89.9286 (Possible Error)<br />
#* ThetaD4 = 317.181; PhiD4 = -55.781; rD4 = 98.3265<br />
# Speaker Positioning : In calibration of the speakers, I used a T-square, laser Line tool, Wire, tape measure, and Protractor. I made sure that the sweet spot would be intuitive upon placing the seat into the center of the Pit.<br />
#* Use obvious methods to align horizontal speakers in an octagon at a arbitrary distance measured from the center of cage. <br />
#* Measure 3 distances from each verticle(above/below) speaker to 3 different horizontal speakers <br />
#* Use [http://en.wikipedia.org/wiki/Trilateration trilateral] calculation to solve xyz position in space<br />
#* Use octagon properties to perform coordinate transformation in order to find position from sweet spot(center of octagon)<br />
#* PD patch in which calculates intersecting spheres located through ccrma-gate at /jsadura/trilateration <br />
# Speaker Calibration<br />
#* settings: Acoustic Space "B"half; Low Freq 37Hz; High Freq 0Hz; Power Mode ON<br />
#* Make sure all bus and gain settings are equal on mixer<br />
#* Adjust gain on speaker and use Pink noise to calibrate equal SPL levels at the sweet spot one at a time<br />
# Time Delay<br />
#* Calculate distance to verticle speakers (R) from trilateration page and find the difference in distance to horizontal speakers<br />
#* At a 44.1kHz sample rate, divide distance in inches by 0.3 to calculate samples of delay<br />
#* on Tascam DM-3200 mixer select "Module" on top right and move cursor down to Delay <br />
#* Hold [http://en.wiktionary.org/wiki/shift#Verb shiFt] while turning third knob for smaller increments of delay in samples.<br />
<br />
== Photo of the Listening Room: without speakers ==<br />
<br />
[[Image:Listeningroom.jpg]]<br />
<br />
<br />
[[Category:CCRMA User Guide]]</div>Craffelhttps://ccrma.stanford.edu/mediawiki/index.php?title=220a-fall-2009/FinalProjects&diff=9179220a-fall-2009/FinalProjects2009-11-07T04:37:41Z<p>Craffel: </p>
<hr />
<div>[http://ccrma.stanford.edu/wiki/220a-fall-2009 BACK TO WIKI MAIN PAGE]<br />
<br />
==Sign up for Meetings with Michelle and Michael==<br />
<br />
* Tuesday, November 17th: <i> ... in 10 minute chunks (from 9am until 12pm) ... </i><br />
**9:00 ~ Brian Yoo<br />
**9:10 ~<br />
**9:20 ~<br />
**9:30 ~ Jacqueline Gordon<br />
**9:40 ~ Adam Sheppard<br />
**9:50 ~<br />
**10:00 ~ Hongchan Choi<br />
**10:10 ~<br />
**10:20 ~<br />
**10:30 ~<br />
**10:40 ~ Matt Bush<br />
**10:50 ~<br />
**11:00 ~ Andrew Plan<br />
**11:10 ~<br />
**11:20 ~<br />
**11:30 ~ Christopher Fajardo<br />
**11:40 ~ Zach Brand<br />
**11:50 ~ Ben Roth<br />
**12:00 ~ Uri Nieto<br />
**12:10 ~ Jonathan Potter<br />
**12:20 ~ Jason Chen<br />
<br />
<br />
* Thursday, November 19th: <i> ... in 10 minute chunks (from 9am until 12pm) ... </i><br />
**9:00 ~<br />
**9:10 ~<br />
**9:20 ~<br />
**9:30 ~<br />
**9:40 ~<br />
**9:50 ~<br />
**10:00 ~dohi moon<br />
**10:10 ~<br />
**10:20 ~<br />
**10:30 ~<br />
**10:40 ~<br />
**10:50 ~<br />
**11:00 ~<br />
**11:10 ~<br />
**11:20 ~<br />
**11:30 ~<br />
**11:40 ~<br />
**11:50 ~Jacob Wittenberg<br />
**12:00 ~ Colin Raffel<br />
**12:10 ~ Tyler Maue<br />
**12:20 ~ Sarah Masimore<br />
<br />
<br />
<br />
== FINAL PRESENTATIONS SCHEDULE ==<br />
*Tuesday, December 1, 2009:<br />
**10:00 ~ Zach Brand<br />
**10:10 ~<br />
**10:20 ~<br />
**10:30 ~dohi moon<br />
**10:40 ~ Matt Bush<br />
**10:50 ~<br />
**11:00 ~ Andrew Plan<br />
**11:10 ~<br />
**11:20 ~<br />
**11:30 ~<br />
**11:40 ~<br />
**11:50 ~<br />
<br />
<br />
*Thursday, December 3, 2009:<br />
**10:00 ~ Uri Nieto<br />
**10:10 ~ Sarah Masimore<br />
**10:20 ~ Ben Roth<br />
**10:30 ~ Jacob Wittenberg<br />
**10:40 ~ Tyler Maue<br />
**10:50 ~ Jonathan Potter<br />
**11:00 ~<br />
**11:10 ~<br />
**11:20 ~<br />
**11:30 ~<br />
**11:40 ~<br />
**11:50 ~<br />
<br />
<br />
*Thursday, December 10, 2009:<br />
**3:30pm ~ Jacqueline Gordon<br />
**3:40pm ~<br />
**3:50pm ~<br />
**4:00pm ~ Christopher Fajardo<br />
**4:10pm ~<br />
**4:20pm ~ Brian Yoo<br />
**4:30pm ~<br />
**4:40pm ~<br />
**4:50pm ~<br />
**5:00pm ~<br />
**5:10pm ~<br />
**5:20pm ~<br />
**DO NOT BOOK AFTER 5:20pm unless ALL OTHER SLOTS ARE FILLED IN<br />
***5:30pm ~<br />
***5:40pm ~<br />
***5:50pm ~<br />
<br />
<br />
...<br />
<br />
----<br />
<br />
<br />
[http://ccrma.stanford.edu/wiki/220a-fall-2009 <b>BACK TO WIKI MAIN PAGE</b>]</div>Craffelhttps://ccrma.stanford.edu/mediawiki/index.php?title=256a-fall-2009/hw3&diff=8989256a-fall-2009/hw32009-10-14T22:36:04Z<p>Craffel: </p>
<hr />
<div>= Homework #3: Sound Peeking =<br />
<br />
Due date: 2009.10.26 11:59:59pm (or thereabout), Monday.<br />
<br />
<br />
<div style="text-align: left;">[[Image:waves-bw.jpg]]</div><br />
<br />
In this assignment, you are to visualize sound in real-time, using OpenGL for the graphics programming.<br />
<br />
<br />
=== Specification (part 1 of 3): naming + compilation ===<br />
* choose a name for your program<br />
* get a framework compiling on your system (keep in mind the final deliverable must be compilable/runnable on the CCRMA machines OR on OS X)<br />
* might wish to start from the [http://ccrma.stanford.edu/courses/256a-fall-2009/lectures/VisualSine VisualSine] example from lecture (time domain waveform rendering)<br />
* additional code from class available [http://ccrma.stanford.edu/courses/256a-fall-2009/lectures/ here]<br />
<br />
<br />
=== Specification (part 2 of 3): Visualizing the spectrum ===<br />
* implement short time fourier transform, and visualize the spectrum over time<br />
* considerations:<br />
** windowing (rectangular, hann, hamming)<br />
** window size<br />
** FFT size<br />
** hop size (for now, hop size can equal window size)<br />
* implement either a waterfall plot (like sndpeek) or a real-time scrolling spectrogram<br />
<br />
<br />
=== Specification (part 3 of 3): Visualize something about the sound ===<br />
* implement and visualize your choice of one of the following:<br />
** vowel vs. consonant<br />
** pitch tracking<br />
** an audio feature<br />
** use the sound to control some type of animation<br />
** (or something of your choosing)<br />
<br />
<br />
=== Note ===<br />
* have fun with it!!!<br />
* your code should compile and run on the CCRMA (or OSX) machines<br />
* comment your code!<br />
* choose your own coding conventions - but '''be consistent'''<br />
* you are welcome to work together, but you must do/turn in your own work (you'll likely get more out of it this way)<br />
<br />
=== Deliverables ===<br />
<br />
'''turn in all files by putting them in your Library/Web/256a/hw3/ directory, and concise online documentation + readme'''<br />
<br />
* 1) source code to the project (*.h, *.cpp, *.c makefile, etc.)<br />
* 2) online page for your project (should be viewable at http://ccrma.stanford.edu/~YOURID/256a/hw3/). It should include:<br />
** links to your files of various kinds<br />
** instructions on building the project (for example, anyone in the class should be able to download<br />
** a short README text section that:<br />
*** conveys your ideas/comments in constructing each program <br />
*** describes any difficulties you encountered in the process<br />
*** lists any collaborators<br />
* 3) '''email Ge''' with the link to your web page, as a confirmation that you are submitting the assignment</div>Craffelhttps://ccrma.stanford.edu/mediawiki/index.php?title=256a-fall-2009/hw3&diff=8988256a-fall-2009/hw32009-10-14T22:35:51Z<p>Craffel: </p>
<hr />
<div>= Homework #3: Sound Peeking =<br />
<br />
Due date: 2009.10.28 11:59:59pm (or thereabout), Monday.<br />
<br />
<br />
<div style="text-align: left;">[[Image:waves-bw.jpg]]</div><br />
<br />
In this assignment, you are to visualize sound in real-time, using OpenGL for the graphics programming.<br />
<br />
<br />
=== Specification (part 1 of 3): naming + compilation ===<br />
* choose a name for your program<br />
* get a framework compiling on your system (keep in mind the final deliverable must be compilable/runnable on the CCRMA machines OR on OS X)<br />
* might wish to start from the [http://ccrma.stanford.edu/courses/256a-fall-2009/lectures/VisualSine VisualSine] example from lecture (time domain waveform rendering)<br />
* additional code from class available [http://ccrma.stanford.edu/courses/256a-fall-2009/lectures/ here]<br />
<br />
<br />
=== Specification (part 2 of 3): Visualizing the spectrum ===<br />
* implement short time fourier transform, and visualize the spectrum over time<br />
* considerations:<br />
** windowing (rectangular, hann, hamming)<br />
** window size<br />
** FFT size<br />
** hop size (for now, hop size can equal window size)<br />
* implement either a waterfall plot (like sndpeek) or a real-time scrolling spectrogram<br />
<br />
<br />
=== Specification (part 3 of 3): Visualize something about the sound ===<br />
* implement and visualize your choice of one of the following:<br />
** vowel vs. consonant<br />
** pitch tracking<br />
** an audio feature<br />
** use the sound to control some type of animation<br />
** (or something of your choosing)<br />
<br />
<br />
=== Note ===<br />
* have fun with it!!!<br />
* your code should compile and run on the CCRMA (or OSX) machines<br />
* comment your code!<br />
* choose your own coding conventions - but '''be consistent'''<br />
* you are welcome to work together, but you must do/turn in your own work (you'll likely get more out of it this way)<br />
<br />
=== Deliverables ===<br />
<br />
'''turn in all files by putting them in your Library/Web/256a/hw3/ directory, and concise online documentation + readme'''<br />
<br />
* 1) source code to the project (*.h, *.cpp, *.c makefile, etc.)<br />
* 2) online page for your project (should be viewable at http://ccrma.stanford.edu/~YOURID/256a/hw3/). It should include:<br />
** links to your files of various kinds<br />
** instructions on building the project (for example, anyone in the class should be able to download<br />
** a short README text section that:<br />
*** conveys your ideas/comments in constructing each program <br />
*** describes any difficulties you encountered in the process<br />
*** lists any collaborators<br />
* 3) '''email Ge''' with the link to your web page, as a confirmation that you are submitting the assignment</div>Craffelhttps://ccrma.stanford.edu/mediawiki/index.php?title=220a-fall-2009/studentmusic&diff=8706220a-fall-2009/studentmusic2009-09-29T17:04:13Z<p>Craffel: /* SIGN-UP for MUSIC Presentations on wiki */</p>
<hr />
<div>== SIGN-UP for MUSIC Presentations on wiki ==<br />
* Sept. 24 = Dohi & Adam<br />
* Sept. 29 = Adam Somers, Uri Nieto, Zach Brand<br />
* Oct. 1 = Sarah Masimore<br />
* Oct. 6 =<br />
* Oct. 8 = <br />
* Oct. 13 = Ben Roth<br />
* Oct. 15 =<br />
* Oct. 20 = Colin Raffel<br />
* Oct. 22 =<br />
* Oct. 27 =<br />
* Oct. 29 =<br />
* Nov. 3 =<br />
* Nov. 5 =<br />
* Nov. 10 =<br />
* Nov. 12 = John Bauer<br />
* Nov.<br />
<br />
<br />
<br />
--<br />
* [http://cm-wiki.stanford.edu/wiki/220a-fall-2009 Back to 220a wiki Page]</div>Craffel