posted 31 January 2007 11:43            

I had asked the very same question when I first got Kyma! the answer from Carla was as follows:

"Although there is not a way to loop the Timeline cursor, you *can*
set up an individual Sound to loop and put a WaitUntil module in the
track above it to keep it looping until you tell it to go on.

For example, you could have a Sample or AnalogSequencer module with
Looping checked and you could put it in track 2. Then you could put
a WaitUntil in Track 1. When the Time Cursor hits the WaitUntil,
your Sound will continue looping until you signal the WaitUntil to
resume."

(I tweak parameters of a sound in the Sound File editor with an external midi sequencer in loop mode.)

posted 01 February 2007 22:30            

quote:

---

Originally posted by SSC:
To generate a MIDI program change, the SoundToGlobalController should have its parameters set to:

Value: !ProgramChange * !Gate
GeneratedEvent: !ProgramNumber

The !Gate is there so you can first select a Program number, and then press Gate in order to send the program change number. (Otherwise it will continuously send the program change and the time cursor will be stuck in a short loop trying to jump back to that marker all the time.)

Since you have the SoundToGlobalController on track 2 and its MIDI channel is set to channel 2, you should also set the Timeline to receive MIDI program changes on channel 2. You can set this by selecting from the drop down menu at the top of the Timeline next to TimeCode (the default display is --).

---

However, this doesn't seem to work. When I hit the !Gate there is no response. If I use a toggle instead I do get the program changes, but the timeline gets stuck at that position of course, as the value continues to be sent while the toggle is on. Any idea why !Gate doesn't work? I tried it also outside the timeline, just displaying the value that would result from the SoundToGlobalController (!ProgramChange * !Gate) with a !Fader, but I don't get any response from !Fader. I would expect to see the fader jump to the selected value and then back to zero immediately, as would be necessary for the program change to work. I can see this happen if I add some smoothing, but that doesn't work for this problem. It would seem that the values sent by !Gate don't get read fast enough to have any effect on the program changes. Any thoughts on this? How could we send program changes from the VCS in a reliable way?

posted 02 February 2007 08:58            

PrgmChngTimeLine.ktl

Here's a simple timeline example for cebec. Pushing the buttons (from an external controller ) will take you to the respective markers, so when the cursor is getting to the end of your sound you can hit the gate to send it back to the begining of that sound and make it acts as if it were looped.

Cheers,

posted 02 February 2007 09:27            

When you put a wait until at the end of a sound the cursor will stay there until you release it, and your sounds will continue to run normally. However, when you do this the parameter automation won't work at that point, as the parameters will stay fixed when the cursor gets to the wait until. So what I do instead in those cases is to make a wavetable with the shape of the desired automation and read it from a function generator into a SoundToGlobalController. This allows the automation of the parameter to loop as the sound continues to run when there's the wait until. I use the AC Toolbox to make the wavetables (export them as soundfiles), and it works great. It is very easy to make tables simply by drawing lines, but you can also use all sorts of lisp functions to generate the behavior you want. You can probably also use a graphical envelope instead of the wavetables, which would make it easier to make small adjustments as in the timeline automation.

Best,