«first  …23 24 25 26 27 28 29 last»

LOSS Livecode History from the Pub

2007-07-24 18:32 livecoding

Here I've attached the SuperCollider history file from my performance at the headphones concert at the live coding festival in Sheffield... livecode.access-space.org (archive.org)

It's a bit embarrassing if you study it more carefully. The use of ~pub near the end is a big mistake for instance. I meant ~out and I don't know what I was thinking there...

You can also look at the file '2007-20-20pub.rtf' for the actual document I used. Some comments in there didn't make it to the history file as I forgot to evaluate them.

Here are also the notes and statistics from my presentation "Live coding practice" in which I talked about my month worth of practising.

Attachments:
070721live_coding_practise.rtf
070721count_classes.rtf
070721table.rtf
2007-20-20pub.rtf
2007-20-20-23h07-History.rtf

June Practice Sessions

2007-06-10 16:28 livecoding

In preparation for the LOSS livecode festival (archive.org) in Sheffield, I'm doing another month of practice. 1 hour/day, start with an empty document, no third-party classes or UGens and then upload the result here on the swiki.

This time my sparring partner is photographer and artist www.fotokatie.com/katier. She's doing a very nice series of 'star shots'.

In addition to getting my live coding chops in shape (hopefully), I got commissioned to analyse and present the outcome at the festival. This is a great thing. So the bet with Katier provides the pressure, the scheduled talk the deadline for analysis, the upcoming gig the motivation and last the commission pays for one strong coffee at my favourite café each day of the period. What could go wrong?

Well, it's summer and I've been working too much as is...

MP3s and code in the post /f0blog/june-practice-sessions-again/


Low Life

2007-04-30 20:38 supercollider

Attached are three programs that all use some sort of audiovisual self-referential code in that they synthesise their own syntax.

As I think this only works on SuperCollider OSX I made some short videos...

One can also write custom 'scores' for these programs to perform...

Note: this code will only work on older OSX versions of SuperCollider (Cocoa, <3.6)

Attachments:
redWorm.zip
redSnake.zip
redSnail.zip



redFingerprint

2007-01-19 00:05 supercollider

A different plot for SuperCollider. Though it is actually more useful as an 'artistic' visualiser rather than a serious way to represent data. It works with collections like arrays, envelopes and wavetables. The technique is to translate them to length/angle pairs and then draw a shape from that.

redFingerprint screenshot 2 redFingerprint screenshot 3 redFingerprint screenshot 6 redFingerprint screenshot 7 redFingerprint screenshot 8 redFingerprint screenshot 9

It's distributed via SuperCollider's package system quarks. All open source.

Quarks.install("redUniverse");
//and then recompile

There's also some older code here that does similar drawings...

swiki.hfbk-hamburg.de:8888/MusicTechnology/833

Data?

redFingerprint screenshot 10 redFingerprint screenshot 11

And of course, it's always more fun when things break. Here the same thing with a nice bug...

redFingerprint screenshot 12 redFingerprint screenshot 13

Updates:

  • 090511: redFingerprint is now part of the redUniverse quark

Work with Mark: RedUniverse - A Simple Toolkit

2007-01-18 22:56 research, supercollider

I made a short demo/poster session at the LAM conference on 19 December 2006 in London. See livealgorithms.org (archive.org)).

Below is the handout describing the toolkit.

RedUniverse screenshot 01 RedUniverse screenshot 08 RedUniverse screenshot 09 RedUniverse screenshot 15

This toolkit is now distributed via SuperCollider's package system quarks. All open source.

How to install:

Quarks.install("redUniverse");

RedUniverse - a simple toolkit

Mark d'Inverno & Fredrik Olofsson

This is basically a set of tools for sonification and visualisation of dynamic systems. It lets us build and experiment with systems as they are running. With the help of these tools, we can quickly try out ideas around simple audiovisual mappings, as well as code very complex agents with strange behaviours.

The toolkit consists of three basic things... Objects, Worlds and a Universe. Supporting these are additional classes for things like particle systems, genetic algorithms, plotting, audio analysis etc. but preferably many of these functions you will want to code your self as a user.

We have chosen to work in the programming language SuperCollider (www.audiosynth.com) as it provides tight integration between real-time sound synthesis and graphics. It also allows for minimal classes that are easy to customise and extend. SuperCollider is also open for communication with other programs and it runs cross-platform.

So to take full advantage of our toolkit, good knowledge of this programming language is required. We do provide help files and examples as templates for exploration, but the more interesting features, like the ability to live-code agents, are hard to fully utilise without knowing this language.

Detailed overview

In SuperCollider we have the three base classes: RedObject, RedWorld and RedUniverse.

  • RedObject - things like particles, boids, agents, rocks, food etc.
  • RedWorld - provides an environment for objects.
  • RedUniverse - a global collection of all available worlds.

Objects all live in a world of some sort. There they obey a simplified set of physical laws. They have a location, velocity, acceleration, size and a mass. They know a little about forces and can collide nicely with other objects.

Pendulums are objects that oscillate. They have an internal oscillation or resonance of some sort.

Particles are objects that ages with time. They keep track of how long they have existed.

Boids are slightly more advanced particles. They have a desire and they can wander around independently seeking it.

Agents are boids that can sense and act. They also carry a state 'dictionary' where basically anything can be stored (sensory data, urges, genome, phenome, likes, dislikes, etc). Both the sense and act functions, as well as the state dictionary, can be manipulated on the fly. Either by the system itself or by the user in runtime.

Worlds provide an environment for the objects. They have properties like size, dimensions, gravity etc and they also keep a list of all objects currently in that world.

For now, there are three world classes:

  • RedWorld - endless in the sense that objects wrap around its borders.
  • RedWorld2 - a world with soft walls. Objects can go through but at a cost. How soft these walls are and how great the cost depends on gravity and world damping.
  • RedWorld3 - a world with hard walls. Objects bounce off the borders - how hard depends on gravity and world damping.

The Universe is there to keep track of worlds. It can interpolate between different worlds. It can sequence worlds, swap and replace, and also migrate objects between worlds. All this while the system is running.

The RedUniverse class also does a complete system store/recall to disk of all objects and worlds.

So the above are the basic tools. They should be flexible enough to work with e.g. objects can live in worlds of any number of dimensions. But as noted, one can easily extend the functionality of these classes by subclassing.

Conclusion

How the objects and worlds behave, sound and look like are open for experimentation. That is, this is left for the user to code. So while there is great potential for customisation, it also requires more work from its users.

The RedUniverse as a whole tries not to enforce a particular type of system. E.g. one can use it purely without any visual output or vice-versa.

We see it both as a playground for agent experiments as well as a serious tool for music composition and performance. We hope it is simple and straightforward and while there is nothing particularly novel about it, we have certainly had fun with it so far. Foremost it makes it easy to come up with interesting mappings between sound and graphics. In a way, we just joyride these simple dynamic systems to create interesting sounds.

The software and examples will be available online on the LAM site. Of course as open source.


Default Synth Hack

2007-01-18 18:10 supercollider

I recently implemented something Nick Collins and I discussed a long time ago (SC2 era - custom event class). It is a 'hack' of the default synth in SuperCollider. That is the one that many of the help and example files uses. So when you install my class, the default file will be overwritten and all the slightly daft pattern examples will from there on spring into new life.

Install it and then run some examples. Most of the ones in Streams-Patterns-Events5 and Streams-Patterns-Events6 work very well. See the RedDefault help file for more info.

(And yes, it is easy to uninstall and get back to the boring default synth)

Just to compare - here's first an example taken from a help file playing on the default synth...

And this is the exact same example with my hack installed...

Not only does it create a new synthesiser it also changes duration, attack/release times, amplitude etc. The pitches are mapped to a diminished chord in a somewhat strange way: the slower the duration - the greater the leap between the notes to quantise to. For example, if half or whole notes, only octaves will be heard.

Updates:

  • 111116: redDefault is no longer a quark. It's available on the page: /code/sc/#classes

«first  …23 24 25 26 27 28 29 last»