game map

games,iphone — nik @ 4:40 pm



freemind is great.

imaginary app

iphone — nik @ 11:37 am

Command /usr/bin/codesign failed with exit code 1

iphone — nik @ 11:42 pm

After many hours of trying to get xcode to compile to my iphone and having “Command /usr/bin/codesign failed with exit code 1″ as my only clue, I came across Amilion75′s post here. Specifically:

1) take care not to have special character in your login name (on the MAC developping machine) my name has a “-” (minus). The result is CSSMERR_TP_NOT_TRUSTED error when you build your app.

So, apparently this problem had nothing to do with the horrendous process of provisioning or plist files (as mostly everything on the internet would have you believe), but simply removing the space in my login name.

thank you Amilion75. I was ready to pull one of these:

processing doodles: metablobs

processing.org — nik @ 11:32 am

I haven’t updated in a while, but now I’m back! Now that I have more time, I’ll hopefully be able to post more now.

The following are some doodles I made last night with Processing. The metablobs are a simple particle system that use RGB values to determine attraction/repulsion. So… where are the particles and why isn’t there any color? It’s because the particles are mapped to a density map, sort of (I think?) how metaballs work. The result is twichy organic blobs that aren’t quite balls.


high contrast:

(more…)

DESKTOP 0

openframeworks — nik @ 1:37 am

download the executable here. requires os x 10.5+ sorry!

while looking to register some new domains…

Uncategorized — nik @ 11:15 pm

screen-shot-2009-10-16-at-121318-am
Gee, thanks!

failbase @ full disclosure

Uncategorized — nik @ 4:04 pm

failbase

Nick Lally and will have a piece in Full Disclosure, a show opening tomorrow in the Sesnon gallery at UCSC. Look at dat pretty Epson TM-88 III. Big thanks to all the information available at http://microprinter.pbworks.com/

Failbase 831.xxx.4046 is a system for the collection and output of participant testimonies of failure. By leaving voicemail or sending SMS (text) messages to (831) xxx-4046, participants can submit their failures. As they speak or type, the failures are printed in the gallery as paper receipts. Visitors to the gallery space are encouraged to submit their own failures, as well as to read, cut, notate and file incoming failures according to how they see fit.

Failbase 831.xxx.4046 was conceived and created by Digital Arts and New Media graduate students Nik Hanselmann and Nick Lally under the auspices of E.G. Crichton who invited them to be part of Archive of What’s Left Behind.

comments

Uncategorized — nik @ 9:53 pm

screen-shot-2009-10-05-at-73309-pm

screen-shot-2009-10-05-at-65726-pm

how to scrape AXIS webcams with Processing

processing.org — nik @ 5:38 pm

axis

AXIS webcams are fun to play with because they are generally pretty easy to google, have fast feeds (depending), and sometimes allow user control. Of the thousands of AXIS cams online many of them are public. A somewhat well known trick to turn up thousands of AXIS cameras is to google for:

intitle:"Live View / - AXIS" | inurl:view/view.shtml^

Which will turn up thousands of (mostly) boring feeds. Every once in a while however, something really interesting turns up that you may want to scrape for some reason or another. The typical URL result for the cam is something like:

http://191.22.175.200/view/view.shtml (this URL doesn't work btw)

Which sometimes displays an image in mjpeg format and sometimes displayed with a cgi script. A cool thing the cams do (and cool if you want to scrape) is catalogue all previous images on a server somewhere. This means that if the cam is displaying a mjpeg which is a pain to deal with, never fear! To access plain ol’ jpegs from AXIS web software you need to look here:

http://191.22.175.200/jpg/1/image.jpg?(UNIX TIME)

Where the Unix time is generally a big number. This makes the whole process pretty simple from here on out, as that is simply the location you need to query to get fairly up-to-date images from that camera. The directory structures sometimes change, and sometimes finding the jpeg URL is as simple as viewing the source of the AXIS camera page. Also, especially on faster camera feeds, the main AXIS page occasionally links to a mjpeg which is tricky to deal with.

Processing sketch:

//scrape AXIS web cameras with processing.
//please don't be a jerk with this sketch.

import java.util.Date;
PImage cam;
Date d;
float last_millis;

void setup(){
  size(320,240);
  d = new Date();
}

void draw(){
  cam = loadImage("http://somedomain/jpg/1/image.jpg?"+d.getTime());
  image(cam, 0,0,320, 240);
  last_millis = last_millis - millis();
  println(last_millis);
  last_millis = millis();
}

Pretty simple right? All the math with milliseconds can be deleted, the code is there to see the difference in time between the last time an image was downloaded. Downloading discreet jpegs causes some lag and is a lot slower than using a conventional browser. Also, remember that d.getTime() gets the current Unix time — you can always change that to whatever, assuming the webcam existed at that point.

all these triangles!

processing.org — nik @ 4:10 pm

yay! Finally uploaded something with fine lines to vimeo that didn’t get entirely screwed up by the compression process. Animation Codec @ 720×480 with lots of keyframes seems to do okay.

all these triangles! from nik hanselmann on Vimeo.

Next Page »
This work is licensed under a Creative Commons Attribution-Noncommercial-Share Alike 3.0 Unported License.
(c) 2010 nik’s blog | powered by WordPress with Barecity