hello Ozone,I have spent the last couple of weeks expanding, updating and redesigning a very complete and seamless sound-analysis patch.This patch can extract many features from which the following would be of significance for ozone:

• spectral flatness (noisiness/peakiness).. useful for detecting specific soundevents within/from a soundmass
• tempo, beat/rhythm detection… tempo spectrum is very exciting (lots of micro tempos within signal are detected simultaneously)
• event detection (onset of pitched/unpitched events)… pitched onset detection is useful for detecting human voice and not detecting for example footsteps
• auditory-based loudness and spectral energy
• etc

all of these parameters and detections perform dynamic self calibration and juicy outputs between 0.0-1.0 are ready to be feed into Ozone.Besides analyzing environmental sounds, it would be interesting to have the ozone system listen to its own output and readjust itself and therefore from a non-linear dynamic system (cheap implementation of autopoesis.)

hi guys,So I’ve got just a basic, basic 4-value osc system sending microphonelevels to the group. I plan on adding stuff through this week, butthis is just to get started. The state of cables and mics was indisorder from a lot of migration to/from Frankenstein and then my timeoff, so this took some time to reorganize. There’s a boundary micplaced on the white table — please take to not damage / spill coffee /spill soup on it :)It’s running in Runtime so that hopefully, I can continue developingwhile it’s running and it’s protected from crashes.You may find the values aren’t sensitive enough with the noisy noisefloor (lots of ambient noise, fishtank, etc.), so I will try soon tryto filter some of that stuff out somehow and work on sending slower,more meaningful data. I’m planning to optimize and improvemeteor-shower this week, and so some of its system params and soundlevels I can also send out.I’m sending everything out port 8001. “env-follow” is essentially asignal level between 0. and 1.:/ozone/sound/features/mic.foyer/env-follow f/ozone/sound/features/mic.room-centre/env-follow f/ozone/sound/features/mic.common/env-follow f/ozone/sound/features/mic.table/env-follow fat about 100Hz. There’s no screen mic yet, there seems to be somethingwrong with Navid’s contact mic up there.For now, I’m sending all the data to the ozone network’s broadcast IP,10.0.0.255. So, if you have your local Ozone network config set with arouter of 10.0.0.1 or 10.0.0.239 (the latter being the Netgearswitch), you should automatically be receiving the data, just bindudpreceive to 8001.I plan on integrating Michael/Harry’s OSC serviceregistration/listener system once someone can give me a 5-minutehands-on.. unless it and its helpfile are already in svn?If you’re not getting anything and you notice the scrollingmultisliders not doing anything, try restarting dsp with the purplebutton. If the broadcast isn’t working for you, you can also put inyour IP if you don’t mind editing the patch.pps. Max5 SDK came out on Friday! now people have a chance to porttheir GUI-based objects which broke with Max5’s new interface.Tim

Dear Ozone folks,This Thursday Ozone lab’s ostensive goal is to make state changes palpable via concrete visual and sonic qualia.However, the deep motivation for research work is to realize an experimental apparatus formorphogenesis:  making it possible for us to create objects out of fields.To correct a misconception from the past 5 years of calligraphic video work,the visual  effect I’m after is NOT necessarily vague or fuzzy. The intermediate goal is to make it possible forany one of us, or a prepared inhabitant, to seemingly be able to fashion objects to any degreeof “definiteness” or articulation out of more primordial fieldsin a learnable way, not based on my learning geometric or other cognitive models.The fields may be highly structured, and not homogeneous  – but their inhomogeneity must be potentially meaningful, and not random.And objects, for me, are always temporal (events).Corollary: a visual object that has no sound is not interesting as felt experience.Xin Wei

Dear Ozone team , especially JS, Michael, Harry,There are a couple of nice examples.  For applications that I have in mind — neo-MeteorShower, neo-Cosmicomics, Frankenstein and IL Y A,  I’ll avoid showing explicit, a priori, geometry.  Metric forms, points, lines, and planes, should come out of live activity, not precede it, pace Plato and Kant. It should be easy to do some of that by appropriate rendering, eg using the 0-skeleton (and 1-skeleton) as control points for indexing into textures, etc.  I’d like to work with n-parameter variations of these,  1 < n < 6I think these look promising.http://132.205.138.226/nonnewtonian-poster.jpghttp://132.205.138.226/verlets_2-poster.jpgYou can choose the most parameters that might be most interesting,possibly: speed (acceleration), density, convergence, shape (topological) type (a continuous parameter).Some qualities likehue spatial-distribution, hue-dynamics (sheen or flicker),are applied  by post-processor, of course, but that’s a level of detailbelow the exposed interface to the instrument.Ye Olde Timespace (composite instrument) and Lattice-particle should be two of the instrumentsavailable Thursday.

* * *

Technically-aesthetically, I would set as a minimum challenge to realize  the expressive value ofChris Park’s analog effects, but with realtime computational control.Here’s a bank of examples re-posted from a year ago:http://www.chrisparksart.com/movies2.htmThese seem particularly rich:46141516182022The interesting thing would be to achieve subtle realtime control over the dynamics.The approach to take, given, the  modularized computational fluid dynamics (CFD) processors that Michael Fortin can provide, (advection, pressure, etc.)is to apply a separate layer of  CFD processing,and then drive them by continuous, sometimes densefields of data from live physical movement.The hard part is the CFD that Michael did.It should be quite straightforward to expose them as jitterobjects passing control and video matrices.  Making RICH sound + video instruments work JOINTLYin interesting response to live human movementcan be the goal for a subsequent Ozone lab. It is essential that we be able to parameterize Michael’s CFDprocessors with a dense (ie video, eg motion or optical flow vecor field AKA fur-grass)as well as sparse field.  (e.g. isolated highlight pixels abovea threshhold value)Xin WeiOn 17-Nov-08, at 7:54 AM, Harry Smoak wrote:

NiceBtw are using the blog or the mailing list, and if the answer is both then what should be posted to each?–HarryOn 17-Nov-08, at 4:10, Jean-Sébastien Rousseau <jsrousseau@gmail.com> wrote:

Some samples : http://132.205.138.226/

---

Ozone email:  ozone@concordia.ca 

---

Ozone publically visible blog: http://topologicalmedialab.com/blogs/ozone 

---

Ozone private project WIKI: http://www.topologicalmedialab.net/fields/tml/field.php?n=Projects.Ozone  

---

 I would say:

1. Store “permanent” information in TML WIKI. Permanent means should be of use beyond this term, for future developer,for writing a TML archive catalog,or for writing a paper.  Includes OSC naming conventions, people+roles, references etc.
2. Send persistent info that’s useful for the current term  to Ozone blog,includes items in (1) (which could be referenced by URL to TML WIKI, butbetter to simply copy into the blog).  This is info that your team matesshould find useful for roughly the week, or for the current lab.  (Anything that may be of longer term interest belongs in (1).
3. Email  ozone@concordia.ca to announce every emission in 1 or 2.  For topical info, alerts, Q&A where the answer is not likely to be needed beyondthe moment or the particular interlocutors.  (You never know, hence the blog)I would habitually blog just about everything for persistence,and use email to alert team mates that there’s new info on the blog to look at. 

---

http://topologicalmedialab.com/blogs/ozone/wp-admin/post-new.php  

---

Cheers, Xin Wei  

I’ve reset and reconfigured the Ozone network wireless access point

DI-624 - High-Speed 2.4GHz (802.11g) Wireless 108Mbps Router
http://support.dlink.com/default.asp?orig=2
DI-624_revD
DI-624 Revision D
http://support.dlink.com/products/view.asp?productid=DI-624_revD
AVAILABLE Firmware 4.04 (latest version) 6/13/2007

Followed instructions for reset
Assigned admin password: *****  << the usual
changed ssid tmlozone
Security WPA pass: ************** << same as old password
The IP address of the DI-624: 10.0.0.1
Subnet 255.255.255.0

DHCP available

I’d like to be able to blog by email.  Is someone willing (and already have the necessary access) to set this up?

http://codex.wordpress.org/Blog_by_Email#Step_2_-_Configure_WordPress_to_access_your_new_account

Now that we’re installed in the TML.  Maybe we can think about working with the natural passage of sunlight, and night light.  After implementing the neo-Remedios topology, maybe we can design states that more subtly counter or amplify the natural state of the TML’s room in its day-night cycle.                 On 29-Jul-08, at 7:23 AM, x w wrote:

Hi, I’ll drop in today between 4 and 5 to check in and see what’s up and running or runnable.I’ll try to guinea pig the instructions that Tim left behind.The milestone is to make a 4-state event (adapted from Remedios) work palpably in sound, video, lighting control.We could morph between:      

•  (0) “night” state (show plant timelapse videos on the monitors as screensavers, with their cyclic movement driving sound);
• (1) meteor shower with multi-voice stars, when people are walking under the ceiling camera (the stars should return to initial constellation whose positions are grabbed from highlights in a fixed or periodic sampled frame);
• (2) Interstitial membrane with contact mics when people touch the fastfold;
• (3) bringing up lights around (near) the oval table when the demo area is empty, and there’s activity near the table (as measured by mic or camera).

Dear Freida, Tim, Michael, JS, Harry,

Freida, it was good to catch up with you today :)

Based on recent chats with Michael and Tim
I propose that as a concrete test of Ozone, we go through the “Freida” exercise:
Freida can work with JS and Michael’s instruments to realize some of her effects in realtime.
The goal for May 2009: Freida can work with Tim and JS applying these to work with a live performer.

I’m asking Tim to work locally with JS and Michael instruments, in counterpoint with Freida.

Goals for these 2 weeks (for end of September 2008)

- JS tags a version of his Jitter library so Freida and Tim know there’s a stable version to work with.
Meanwhile we’ll work with what’s in SVN.

- Tim reviews the particle instruments (vintage July from the movement+media workshop — ask Morgan).
Tim can build some parameterization mappings from these Jitter patches to sound instruments. (MeteorShower +++) Parallel to Tim + Freida discussion about zippering (a medium-term goal) Our first test could be for Oct 3-5 with Bev Johnston , Navid can understudy with Tim for this.

- Michael Fortin and Tim wrap Michael’s new externals under JS’s (current) template, so they can be used alongside existing JS instruments. They should do this as an exercise.

- Freida and JS can look at JS instruments together
- Freida should get a set of MaxLibrary under “non-disclosure” to work with in Providence.(Ask Michael Fortin how to use SVN)

Morgan and Xin Wei are busy on assignment to Pneuma, but Morgan’s learning a lot about coding with sensors, so that’ll be useful and relevant :)

Harry’ll be back with ideas for experimental structured light using video and lights.

- Xin Wei

Ozone is the current incarnation of a media choreography system  designed by Sha Xin Wei for the dynamical shaping of a responsive media environment according to the activities of its inhabitants and the prior intent of its composers.    If you are an Ozone creator, please read the TML WIKI entries in the Media Choreography category, especially the internal technical reports on the physics and engineering design specs behind Eerm (2001), tgvu-code (2001-2004), txOom (2002), and applications such as MeteorShower (2007) and the software part of Remedios Terrarium (2008).  It should be documented in TML WIKI in its own project page, Projects.MediaChoreography.Ozone.

The code in TML’s SVN is not public domain, but many of its applications are public.