MIDI Kinetics Forum

Over the last week i started to built a Lemur template for the Thor Sequencer. But it is not meant to be a Map for a single Sequencer. In the end i want to have 16or more Sequencers distributed over two interfaces with running lights and all the shizznizz.

The Interface for the first 8 rows is done so i figured i upload it.

So the thing works as follows:

In the zip Thor8Sequencer you finde the Lemur template as a .jzml file and two folders for the remote files "Map" and "luacodecs" which each have subfolders "electrofux".

1.) load the template into lemur and go to the Default interface.
2.) put the folder "electrofux" under Maps into the Reason Map Folder
3.) put the folder "electrofux" under Luacodecs into the Reason luacodecs folder
4.) run Reason and add 8 remote surfaces Thorsequ1 to Thorseq8 and connect them via your Midi-driver of choice to your Ipad -i use loopbe and wifi (the Questions Mark that turns up in the Reason Remote Menu should not be a problem)
5.) load 8 Thors and assign each to one of the 8 remote surfaces

I have included a Reason file where the 8 Thors sit in one Combinator connected each to a OchenK Tuner (not needed though, it should be bypassed when you do't have it) and i have broken out the Gate connections for Note CV, Gate, Curve1 and Curve 2 to another Combinator where the corresponding spiders sit, so you dont have to go through the Thor interface when connecting Synths.
You can however use it for any thor sequencers anywhere aslong as you lock one of the 8 remote surfaces to it.
You can even chain a couple of sequencers to get 64step lines. Or use a matrix or Dr. Rex connected to the Step input cv in Step Mode to add shuffle.

That's it for setup.

Now the template:

You see 8 rows which correspond to 8 Thor Sequencers.

The grey row at the bottom shows the Run button for the 8 Sequencers. But simply hit play and they should all run if the setup was ok and the Thor sequencers were set to loop mode!

The rightmost collumn shows the switches for the slider section for each row.
So hit the first one and the sliders become grass green, hit the second and the sliders become light green and so on.

There are buttons for incrementing and decrementing each slider on top of them.
The red up and down buttons increment decrement all Sliders.

The Grey slider is sort of an endless slider to increment/decrement all. It does not work 100% to my satisfaction because of the bidirectional nature.

The 7 Buttons in the top left (Note to Curve2) switch the sliders of the corresponding row to the different functions in the Thor Sequencer (like Velocity, Gate, Curve1...). And they should get a border to show what function is active. This is a bit buggy atm (sometimes it changes the function in thor but then the border jumps back- just hit it again so you don't get confused.

The Steps button works different. When you hit it it becomes Red and then the 16 "up" buttons above the sliders represent the last step for the sequence. So hit one and the sequence length is set. Hit the steps button again and it should become white again and the up button should revert to their original function.

There are Menu items for the Note Octave Setting and Rate which work bidirectionally. Only the rate Menu doesnt work bidirectionally and it also doesn't feature all possible rates due to size restrictions. To see all the availabe rates hit "big" which increases the size of the slider section.

Copy, copies the current values for the 16 sliders and Paste, well, pastes them.

Slider 127/0/64 and Random sets all sliders to that value.

Thats it so far. I am planning on building in a routing structure to get 32/64 steps on a button Press but this is going to be complicated.
But the next interface will feature more rows dedicated to drums. I also want to integrate a buffre and glitch page to have a nice stepsequencing environment in then end.

There might be some bugs, i haven't tested it for a really long time. So if anything comes up i appreciate any feedback.

Now to the running light Problem:

There is a script called "running" on each of the Pads Object (Pads to Pads8). It works On Midi and expects note data from 17 to 32 (for the uneven row numbers) which the Thor Sequencer sends with its LEDs. I have checked that via Midi Ox those notes are sent to the Lemur. Depending on which Note is received it lights up the corresponding pad. Normally i would have done that in a for loop but because it wasnt working as expected i made a row of "if" clauses to get to where the problem lies. It turned out that the first pad that should react on Note Number 17 isn't getting lighted and i have no idea why this is so. That is the Reason why i set to 32 (dirty trick) so it seems to be running through. If you want to test it just set the first if clause in the "running" script to 17 to see what is happening.

I would love to get this fixed, so if anyone has an idea what i am doing wrong, i would be happy to hear it.

Hi Electroflux,

Not a reason user and bad english skills, but that looks good though.

I made a small example for running sequencer lights.

The fuction is
You will see the seqLen and seqStep variables inside of pad object.

segLen can be a constant if the sequence len doesn't change it it's fixed.
and seqStep is where (I think) you could pass the note id and modulo it by seqLen.

Does that helps?

Cheers,
AB

Thx, this looks alot more advanced I will try to implement it when i come home.

Hey, just attached other (not checked with lemur), there is midi script to pass the note id to pos variable.

Hope that helps,

Cheers

Omg this is so weird. At first it didn't work. The first and the last step were lighted only.
Then i changed:

pos = MIDI_ARGS[1] - 1;
to
pos = MIDI_ARGS[0] - 1;

Then the lights started running BUT again the first pad wouldnt light up. It is as if the Reason Sequencer is not sending the first Note. But it is, but on second look in Midi Ox it seems to hick up as the Midi Ox screenshot that i have attached shows. It is sending two note ons successively just at the last and the first step. At least i found the cause for the problem though i have no idea how to solve it.

Hi Electroflux,

Difficult to me to check this out without reason app.

You did well changing MIDI argument to [0].

So, if you press play in reason, the sequence starts at the step #2? Maybe you can try to filter note off messages by adding a if condition in midi script, don't know if this will fix the issue.

if(MIDI_ARGS[1]){ pos = MIDI_ARGS[0] - 1;}

Note I am using -1 because I read it sends 17-32 values?

Cheers,
AB

lABl wrote:Hi Electroflux,

Difficult to me to check this out without reason app.

You did well changing MIDI argument to [0].

So, if you press play in reason, the sequence starts at the step #2? Maybe you can try to filter note off messages by adding a if condition in midi script, don't know if this will fix the issue.

if(MIDI_ARGS[1]){ pos = MIDI_ARGS[0] - 1;}

Note I am using -1 because I read it sends 17-32 values?

Cheers,
AB

Luckily it is only the LEDs that mess up and the LEDs send no soundcritical data. Everything else is ok.

I thought about the filtering too and tried to do it externally first but i think i did something wrong. I will try the internal filtering tonight.

Thx for the help.

No problem, hope you have it working.

Good luck!
AB

I think i got the problem nailed down and it is most likely a Reason bug.
The single running light always send two conescutive Midi messages which can be sprecified as eg program changes from 17-32.
So LED1 sends PC17 and PC17, LED2 sends PC18 and PC18.
But when the last step of the sequence comes (depending on the last step settings in the Sequencer) it sends (lets say last step is 12) PC 12, PC1, PC12,PC1. Which leads to not lighting the first LED somehow.
I can however rewrite the stream so that it sends PC12,PC12,PC1,PC1 BUT this is getting messy when different running directions come into play. I am not so sure if i just leave it like it is, wait for a Reason update or help from their side, or just get my head around an algorithm that changes the stream depending on last step AND running direction.