128-spring-2010-Assignment3

Group (example)

• members: Jieun Oh
• (tentative) title of piece: Converge
• summary of piece concept: collect data (location, time, audio recording, text, pictures, tapping gestures) from performers prior to the concert, and combine the elements into a piece during performance based on audience preference
• link to all related files (chuck, audio files, instructions, scores) : converge files
• documentation of what you tried as of May 11: blah blah blah

Virtual Handbell Choir

• members: Nick, Daniel, Jay
• (tentative) title of piece: Virtual Handbell Choir (very tentative)
• summary of piece concept: Air handbells for 10 slork stations w/Golf Controlllers, featuring a guitar hero-like GUI which will automatically disseminate the parts of a MIDI song to each Slork station, with each player being in charge of two bells.
• link to all related files (chuck, audio files, instructions, scores) : source files

Milestones - 
check! Instrument - Nick, Daniel - Wednesday 12th
check! Network - Jay - Monday 10th (something done to pass to daniel)
check! MIDI - Jay - Monday 10th (something done to pass to daniel)
check! Graphics - Daniel - Monday 17th
check! INTEGRATION - ALL - Wednesday 19th
check! Piece - Nick - At least something by Wednesday 19th

Refine code and graphics, compile into Audicle - Wednesday 26th First version of final piece - Wednesday 26th

ideas for network: 
1.) songs stored on server - client downloads midi, parses - determines what it needs and displays that
2.) songs stored on server - server parses song - client looks to server for specific part it needs - downloads and displays that

ideas for graphics:
- flies at you at an angle like rock band
- hits are circles, higher velocity = larger circle + different color
- long rectangle for the fast dinging thing
- lower horizontal bar to show you need to dampen

ideas for instrument:
- dampen to your chest and/or with pedal - at least have pedal be a "kill switch" in case of error	
- use STK shaker code to excite the bell sound

• documentation of what you tried as of May 11:

• • Nick: processing of handbell samples to transpose into 3 full octaves and basic, functioning control with controller
  • Daniel: Worked the instrument so that it is now up to scratch. Definitely not a final version of the instrument, but its a lot more responsive - I've modified the original work done for the instrument, and the main problem we were having is that it wasn't sensing a lot of the "hits." This is fixed through a sort of memory structure that I created so the instrument is a little more intelligent and can therefore not be so bad at triggering.
  • Jay:

• documentation of what you tried as of May 17:

- fully working v1.0 of guitar hero style score reader - revised instrument with aftertouch vibrato - OSC networked "start" button - etude.mid for rehearsal - printed step by step instructions for smoother rehearsal

Group Awesome

• members: Giancarlo Daniele, Ben Holtz, Linden Melvin
• (tentative) title of piece: Sampling Machine
• summary of piece concept: Our goal is to use sampling as a form of expression. Each slork station will have twenty samples at their disposal (mapped to keyboard keys) from iconic songs defining decades in American music. Each machine is an "instrument" capable of taking the samples and passing it through a chuck effect or filter. Our piece has a few tentative components 1) A game component, where one station plays one sample at a time and passes it to another station, which has to play that sample, add a new sample, and pass it along. 2) A score-d component, where each station will read keypresses, etc from a score 3) An improvised component, where a conductor points stations that are responsible for playing certain parts.
• link to all related files (chuck, audio files, instructions, scores) :
• documentation of what you tried as of May 11: As a group, we've come up with a variety of different samples, "instruments" (coded chuck w/ sndbuff effects), and a very preliminary idea the various components of our piece.

Everybodyeverybody

• members: Alan Hshieh, Aaron Zarraga, Isaac Wang
• (tentative) title of piece: Fanfare for the Common Man
• summary of piece concept: The idea for our piece is that we want to combine "live" coding with a pre-written score in order to simulate a full orchestra. Each SlOrk station will be a different orchestral section and they will have an assigned part to play. The piece will be slow and harmonic to allow each person to physically type in a new note's frequency value for their instrument. These coding screens will be projected in order to show off the live coding aspect. We want to create a piece that is interesting to watch as well. We plan to make the smack sensor swap out the current shread with the new one that is currently being typed. Therefore everyone will be striking their instrument at the appropriate times to play each note. This will be awesome to look at, especially since we plan on having some Taiko drums in the orchestra. We are still trying to develop our ideas as far as what we want for the final piece, but we know that we want the song to be epic.
• link to all related files (chuck, audio files, instructions, scores) : http://hshieh.com/slork
• documentation of what you tried as of May 11: We worked out our concept, figured out a basic rendition of Twinkle Twinkle Little Star to demo in class, and will be meeting May 12th to compose and find tune.

noise and headbanging

• members: adam somers, uri nieto, charlie forkish
• (tentative) title of piece: Concerto For Touchboard and Headbang Orchestra
• summary of piece concept: the headbang orchestra will be composed of twelve players wearing GameTrak controller gloves around their necks triggering samples by headbanging. there will be a percussion section composed of two kick drum players, one snare drum player, and four hi-hat players. there will be three guitar players each on a different power chord, and two more each triggering a different riff or shred. the soloists will be adam playing noisy awesome on the touchboard and uri modulating adam's awesome by headbanging and hairswirling. charlie will be conducting the piece.
• link to all related files (chuck, audio files, instructions, scores) : concerto.zip
• documentation of what you tried as of May 11: we have written a basic chuck patch for the headbang orchestra to trigger their samples, a basic patch to modulate noise by headbanging, and a rough outline of what the headbang orchestra will be playing underneath the soloists.

Spaetial

• members: Lekan Wang
• (tentative) title of piece: Spaetial Multithreaded Sound Balls? (this is tentative, right?)
• summary of piece concept: The idea is to have everyone control every speaker by interacting with so-called "Sound Balls" on a common canvas that's projected onto a large screen. Each ball is individually affected by gravity and viscosity, and makes sounds as it floats, bounces, gets near other balls, collides, and dies. There is a server running, and all laptops are clients. When a sound is generated by a ball, the server uses the location of the ball on the canvas to calculate which speakers should play the sound and at what gains. The effect for the audience is that the sounds the balls are making are actually physically moving across the stage. The piece I'm thinking about composing takes advantage of this by tightly integrating space and visual imagery into the composition--various sounds may start on the opposite ends of the stage, but when they combine, they form a whole that has its own character, and can be see on the screen as translucent balls blending with each other.
• link to all related files (chuck, audio files, instructions, scores) : [1]
• documentation of what you tried as of May 11: Completed the networking protocol, and the basic infrastructure for the rest of the code. Currently, you can create a "Basic Ball" and it will make sounds in the appropriate speakers, but I purposefully made the code extremely extensible, so it should be pretty easy now to add in the other features.

Plan for the Future +++Core -- Finish by end of 5/14+++

• Debug polyphony/chuck sporking issue
• Select/delete balls
• Clear all balls
• Variable gravity
• Ball types/Note select
• Continuous and proximity sounds

+++Tier 1 -- Finish by 5/16+++

• Make the server work on not just my laptop...
• Ball transparency
• Automatically kill chuck when quitting
• Route all low-freq signals to laptops with subs connected
• Size of ball inversely proportional to freq
• Color should match the type of sound in some way
• Update speaker selection and gain algorithm so audience member will perceive same sound pressure uniformly across stage

+++Tier 2 -- If time permits+++

• Quantization/Metronome
• Cleaner client view of balls (transparency?)
• Multichannel, Stereo/rotation effects

Group twt

• members: Jorge, Visda, Stephen, Luke, Carr
• (tentative) title of piece: under construction
• summary of piece concept: audience and performers are tweeting, we transform it into an audio visual piece in real time
• link to all related files (chuck, audio files, instructions, scores) : ccrma-gate.stanford.edu/user/j/jorgeh/svn-reps/projects/twttr/
• documentation of what you tried as of May 11:
• Carr: is working on the visualization of the txt using processing
• Jorge and Stephen: are working on server app and also on the twitter web-client capable of posting tweets
• Visda and Luke: are working on sound design

so far the connection between the tweets and chuck files via osc is working. we can manipulate simple sound structures using the receiving osc messages from the server.

Instructions for the slorkers:

• create a twitter account or use your own twitter account if you have one.
• use the #tags we ask for; for example when use #slork in your tweets.

Instructions for the concert:

• set MOTU to -25 dB
• on command line go to the directory slork/groups/2010/visda-jorge-stephen/twttr
• on the command line type ./twt.sh
• keep on tweeting till we ask you to stop

Group

• members:
• (tentative) title of piece:
• summary of piece concept:
• link to all related files (chuck, audio files, instructions, scores) :
• documentation of what you tried as of May 11: