Difference between revisions of "PLOrk2009/MarkCerqueiraFinalProject"
From CSWiki
(→Rebecca's Final Project) |
(→Mark's Final Project: iPhone => ChucK) |
||
| Line 1: | Line 1: | ||
| − | == | + | == iPhone => ChucK == |
| − | A project to natively read in data sent over OSC from the iPhone app | + | A project to natively read in data sent over OSC from the iPhone app OSCemote in ChucK. |
| − | === | + | === Introduction === |
| − | + | This project was conceived when I realized there was a bunch of iPhone/iPod touch apps in the App Store that could send Open Sound Control (OSC) messages to a computer. Many of these apps had patches/programs that connected to music-producing software like Max/MSP, PureData, and Ableton, but nothing for ChucK, so I set out to make one of the many iPhone-OSC apps talk to ChucK natively. I ended up going with OSCemote ($4.99): http://lux.vu/blog/oscemote/ | |
| − | |||
| − | |||
| − | |||
| − | |||
=== This is another subsection === | === This is another subsection === | ||
Revision as of 11:47, 10 May 2009
Contents
iPhone => ChucK
A project to natively read in data sent over OSC from the iPhone app OSCemote in ChucK.
Introduction
This project was conceived when I realized there was a bunch of iPhone/iPod touch apps in the App Store that could send Open Sound Control (OSC) messages to a computer. Many of these apps had patches/programs that connected to music-producing software like Max/MSP, PureData, and Ableton, but nothing for ChucK, so I set out to make one of the many iPhone-OSC apps talk to ChucK natively. I ended up going with OSCemote ($4.99): http://lux.vu/blog/oscemote/
This is another subsection
What to include on your project page
- A description of your project
- Your code
- If it's short, you can make a new page for it like this one
- Or, if there's a lot of it, put it in a .zip file so that people can upload it.
- We suggest: put it in your public_html directory on your network drive, then make a link, e.g. to http://www.princeton.edu/~yourname/yourfile.zip. Let us know if you need any help!
- Instructions on how to run your code
- A sound or video recording of your piece. Going lo-fi and using built-in webcam from another laptop (e.g. PLOrk machine in studio B) is fine. But for audio, if you're using chuck, best to use rec.ck for writing chuck's output directly to a file.
- See directions above on putting it on your network drive and linking to it
