MEETING MINUTES

MEETING June 12, 2012

PURPOSE:  Update on KIns project and general discussion

DISCUSSION:  We are working with a lot of pre-existing code to create modifications and build our own instrumentation and compositions.  Given that the class is geared towards students with no programming experience, we agreed this would be a good way for them to "dive in" into the code and learn how it works because they can manipulate the code and immediately hear the result.  This will give them some familiarity with code structure and documentation.  Giving students partially completed code in a lab would give them a chance to work with the code, and the assignment following would expand this.  There is a plethora of code available as open source.  An exercise may include asking them to add a feature, or show how they took existing code to create new sounds, compositions, beats, et cetera.  We discussed generally to keep in mind exercises and labs to create from the KIns development.

PLAN:  Freda and Lucy will post their code on the KIns instrument.  Lucy is working with MAUI Elements to create a GUI.   Jan and Julia are developing a graphic visualization using Processing/OSC/chucK, and Jan is continuing to review code samples/examples to incorporate in our own development.

QUESTION:  Would students be expected to code from scratch given the basics of chucK?  Would they be encouraged to look at open source pre-existing code to incorporate in their projects?

MEETING June 11, 2012

PURPOSE:  Monday morning check-in and discuss our goals for the week.

DISCUSSION:  Reviewed last week's accomplishments:

• Reviewed chucK demos for multiple shreds
• Mapped keyboard with chucK to create different sounds
• 
  
• Networked between computers using OSC, successfully sent shreds remotely
• Production of materials for intro class:
• Audacity exercise and lab suggestion
• Powerpoints in Digital Audio, ADC to DAC, WaveTables, Sound Waves, etc.
• Tested out system to show mic input with 3-D graphic showing how sound is affected
• Need pre-amp to use provided microphone
• Need 1/4" female stereo to 1/8" male stereo connector 
• Possibly need stereo male RCA (left/right) to 1/8" stereo male input cable

SUGGESTIONS:

Label posts and include "Finished" as an option.

Meet later in week as a group to review PowerPoints in conference room to discuss.

Create materials addressing music composition/theory basics

PLAN:

Julia - Working on production of materials and power points to teach synthesis and music concepts

Freda and Lucy - Research on creating musical instrument and report in programs, i.e. (S.M.E.L.T, GarageBand, Ableton, etc.)

Jan - Explore chuck coding for specific sounds and how it is created, i.e., snare drum, hit-hat symbol.  Review all chuck Demo code.

Present to each other on our findings.

QUESTION:

Ask Judy for any specific goals she has for us this week.  See Judy F. Post on June 11

MEETING June 8, 2012

PURPOSE:  Brief meeting where we updated Lucy on yesterday and brainstormed a bit.

DISCUSSION:  Review MAUI Elements in miniAudicle to create GUIs for different functions.

GUIs:

• Create a text window to type in so a user can record the sequence of notes to create and share their own musical scores.
• Additional data to save may include how long a key is held down
• Define composition tools
• Understand better how synchronization works in chucK between multiple tracks  

QUESTION:  Can you use Java to expand chucK programs?  ANSWER:  Yes, but there are other programs that can be used.  Judy F. sent a link to Processing/OSC/Chuck.  The Chuck Users Forum also has a lot of options discussed for bidirectional communication and open source alternatives.

MEETING June 7, 2012

PURPOSE:  To update our progress and areas of research to each other.  To discuss goals and direction of our research towards a practical application.

DISCUSSION:  Everyone agreed that it would be rewarding at the end of our summer research to have a practical application developed that incorporates what we have learned.  Freda's suggestion stemmed from both her and Lucy's posts about creating a musical instrument from your laptop.  Julia felt this would be a good way to offer tutorials in music theory and basic computer programming.  Jan suggested researching current applications that may be similar to refine and develop the idea further.  The development process
could be incorporated into a final project idea for the Intro to chucK Programming class where students would create their own musical instrument design that could be added to the application.

GOAL:  To create a digital instrument that is somewhat analogous to a real, physical instrument that is open source, free, very easy to learn and use, and can be a gateway to a deeper understand of both musical theory and digital audio.  Create an open source, downloadable GUI application to turn a user's laptop into a musical instrument.  Targeted audience: users with no musical background or computer programming experience. The purpose is to engage users who do not have access to musical instruments or training and to expose them to musical theory and computer programming.  The focus is on building the instrument, not necessarily composition.

TO DO:

Define the practical application in detail.

1. Research similar applications that currently exist.
2. Create tutorials:
1. Digital Audio Basics
2. Terminology / Definitions
3. Soundwaves
4. DAC / ADC 
5. Wavetable / Wavetable Synthesis
6. Granular Synthesis 
3. Build website

Break down the development tasks.

1. Development classes for instruments
1. Chuck STK Instrument Classes
2. Define and create the GUI Interface
1. miniAudicle MAUI Elements
3. Research other electronic music programs for ideas and comparison - See post on KIns
4. Lucy and Freda work together on musical instrument 
5. Learn how to map keyboard 
6. Set up network to other computers using OSC

Prioritize the tasks.

<See Freda's posting on KIns Project>

Create development milestones to measure progress