So, I really like the simplistic approach. Though I am having some issues. First one is that the grid, although it is slectable does not show up in the window. Another trouble I seem to have is that with different apps on different tracks doesn’t show the grid at all, only option I get is “none”. I might be doing something horribly wrong. I also miss being able to choose the grid orientation.
Loving this set Trent …dope…
Just a quick note to say thanks for the work on Terms. I’ve just done a quick hack to get Step working across two 8x8 grids.
So far I’ve got input and output working correctly. I still need to update the way the play head is displayed across the spanned grids, as that uses the row syntax and I need to do a bit more work to get that correctly translated.
Stretta’s BEAP examples of using two grids was really useful to work out how to do this.
Once I’ve got something working properly for Step I’ll share it and hopefully it will be not too hard to add spanning to other Terms devices.
So far all working well my end with my 256 in Ableton. Not a DAW fan really but this has simplified Ableton for me in terms of workflow. Great so far but look forward to finished release pending @Galapagoose
Nice work mate thanks
I’ve been trying these out over the weekend and found them to be a bit hit and miss.
Sometimes the serialosc dropdown is blank or shows ‘none’. Sometimes it shows my monome but the keys don’t light or seem to send any messages to the chosen app. Sometimes an app (polygome for example) will be working on the monome but no midi data is bing detected in live.
All these issues seem to be intermittent, sometimes a restart of live fixes it but not always.
Anyone else having similar problems?
mac osx 10.6.8, live 9
Since it probably got buried a bit, @Galapagoose mentioned a while back that this isn’t completely finished yet, so bugs are probably a common occurrence:
didn’t spot that - cheers i’ll wait for the proper release
Very cool. Can’t wait for the official release!
When entering a note on the step sequencer, it would be dope if velocity decreased from maximum as you held the button. So a quick press would be full velocity or hold like two seconds for minimum.
…kind of a random thought that could apply to any monome step sequencer, sorry.
Also, the clip launcher doesn’t always recognize my monome after computer sleep.
Oh, and the synth is great! So versatile and easy to use. Loving it!
Simply great work.
@Galapagoose thanks for the update! I’ve had limited testing, but serialosc seems to be working better to connect when I load a set that has an instant of terms.
So I’m pretty late to the party: only discovered terms yesterday, having spent several months away from thinking actively about my monome grid (and developing a rather unhealthy eurorack obsession in the interim).
What a graceful and consistent implementation of so many beautiful apps! Very excited about getting to grips with it.
From my initial digging around with the included patches, I had a couple of questions. Apologies if they’ve already been covered (did a quick search and couldn’t find anything):
Is there a specific external or Max object for autofocus? I’m interested in building my own devices, so I had a dig around inside the devices included in terms, but couldn’t immediately untangle the bits required for autofocusing the grid by track or device selection.
When using the M4L version of corners (this is in @elquinto’s expanded M4L suite rather than terms itself) is there a way to map the outgoing values for x and y to controls within Live? Corners appears to be outputting MIDI CCs, but I can’t map them to anything.
Is there a way to bypass polygome’s pattern playback, and just play the MIDI notes I’m pressing on the grid? I’ve tried shortening the pattern length to 1 (again in elquinto’s expanded version of the device), but the notes output from polygome seem to suffer from noticeable latency. Ideally, I want to be able to use the grid as a simple keyboard at times, but still take advantage of polygome’s note layout & scales, then switch on polygome’s patterns when needed.
new update posted yesterday: https://github.com/monome/Terms/releases
-open up one of the patches in your max editor, cmd-f search for autofocus, and you will find a patcher ‘p autofocus’ that handles all that stuff.
-the way i do it, i output the (corners) track’s midi to an iac bus. in live midi prefs, make sure that this iac bus has track and remote enabled for input, and then you should be able to map corners cc’s using live’s midi learn.
-if you’re in polygome’s record mode, it’ll bypass pattern playback and act much like a playable keyboard.
hope that helps!
Wow, Terms! Sum, while awesome in its stand alone glory, seemed more like a proof of concept compared to this which is just really well integrated. Easy. I didn’t quite get the previous m4l versions working and like you might expect only really get around to this depth of getting involved with Max patches. Extra thanks for the idiot proof installation procedure. Amazing.
Just a quick note to say there’s another new version updated with some minor fixes included.
Fixes a number of display issues particularly if you’re on Push or wanting to automate parameters in Arrangement view.
Should have an automated Live Pack put together for us in the very near future to further idiot-proof the procedure!
The documentation has also been extensively updated with some corrections and deeper explanations: http://monome.org/docs/app/terms/
amazing! thank you, have already used that autofocus info here: Matrix m4l device for routing MIDI signals on the fly
awesome ! thank you so much !
Having too much fun with these. Oddly I didn’t get into the smaller ones (Notes, Time) yet. Flin I found to be marvelous for bass lines. Polygome for just about everything else! Amazing, really opens things up. Thank you so much. As little time as I have to spend on music this feels very special. Currently I’m not able to record midi so right now doing long passes of audio, recording to a different track in Ableton. Not sure I want to do it differently at this point really as it eliminates tedious midi event editing and sound design.
Just curious to these things as well:
What’s the verdict on MLRV - too complex for being ported to M4L? Looks overwhelmingly cool when opened in my Max trial and perhaps slightly easier to grasp in Sum. I couldn’t immediately figure out how to load samples though. The time I spent typing this might have been all I needed to get a grip of what’s going on, I suppose.
Looking for some neat way to stop using Audioprism on iOS and start using my 128 for this as well. Is there a more recent take on this than any of these:
Thank you lots and lots.
for something close to mlrv that runs in m4l, have a look at elquinto’s re:mix.
you’ll find the relevant thread a little further down in the forum.
Hi! thanks a lot for terms!
Im trying to figure out a couple of modifications on the sequencer and i hope some one can point me to the right directions;
-Add more rows and be able to scroll up & down with a button combo (like alt +button for up) (alt+button for down)
-Save and load presets
-Mute / unmute parts
Thanks a lot!
Great to see Terms working and that new updates are coming! I just wish there was also a version for non-varibright devices. (256 here). I’m sure many users of an older Monomes would love to see it as well. Just even for a simple lunchpad page to make currently playing pad blink till it’s stop. I guess it’s pretty simple modification. Maybe somebody has done that already?