This is some sort of devlog from the Summer Session residency at V2.
Object Oriented Choreography got selected from Sardegna Teatro and we were sent in the Netherlands* to work for the whole summer**.
\* actually i was already here
\*\* actually my plan for the summer was really different but what can i do
Take everything as a WIP because it's literally that
## Workshop?
@ -40,8 +52,6 @@ The third iteration of OOC could be two-parts workshop: in the first moment part
* improvisation
### Outcomes:
1. documentation of the workshop
@ -276,6 +286,7 @@ The VR editor is used as an installation. Other than the normal functionalities
Both options can be activated multiple times, with different results. The resulting 3D environments can be archived on a dedicated space (like a showcase website) in order to document, (communicate, and $ell the project again for further iterations)
# BREAKING CHANGES HERE
### Meeting with Sofia and Iulia
@ -283,7 +294,6 @@ Both options can be activated multiple times, with different results. The result
**ok ok ok no workshop let's stick to what we have and polish it**
- interaction from the public change the space
- facilitate access to the website
- website: intro, brief overview
@ -352,6 +362,7 @@ Both options can be activated multiple times, with different results. The result
## 29/7 - Prototype Setup \& other
The building block is the Stage. Each stage is a description of what's happening at the edge of the performance: what the screen is displaying, what's inside the VR, what's happening on users' smartphone.
We can place a series of stages on a timeline and write a dramaturgy that it's based on the relation between these three elements.
@ -411,17 +422,25 @@ happy with it! it's much more flexible than the long if snake
## 1-2/08 - two Displays & Prototype setup
Yesterday together with Richard we setup the two screens to show what's happening inside the VR for the public. Initially they were mounted next to each other, in vertical.
With Iulia we thought how to place them. Instead of keeping them together probably it would be better to use them at the edge of the interactive zone. Even if the screen surface seems smaller, it's a creative constraint \& it creates more the space of the performance.
Ideallly the viewer can see at the same time both screens and the performer.
The screens can display either the same or different things.
And now some general thoughts:
the username should be central in the visualization of the interaction, since it's the main connection point between between whats happening outside and inside? could it be something different than a name? could it be a color? using a drawing as an avatar?
### types of interaction
@ -614,6 +633,7 @@ Invitation and definition of the domain: touch interaction and public partecipat
from partecipation to collective ritual
## 6-08
Two ideas for the performance:
@ -640,6 +660,12 @@ How wide or specific our bestiary should be? A whole range of different object a
From here --> visual identity with 3D scan?
<videosrc="prime.mp4"controls></video>
### The Three Interactions
All the interactions are focused on the physical use of touchscreen. They are simple and intuitive gestures, that dialogue with the movements of the performer.
@ -717,6 +743,10 @@ Actually the prototype works fine just with the decreasing intensity, i didn't t
Also: displacing the textures doesn't look nice. It just feels broken and glitchy, not really an object.
<videosrc="bici.mov"controls></video>
**for what concerns the display:**
1. in one screen we cluster all the objects in a plain view, something like a grid (really packed i presume? it depends on the amount)
@ -727,6 +757,9 @@ we could also display the same thing in two screens, to lower the density of obj
how this interaction interacts with the choreography? is it enough for the performer to be just a point of view?
