MIDI Kinetics Forum

Hello,

i want to program a Sequencer in Lemur which is similar to this:

http://www.youtube.com/watch?v=uV9-XA5MPwY

For this i need a very good control over the step as i want it to run forward, backward, trigger steps multiple times etc.
As far as i can see, the standard Lemur Sequencers are just able to run froward step by step with each pulse so i figured i need a custom on clock script which controls the step and sends the noteout dependant on switches and multisliders.

I have started this and have said onclock script which drives a running light on a standard switch object and sends noteouts according to the switches setting.
But i soon realized that there will be some issues where i wonder how i can do it. First thing is noteoffs/gatelength. Where do i put the noteoffs? The finest resolution of the clock pulse is 1/64th, so in a 16th note sequence i can just imagine 3 different gate lengths or is there a way to achieve finer resolutions which will be needed when i come to things like swing?

I think what is needed is an On tick script. Is that possible to add? Or any other way to implement a fine Resolution Gate Length in a custom Sequencer?

Just wondering if the Pad release feature can be used for a finer grained gate length in a custom Seqencer Szenario. Like when the on Clock triggers the note on according to the set triggers on the Switch Object, it also triggers a Pad which in turn uses the release feature to send the note off?

I have not used the release feature that much but does that make any sense?

The smallest time grain is 1/64. Sequencer optimization applies only to the Step* objects and the On Clock scripts. Attributes of other objects (such as Pad release) do not benefit from the clock optimizations and will revet to updates on the frame rate of the app.

nick_liine wrote:The smallest time grain is 1/64. Sequencer optimization applies only to the Step* objects and the On Clock scripts. Attributes of other objects (such as Pad release) do not benefit from the clock optimizations and will revet to updates on the frame rate of the app.

So no way to make custom sequencer with a finely adjustable Gate Length or Swing? No trickery somewhere hidden?

Or on the other hand is there any way to make the sequencer objects run backwards, skip steps, trigger one step multiple times before it goes on?

electrofux wrote:

nick_liine wrote:The smallest time grain is 1/64. Sequencer optimization applies only to the Step* objects and the On Clock scripts. Attributes of other objects (such as Pad release) do not benefit from the clock optimizations and will revet to updates on the frame rate of the app.

So no way to make custom sequencer with a finely adjustable Gate Length or Swing? No trickery somewhere hidden?

Swing is always adjustable. When using the Step* objects, gate length I'm afraid cannot be finer than the step length you choose in your object.

electrofux wrote:Or on the other hand is there any way to make the sequencer objects run backwards, skip steps, trigger one step multiple times before it goes on?

Yes, all that is possible with On Clock scripts and building your own sequencer from scratch.

Hi Nick,

i think i mixed up too much stuff in my question. Therefore i have attached a file with a custom sequencer that runs only on an on clock script and has no Sequencer Modules involved because i want to have controll over the step. In this case it has the ability to run the sequence backwards.

But i have no idea how to adjust the Gate length like in the setpsequencer objects the same goes for swing.

Do you have any idea how this can be implemented?

Just chiming in to say, that the Pad objects release wouldnt work anyway....the envelope settings of objects are disregarded when the object's x expression has been set programmatically (via script)

yeah i noticed that when reading the pdf another time that is bound to a touch event.

Swing is going to be a Problem. Well, length too but that is not that dramatic.