mac online apple blackjack

Processing Google Streetview

Coding is completely new to me, and trying to figure out Processing was like trying to learn a new language. This Google Streetview code took a little while for me to get my head around, but after what felt like hours of staring at what seemed like random sequences of symbols on the screen I finally got there.

So what was I trying to achieve? Tom set the CAP students a task of trying to get as close as possible to a location in Google Streetview, then create a 360 view of that location using Processing. My location? Area 51. I am not one of those people who are massively into aliens, space or anything else related to that particular theme. But I do like to know things that i am not supposed to, and the intrigue of a mysterious location which houses who knows how many secrets that we the general public will never find out is something that really stands out to me. I decided on this location to see how close Google can get me to those secrets.

The answer is, not very close.

I can get to the main highway that runs adjacent to the facility. I can get to several viewing points in the Nevada wastelands. There is no major security gate, there is miles and miles of land.

I chose one of the locations on the highway, closest to the turn off to the facility. This is where Processing left me stumped. I loaded the co-ordinates into the code, set it to how it should work, pressed run and came across a frozen still of the location. Something isn’t right, I thought. So I tried it again… And again… Hoping for better results. Madness, I know. Rather than being impatient, like the first few times, I waited, just to see whether or not the full 360 would eventually load.

It did.

Kind of.

Rather than having a full 360, I had a long section of one still, and then a half loop of the rest of the scene. Okay, so that’s progress.

After a little while of playing around, trying to see if I could make it work, I decided to try a different set of co-ordinates. One of the viewing stations, equidistant to my original set of co-ordinates. Cautiously optimistic, I loaded them into the code and this time it worked. I had a full 360 view of my location. After a little bit of investigating I found that the original co-ordinates did not supply all of the images needed to make the full 360 loop, which is why my first attempt was so unsuccessful. This put my mind to rest, it was not me failing to understand the code.


I will upload videos later showing the two different co-ordinates and their results.

Ghibli FanFiction Stage 2


Working with Kinect in Processing (supervised by Tom Schofield), and he now finally can listen to my hand’s response. You rock! This is what I like about you ススワタリ, always hard working.

I will going to capture and send you to Pure Data in the next Stage. You will carry the X and Y coordinates for me, won’t you?  Trust me, you’ll be fine. All you have to do is to bang a Bang in Pure Data, then you can meet all your pals there in the boiler room. This time Kamaji won’t be there so don’t worry.

Alright. Good luck to both of us.

Project Work: tests with tint()

Tint function using the mouse position to control the alpha channel and thus the blending.

here the alpha is controlled by data from the distance sensor, it’s not smooth and the readings are really wild switching from 10 to 100 and back. Either the sensor is inaccurate or I’m doing something wrong with the Arduino sketch.

Project Work: quick and simple line in visualization with Processing


Something to keep me distracted while doing research.

import ddf.minim.spi.*;
import ddf.minim.signals.*;
import ddf.minim.*;
import ddf.minim.analysis.*;
import ddf.minim.ugens.*;
import ddf.minim.effects.*;

Minim minim;
AudioInput in;
FFT fft;

void setup()
size( 1024, 480 );
minim = new Minim( this );
in = minim.getLineIn(Minim.STEREO, 1024);
fft = new FFT( in.bufferSize(), in.sampleRate() );
strokeWeight( 1 );
void draw()
background( 0 );
translate( 0, height/2 );
// right channel
stroke( 255, 0, 0 );
for ( int i = 0; i < in.right.size(); i++ ) {
float y = in.right.get( i ) * 220;
point( i, y );
// left channel
stroke( 255 );
for ( int i = 0; i < in.left.size(); i++ ) {
float y = in.left.get( i ) * 220;
point( i, y );
void stop()

☹ + ♫ = ☺


My Demo ここ:


My bedroom became a discotheque by running a song loop for the whole night with this test. Only one RGB led was found on the kit, so could not make a trivalent blinking try.

This little board opens a whole imaginary world to creative people for sure. Wiring is the most time consuming part maybe, but once we think of the result we are going to see, we will almost forget who we are. In fact, we are no-one in this world… So… shut the light off… It is time for some music with LEDs.

Arduino to Processing


I identified two possible projects for HSS8120, but still need further research un.til deciding which way to go. Learning to send data, sensor data, from Arduino to Processing is going to be part of either projects and thinking about the live event as well. The following is a simple test, sending and visualizing  data from a Piezo disk.

Web Scraping with Processing

After our workshop with Tom on Webscraping we were asked to go and try scraping some data ourselves. We looked at writing a scraper in Python, which I found a little hard to get my head around. As I have worked in Processing before it seemed logical to try and replicate a scraper using P5.

The following code can be inout into Processing and used to scrape the HTML data from a given URL and output a number based on the amount of lines scraped.

String lines[] = loadStrings(“”);  //Input chosen URL here
void draw(){
println(“there are ” + lines.length + ” lines”); //This states “There are X lines”
for (int i = 0 ; i < lines.length; i++) { //following counts ‘i’ for each line scraped
  println(lines[i]); //Prints ‘i’ after counted
delay(1000); //Time delay for scraper to run

My idea for the use of this webscraper would be to be used on a live updated webpage, hence the addition of the timer (delay) at the bottom instead of a stop command.

Practice Project 03: Simple Processing Alterations (Pulse Sensor)

Screen Shot 2014-06-20 at 00.15.43

After viewing a quick video on the basics of processing, I changed some of the RGB values, locations, and sizes of the properties within each window.

Mouse function…

Tracing most recent 20 lines…

The above images have been altered from the poincare plot graph (below) which records heart rate variability.

Practice Project 02: Initial Pulse Sensor Testing (Arduino and Processing)


First, I downloaded the latest pulse sensor amped code and did a quick test to see if the sensor was working. It was! Here, it was important to temporarily cover the back of the sensor with a velcro dot, to temporarily protect the mechanisms on the back. It was also important to place a protective sticker onto the the front of the sensor to keep out natural oils from the fingertip.

Click to view the pulse working on an Arduino Uno board…

For quickness, I just plugged the sensor straight into the uno board to affect the board’s built in light – the video shows it blinking in time with my pulse. There are all sorts of experiments that can be performed with arduino and the sensor, but due to limited time I will focus on digital processing for the moment, and next connecting the pulse sensor to pure data via firmata. The sensor is clever – it works by infrared, detecting the amount of light with the blood movement in your finger tip, so that when the heart beats less light is detected and so forth.

Next I ran the processing code. Here, it was important to make sure Arduino was communicating with processing. At first, it wasn’t. This was due to, I discovered, the incorrect serial port number in the code. The code was set to port 0, but the serial port in use by Arduino was port 7 – the way to recognise this is by counting the number of ports listed at the bottom of the processing window. However, I changed this back and forth for a few hours, and still nothing. I tried a few different ways and discovered that Arduino must be set to the correct baud rate, in this case 115200, and uploaded onto the board at this correct baud rate before it will communicate with Processing. Still, after this it wasn’t working. Then I remembered – a lesson I learned in first semester – that one of my USB ports in my Mac doesn’t work with Arduino. So I moved it to a new port – and it worked.

Initially, I tried it on my own pulse, but Jaejun was passing by and came to have a look – so we tried it on his pulse. The above screenshots are of Jun’s pulse, who had been running to Culture Lab so his pulse was still quite high – the readings are 91 and 100 but I’m not completely sure how accurate the sensor is. It seems accurate enough though.

After Jaejun, I tried it on my own pulse again – which was super low (below). Perhaps this was an incorrect reading in contrast with Jun’s fast pulse, but perhaps it wasn’t – I was really tired!

So, after I realised it was working, I permanently sealed the back of the sensor with a protective film – as instructed by the guide – using hot glue (below). Squeezing a blob of hot glue onto the back of the sensor and pressing it against the sticky side of tape allows the whole surface to get covered. Once the glue has dried, the tape is able to be peeled off. After this, the excess glue can be trimmed, and the velcro dot put onto the back of the glue. Then, the sensor is ready to be stuck to the velcro strap so that it can be attached to the finger.

Click to see the pulse sensor working via processing…

After trying the sensor on the earlobe, too, I decided the fingertip definitely proved to detect the pulse more easily – so I chose not to glue the ear clip onto the sensor. This was, too, because in an exhibition context, some viewers may be wearing earrings. The above video shows a reading of my pulse (less tired) which is a normal reading around 70. The next step is to do some experiments with code in processing.

Practice Project 01: Getting Started With Pulse Sensor Amped

Screen Shot 2014-06-17 at 14.32.15

Arduino code:

Processing code: