From: Spencer Russell <Spencer.Russell(a)oberlin.edu> Sorry for the late reply. I have read the responses! Some interesting leads! Postfish looks interesting if I could get it to compile. :)) Not yet, I will join now. At the moment, the backing tracks (about 5 channels) which just play, and few triggarable samples. The way of getting from one scene to another is different for each scene too. Some crossfade, others I catch a sound in a reverb, and cue the next track as it dies away. Part of the problem with this kind of stuff, as I'm sure you know, is that the stage action for the next cue does not often fall in a musically useful place. Hence the messing about with crossfades etc. I've been doing ambient loops just by copy and pasting a loop to make a long track, then playing the whole lot in the same way. Real looping would be nicer as a few abstract loops could be out of sync which would break any audible repitition. Simple is good. I think it's perfectly possible to make a useful gui in pd for this kind of thing. I end up usually with loads of bangs attached to number boxes for the initial space. I have seen pd patches where all the data is in files and is loaded and parsed on the load bang, but it looked kinda complicated. Perhaps the whole thing could be broken down into pd patches. A scene backing player, a triggarable sampler, a programmable cross fader. Then you could assemble the ones you need for each scene. The difficulty is as you say in saving the state and seamless transitions between each collection of modules.