001 | SR + EP

Jun 07

001 | SR + EP from Sebastien Rien on Vimeo.

Untitled

Apr 03

Cute glitch appeared in the process:

Ordinateur Central

Dec 24

Just coming back from a residence in France (Le Vigan, coproduction OUDEIS) where I worked on a performance with the PHASE3 team. The project was called “Sinon…”.
See the residence blog for more: phase3-sinon.tumblr.com


Photo: Gaspard – OUDEIS

Here is the plot: “Sinon” means “otherwise”, “or else”. It’s about “what will happen if I don’t [do something]“. We don’t know so we produce, we prey, we consume, … endlessly, too afraid of what would happen if we stop doing it. We translated this concept into a techno-mystical religion assisted by a super computer (Ordinateur Central). The story says that this mythic computer has been built by a team of high level scientists, then took to an unknown location on earth. The team lost contact for mysterious reasons, leaving the computer running and the PHASE3 team with a connexion to it.

Ordinateur Central (OC) job is to optimize the real world. It analyses and produce reports and warnings. During the performance, all actions happen because the OC told to. Loud alarms would turn on sometimes, urging the operators to stop it. We don’t understand why we have to do things, but we do it since we highly trust the output of the super computer.

So I had to build this computer (somehow). I worked a long time on it and after the show, I could not let it go. I wanted to make it alive and give it a face on the internet. http://ordinateur-central.com is the web window to Ordinateur Central. There you can see what this super machine is up to. I worked the visuals from a decomposition of traditional “megatron” faces into simpler, more abstract shapes:

It is all rendered without a single image, pure HTML/CSS. (It is possible that it won’t work in IE. OC seems to hate this software…)

ordinateur-central.com will evolve, who knows what OC is up to….

Google Reader Share

Nov 03

The morning Google actually made the switch to the new UI and +1 feature, I had the whole day free. Thank God for that ! I quickly went through the sharing options and found out the ugly truth: no more sharing. I just couldn’t live with it and I knew how to recreate it, and so did I.

- Get the plugin -

The word “share” is everywhere now, but gReader’s share had something else. It was not a social share as those guys at Google and Facebook seem to understand it now. It was an open sharing. You did not need to log into some fancy social network with tons of options, where “friends” would be waiting for you to talk in real-time and everything… It was like.. more peaceful. But now they want you on their network. They don’t want you to use standard and open ways to share stuff. I think they’re wrong, and it seems I’m not the only one.

My point in making this plugin is that the share feature should be OPEN and STANDARD. I’m willing to gather a community and define a standard way to share items (anything) via bookmarklet or even a new sharing button in ALL reader apps ! Just like you can tweet any link, you could share any feed item.

Seeing such a terrible update on one of my favorite webapp, I got mad. I spent the whole day coding the damn feature. Short note on the dev part, I insert script tags in gReader’s DOM and use JSONP to talk to lipsumarium.com’s server. And it just worked ! Now the hardest part is coming…

How to tell millions of deceived gReader users the battle is not over ? That we can work together, without Google, to actually have an open way to share, keep using gReader and have friend lists. I’m working hard on Twitter to get the word out. It is crucial that gReader users know about it. So if you can help spreading the news, please do.

Google made a very bad choice here. That’s not how the web should be (notice usually *they* say that), thats why I made it and will continue to enhance it. I host it on lipsumarium.com but somehow temporarily, as if the project get tons of users I’ll need to scale the thing up. But I deeply believe that if a community grows around this project, I’ll find great people to help me with this. I’m not willing to build this project on my own, it should be community driven. The share spirit, well, you got it.

So try it, report any bugs or weirdness and share your ideas for a better sharing web.

Eternity

Sep 15

Eternity

A moment passes and the next comes as quickly as we forget the later one.

http://lipsumarium.com/lab/eternity/

Experimental Study on Web Asynchronicity

Apr 02

Experiments using the “web time noise” as a way of composition.
The noise seen has not been coded with a random function of some sort, it is the network response time and the browser’s imprecisions that create the asynchronicity.

http://lipsumarium.com/lab/asynchronicity/

erip leunamme by Videogrammo

Feb 18

by Videogrammo

Contemplation de l’angoisse

Nov 25

Visuals for Sebastien Rien’s live @ Antwerp.

Some kind of glitch

Nov 04

I love graphical glitch. When the machine, usually video compressor, makes a mistake, but doesn’t crash. You end up with amazing effects sometimes, like this one:

This image is a screen shot, untouched. (from my personal glitch collection)

With Glitcher, I try to render the same kind of bugs, but on still images. The animation is the glitching process itself. My first experimentations were on images, like those:

I wasn’t very satisfied with these: too simple algorithm, no movement. I also discovered that simpler imagery, even very abstract gives the best result. So I worked it again, and here is the V2:

The circular effect on the last 2 has been created for the use of “Glitcher” live, while rehearsing for an upcoming project “TO”. More on this later…

ROST

Oct 24

ROST a été présenté lors du vernissage de l’exposition “No Trouble Interactive Exhibition“, dont le thème était “le trouble”.

Le trouble apparait comme un état complexe car incompréhensible, impossible à appréhender. Nous le connaissons en tant qu’humains mais que serait le trouble pour une machine ?
Un bug informatique ? Non, la machine soit n’en a pas conscience car elle est «morte» en même temps, soit c’est pour elle un paramètre parfaitement mesurable et quantifiable.
Une corruption de donnée ? Elle n’a même pas conscience de ce que signifie la donnée.

La machine n’a aucune idée de ce qu’elle est en train d’accomplir, elle ne fait que brasser des données.
Au vu de la quantité astronomique de calculs qu’une machine est obligée de faire pour appréhender notre réalité, sortir du trouble de notre réalité – et encore, elle n’aura alors fait que transformer des données sans sens en autres données qui n’en ont pas plus pour elle: des cordonnées spatiales, des intensités de signaux,… – on peut dire que la machine n’a qu’une vision trouble de notre réalité.

La “vision” d’une machine, le seul langage qu’elle puisse appréhender se trouve dans le domaine mathématique:

4,75,2,753,91,29 – est trouble, n’a pas de sens
2,4,29,75,91,753 – a du sens.

L’image d’un visage ou d’un corps a du sens pour nous, humains. Pour une machine, il ne s’agit que d’une suite de couleurs organisées de manière incompréhensible.
La machine «rost» nous montre sa propre vision de notre réalité. Plutôt que d’afficher des pixels dans un ordre qui n’a aucun sens, elle les trie, les organise selon ses critères de machine* afin de leur donner un ordre, une représentation qui ait du sens pour elle.

Dès que la machine sort du trouble, nous y tombons. Nos visages et nos corps n’ont plus de sens. Pourtant tout est là, trouble.

*Le langage de programmation de «rost» (Processing, donc Java) définit une couleur au moyen de 32 bits. Dans ces 32 bits sont stockées 4 informations: transparence, rouge, vert, bleu. Chacune de ces information dispose de 8bit, soit une valeur entre 0 et 255. Par exemple, la couleur rouge s’exprime comme ceci:
00000000 11111111 00000000 00000000
On peut exprimer ces 32bits en décimal, ce qui pour notre exemple donne 16711680. Voilà comment «rost» obtient un nombre pour chaque pixel qu’il reçoit de la camera, et peut ensuite les trier.