Being able to scroll left>right on the launch controller would be very useful for me.

2 Likes

So is there a record function in this ā€˜Terms’ version of polygome? I can’t seem to find one. If not how else could I use my monome with Ableton? Thanks!

Did you try recording audio (or midi) to a different track in Ableton?

Thanks so much for replying. I was referring to recording notes to be played inside Polygome… In older versions there was a ā€œrecordā€ function that allowed for the input of notes that would be ā€˜polygomized’ for lack of a better term

Does anyone have an idea ?

I don’t believe there is that option on the latest m4l version.

I love this little suite of devices, exactly what I’ve been looking for, but I am encountering an issue: why am I only able to hot swap between a maximum of four instances of these plug-ins? If I add a fifth, Monome only shows the fourth plug-in added to the Ableton session.

I’d love some pointers on what I’m doing wrong.

Beautiful! Is there a way to record midi? I can’t figure it out. Everything works fine but no midi notes recorded…

The updated .alp with installer will only work on updated ableton version? Won’t it work on 9.1.1?

Hey Fluxta,

The .alp packing process to make the install seamless requires a certain version of Live.
Needing to update to a more recent Live version is the price for the easy install unfortunately.

If you want the source .amxd’s you can probably just grab them from github and they’ll work in older versions. Is there a reason you don’t want to use a newer version of Live?

Hey mate. Yeah I have it installed already was just interested in trying be automatic installer. Simply haven’t upgraded my live yet as was waiting for bugs to be smoothed out :smiley:

Please pardon my M4L ignorance, I’m only getting started with it. Is there a way to save a pattern in terms as a preset? For example, if I have a pattern drawn in with step, can I save it to recall later? Step is easy enough to recreate patterns in, but I’ve also been experimenting with the M4L version of Parc, and it would be great to be able to save patterns created there, which are much more complex. Perhaps I’m overlooking the obvious…

Thanks!

1 Like

Okay, so I figured this out for parc. Write Settings. Read settings. Yeah. But it seems there is no similar functionality for terms, correct?

So is there any way to load parc settings via program change?

@thopa & @hypnosapien - I have been working on a branch of Step with some extra features like velocity per step (which can also act as a mute) as well as two CC values and probability per step. Nothing that hasn’t been done before in other monome sequencers, but I’m keen to have it all running in an M4L device.
As I have 2 64s, I also want a sequencer that works with both spanned together to make 16X8.

I hope to share a version soon. I don’t have varibright grids so I expect I’ve broken some of that but it should be easy to add back in.

I thought the best way to support spanning in M4L at the moment was to build it in to the M4L device instead of relying on third party spanning solutions - at least until spanning ends up built in to serialosc.

I’m also planning to add in pattern switching, and it will probably make sense to allow for patterns to be saved and loaded - if I can work out how to enable the save and load to be just part of the Live set, I’d be happy with that (vaguely recall there are things you can do with the pattr object that enable to M4L settings to be remembered as part of a Live set, but whether this can extend all the way for sequencer patterns I’m not sure).

anyway, this is still a work in progress, and the pattern switching will be the trickiest bit yet, since it’ll involve working with the javascript that is at the heart of Step, but hopefully I’ll get my head around it…

1 Like

@chailight - I would be happy to help you test this on my 128, as it sounds like a great evolution of step, with some of the parc-like probability features. This would be very useful to me, and I’m sure it would also be to others.

@chailight That is great news!
I also have been busy working on some max for live sequencers, i should have them ready for next week.
Here is a resume:
*A 256 Drum Sequencer primary designed to be used with Abletons Drum Rack, with various pages including, Sequencer, Note Repeat, velocity, lenght, groove, change kit, loop start / end, presets manager and presets chaining ( no javascript), voice mutes on most of pages, and autofocus.
*128 Note Sequencer, with Velocity, Pitch, Octave, Scale, playmodes, loop start / end, preset manager and preset chaining & Autofocus
*128 Sequencer, with 4 independent sequencers, each with Velocity, Lenght, Pitch, loop start and end, and reset sequence with different time divisions & Autofocus
*Same as above but with 2 sequencers, scales & presets.
Will share assap if someone fancies testing them.
Gracias!

1 Like

sounds great! I’m about a week or so away from having something worth sharing too, hopefully.

@thopa - I won’t be the best beta tester because I’m not running a regular 128 grid - but happy to give it a go… Perhaps I can package the spanning logic I’m using so that it’s easy to include in other devices. Likewise, perhaps I can learn from what you’re doing with preset management so we end up with a reusable solution for other M4L grid devices.

1 Like

@thopa - I would be happy to test this with my 2015 128. Thanks!

Has anybody experienced this issue?

Say you have a few M4L instances going and you are switching back and forth between instances. Say you have a flin, a boiiing, and something else going and you are bouncing around.

I have been getting this issue where autofocus won’t work right. It will stop connecting to say booing or flin and then I have to click on connect to reconnect. Then as soon as I switch to a different instance it disconnects again!

Anyone else dealing with this?

i experienced this issue :confused: