der hess http://blog.derhess.de am medialen werkeln Sat, 10 Mar 2012 09:32:20 +0000 en hourly 1 http://wordpress.org/?v=3.3.2 My most important Twitter Messages #13 http://blog.derhess.de/2012/02/21/my-most-important-twitter-messages-13/ http://blog.derhess.de/2012/02/21/my-most-important-twitter-messages-13/#comments Tue, 21 Feb 2012 13:06:44 +0000 admin http://blog.derhess.de/?p=1780
  • My most important Twitter Messages #6
  • My most important Twitter Messages #5
  • My most important Twitter Messages #10
    • ]]>     Twitter von der hess

    A small summary of my Twitter messages from December 2011- February 2012:

    Allgemein (General)

    Generative Art:

    Info Design and Visualization

    UX and Interaction Design:

    Projekte und Experimente (Projects and experiments)

    Neue Technologie (new Technologies)

    Programmierung und Software Design (Programming)

    Physical Computing

    Game Developing:

    Mobile

    Flash and Flex

    Related posts:

    1. My most important Twitter Messages #6
    2. My most important Twitter Messages #5
    3. My most important Twitter Messages #10

    flattr this!

    ]]>     http://blog.derhess.de/2012/02/21/my-most-important-twitter-messages-13/feed/ 0     “TAKE ME PLACES” artwork is aborted http://blog.derhess.de/2012/02/07/take-me-places-artwork-is-aborted/ http://blog.derhess.de/2012/02/07/take-me-places-artwork-is-aborted/#comments Tue, 07 Feb 2012 11:51:32 +0000 admin http://blog.derhess.de/?p=1756
  • SENSEWARE – How to Create the Experience’s Architecture
  • My artwork at the Incuratable Art – Exhibition in Paris
  • Interactive Media Installation: Sound Drawings
    • ]]>

    Last year at september Me and Andrea Suter started a location-based experiment with the name Take me Places. Our basic idea was:

    TAKE ME PLACES is an art project, which plays with the notions of territory and dislocation, orientation and the loss of such. TAKE ME PLACES will travel around the world until July 2012. At the end of its travels the photographs as well as the added artefacts will be exhibited. TAKE ME PLACES plays with public spaces, is participatory, involves a random the public, is dependent upon it.

    We decided to place two suitcases in public spaces. Each suitcase were equipped with a photocamera, kind of a map, kind of a container, and instructions.  One suitcase represented an anolog version (Analog camera, paper maps, suitcase box for additional artworks) and a digital version (digital camera, digital map with QR Code, USB Stick as a container for additional digital artworks). People were supposed to take the suitcase with them and add some personal value to it.

    suitcase in Berlin

    suitcase around yarn

    suitcase around yarn

    somewhere in vienna

    somewhere in vienna

     

     

     

     

     

     

     

    We hoped that the suitcases will travel around the world. Furthermore we had the hope that we can uncover the different expression of people feelings based on the used digital or analog media. The project started well, especially the digital suitcase traveled nicely through Austria until it ended in Berlin. After the placement in Berlin we never got any feedback back. So unfortunately the experiment failed... During this time I learnt some weak points in our concept and technical implemtation, but  in the same time I had some nice experiences. More about the project and some travel stories your can read on our project website.

    Maybe at some time the motivation comes back to initialize an improved version of this experiment. I really enjoyed our low tech approach. What do you think about our project and do you know similiar digital artworks?

    Related posts:

    1. SENSEWARE – How to Create the Experience’s Architecture
    2. My artwork at the Incuratable Art – Exhibition in Paris
    3. Interactive Media Installation: Sound Drawings

    flattr this!

    ]]>     http://blog.derhess.de/2012/02/07/take-me-places-artwork-is-aborted/feed/ 2     Book review: Developing Flex 4 Components http://blog.derhess.de/2012/02/01/book-review-developing-flex-4-components/ http://blog.derhess.de/2012/02/01/book-review-developing-flex-4-components/#comments Wed, 01 Feb 2012 12:00:38 +0000 admin http://blog.derhess.de/?p=1747
  • Book review: Adobe Flex – Training from the source
  • Book review: Generative Gestaltung
  • Book review: Form + Code (Generative Art & Design)
    • ]]>     A couple of weeks ago I finished reading  the book "Developing Flex 4 Components" by Mike Jones. The reviews on Amazon.com were very promising and during my Flex 3 developing I always wished such a book. For this reason my expectations were very high.

    I wasn't disappointed. The book is a perfect continuation of the Flex 4 beginner book "Flex 4 - Training from the source". Even it repeats some content like Data Binding and basics of developing custom compontents, it was enjoyable to read. Mike Jones has a really nice writing style for explaining the core concepts of the Flex 4 component and skinning architecture very easily. These chapters are really one of the best availabe informations to  these kind of topics. Completely new for me was the chapter about "working with Metadata". I learnt some deep concepts behind the Meta-tag usage of the Flex Framework. The same is valid for the "Distribution" part of the book. The development worklflow with Flash Library Project, Component Integraton in Flash Builder 4, and the Documentation part are very helpful for my future projects.

    I can highly recommend this book for experienced beginner and intermediate Flex Developers. For really advanced Flex developers I missed some more deeper information. Here is my wishlist for a second edition (maybe it comes some time?!):

    • Data Binding: This topic is mentioned but I wish more deeper information like the presentation "Diving in the Flex Data Binding Waters" by Michael Labriola and the compound data object approach  by Olikhver Sergey
    • Component Skinning architecture for multi-screen objects: If you have a very complex application or you have to create various skins for various devices, you can run very fast in an architecture nightmare. See the article Advanced Flex 4 Skinning Techniques by Pavel Jacko
    • Differences between mobile component and desktop component development
    • For some certain cases the hack with the mx_internal namespace makes still sense.  A short segment or a mini chapter about the use of this approach would be nice.
    • Test Driven Development with Flex Unit: I don't know if Flex Unit really belongs to this kind of book, but if you are creating a component library, then you should use Flex Unit. Just for ensure the quality of your compontes for upcoming versions. Especially, writing and managing Flex Unit code for visual components is always tricky. Some advices for this topic would be so nice.

    That is all what I can say. Mike Jones wrote a really good book about Flex 4 component development. It is a must-buy for every Flex Developer.

    Related posts:

    1. Book review: Adobe Flex – Training from the source
    2. Book review: Generative Gestaltung
    3. Book review: Form + Code (Generative Art & Design)

    flattr this!

    ]]>     http://blog.derhess.de/2012/02/01/book-review-developing-flex-4-components/feed/ 0     Book review: Adobe Flex – Training from the source http://blog.derhess.de/2011/12/16/book-review-adobe-flex-training-from-the-source/ http://blog.derhess.de/2011/12/16/book-review-adobe-flex-training-from-the-source/#comments Fri, 16 Dec 2011 10:20:58 +0000 admin http://blog.derhess.de/?p=1736
  • Book review: Developing Flex 4 Components
  • An Adobe Air Component for the Vimeo Moogaloop API
  • Book review: Generative Gestaltung
    • ]]>     A couple of weeks ago I read the book Flex 4 - Training from the source. It is the officially introduction book for Flex 4 from Adobe.  I was very curious about the book, because I started learning Flex 3 with no good start. For Flex 4 I wanted to learn it how I like to learn new things.

    Content review:

    The books starts with the typical introduction about Rich Internet Applications. I skipped this chapter, because it is always the same bla bla... The chapters 2 talks about the new Flash Builder IDE. Even I was pretty familiar with the IDE I could find some nice features during reading this chapters. So I learnt already something new. Especially, the chapter 3 and 4 gave me a really good introduction and understanding about the new layout architecture and component infrastructure. The chapters Handling Events, Using Remote XML Data, Creating Classes are not so interesting for an already experienced Flex Developer. The difference between Flex 3 and Flex 4 is not big in these cases. The chapter about Data Binding was good to read again, because Binding is very helpful but sometimes not so easy to deal with. I highly recommend the chapter 10 about DataGroups and Lists and the chapter 12 about Item Renderes. On these topics the change from Flex 3 to Flex 3 is very big. Unfortunately, the chapter 15 about Formatters and Validators is pretty outdatet, because Flex 4.5 offers new Spark based Formatters and Validators. The last three chapters about Skinning and custom Actionscript components are very basic written. For beginners easy to understand and experienced Flex Developers get an idea about the differences between Flex 3 and Flex 4 component development.

    Structure:

    I have to admit I am keen on the book structure. The chapters are structured like school lessons. Every lessons has an approximate time, which works very well in my case. Additionally, it is very useful for organizing the learning with your daily schedule. However, every end of a chapter provides a good summary of the learnt content. So you automatically repeat the learnt stuff. The code examples are nice described and easy to work with, too.

    Result:

    Flex 4 - Training from the source is a really good book for Flex 4 beginners.  Already experienced Flex Developers can get bored about some content. It depends on your learning type. I like reading books, so for me it was perfect to get an overview. If you like more reading online resources or watching video tutorials, then go for it. There are enough documentations and tutorials available.

    Related posts:

    1. Book review: Developing Flex 4 Components
    2. An Adobe Air Component for the Vimeo Moogaloop API
    3. Book review: Generative Gestaltung

    flattr this!

    ]]>     http://blog.derhess.de/2011/12/16/book-review-adobe-flex-training-from-the-source/feed/ 2     My most important Twitter Messages #12 http://blog.derhess.de/2011/11/26/my-most-important-twitter-messages-12/ http://blog.derhess.de/2011/11/26/my-most-important-twitter-messages-12/#comments Sat, 26 Nov 2011 20:45:57 +0000 admin http://blog.derhess.de/?p=1723
  • My most important Twitter Messages #6
  • My most important Twitter Messages #10
  • My most important Twitter Messages #11
    • ]]>     Twitter von der hess
    A small summary of my Twitter messages from August - November 2011:

    Allgemein (General)

    Generative Art:

    • Our lecture from the "Design the Future" series at Carnegie Mellon University is now online

    Info Design and Visualization

    UX and Interaction Design:

    Projekte und Experimente (Projects and experiments)

    Neue Technologie (new Technologies)

    Programmierung und Software Design (Programming)

    Physical Computing

    Game Developing:

    Flash and Flex

    Related posts:

    1. My most important Twitter Messages #6
    2. My most important Twitter Messages #10
    3. My most important Twitter Messages #11

    flattr this!

    ]]>     http://blog.derhess.de/2011/11/26/my-most-important-twitter-messages-12/feed/ 0     My most important Twitter Messages #11 http://blog.derhess.de/2011/08/31/my-most-important-twitter-messages-11-2/ http://blog.derhess.de/2011/08/31/my-most-important-twitter-messages-11-2/#comments Wed, 31 Aug 2011 10:00:29 +0000 admin http://blog.derhess.de/?p=1683
  • My most important Twitter Messages #6
  • My most important Twitter Messages #4
  • My most important Twitter Messages #5
    • ]]>     Twitter von der hess
    A small summary of my Twitter messages from June - August 2011:

    Allgemein (General)

    Generative Art:

    Info Design and Visualization

    UX and Interaction Design:

    Projekte und Experimente (Projects and experiments)

    Neue Technologie (new Technologies)

    Programmierung und Software Design (Programming)

    Physical Computing

    Game Developing:

    Flash and Flex

    Related posts:

    1. My most important Twitter Messages #6
    2. My most important Twitter Messages #4
    3. My most important Twitter Messages #5

    flattr this!

    ]]>     http://blog.derhess.de/2011/08/31/my-most-important-twitter-messages-11-2/feed/ 0     Flash talks to Max MSP via OSC http://blog.derhess.de/2011/08/16/flash-talks-to-max-msp-via-osc/ http://blog.derhess.de/2011/08/16/flash-talks-to-max-msp-via-osc/#comments Tue, 16 Aug 2011 10:38:25 +0000 admin http://blog.derhess.de/?p=1549
  • My most important Twitter Messages #9
  • My most important Twitter Messages #6
    • ]]>

    As I already mentioned  in an earlier blog post, for reimplementing my "Sound drawing" project to Flash I had to create a communication layer between Max/Msp and Flash. In this blog post I will report about my results and some technical information. If you want to jump directly to the technical part, please skip the part "Why am I doing this".

    Why am I doing this?

    I want to have access to more performance in general, I want to have access to more technical advanced stuff, I want an easy way for using external hardware devices, and last point, I want to collaborate with other media artists (without changin the working environment).

    Flash is a very nice for working with graphics, videos and other media based stuff. That is the total strength of Flash, but it fails in some performance issues (compared to C++) and some algorithmic libraries (compared to libraries like IanniX, Math, OpenCV, and Sphinx4). One motivation for me in this project lies to combine the advantages of these worlds. But I don't want to change the usage of these libraries. Some libraries have to be executes as an exe Application and they just perform great in C++, and not in a Flash environment (in some cases Alchemy could be a solution).

    Next point of performance is creating a scalable approach for media installation. Some media installation can't  be run by only one machine.  You need more computers, which talks to each other. For this reason, I put my focus on the Open Sound Control network protocol. As the OSC team drescribed, this protocol is made for communication between computers and media devices. It is often used in very robust environments and the documentation is very well, too. Almost every creative coding software supports the OSC communication, which is very good for collaborating with other media artists (everyone can still work in the preferred software environment).

    Some hardware can already talk OSC or it uses an communication software like TUIO, iOSC, AndroidOSC. For Midi controllers you can use graphical environments like Max/Msp or PureData. These softwares have directly access to the midi hardware and can configure the most things. Afterwards you send the midi data from Max/Msp (or PureData) to Flash via OSC. In this way Flash gets access to a new level of external devices...

    Flash talks OSC

    First I was a little bit scared, because I thought I have to dive into the nerdie byte array socket programming part in Flash. Luckily, I found information about the FlOSC project. FlOSC is Java based application, which receives the OSC messages and routing them to the Flash XML socket. There are some great tutorials available by Eric Socolofsky and Tim Poulin (part 1, part 2, part 3). After watching all of these tutorials, I was a little bit scared of the reliable performance of this approach. The Flash XML socket is nice for chat applications or some round-based multiplayer games, but for realtime data transmission I heard bad things...

    Luckily again, some time passed since FlOSC were created and Adobe provided a new binary socket API for the Flash Player. Things became even better. Since Version 2 of Adobe Air, Air supports the network UDP layer for really fast data transmission. I have not to mention that the Flash open-source is great ;-) , so I could find easily a nice library.  The tuio flash library solved almost everything I needed. I had to write my own OSCListener, which is great explained in the tuio guide and in its comments. During development I had sometimes problems with the binding of the DatagramSocket. It was obvious that the (binded) port was never closed. I had to wait until Windows shutted it down or just do it manually. Unfortunately, the UDPConnector class does not provide a close function. Therefore I added a close function by myself at the end of the class. Extending or creating a custom UDP Connector was not possible, because all members of the class are private.

    public function close():void {
    if(this.connection) {
           this.connection.close();
    }
}

    Max/MSP talks OSC

    After this minor coding everything worked fine. So I could jump to Max/MSP. Using OSC in Max/Msp is not very difficult. The documentation is pretty good and the provided example file helps a lot. I just extended the example with one function. If the max patch receives successfully a message from the Flash Client (Adobe Air app), then send a message back to the Flash client.  For the second example you have to install the fiddle plugIn (for Windows) for Max/Msp.

     

    Max/Msp and Flash in love

    I created two mini examples. Example one just demonstrates sending messages between Flash and Max/Msp. The second example is little bit more complicated and shoud give you an idea of a real life project. The max patch analyzes an audio file and sends the pitch tracking + volume tracking data to the Flash client. The flash client reads the data and draw it on the canvas. As you can see on my screen capture video above. The performance of this test application is pretty solid and robust. Now imagine instead of the tracking data we send midi data or just some image processing data. Or we do some heavy image processing on one machine and send the data to another machine, which only renders the Flash output... I guess there are many new things possible :-)

    Download Code

    The source code is available on my google project SVN or download the zip file. For the examples you must have installed Max/Msp 5, fiddle plugIn (for Windows), Flex SDK 4.5, Flash CS5 or Flash Builder 4. The code examples also requires the additional ActionScript libraries MinimalComps, MonsterDebugger, and TUIO Flash.

    Related posts:

    1. My most important Twitter Messages #9
    2. My most important Twitter Messages #6

    flattr this!

    ]]>     http://blog.derhess.de/2011/08/16/flash-talks-to-max-msp-via-osc/feed/ 2     Mr. Doobs Harmony project ported to Flash AS3 http://blog.derhess.de/2011/08/09/mr-doobs-harmony-project-ported-to-flash-as3/ http://blog.derhess.de/2011/08/09/mr-doobs-harmony-project-ported-to-flash-as3/#comments Tue, 09 Aug 2011 10:00:15 +0000 admin http://blog.derhess.de/?p=1645
  • Mr. Doobs Harmony drawing APP ported to MAX / MSP
  • Harmony in Max / MSP with multiple brushes
    • ]]>

    Some time ago I ported the great Harmony drawing app by Mr. Doob to Max/Msp. This Max/Msp Version I used for my media installation "Sound drawings". During the development and testing with the musicians I was not so happy with my workflow. Furthermore I felt that the Max/Msp environment causes some certain useless obstacles for me. Especially for the visual part of my work. Now I have time to check how useful Flash can be as a renderer. The first step was to port the drawing functions to ActionScript. Here is the result:

    Get Adobe Flash player

    For drawing in full size mode please visit the html File. The code is available on my Google project site. Before using the code in your projects, please check the requirements of the GPL license Version 3 and read Mr. Doobs blog post about using his code. The API is still the same as the orginial JavaScript version. Every brush has to implement the IBrush Interface methods:

    public function init(); // for re-creating the brush (after calling destroy)
public function destroy(); //destroy the brush data and free the memory
 
////////// Drawing functions ///////////////
public function strokeStart(mouseX:int, mouseY:int):void; // set first drawing point
public function stroke(mouseX:int, mouseY:int):void; // set following drawing points
public function strokeEnd():void; // stop drawing

    Brushes are very easy to use, but for performance issues you have to consider, that the drawing commands are expensive for the computer. I already ran into some performance problems after a few seconds. For this reason, I decided to store the drawing result of each frame into a BitmapData object. The Hype Framework is using the same approach. Here you can see the most important code lines for the bitmap storing approach...

    public fundction handleEnterFrame(e:Event):void {
   // some code before
 
   // draw the stroke for one(!) frame
   brush.stroke(e.target.mouseX,e.target.mouseY);
   // save the drawing in a bitmapData Object for performance
   bmpCanvas.draw(canvas);
   // clean the canvas again for new drawings.
   canvas.graphics.clear();
 
  // some code later...
}

    Nothing more I can say. Have fun and keep on coding!

     

    Related posts:

    1. Mr. Doobs Harmony drawing APP ported to MAX / MSP
    2. Harmony in Max / MSP with multiple brushes

    flattr this!

    ]]>     http://blog.derhess.de/2011/08/09/mr-doobs-harmony-project-ported-to-flash-as3/feed/ 2     Arduino Prototype: The “plate” Gaming Device http://blog.derhess.de/2011/08/02/arduino-prototype-the-plate-gaming-device/ http://blog.derhess.de/2011/08/02/arduino-prototype-the-plate-gaming-device/#comments Tue, 02 Aug 2011 11:39:22 +0000 admin http://blog.derhess.de/?p=1614
  • Moodumbrella – a self em-powered device for well-being
    • ]]>     For two or three years I wanted to work seriously with Arduino. During this time I have done the same basic LED exercises again and again. Just for keeping alive my basic knowledge. Finally and luckily, I had to visit the Advanced Microcontroller lecture by Laurent Mignonneau. Laurent is the definition of a Geek himself. Not much talking, just doing, and a fucking huge amount of knowledge in electronics and programming. The assignment for his lecture was to create SOMETHING with a low resolution screen. Really advanced examples of a low resolution screen are the androp project (Making of | strobo animation) or Laurent's solar display (concept).

    Plate Game Device Front

    Device Front

    device form

    Device shot

    Plate Game Device opened
    Device opened

     

     

     

     

     

     

    Plate Game Device opened

    Device opened back

    Plate under the hood

    Under the hood

    Plate internal parts

    Internal parts

     

     

     

     

     

     

     

    Hot glue fixing
    Hot glue fixing
    display resistors
    display resistors

     

     

     

     

     

     

     

     

    However, one day in May I woke up and had this game device idea, which looks like a plate or a steering wheel. After some consideration the idea felt good. The very simple form allows me to integrate a low resoultion screen very easily. Furthermore the usage range of this kind of device would be broad. I was very happy. For the size of the device I got inspiration of a real plate. It has the perfect size for not entering the private area of other players, but still feel connected to them. The metaphor came to me when I observed the interaction between a waiter and his guests in a restaurant. When the waiter hands the plate to one guest, there exist for a short time a connection between them. The connection is mediated and supported by the plate. The physical distance provided by the plate is small enough for feeling welcome, but also big enough for respecting the private zone. For this reason the form of the device is not only usable for a remote control, it is even usable for a multiplayer gaming device. In this context I got a childhood memory... uh yeah... fighting all the time with my sister for the power of the TV remote control. That memory brought me to a new version of the game "tug of war". The plate has four handholds. For each player one. In the middle of the device the screen is placed. The screen shows two lines, like a cross.  The aim of the game is to pull the device hard enough, that one line (the opposite line of the player) comes closer. If the line jumps out of the screen the player has won. An arrow shows it. Afterwards the game starts again. I uploaded a short video for getting an idea and see the device in action.

    The technical implementation of my device is very simple, I have to admit... The wood and some other fixing stuff I found in the trash of the university and the Linzer DIY stores. I had almost the feeling of Gambiologia ;-) However, I cut the wood our university wood workshop. Further parts were:

    During development I ran into some pitfalls. My soldering skills are not very great and for this reason at least four or five times a cable lost the connection... In the end I stabilized the cable connection with hot glue (look at the pictures). That worked very well and I had no such problems anymore. Laurent gave me the advice to avoid cables everywhere I can. The possibility that the cable lost the connection is very high. Using plugs and connectors are good alternatives... So for the next projects I try my best to consider it.  Second pitfall was related to programming. I got a Arduino Nano Board from Laurent. I tried to replace the Nano board with my Uno board. But unfortunatley the provided Arduino Code for the LED Dot Matrix messed up. In the end the Arduino Code for Nano board was not compatible with my new Arduino Uno board. I don't know the exact reason. May one of my readers have an idea?! I would appreciate it. :-) Next issue, not a very big one, was dealing with the accelerometer data. Every motion caused a motion in the opposite direction. You can see the values at my Excel File. I implemented a simple time checking code for the sensor. It works good for the first tests, but maybe one of you can recommend me a good library or code snippet for dealing with accelerometer values...?! The source code of this project is available as usual on my Google SVN. I am pretty happy with the result of my first Arduino project. Even the feedback I got from the other students were great. So I would like to continue the development. For a much better wood cut I hope I can use the laser cutter at the AEC or the Fab lab in Berlin. The device should get some extensions, like pressure sensors on each handhold. Adding four InraRed LEDs on the back of the device. The IR LEDs are interesting for some (3D) tracking projects a la Johnny Chung Lee. I hope I can implement all these ideas... Happy coding and soldering!

    Related posts:

    1. Moodumbrella – a self em-powered device for well-being

    flattr this!

    ]]>     http://blog.derhess.de/2011/08/02/arduino-prototype-the-plate-gaming-device/feed/ 0     Processing meets Box2D and blob detection http://blog.derhess.de/2011/06/27/processing-meets-box2d-and-blob-detection/ http://blog.derhess.de/2011/06/27/processing-meets-box2d-and-blob-detection/#comments Mon, 27 Jun 2011 10:55:18 +0000 admin http://blog.derhess.de/?p=1601
    For the Programming II Workshop at our Interface Culture department I decided to do an small experiment with Box 2D. For a long time I wanted to play around with Box 2D. Especially merging real world objects with virtual object fascinates me very much. I don't like so much the common Augmented Reality stuff. However, some stuff is really cool and inspires me. Here are some projects I got my inspiration from: EdgeBomber, Laser Sound test, Phun, Crayon Physics, 2d Sketches becomes 3d Reality, ILoveSketch, MotionBeam, Tangible Fire Controlls.

    Now talking about the technical stuff. In my experiment I am using the Blobscanner library and the Box2D code of Daniel Shiffman. It is really a small experiment, I just wanted to check out how difficult it is to combine camera data and virtual data. For the first test I am using a easy .jpg file with 3 rectangles. This examples works pretty well. The next map has some diagonal rectangles. The first problems appears. The upper right rectangles are drawn in the wrong direction. This is the reason why the physics simulation fails. At the moment I am using the Surface object of Box2D for drawing more complex objects. For the surface object is the direction of drawing very important. You have to draw counter clockwise. So  that the normal vectors does not point inside the object (check chapter 4.4 Polygon Shapes). Even using a polygon object would make more sense instead of using the surface object...

    Another issue I have, is the correct recognition of the shapes. This problem is caused by two challenges. First challenge is to order the edge points array correctly. I get only edge points and I don't know is it the right or the left side of the object. My sorting algoritm is not implemented very well. For this reason some of my recognitions fails. But for doing a fast check on simple objects to get an idea, it was enough. However, this paper about edge detection can solve my problem, or I just have to implement a "find the shortest distance algorithm". If you have some better advices, please leave a comment. Thx! The second challenge is minimizing the size of the edge points array. For this I found a nice article: Line Generalization (Smoothing, Simplifying). I ported the ActionScript code to processing and it seemed to work. Tough a better approach could be to vectorize the camera data. Nicolas Barradeau wrote two nice blog posts about vectorization v0 and vectorization v1. His code I defintely have to check out. I guess there are some  hidden solutions for my problems.

    So far about my experiment. My code is online on my google project site or download it. Please consider that my code is far far away from perfect. Big thanks to the great tutorial writers. I shit love the ActionScript community and the processing community ;-) Knowledge sharing, ahoi!!

    No related posts.

    flattr this!

    ]]>     http://blog.derhess.de/2011/06/27/processing-meets-box2d-and-blob-detection/feed/ 3