Project 3

The basic programming code that I'll be using for the exhibition for Project 3 is the 'if/then/else' code. We have been asked to find Processing applications on openProcessing and study their use of statements.

http://www.openprocessing.org/visuals/?visualID=7841

This is a sketch using alot of simple if/then statements. They have made it into a 'Choose your own adventure' story used in books like Goosebumps. They use the if statement to let the user choose between two options. They have used many pages and uses the if/else statement to navigate between them.

Code example:

    if (overButton(b3x, b3y, b3w, b3h) == true) {

page = 12;}

    }else if (page == 8) {

http://www.openprocessing.org/visuals/?visualID=23662
 

This is a sketch uses if/else statements to choose a flag from a set. They use the if/else by checking to see which subprocess to run. 'If select <2, then run "scandinavia", else run "flag" etc.. This person uses the code slightly differently to the last as they use it with a random number to check and run the right process, where the other is using it for changing screens based on users decisions.

Code:

 float select = random(14);

   if (select <2){

scandinavia();

} else if (select <4){

england();

} else if (select <6){

france();

} else if (select <8){

germany();

} else if (select <10){

france();

} else if (select <12){

japan();

} else{

libya();

}

http://www.openprocessing.org/visuals/?visualID=26683 




This is a sketch using if statements to change the picture depending on where the mouse is. This is more similar to the first sketch than the last as the if/else statement is based around the users decision. This sketch changes the picture, lighting up a skyline of buildings judging on how far the users mouse is across the sketch. The if statement shows the picture based on the cursor.




Code:




 if ((mouseX > 0) && (mouseX<50)) {

image(lights1, 0,0);

}

else if ((mouseX > 50) && (mouseX < 100)) {

image(lights2, 0,0);

Project 2 Reflection

Reflection Questions:

1. My first hypothesis was that by giving you a topic that is open for your own interpretation, you got the chance to design something that is meaningful to you. 

a. Did you end up designing something that is meaningful to you?

I did . As you may have noticed, I am incredibly interested and influenced my music and musical instruments. This project gave me freedom in which I could use music and sound in the sketch, which was especially fun and exciting for me.

b. Did you like this open-ended task or would you have preferred a clearer defined outcome like in the first project? 

At the moment, I liked the open-ended task better, because I value freedom a lot, which is why maybe I liked this project so much. However, the more freedom I am given, the higher the chance I could sway away from the intended task, so I guess I'll wait to see the grades!

2. My second hypothesis was that by letting you find your own direction you would be motivated to learn the required programming code by yourself (individually). 

a.Was this the case?

In a way. It definately challened me to learn the code, however, I did come across some hiccups but was quickly helped by peers/tutors.

b.How far did you have to rely on the tutors?

I wouldn't say I relied on tutors, but they did give me help I needed.

c. What were the main challenges?

 Sorting out all the code and trying to remain focussed so I don't miss anything out. There was a lot of code in my Project 2 sketch, and a lot of audio files, so it was challenging keeping track of everything.

3. How far are you over-all satisfied with this project?

I wouldn't say I'm completely satisfied. There are a number of things I would change and improve if given the chance, but I'm not necessarily disappointed in my sketch.

4. Any other comments/ suggestions?

Thank you tutors for the help!

 

Project 2 Final

 Project 2 - Transformation

Sketch link:

http://www.openprocessing.org/visuals/?visualID=28073
(loading time is ridonkulous!)

 I, along probably a lot of others, would of loved to make changes to my final, such as better audio quality, smaller files, getting files to play smoother and not sound really jumpy.. etc, but oh well! I have definately learned alot about coding, but clearly have alot more to learn and grasp. This project was fun and challenging, giving us alot of freedom to experiment and create something nice. 

The idea of my sketch is that there are 6 different instrument sounds to choose from, each with a small little interface in which I tried to design to reflect the feel and sound of. Given more time, I would probably have liked to added something more, something more interactive, such as maybe a backing loop track, giving the user something to play to. The presentations really helped me, and I was quite relieved when I got some positive feedback from Ben.

This sketch took a lot of code. Now I mean a lot of code, and there is most likely a shorter method I could have taken, resulting in minimal lines of code, but I have definately learnt from that. Not only is there alot of code, but each note of each instrument track was recorded/created individually. Thats around 200 audio files! Yikes! 

If you'd go back and see my progress, I changed my idea from just one sound with different EQ frequencies to 6 different sounds. I realised that there was very little to no point in the differentiating frequencies, and thought that my sketch would benefit much more from a set of varying sounds/instruments.

I thoroughly enjoyed this project and the challenge and inspiration it gave me.

I would also like to thank Ben, Angela, Luke, and Julian for all the help they gave.

DSDN 142 Project 2 Test Code

http://www.openprocessing.org/visuals/?visualID=27107



There seems to be a pretty annoying error in which it stops when hovering over certain points. Design still needs to be altered to not look so stupid.

DSDN 142 Project 2 Progress

This is just some of the examples of progress I've made in the making of my project.

I used a MIDI controller to create the notes in a music editing software (I used Acoustica Mixcraft), and then proceeded to EQ the sounds, making 6 different types of each pitch. The notes in my project go from E3 to G7, crossing 4 octaves. 

After each sound was exported from Mixcraft, I used Audacity to shorten the sound files.

Project 2 concept

 

This is the main screen you will see without clicking anything. Extremely simple, nothing going on.
Dark red fade to light red at the top.

 

This is the structure of the program (you don’t see this). There is a grid, and in each space holds a different sound. From left to right the pitches are in the E Aeolian mode, or E minor scale. Going from bottom to top is the frequency modulation.  For example, the right bottom corner box is E, with a very ‘bassy, low’ frequency. The top right corner is still the same E pitch, but with a much higher, sharper frequency. 

 

When you click on the screen, a sound will play, continuously until you take your finger off the click. When the mouse button is held down, a visual pattern will circulate around the mouse. The pictures don’t show the proper design, but are just an example.

When you have the mouse clicked down, the sound will continue to play. You are able to click and drag the curser around the screen, changing the modulation and pitch as you enter different boxes on the grid. Although you can’t see these boxes, you will have to experiment yourself.