.....Prototype might be strong word.....
http://www.youtube.com/watch?v=zy7it7ZGE4s
Sorry for the sidewaysness and low level audio.
Tuesday, March 9, 2010
Friday, March 5, 2010
Monday, March 1, 2010
Phototransistor
Here some random video showing how to use a phototransistor. It works even simpler than the photo-resistor we all know and love not to mention it's really really cheap ($.14 cents). Think of it like a switch activated by light (infrared in this case although other types are available) Super simple and way affordable. Can be made into a switch type device for Arduino easy.
Friday, February 26, 2010
project update - signal flow with super fancy graphic
So here's the overview of the signal flow for our final project installation. As you can see by my immaculate diagram I spared no expense in elaborately detailing and conveying the specifics.....

So here's what's going on, what technology we have ready to go, and what technology we need to finish: Input (on the left symbolized by a keyboard and theremin) will be best case scenario proximity detection using capacitance sensing circuit just like a theremin. (simplist theremin schematic I could find using 4093 quad nand and 4077 quad xnor or 4070 quad xor)

I hope to test circuits this weekend when I can get to Norvak for parts when they are open. Since this technology isn't built or tested yet we need a good backup so we could use Colin's giant proximity sensing pad thing which puts out midi or any other device that puts out midi like a keyboard or anything really. It would be easy enough to build arduino devices that do this using phototransistors(much cheaper than photoresistors it turns out). This info will go to a midi to usb converter (anybody have one of these?) into a computer(middle part of diagram in dotted lines). On the computer software called Vixen (with the midi plug in) will take in the midi and send out controls via the serial port (may need a usb to old fashion serial here - need to some research) to the renard ss16 controllers(right side of diagram - on their way according to usps). The controllers will then have Christmas tree lights plugged into them. Additionally in the computer, MaxMsp will be listening to the incoming midi and generating music accordingly. Sooooooooooooo left to do is testing building some sort of controller (Clay) get midiUsb interface, usb,serial interface, program vixen (Clay) and Max (Iris) solder up and test and refine. Is anyone actually reading this far? It was a dark and stormy night. Suddenly, a shot rang out. The maid screamed.....
update.......
I couldn't make the theremin circuit above work :-( I did make this other one work (see video) but in order to use it in our project it would need some way to change the frequency into a control voltage. The paia theremax does this but with a pretty heavy parts count and since we need this circuit 16 times over (for 16 separate inputs) the complexity just got toooooo much. So I'm thinking were abondoning capacitance based proximity sensing and figure out some other way of sensing user movement. The idea is to keep it easy so people can walk right up to it and immediately cause an interaction without having to figure too much out.

So here's what's going on, what technology we have ready to go, and what technology we need to finish: Input (on the left symbolized by a keyboard and theremin) will be best case scenario proximity detection using capacitance sensing circuit just like a theremin. (simplist theremin schematic I could find using 4093 quad nand and 4077 quad xnor or 4070 quad xor)

I hope to test circuits this weekend when I can get to Norvak for parts when they are open. Since this technology isn't built or tested yet we need a good backup so we could use Colin's giant proximity sensing pad thing which puts out midi or any other device that puts out midi like a keyboard or anything really. It would be easy enough to build arduino devices that do this using phototransistors(much cheaper than photoresistors it turns out). This info will go to a midi to usb converter (anybody have one of these?) into a computer(middle part of diagram in dotted lines). On the computer software called Vixen (with the midi plug in) will take in the midi and send out controls via the serial port (may need a usb to old fashion serial here - need to some research) to the renard ss16 controllers(right side of diagram - on their way according to usps). The controllers will then have Christmas tree lights plugged into them. Additionally in the computer, MaxMsp will be listening to the incoming midi and generating music accordingly. Sooooooooooooo left to do is testing building some sort of controller (Clay) get midiUsb interface, usb,serial interface, program vixen (Clay) and Max (Iris) solder up and test and refine. Is anyone actually reading this far? It was a dark and stormy night. Suddenly, a shot rang out. The maid screamed.....
update.......
I couldn't make the theremin circuit above work :-( I did make this other one work (see video) but in order to use it in our project it would need some way to change the frequency into a control voltage. The paia theremax does this but with a pretty heavy parts count and since we need this circuit 16 times over (for 16 separate inputs) the complexity just got toooooo much. So I'm thinking were abondoning capacitance based proximity sensing and figure out some other way of sensing user movement. The idea is to keep it easy so people can walk right up to it and immediately cause an interaction without having to figure too much out.
Tuesday, February 23, 2010
Project Update - Christmas tree lights
Our original idea was to have Christmas tree lights strung about and you could play them like a giant harp. (the hand held controller is our backup idea in case this is impossible) Still not sure how to trigger them (capacitance?(would be ideal) light sensors?(not as ideal but will work)) but the animated their display part of this is going to work (pending receiving parts in a timely fashion) It turns out there is a community of people who put on Christmas tree decorated lawn shows shows that blink/flash/sequence the lights to music. This is done through controller packs similar to DMX-512 stage show lighting packs (the kind used in stadium concerts, etc) but less powerful (2 amps per channel - plenty for a string of lights but not for a simulated volcano) and waaaay cheaper since they are a DIY project. So I finally found someone selling the PCB boards off season and Mouser has the parts and we'll hook it up to be controlled by whatever we feel like (that can spit out a serial signal). The specific board I decided on (it was available and did what we needed) is the Renard 16SS -- 16 channel, onboard SSR (solid state relays (just triacs I think))
Some interesting links:
Good Overview:
http://www.dv-fansler.com/Computer%20Lights/computer_lights.htm
General Wiki:
http://www.christmasinshirley.com/wiki/index.php?title=Main_Page
There is a forum http://doityourselfchristmas.com/forums/index.php , however the defaults display modes on the forum make it completely confusing for a newbie. (I prefer the classical pronunciation) as everything seems to display backwards (latest post first - so you have to go to the last post of any thread to follow a conversation)
The other major forum:
http://diylightanimation.com/index.php?board=21.0
Some interesting links:
Good Overview:
http://www.dv-fansler.com/Computer%20Lights/computer_lights.htm
General Wiki:
http://www.christmasinshirley.com/wiki/index.php?title=Main_Page
There is a forum http://doityourselfchristmas.com/forums/index.php , however the defaults display modes on the forum make it completely confusing for a newbie. (I prefer the classical pronunciation) as everything seems to display backwards (latest post first - so you have to go to the last post of any thread to follow a conversation)
The other major forum:
http://diylightanimation.com/index.php?board=21.0
Final Project Proposal
What to Christmas tree lights, theremins, lasers, and harps have in common? The final project of course. Iris and I are collaborating on building an interactive music instrument that could best be described as a Christmas tree light harp. It's a little soon to tell how this will eventually evolve into a final project but here is the initial pitch we came up with (also posted on Iris' blog):
Our goal for the final project is to build a interactive instrument which can switch between different sound timbres and background environment sound texture responding to human body gesture interacting with LED light sensors.
We will be constructing a musical instrument interface to send data and control parameters to MaxMSP/Jitter which will actually create the music. Our controller ideas data flow are influenced by Kevin Patton and Carmon Montoya's workshop but hopefully will expand upon that making a system, that if you chose to and had the skill, you could play traditional familiar music with scales, notes, chords and such.
For the sound part, once Max receive a trigger from each individual LED light sensor. It will generate different banks of sound as well as background sound texture using MAX/MSP/Jitter. some specific object such as mono reverb and different types of filters which will be external max objects will be applied for the sound effects. Further more, once we are able to control the sensor confidently, we will try to create a piece based on human body gesture which can be interpret in to music sequenced in Logic.
The controller itself will be a freestanding battery controlled wireless arduino based device but using a gyroscope in addition to an accelerometer to more accurately track movement and allowing us to capture yaw (spin around a y axis) data which an accelerometer alone cannot do. Furthermore logic to decipher movement will be placed on the arduino chip making it a more universal controller. For example not only will 3 axis rotation data be available but imagine playing air drums that alter the instrument and or note to be triggered depending on the angle the controller is at when the initial strike starts. The controller itself will have some traditional button like inputs for finger input control except they will be pressure sensors allowing us a range of data depending on how hard we 'chord' the input. This aspect may be very similar to Kevin and Carmen's fossile input - I'm not exactly sure how there device worked. (This is our backup idea incase the thermin/harp/christmastree lights won't work out)
Time and resource and technology permitting we will investigate other non-traditional forms of electronic input - specifically proximity detection through capacitive circuits like like a theremin but using ordinary Christmas tree lights.
http://www.imagineeringezine.com/e-zine/capacitance-11.html
http://www.discovercircuits.com/C/capacitance-sw.htm
http://www.discovercircuits.com/DJ-Circuits/3vtchmom2.htm
http://users.otenet.gr/~athsam/touch_dimmer.htm
http://www.epanorama.net/links/lights.html#dimrouch fun sight to get lost on
http://www.akustische-kunst.org/maxmsp/
http://web.media.mit.edu/~tristan/maxmsp.html
Our goal for the final project is to build a interactive instrument which can switch between different sound timbres and background environment sound texture responding to human body gesture interacting with LED light sensors.
We will be constructing a musical instrument interface to send data and control parameters to MaxMSP/Jitter which will actually create the music. Our controller ideas data flow are influenced by Kevin Patton and Carmon Montoya's workshop but hopefully will expand upon that making a system, that if you chose to and had the skill, you could play traditional familiar music with scales, notes, chords and such.
For the sound part, once Max receive a trigger from each individual LED light sensor. It will generate different banks of sound as well as background sound texture using MAX/MSP/Jitter. some specific object such as mono reverb and different types of filters which will be external max objects will be applied for the sound effects. Further more, once we are able to control the sensor confidently, we will try to create a piece based on human body gesture which can be interpret in to music sequenced in Logic.
The controller itself will be a freestanding battery controlled wireless arduino based device but using a gyroscope in addition to an accelerometer to more accurately track movement and allowing us to capture yaw (spin around a y axis) data which an accelerometer alone cannot do. Furthermore logic to decipher movement will be placed on the arduino chip making it a more universal controller. For example not only will 3 axis rotation data be available but imagine playing air drums that alter the instrument and or note to be triggered depending on the angle the controller is at when the initial strike starts. The controller itself will have some traditional button like inputs for finger input control except they will be pressure sensors allowing us a range of data depending on how hard we 'chord' the input. This aspect may be very similar to Kevin and Carmen's fossile input - I'm not exactly sure how there device worked. (This is our backup idea incase the thermin/harp/christmastree lights won't work out)
Time and resource and technology permitting we will investigate other non-traditional forms of electronic input - specifically proximity detection through capacitive circuits like like a theremin but using ordinary Christmas tree lights.
http://www.imagineeringezine.com/e-zine/capacitance-11.html
http://www.discovercircuits.com/C/capacitance-sw.htm
http://www.discovercircuits.com/DJ-Circuits/3vtchmom2.htm
http://users.otenet.gr/~athsam/touch_dimmer.htm
http://www.epanorama.net/links/lights.html#dimrouch fun sight to get lost on
http://www.akustische-kunst.org/maxmsp/
http://web.media.mit.edu/~tristan/maxmsp.html
Sunday, February 14, 2010
Hardware Computing/Wireless Instrument Workshop
Kevin Patton & Carmen Montoya Electronic Music and Hardware workshop University of Oregon Jan 27 2010
In this very cool workshop from artists Kevin Patton and Carmen Montoya we got to build a wireless musical instrument setup using a jeenode (essentially an Arduino) and MaxMSP/Jitter software. I got a variety of R2D2 type noises but if you were good you good conceivably create music just like you would any traditional musical instrument. (see video in previous post for final result)
At the core is an arduino like controller called a Jeenode which uses the AtMega328 Chip and has an onboard radio system (like an xbee but cheaper) to relay data. Attached to Jeenode was 3 axis accelerometer (we only used 2) and a 9V battery making it completely wireless.

On the receiving end was a usb thumb drive type device called a Jeelink which is also a programmable arduino w/radio setup which was is used to receive the data from the jeenode (That's 2 arduino devices total in this setup)

From their accelerometer data came in as a regular serial information which was routed to MaxMsp/Jitter. 2 Max patches were written to accept and process this information into sound. (these are available online) One creates an FM synthesis simulation tone and the other controlles sample playback. You could use both patches simultaneously if you wanted for complex tones. The end result for me was much fun making a whole lot of sci fi droid like noises. A bit of skill and practice would be required to start creating intentionally thought out music: The Music dept got to keep 4 of the devices and digital arts got to keep the other 4 so they are available for our use if you wanted to take a crack at some of this or modify it for your own purposes. Here's the details on how to get it all up and running.
You will need:
1)The jeenode/jeelink pair plus a programmng bub (more on the bub later) available from digital art dept which I'm in and most likley the music dept which I'm not in. Alternately you can buy them from Modern Device however you need to also pick up an accelerometer and 9 volt battery + battery holster and some sort of on/off switch.
2) Arduino compiler V1.7 (or better) available free
3) MaxMsp/Jitter 5.1 free 30 day demo (if you have already used up your demo already you can still use the runtime environment to play the patches but not edit them) [cycling 74 offers some steep discounts for students if you're interested in buying like around $200 or something]
4) Various support files available here (HardwareWorkshop-docs.zip) from Kevin and Carmen (if no longer available email me [link at end] I still have my copy - anyone know how to upload a file to a blog?)
5) Mac of some sort (PC versions of all these files actually exist and should work just fine but you're own your own when it comes to the usb/serial driver files. I'm sure they exist somewhere on the net)
Configuration
Step 1: Jeenod/Stick configuration. This is 90% of the setup and if you are using the ones left for the UofO they are already configured so you don't have to worry about any of this and skip to running the software unless you want to modify anything or are curious how this works.
Assemble the device: Attach the power shield just straight on top of the Jeenode as the pins slide in to the recepticles below. Pay attention to orientation so you don't install it upside down. Repeat same exact thing with accelerometer shield on lower pin receptacles. (This makes perfect sense once your holding it in your hand - see the pics for a guide as what to expect. If confused on orientation make sure the data lines goto DIO (digital in out) and power goes to 3.3v (positive) and ground). If you purchased these items yourself you may have to assemble the shields out of some header strips and perf board or come up with some other way of holding all the parts together. Final result will look something like this.......






Step 2 program the device: Before installing/launching arduino, install the FTDIUSBSerialDriver_v2_2_10.dmg driver (necesarry to get arduino serial data into the computer) which is included in the HardwareWorkshop-docs.zip and also possibly in the arduino install dmg
This driver won't work with earlier version of arduino so you will need to make sure you have at least the 1.7 arduino environment installed. Drag the arduino program to your applications (or wherever you want it locally) folder. Next Right click (cntrl click) on the arduino app and select show package contents. Navigate to Arduino > Contents > Resources > Java > Hardware > Libraries>Ports (create if necesarry)
Copy the Files from HardwareWorkshop-docs.zip>JeeNodeLibraries>Ports to the Arduino Ports folder opened above
Next copy the Files from HardwareWorkshop-docs.zip>JeeNodeLibraries>RF12 to the Arduino > Contents > Resources > Java > Hardware > Libraries>RF12 folder (create if necesarry)
I believe these are support for the radio interfaces installed on the jeenodes.
-------this part on needs editing and correcting ---going from memory and notes right now -----
Load the configuration code (note, this is not the final code that runs on the instrument trasnmitter arduino or the usb receiver arduino. This is just the code that allows us to configure it all and pair the controller device to the reciever device so that multiple arduino instruments can be run at the same time without interfering with each other )
Turn on the Jeenode.
Plug the jeenode controller into the bub and the bub into the usb port. (Note, UofO may not have gotten the bub in which case you can't program the jeenodes directly. However, if you are clever you might be able to pop out the atmega328 chip, stick it in a compatible arduino - and load up the code from there - haven't tried this though)

Select the correct serial device from the arduino>>tools >Serial Port >> ??? (usually the top one will have tty in there somewhere)
select Tools > Board > atmega328 (the top one)
press the upload button and wait a few moments for the code to upload
Once uploaded, press the serial monitor button - a window appears. If it's jibberish change the baud rate to 38400. If regular text doesn't appear, change it to 56700
Now we manually configure the device by sending text the thre serial monitor.
pick a unique letter for the groupId (jeenode pairing id)(using 'K' for this example but anything works as long as it isn't already in use by other jeenode pairs - not an issue if you are only using one jeenode/jeelink set)
enter : iK
for some reason it doesn't always take the first time so repeat all commands twice
enter : iK
set the radio to the correct frequencie (915mhz)
enter: b9
repeat
enter: b9
set the group number (using 50 here arbitrarily)
enter: g50
enter: g50
see your final config by entering k. the config prints out NodeId,GroupId,Console
once configured you can upload the real code. Open the ReadAllPorts_Send.pde file and press the upload button. Once the lights stop flashing the transmitter is done.
Next configure the receiving device. Unplug the bub and the device and plug in the jeelink device and repeat the exact same steps as above using the configuration code and plugging in the same node,group,and frequencie parameters numbers except for the device node make sure it has a different number ex transmitter is 1 receiver is 2. check the final configuration by clicking k
-------------above part needs editing and correcting------wil do soon I promise---------
Now open the ReceiverCode.pde file and upload it to the jeelink
Finally, Open the serial monitor,and check to see if data in coming in changes as you rotate the controller. Hopefully this works, if so congratulations! you are ready to make some noise
Running the software
Make sure Arduino is closed and then open Max/SerialIn-SimpleFM.maxpat with MaxMsp/Jitter or the MaxMSP/Jitter Runtime environment.
Select the corect serial device in the yellow part one box of the max patch
Click the 'turn on' button to activate serial input
click the speaker button at the bottom and adjust the volume slider to desired volume
notice the an1-an4 text fields show changing data when controller is moved around
adjust the presets/carrier,modulation,harmonocity to alter the tone
For sample based noises, keep the previous maxpat file open and running and also open Max/SampleScrubber.maxpat
Drag and drop a folder of any kind of mp3s to use as sample sources into the sample area, click all (or some for different controll effects) of the crosshair button controls at the top and click the play button and adjust volume. (some weird fiddling and volume adjustments and other controls in the max patches are usually necessary here - just keep tweeking it till you here both going simultaneously. For some reason it does't work perfectly instantly at this point but will eventually if you keep fiddling -I'm not a max person, not quite sure why it does this or specifically what fixes it other than just 'random fiddling' - if someone has a better explenation of any of this - email me)

You should be getting sound at the point, start playing with the controls and making music.
If you're so inclined you can program your own max patches to do whatever you want sound/visual wise with the incoming serial data from the jeenode controllers. The software on the jeenode transmitter simply relays whatever inputs it is receiving on it's 4 ports so you could use any kind of data you can plug into the jeenode like buttons, photoresistor values, bend sensors, pressure sensors, proximity sensors, potentiometers, etc etc.
Other software than can use the serial information from the jeenodes includes but is not limited to: processing and isadora
That's it - email me with corrections/questions/whatever - Thanks Clay ckent@youoregun.edu (misspelled)
In this very cool workshop from artists Kevin Patton and Carmen Montoya we got to build a wireless musical instrument setup using a jeenode (essentially an Arduino) and MaxMSP/Jitter software. I got a variety of R2D2 type noises but if you were good you good conceivably create music just like you would any traditional musical instrument. (see video in previous post for final result)
At the core is an arduino like controller called a Jeenode which uses the AtMega328 Chip and has an onboard radio system (like an xbee but cheaper) to relay data. Attached to Jeenode was 3 axis accelerometer (we only used 2) and a 9V battery making it completely wireless.

On the receiving end was a usb thumb drive type device called a Jeelink which is also a programmable arduino w/radio setup which was is used to receive the data from the jeenode (That's 2 arduino devices total in this setup)

From their accelerometer data came in as a regular serial information which was routed to MaxMsp/Jitter. 2 Max patches were written to accept and process this information into sound. (these are available online) One creates an FM synthesis simulation tone and the other controlles sample playback. You could use both patches simultaneously if you wanted for complex tones. The end result for me was much fun making a whole lot of sci fi droid like noises. A bit of skill and practice would be required to start creating intentionally thought out music: The Music dept got to keep 4 of the devices and digital arts got to keep the other 4 so they are available for our use if you wanted to take a crack at some of this or modify it for your own purposes. Here's the details on how to get it all up and running.
You will need:
1)The jeenode/jeelink pair plus a programmng bub (more on the bub later) available from digital art dept which I'm in and most likley the music dept which I'm not in. Alternately you can buy them from Modern Device however you need to also pick up an accelerometer and 9 volt battery + battery holster and some sort of on/off switch.
2) Arduino compiler V1.7 (or better) available free
3) MaxMsp/Jitter 5.1 free 30 day demo (if you have already used up your demo already you can still use the runtime environment to play the patches but not edit them) [cycling 74 offers some steep discounts for students if you're interested in buying like around $200 or something]
4) Various support files available here (HardwareWorkshop-docs.zip) from Kevin and Carmen (if no longer available email me [link at end] I still have my copy - anyone know how to upload a file to a blog?)
5) Mac of some sort (PC versions of all these files actually exist and should work just fine but you're own your own when it comes to the usb/serial driver files. I'm sure they exist somewhere on the net)
Configuration
Step 1: Jeenod/Stick configuration. This is 90% of the setup and if you are using the ones left for the UofO they are already configured so you don't have to worry about any of this and skip to running the software unless you want to modify anything or are curious how this works.
Assemble the device: Attach the power shield just straight on top of the Jeenode as the pins slide in to the recepticles below. Pay attention to orientation so you don't install it upside down. Repeat same exact thing with accelerometer shield on lower pin receptacles. (This makes perfect sense once your holding it in your hand - see the pics for a guide as what to expect. If confused on orientation make sure the data lines goto DIO (digital in out) and power goes to 3.3v (positive) and ground). If you purchased these items yourself you may have to assemble the shields out of some header strips and perf board or come up with some other way of holding all the parts together. Final result will look something like this.......
Step 2 program the device: Before installing/launching arduino, install the FTDIUSBSerialDriver_v2_2_10.dmg driver (necesarry to get arduino serial data into the computer) which is included in the HardwareWorkshop-docs.zip and also possibly in the arduino install dmg
This driver won't work with earlier version of arduino so you will need to make sure you have at least the 1.7 arduino environment installed. Drag the arduino program to your applications (or wherever you want it locally) folder. Next Right click (cntrl click) on the arduino app and select show package contents. Navigate to Arduino > Contents > Resources > Java > Hardware > Libraries>Ports (create if necesarry)
Copy the Files from HardwareWorkshop-docs.zip>JeeNodeLibraries>Ports to the Arduino Ports folder opened above
Next copy the Files from HardwareWorkshop-docs.zip>JeeNodeLibraries>RF12 to the Arduino > Contents > Resources > Java > Hardware > Libraries>RF12 folder (create if necesarry)
I believe these are support for the radio interfaces installed on the jeenodes.
-------this part on needs editing and correcting ---going from memory and notes right now -----
Load the configuration code (note, this is not the final code that runs on the instrument trasnmitter arduino or the usb receiver arduino. This is just the code that allows us to configure it all and pair the controller device to the reciever device so that multiple arduino instruments can be run at the same time without interfering with each other )
Turn on the Jeenode.
Plug the jeenode controller into the bub and the bub into the usb port. (Note, UofO may not have gotten the bub in which case you can't program the jeenodes directly. However, if you are clever you might be able to pop out the atmega328 chip, stick it in a compatible arduino - and load up the code from there - haven't tried this though)
Select the correct serial device from the arduino>>tools >Serial Port >> ??? (usually the top one will have tty in there somewhere)
select Tools > Board > atmega328 (the top one)
press the upload button and wait a few moments for the code to upload
Once uploaded, press the serial monitor button - a window appears. If it's jibberish change the baud rate to 38400. If regular text doesn't appear, change it to 56700
Now we manually configure the device by sending text the thre serial monitor.
pick a unique letter for the groupId (jeenode pairing id)(using 'K' for this example but anything works as long as it isn't already in use by other jeenode pairs - not an issue if you are only using one jeenode/jeelink set)
enter : iK
for some reason it doesn't always take the first time so repeat all commands twice
enter : iK
set the radio to the correct frequencie (915mhz)
enter: b9
repeat
enter: b9
set the group number (using 50 here arbitrarily)
enter: g50
enter: g50
see your final config by entering k. the config prints out NodeId,GroupId,Console
once configured you can upload the real code. Open the ReadAllPorts_Send.pde file and press the upload button. Once the lights stop flashing the transmitter is done.
Next configure the receiving device. Unplug the bub and the device and plug in the jeelink device and repeat the exact same steps as above using the configuration code and plugging in the same node,group,and frequencie parameters numbers except for the device node make sure it has a different number ex transmitter is 1 receiver is 2. check the final configuration by clicking k
-------------above part needs editing and correcting------wil do soon I promise---------
Now open the ReceiverCode.pde file and upload it to the jeelink
Finally, Open the serial monitor,and check to see if data in coming in changes as you rotate the controller. Hopefully this works, if so congratulations! you are ready to make some noise
Running the software
Make sure Arduino is closed and then open Max/SerialIn-SimpleFM.maxpat with MaxMsp/Jitter or the MaxMSP/Jitter Runtime environment.
Select the corect serial device in the yellow part one box of the max patch
Click the 'turn on' button to activate serial input
click the speaker button at the bottom and adjust the volume slider to desired volume
notice the an1-an4 text fields show changing data when controller is moved around
adjust the presets/carrier,modulation,harmonocity to alter the tone
For sample based noises, keep the previous maxpat file open and running and also open Max/SampleScrubber.maxpat
Drag and drop a folder of any kind of mp3s to use as sample sources into the sample area, click all (or some for different controll effects) of the crosshair button controls at the top and click the play button and adjust volume. (some weird fiddling and volume adjustments and other controls in the max patches are usually necessary here - just keep tweeking it till you here both going simultaneously. For some reason it does't work perfectly instantly at this point but will eventually if you keep fiddling -I'm not a max person, not quite sure why it does this or specifically what fixes it other than just 'random fiddling' - if someone has a better explenation of any of this - email me)

You should be getting sound at the point, start playing with the controls and making music.
If you're so inclined you can program your own max patches to do whatever you want sound/visual wise with the incoming serial data from the jeenode controllers. The software on the jeenode transmitter simply relays whatever inputs it is receiving on it's 4 ports so you could use any kind of data you can plug into the jeenode like buttons, photoresistor values, bend sensors, pressure sensors, proximity sensors, potentiometers, etc etc.
Other software than can use the serial information from the jeenodes includes but is not limited to: processing and isadora
That's it - email me with corrections/questions/whatever - Thanks Clay ckent@youoregun.edu (misspelled)
Wednesday, January 27, 2010
Electronic Music/Hardware Workshop footage
Hardware computing/Wireless instrument workshop
Jan 27 2010
Kevin Patton & Carmen Montoya
Jan 27 2010
Kevin Patton & Carmen Montoya
Sorry for the cell phone video quality.
I took notes on how all this works. Stay tuned for more details....
Monday, January 11, 2010
Subscribe to:
Posts (Atom)