"Josh Lawrence" <hardbop200@xxxxxxxxx> writes: > A very good friend of mine [..] doing some rap music I'd like to hear him;) > The computer would be providing beats. There should be a set of > beats preplanned Exactly. > able to be changed on the fly. Right > Seq24, maybe? Seq24 does not have a way to easily manage this. > It would be really nice if everything could sync to MIDI clock Yeah, I have a problem with that, too, so I have to do everything inside SuperCollider, at the moment. > What do you all think? I'm doing everything in SuperCollider, but trying to move all synthesis over to Common Lisp Music. The sequencing, I'll still do in SC, but I would need JACK MIDI, JACK OSC and JACK TRANSPORT in both SC and CLM to be able to have a working setup;). > Are any of you doing anything like this I am;). > how are you doing it? SuperCollider. This is how it works: The client is using timestamped OSC messages, sent a little time before the event is scheduled to happen. This ensures exact timing and gives the synth server some time to set up the graph. Each event reads from a bus when it's scheduled to trigger a synthesis network in the synth server. The value on this bus is exported from SuperCollider and may be set via MIDI/OSC. Each synthesis graph on the server has its parameters exported as well, and may be realtime manipulated over MIDI/OSC. In its most basic form and the functionality you're after, you're able to switch patterns (beats) on exact end of beat. This means you can change the drum loop or any part of the arrangement at any time. Each event object is also a separate instance, which means you can manipulate each event individually. In your case, you can use samples if you prefer, but I'm trying to do everything in synthesis, which I haven't actually gotten to a pleasing state. I use a BCF2000 to control everything. -- Esben Stien is b0ef@e s a http://www. s t n m irc://irc. b - i . e/%23contact sip:b0ef@ e e jid:b0ef@ n n