Archive for the ‘Max5’ Category:
here is a new patch I´ve made in max/msp with a control surface for the Lemur.
It is called “Route n Range” and what it does is: It takes an incoming MidiControlChange message from external gear, display it on the Lemur, where you can range it, and send it out to another Midi destination.
Incoming Midi CC can be linked to 8 Controllers. Pressing the top bvutton will link the aligned Fader to the actual incoming Midi (Midilearn). Channel and Controllernumber can be also set manually by pressing switches in the 2nd row and turning the endless knobs for Channel and Controller. By activating the switches at the bottom line, values for Channel and Controller for Midiout can be changed with the 2 knobs too.
Each Fader got a attached range, which controls the value output, displayed in a monitor below. This allows to transform the full movement of a hardware rotary encoder (0-127) to only send between concrete values (e.g. 35-76). However – the fader will follow the Midi input (0-127). Midiinput can also be overwritten by moving the Fader directly.
Settings of all In and Out routings and ranges can be saved in 12 sets. If the numberpad is green, it is in load mode. For saving change to record mode by pressing the red switch above. Notice that these sets will only load the routings, they are not snapshots of the CCvalues! After a jump triggering is initiated by hardware input, where here all 8 Controls act independent from each other (no list processing).
The Midiports for in and out can be chosen on the maxpatch. They are split for Controller 1-4 and 5-8, so you can use different Midiports or just the same. Choice of Midiports can be done only direct on the maxptach, not on the Lemur. But Midiports are also saved within presets, which can be loaded from the lemur.
Between the maxpatch and the lemur surface is a bidirectional OSC connection. So the lemur controls the patch, while all Midi is handled in max/msp. (In fact the patch also works completely without a lemur.)
You might ask: What the hell is that good for???
As you can route your external Midigear directly within your DAW, why this circuitous way with a maxpatch and a lemur in between? The answer lays deep in my personal setup: I have a very well defined Midirouting in my DAW where I controll over 200 CCs. As I have learned many functions to concrete controllers, I do want to change the sending side of Midi, not receiving in my DAW. While most USBcontrollers can do that easily, my beloved “Doepfer Pocket Control” – best feeling encoders ever – has only a small DIPswitch, which makes midirouting unconfortable. Therefore, I needed the patch to switch the Encoders to different Controllernumbers. Furthermore I wanted to have a range, so I got more detailed control and I wanted to switch during playback. …thats where the patch comes from.
I admit that this is a very specific use. But it might be, that there are some other users, who also have (old) Midigear and want to link it up dynamically, so here is the patch btw: the maxpatch is open for editing. I think it can be easily expanded to 16 Controllers if necessary.
I re-released my SequencomatV1 for iPad:
Threat in Liines forum: http://liine.net/forum/viewtopic.php?f=26&t=1225
V1 was first released september 2009. I had only some minor changes on maxptach, but I resized the interface, try to make it a bit “clearer” and also added physics on the Velocity and Length MultiSlider for trackvalues. I also put some effort in writing a manual/documentation. It is attached in the zip as pdf and available online: http://www.tonvibration.de/extra/SequencomatV1_2012_manual.pdf. The manual also contains some scripting tutorials, because most variables are calculated on the lemur in V1 and only triggering of those is done in max.
Naturally V2 and V3 of Sequencomat give more detailed control, but V1 with its direct controls has its own charme. A comparison of all Sequencomat sequencers is given in the FAQ of the manual. In common: Global values in V1 (Midichannel, grid, playdirection, steprange, startpoint) become trackvalues in V3; and track values in V1 (pitch, velocity, length) become stepvalues in V3. There is a video where I compare V1 (old legacy surface) and full V3.1: http://youtu.be/v4pdzmYzrxQ
There is also a playlist (3 videos) that show functions of V1: http://www.youtube.com/playlist?list=PL55F20A2D3AFEA7AE (videos are also with old legacy surface, but demonstrate functions quite well)
V1 is combinable with V3 and/or V3 lite. This can be done as different interfaces within one lemur project, but also on different lemurs (legacy/iPad). You just have to run both patches in max and set right IP and OSC for communication. For sync V1 and V3lite use rewire clock on both, cause it is the only clock V1 has. For sync V1 and fullV3, deactivate rewire and V1 will automatically follow V3 settings (it uses the same clock variable names).
Here is a video showing Sequencomat V3 lite + full version
running parallel on an Ipad via WiFi connection.
Finally, it works
Before I had lag in feedback and even dropouts (only visual feedback, triggering was not effected)
But changing the channel of my router helped a lot to get better feedback (as to be seen in the video).
Using an ad hoc network instead of WiFi can make communication even more fluent and save.
Well, I tested with Wifi and I am really impressed that it works great job, people at line!
At the moment I am still testing SequencomatV3 for Ipad, have found some beta testers in the forum.
In common all looks fine. seems that the knob object (used for BPM control and position) is somehow broken in Lemur 3.0.
Unfortunately the Endless Knobs always fall back to value 0 if touched, which is no good idea for bpm. So for the moment you have to set the tempo in once at the beginning. You can make small changes by using the BPMfine knob later…. If Liine can not fix that, I will enter another control typ for bpm and position.
- The bidirectional OSC communication between Lemur and maxpatch was designed for ethernet connection on its original hardware Lemur. The full version of SequencomatV3 sends about 4000 values forth and back in realtime. On original Lemur that was never a problem (while internal 4MB memory sure was!), on Ipad it clearly depends on your network settings. Ad hoc works fine. But even wifi can work as shown in the video…. However: If lite version works, full versions works also and you can even run both.
“Offical” release of full version will be early 2012
Read manual of SequencomatV3.
The app is out for about a week now and I ve already started to resize my modules to Ipad resolution. I will upload them soon to the new Liine user Library.
Sequencomat is also working, here I show version 3lite. Well, visual feedback is less fluent as on original lemur as you can see in some parts of the video, but at all it works. Next I will try the full version 3.3….
Nice to see Lemur living further on Ipad
I attached a zip with all modules in the video and Sequencomat in the thread in the forum:
Any feedback is highley welcome!
is the little brother of the full version 3.3.
It has less functions, but still a mighty stepsequencer and it runs paralle with the full version! (so full users got now 14 tracks of stepsequencing)
Setup of the new “lite” version is the same as on full version, but sets (and patterns) of lite version and the version are not compatible. To run both sequencers at once, make one a midi clock master and the other a slave….. or slave both to another clock source.
- 6 tracks with 16 steps each
- 3 clock options (Midimaster, Midislave, Rewireslave)
- independent trackvalues for timing, play direction, Midichannel, steprange, startpoint
- stepvalues for octave, note, velocity, length
- a global swing function
- 50 patterns to save and jump in realtime
- set and patterns saved via max
SequencomatV3_lite is available in the Jazzmutant user section…. for free!
However there is still a noticable gap between free lite and paid full version.
To mention some aspects:
- 6 tracks vs 8 tracks on full version
- no random step values at all
- no step propability
- a global swing instead a detailed swing independent on each track
- no pattern chains
- no exclude function
- no autosave
- only 50 patterns instead 100 patterns
- only chromatic scale instead of free definable scales
- no split of midiport
…and much more
To illustrate: While full version is 5.8 MB, the lite version is only 2.3 MB.
Here is a new video about my Sequencomat – that Midi stepsequencer I made in MaxMSP for the Jazzmutant Lemur…. was about time – the last video is 9 month ago and introduced V3.2, while I release V3.3 in March…
Here I demonstrate some new functions in V3.3:
- free definable scales, using a pentatonic based on D#
- random on note
- transpose (scale dependent)
- color scripts, changing all control colors
- and more…
For details see the manual of Sequencomat V3.3:
During the last year I was so busy in adding new functions to the sequencer, that I forgot an important thing:
How beautyfull the colors of the Lemur are!
So I made a new Lemurmodule, where you can change the color of the controls with one click on a dropdownmenu. You got 6 predefined colors and you can even build your own color shade by only changing the color of some special controls in the Jazzeditor, then press a button and the colors are routed to all other controls (with same meaning) via some scripts.
You can learn more about Sequencomat colors here:
The new Lemurmodule “SequencomatV3_3colors” works with the same maxpatch as normal V3.3.
You can use either the old standard Lemurmodule or the new one, but not both at once.
“SequencomatV3_3colors” claims 42% Lemur memory (1% more than normal module).
I made a demo video of the new functions in my Sequencomat_V3.2. I recorded a spontanious jam so the music is a little …weird (?)….boring (?) (cause simple 4 on the floor)… strange (?) …whatever.
I start with simple a 8th baseline and the comments demonstrate the functions quite well:
- random on length
- CCs (purple)
- setting CCs
- use range
- step propability
- copy/paste track
- change note/octave
- using different instruments (via midichannel)
- random on CC
- (forgot to show) random on velocity
- switching samples through octave on drumrack
- create grooves / swing on HH (via delay)
- adding 1 more instrument
- save / load / jump pattern
- XYpad triggering
- step mute / demute
…well…a lot of functions I go through…hope you enjoy the video. All the best, mat.
Hey, I´ve updated the sequencomatV3.
V3.2 is a big update. I completely reworked the maxpatch and added some new major functions:
For each step on each track a propability can be set, if a step is played or not. More concrete it is a “unlikeliness” function, because, the higher the bars are, the more unlikely it is that a tone is played (of course only if it is activated in the stepmatrix) That way you can bring in some nice variation in the pattern. However, it might be disturbing if you have set a tone in the matrix and it is not played. Therefore I made an indicatorLED on the tracks mainmatrix showing if a tone is played or not.
8 CC attached to track
Now a CC is attached to each of the 8 tracks. Channel and Controllernumber can be set in a popup container (as shown above) and are saved within the pattern.
random step value for velocity, length, CC.
Small buttons below the MultiSlider set the corresponding step value to random, each time it is triggered it generates an new value and feedback on the slider. All stepvalues work within the range (left), so random is a bit more controlled than a pure 0-127.
The new functions are really fun. Unfortunately I have no video yet….but soon, I guess
The size of the patch jumped from 2.0MB to 3.7MB and I am still fixing some minor bugs. But after all, it seems to stay stable….