Difference between revisions of "User:Jerryestie"

From DigitalCraft_Wiki
Jump to navigation Jump to search
 
(115 intermediate revisions by 2 users not shown)
Line 1: Line 1:
==Main Information==
+
=Main Information=
 
[[Category:Student Information]]
 
[[Category:Student Information]]
 
Jerry Estié
 
Jerry Estié
Line 6: Line 6:
  
 
0902472@hr.nl
 
0902472@hr.nl
==Image Research==
 
[[Category:Image Research]]
 
=====Pre-Industrial=====
 
[[File:A4 Images_ok2.jpg|thumb|Pre-Industrial]]
 
A very common technique, the needle and thread.
 
=====Industrial=====
 
[[File:A4 Images_ok3.jpg|thumb|Industrial]]
 
For the industrial period I chose Barthélemy Thimonnier. I found him and his sewing machines interesting because he was at the forefront of the industrial revolution with his machines. However, he became a target for workers in the sewing industry, who were afraid of the competition. In the end, his machines never became common and the man died poor. We think of the industrial revolution as this thing that just sort of 'happened' because now we look back at the succes. I just find these little footnotes in history more interesting.
 
=====Contemporary=====
 
[[File:A4 Images_ok4.jpg|thumb|Contemporary]]
 
Just like the first image, I kept it simple in a way. When looking for modern stitching techniques in shops or other places you will still find sewing machines. They're still as big a part of modern sewing technologies as ever.
 
=====Sigrid Calon=====
 
[[File:A4 Images_ok5.jpg|thumb|Het Kanten Huis]]
 
Sigrid Calon is a personal favorite of mine, coming from a textile-oriented education she eventually made the step over to graphic design. However, her designs are still based on her previous embroidery works. She designed shapes and forms using a sort of embroidery technique in her head. So even there is never a thread to be seen, it is still very much part of her graphic design work. This, however, has more to do with knitting. As a promotion for Het Kanten Huis she knitted over an entire house.
 
  
 +
==Practice Q7: Making is Connecting ==
 +
For my second year project please look at [[User:Jerryestie/Making | Making is Connecting 2016]]
  
 +
[[File:workjr7.jpg|500px|Caption]]
  
 +
==Practice Q9 & Q10: Craft & Radiation ==
 +
For my third year project please look at [[User:Jerryestie/Practice | Craft and Radiation 2017]]
  
 +
[[File:Gifcensor.gif|500px|Caption]]
  
 +
=Minor: Human?=
 +
[[File:Westworld-skele-fb-1.jpg‎]]
 +
[[File:Bladerr.jpg]]
  
 +
==Week 1: Kick-Off==
 +
===Beginning===
 +
My group with Jochem and Naomi had the body parts of index finger, pink and the eye(s). We started out with topics that we found fitting before coming up with a more concrete subject. Things like Identity and security came up often and also folklore and myths involving hands and eyes. For instance: How in Japan would cut off their pinks as a way of apology, or how ISIS followers point up their index finger to the sky.
  
 +
===Initial Ideas===
 +
There were a few quick concepts we came up with before ending up with our hand-eye dis coordination box.
  
 +
=====Pointing fingers=====
 +
[[File:Wewantu.jpg]]
  
 +
When a finger points at you it creates this immediate connection. It can be a bit uncomfortable and we wanted to play with this feeling. One of the ideas was to walk into a room where fingers would follow you (through the use of a Kinect) and point at you. Another was a closed-off space where you would have to point into the camera before entering and then being confronted by the previous visitor pointing at you. There was a variation where it would connect the people pointing.
  
 +
[[File:Sketchjer1.jpg]]
 +
[[File:Sketchjer2.jpg]]
  
 +
=====Games=====
 +
There were several variations where we played with the idea of a 2-screen/2-user installation. This set-up would have two players use the installation against each other in several ways. The 'controller' would force the player to use only the pink and index in a rapid order to force a sort of carpal tunnel syndrome. The player who would use the controller the fastest would induce a flashing/annoying eye-strain creating image to the other player. Another variation to this was the cheat screen. The cheat screen would give one player, unbeknownst to the other player, a sort of cheat screen that could make things worse or better for both the player and its competition.
  
 +
[[File:Screeeeeeeeb.png]]
  
 +
===Hand-Eye Discoordination===
 +
With some time pressure from Tim we ended on a final concept of putting the coordination between eyes and hand on trial. The question basically became "what would happen if you can't see what your hand is doing anymore."
  
 +
=====Buttons=====
 +
We decided to find several buttons and hide them from plain sight. By using these buttons you would get a visual feedback of what you were doing. We went to the piekfijn to try and fide specific buttons so that each one would be a different sensation.
  
 +
=====Arduino Coding=====
 +
I focused on coding the Arduino and getting an input from the buttons that are pressed. There had to be a way to have each button have an unique identifier so Processing would know which button was pressed, since all input came in as the same numbers. I did this by adding a line to the serialprint that adds a different letter per button. This way Processing was able to differentiate all the different inputs.
  
 +
=====Exhibition=====
 +
filler
 +
soon im too lazy to export pics atm
  
 +
=====Observations and Feedback=====
 +
One of the things that was immediately clear during the exhibition is that people didn't get that they had to turn around and watch the screen. They would either just look at the box and play around and then turn around after moving something or pressing a button. We did not communicate this properly or force the user to stand in the way we intended.
  
 +
In general most people didn't (immediately or at all) get what the project was about or what was going on. The interactivity helped spark people's interest but the concept wasn't easy to see or understand through our installation.
  
 +
The buttons were also too hard to find, whether this was actually a good or bad thing I haven't made my mind up about yet. I feel like it's in a middle ground right now, it could either be a lot harder and become this sort of brutal installation or easier but then how do you add a challenge to the lack of eye coordination?
  
 +
The visuals also had a disconnect with what you were doing, it didn't seem to be a whole product but rather two separate things.
 +
==Sensor==
 +
For the sensor I want to use sound as an unlocking mechanism. Using a distinct sound or sounds made in a distinct order.
 +
===Research Links===
 +
[https://forum.processing.org/two/discussion/14502/create-tap-tempo-metronome Getting BPM]
  
  
 
+
----
 
+
float bpm = 80;
 
+
float minute = 60000;
 
+
float interval = minute / bpm;
 
+
int time;
 
+
int beats = 0;
 
+
 
 
+
 
 
+
void setup() {
 
+
  size(300, 300);
 
+
  fill(255, 0, 0);
 
+
  noStroke();
==Felt Techniques==
+
  time = millis();
=====Old Technique - Felting=====
+
}
[[File:Work1.jpg|500px|Caption]]
+
 
 
+
void draw() {
For my old technique I choose felting and decided that I wanted to focus on this material for the rest of the quarter. I immediately found felting aesthetically pleasing and wanted to see if I could use it's potential. For the first test I used hot water and soap to bond the felt together.
+
  background(255);
 
+
 
=====Industrial Technique: Knitting=====
+
  if (millis() - time > interval ) {
[[File:work2jr.jpg|500px|Caption]]
+
    ellipse(width/2, height/2, 50, 50);
=====Combining: Felting and knitting=====
+
    beats ++;
[[File:work3jr.jpg|500px|Caption]]
+
    time = millis();
=====Technique to the limit=====
+
  }
[[File:work4jr.jpg|500px|Caption]]
+
 
=====Final Work=====
+
 
[[File:posterjr.jpg|500px|Caption]]
+
  text(beats, 30, height - 25);
 
+
}
==Why I'm a maker==
+
----
I am a maker.
 
 
 
I make because I enjoy getting the satisfaction of learning new techniques. Whether it’s a graphic design assignment on a computer screen where I’m kerning every single letter just right to a multi-layered silkscreen poster with the paint layers pressed perfectly on top of each other for the first time. It is the reason why I chose to be a graphic designer.
 
 
 
However, it is not as simple as that. I think the real joy in making, for me at least, is learning how to do things well. Starting out with a new technique is usually challenging at first. After putting time into gaining knowledge, either by classes or trial and error, you slowly become better at the craft you are practicing.
 
 
 
I have previously mentioned my graphic design study and think that is my big source of inspiration for making things. When I started my second year at Willem de Kooning Academy I made myself a manifesto. In this manifesto I promised to use a different medium than print for each work I created, unless the assignment clearly stated that I should use print.
 
 
 
The reason for making this manifesto was my personal belief that to improve as a graphic designer I need to learn about as many techniques as I can. The more knowledge about techniques you have, the broader you think creatively.
 
 
 
An example of this is the Xerox copier at school. For my research on April Greiman, a graphic designer who was active in the 70s and 80s and known for her skills with the Xerox, I studied the copier for a couple of weeks, refusing to use the computer and cutting my work by hand then copying it. I used the copier’s color and magnification settings to create my own artworks, focusing heavily on patterns. While annoying at first, the more I experimented with the Xerox copier the more joy I got out of making my patterns and experiments. Suddenly the annoyances were gone and I was able to generate good looking patterns with relative ease.
 
 
 
Now, almost a year after I had this project, I have the knowledge and skill available to me to be used in different projects. And the thing is, I really use that knowledge of new tools and skills. For my current graphic design project, I am working a lot with interchanging small and big texts or objects. Using my previously gained Xerox copier skills I was able to quickly create graphics that I thought of because I know how the machine works. I might have thought about it before ever using a Xerox copier as much as I did last year, but now I knew exactly what I would be able to do with it.
 
 
 
To put the topic of ‘craft’ on the table, I chose the Xerox as the example for this story because I consider the work you can create with it as craft. For me craft is, in a broad way of putting it, making things right with skill and knowledge. As discussed in class I think a lot of people think of things like woodworking and ‘working with your hands’ when they hear the word craft. It’s a word that brings up thoughts of physical work and skill.
 
 
 
But is using a machine that is intended to copy other things craft when you create your own artwork with it? You gain knowledge of a tool, whether it’s digital or physical. What about a DTP worker, making sure that a document gets printed in just the right color and specifications? I think these things count as craft, and they are part of the reasons why I am a maker: They are all part of me looking to learn new things to study and improve my skillset and knowledge with.
 
 
 
 
 
 
 
So, for my final example I decided to put what I learned with this practice back to my graphic design study: Taking the technique I learned and apply it to graphic design. I have used the felt to make my exhibition poster that ultimately says why I’m a maker:
 
 
 
To learn new things
 

Latest revision as of 11:33, 4 September 2017

Main Information

Jerry Estié

0902472

0902472@hr.nl

Practice Q7: Making is Connecting

For my second year project please look at Making is Connecting 2016

Caption

Practice Q9 & Q10: Craft & Radiation

For my third year project please look at Craft and Radiation 2017

Caption

Minor: Human?

Westworld-skele-fb-1.jpg Bladerr.jpg

Week 1: Kick-Off

Beginning

My group with Jochem and Naomi had the body parts of index finger, pink and the eye(s). We started out with topics that we found fitting before coming up with a more concrete subject. Things like Identity and security came up often and also folklore and myths involving hands and eyes. For instance: How in Japan would cut off their pinks as a way of apology, or how ISIS followers point up their index finger to the sky.

Initial Ideas

There were a few quick concepts we came up with before ending up with our hand-eye dis coordination box.

Pointing fingers

Wewantu.jpg

When a finger points at you it creates this immediate connection. It can be a bit uncomfortable and we wanted to play with this feeling. One of the ideas was to walk into a room where fingers would follow you (through the use of a Kinect) and point at you. Another was a closed-off space where you would have to point into the camera before entering and then being confronted by the previous visitor pointing at you. There was a variation where it would connect the people pointing.

Sketchjer1.jpg Sketchjer2.jpg

Games

There were several variations where we played with the idea of a 2-screen/2-user installation. This set-up would have two players use the installation against each other in several ways. The 'controller' would force the player to use only the pink and index in a rapid order to force a sort of carpal tunnel syndrome. The player who would use the controller the fastest would induce a flashing/annoying eye-strain creating image to the other player. Another variation to this was the cheat screen. The cheat screen would give one player, unbeknownst to the other player, a sort of cheat screen that could make things worse or better for both the player and its competition.

Screeeeeeeeb.png

Hand-Eye Discoordination

With some time pressure from Tim we ended on a final concept of putting the coordination between eyes and hand on trial. The question basically became "what would happen if you can't see what your hand is doing anymore."

Buttons

We decided to find several buttons and hide them from plain sight. By using these buttons you would get a visual feedback of what you were doing. We went to the piekfijn to try and fide specific buttons so that each one would be a different sensation.

Arduino Coding

I focused on coding the Arduino and getting an input from the buttons that are pressed. There had to be a way to have each button have an unique identifier so Processing would know which button was pressed, since all input came in as the same numbers. I did this by adding a line to the serialprint that adds a different letter per button. This way Processing was able to differentiate all the different inputs.

Exhibition

filler soon im too lazy to export pics atm

Observations and Feedback

One of the things that was immediately clear during the exhibition is that people didn't get that they had to turn around and watch the screen. They would either just look at the box and play around and then turn around after moving something or pressing a button. We did not communicate this properly or force the user to stand in the way we intended.

In general most people didn't (immediately or at all) get what the project was about or what was going on. The interactivity helped spark people's interest but the concept wasn't easy to see or understand through our installation.

The buttons were also too hard to find, whether this was actually a good or bad thing I haven't made my mind up about yet. I feel like it's in a middle ground right now, it could either be a lot harder and become this sort of brutal installation or easier but then how do you add a challenge to the lack of eye coordination?

The visuals also had a disconnect with what you were doing, it didn't seem to be a whole product but rather two separate things.

Sensor

For the sensor I want to use sound as an unlocking mechanism. Using a distinct sound or sounds made in a distinct order.

Research Links

Getting BPM



float bpm = 80; float minute = 60000; float interval = minute / bpm; int time; int beats = 0;     void setup() {   size(300, 300);   fill(255, 0, 0);   noStroke();   time = millis(); }   void draw() {   background(255);     if (millis() - time > interval ) {     ellipse(width/2, height/2, 50, 50);     beats ++;     time = millis();   }       text(beats, 30, height - 25); }