Sequencomat v1: Drum/Notes Midi-Sequencer

[Mat]

Hey Mutants,

I made a new Midisequencer for the Lemur
http://www.jazzmutant.com/lemuruser_moduledetails.php?id=153

You can see a video that demonstrates the functions here:
http://www.youtube.com/watch?v=rERe3wn8dGA

It is done in Max5, but will also work with the free runtime version of Max you migth get at the cycling74 homepage. The reason therefore is a more reliable timting while doing the triggering in Max. Some variables are also calculated on the Lemur.

The sequencer comes as a module so you can add it to your existing projects, just don´t change the name of the container or controls.

If you´re new to Max and that OSC-connection thing I suggest that you go through some of the tutorials in the workshop section....

Here is in short what to do to get this sequencer run:

Add the module-file to a new interface
On the Lemur go to settings -> OSC -> enter on OSCtarget 0 the IP of your computer (port=8000).
Open your rewire host.
Open Max (runtime), choose "ad_rewire" in DSPstatus, load patch.
Enter IP of your Lemur inside the patch. (yeah, my Lemur IP is really...6.66, so this wasn´t ment as a silly joke)
Choose your Miditarget in the patch
Activate Switch X
-> Now the buttongrid should turn green and you´re ready to start.

Enjoy!

[Plyci]

Very Very Nice Mat!!!!

Im going to have a play with this later tonight!


_________________
www.myspace.com/plyci

[Mat]

This sequencer will not work with Max runtime in this version, although I promised that. I´m very sorry for that fault.

I´ll try to fix that as soon as possible.
For more details read here: (both sequencers use the same engine)
http://forum.jazzmutant.com/viewtopic.php?t=2264

Any help of more experienced Max-users is highly appreciated!

[Mat]

I guess I´ve fixed that problem with a little help from the forum....

So now everything should work with the free Max runtime !

The difference is that the runtime of Max doesn´t have the ->options->dsp-status menu..... so now choose your driver directly at the patch.

Can anyone with runtime only test it and repond here?

[yllosch]

works well-no problems with max runtime
wish:1. groove-funktion (like ableton live)
2. different tempo-div. for each track

thank you for this

cheers
norbert

[Mat]

Thanks Norbert for your report

I tried to keep it simple in that patch - for me as a Max starter to get the projects done, but also for the user to make a quick and clear interface (in the other sequencers where you can change the tempo on each track I always missed a function to skip the whole bunch)
But as you see in the ".....v1"-ending, there is hope for future sequencers with more complexity. My dream sequencer goes far, far beyond....

Meanwhile I like that step-range-thing (as always...guess I´m addicted to ranges) and that this sequencer is also nice for playing tones (in the "pairofx0x" the tone setup has to be done in the maxpatch and with the great gueglay sequencer I experienced that it doesn´t send noteoff proper - well, I love these sequencers, but that was the reason why I developed mine)
Anyway, your free to choose and now you got one more sequencer with tight timing on the Lemur...

G*Mat

[Mat]

I´ve update the Sequencomat.

Now you can shift the whole sequence with the blue bar at the bottom and
- more important - you have 16 presets to save and load !

The saving is done on the Lemur and not in Max. But the perfomance is very well and it raised the impact on internal memory only slightly (31%->37%). While saving and loading you have 3 modes: grid/note/both.
In grid it saves the matrix, the grid, direction, volume and notelength (including the ranges), the steprange and the startpoint (to shift the sequence).
In note it saves the notes, octace and transpose.
In both (default) it saves both - of course....
The advantage of that is you can route the notes of one preset to the rhythmic section of another preset or vice versa - more interesting when playing notes than when playing drums.

The mute-switches are not saved. This is because I see them as independent from the patterns. If I have muted the bassdrum for instance I want it to stay muted even if I change the pattern. And as long as the Lemur is multitouch I can let the bassdrum come in and change the pattern if I want to. But you can expand the script....or drop me a line if you all think, that the mute-switches should also be saved.

Enjoy!

btw: this sequencer doesn´t have a volume for each step (what is really a pitty), but with the note-patch you can route the same drum to different tracks with different volumes if you need that for a special pattern.....

[yllosch]

thank you for this update

lots of fun
cheers
norbert

[yllosch]

thank you for this update

lots of fun
cheers
norbert

[Jannis]

I really enjoy your template!
Spezial with Impuls it´s big fun!!!
I think the timing is more exactly
then with most other Lemur sequencers i tried!

But there is a question i have:
In Ableton witch midi In´s and out`s you activate from the midiport
i took all In´s and out`s like track, sync and switch them on,
but sometimes Ableton crashes then.

Thanks for sharing this beautiful template
Jannis

[rafa]

i really like the sequencer is very Very Nice Mat. i been playing around with it for hours so congratulations

[Mat]

Thanks for your positive feedback
...I really appreciate that! (I started thinking, that the template is not so good at all after 100 downloads and nearly no feedback)

@ Jannis
This sequencer is synched by rewire. So you don´t need to activate any sync in Ableton. You just have to open your rewire host first before running the max-patch.
Furthermore it doesn´t send any remote data (like CC), so you don´t need to open any "remote" in.
The sequencer only sends note information on one output. That output you choose on the Maxpatch (one of your virtual midicables). This is the only "track"in you have to activate in Ableton!
(btw: This could be the same you use for your Lemur targets, but it could be also a complete other to avoid conflicts.)

[Mat]

One more update on the Sequencomat.
http://www.jazzmutant.com/lemuruser_moduledetails.php?id=153

I added a random function on the step and a on/off switch for transpose.
Watch a video here:http://www.youtube.com/watch?v=1gNp7u3TlRw

The ZIP ("SequencomatV14.zip")contains 3 template-files differing in Lemur CPU usage, because this Sequencer - in the video version - claims 45% of Lemur ressource! It works nice with other templates as shown, but if you already have a "crowdy" project 45%percent might be too much. Therefore:
"SequencomatV1_nopreset.jzlib" - 30% (without presets and random)
"SequencomatV1.jzlib" - 38% (presets, but no random)
"SequencomatV1_random.jzlib" - 45% (the whole package;)
Huuuuh...beneath graphical elements like more and more containers popping up, the variable programming counts high on the Lemur (the random thing is also done on the lemur - 2 scripts inside each "track") - for future versions I have to skip more of this to the max-patch (which is still the same)
The "SequencomatV1.maxpat" runs with each of these 3 templates, but not parallel. (The name of the templates container is always "SequencomatV1" and this is a path in the Maxpatch, so if you add more confusion happens).
You can change the apperance of that module in size and color if you like just don´t change the names or delete some relevant stuff.

If you got any problems running that thing, ideas for future versions, great joy while playing with it, or whatever feel free to refer here or contact me or via http://www.music-interface.com

Happy Lemuring
Mat

[Mat]

Dear users, please report if you got any clock or timing problems with the Sequencomat.

Although the rewire clock is a really comfortable clock source, it turned out that 2 kind of timing problems could occur:
- latency shift (all notes coming a few msec to early or to late)
- unstable clock (sometimes notes come to late)

The latency shift is normally very small and could be corrected by "track delay" (It will not work with Midi-clock-sync-shift on a rewire clock)
The stability of the clock strongly depends on your DAW. It is perfect on Logic (as some users told me), but Ableton live got sometimes problems in sending a stable clock. It differs with your sytem, cpu-usage, buffer...etc....so most of you will have no problems.

While working on future updates and other sequencers I need your feedback:
-your computer-config
-your daw
-your timing problems (if you got any or also if you got none)

Thanks

G*Mat

[Jannis]

As you know i am on a 2 Gigahertz macbook with latest OSX and latest Live8.
And after Updating both,
Timing still works like a charm for me!
This means it is the best sync experience i had with max patches!
(m4l not Included)

Thx for your beautiful Patch again!

Looking forward for Updates!