Max/msp & max4live (the thread)

[_mark]

Yeah, stuff breaking in max is pretty damn annoying. I’m thinking more small patches for individual compositions rather than devices, so should not be an issue. The opening patch with the segmented shaker controlled by a single slider has so many possibilities. Going to try and use it for this lcrp.

[Rodrigo]

Yeah, in that case go for it. Quite powerful indeed.

[Wurrm]

Hi All,

I have just released my first Max For Live device. It’s a simple tool for creating generative music. You can read about it and grab a free copy via my website. It’s my first software release so I would be greatful for any feedback you my have.

WurrmGen

[chapelierfou]

I would try it, but the “shop” adds a £5 for shipping.

[Wurrm]

Thanks for the heads up, chapelierfou! The shop is new to me too. I believe I have disabled all shipping costs. Would you mind testing it to see if the shipping charge has been removed?

[chapelierfou]

Yes,
I guess you could just post it here ?

[darwingrosse]

@Wurrm - the “Paypal Buy It Now” button goes haywire. The regular cart/checkout works fine, except now you’ve got all my mailing information, so I expect to get something nice in the mail!

[Wurrm]

@darwingrosse, thank you for your feedback. That’s really helpful.

It seems like the shop is a bit overkill! I have changed the download activation to a simple form.

I’ll keep the shop for physical products.

[thopa]

Hiya!

So after a few years away from max (thanks to you @darwingrosse and the ardcore) im slowly (trying to learn) my way back with max.

I opened my old max devices and started scratching my head, i pretty much have forgotten most of what i had learned!

I have done the grid studies again and its great to see there are plenty of new approaches (gridlab, beap, etc) but its also true that monome has becamed less max centric which is guess its a good thing.

Still i like the max ability to change devices with the autofocus, which seems to not be possible so far on norns.

Would like to have a hybrid setup where i could use both. I dont mind having to use a computer at all, so thats not a problem.

Still, with max im finding out (again) that there is quite a steep learning curve, so wondering if i should give the norns tutorials a go and se how it goes.

So would this be a good place to ask for monome-max related help?
I already have found a brick wall on one of my devices.
Thanks!

(Edited)

So this seems to be the right place then!

I found this great patch by @darwingrosse, its a scrolling step sequencer:

secondmonome-4.maxpat (12.7 KB)

So i have an old sequencer where i can change the step division, direction etc and i would like to implement the attached sequencer for my monome 256.

What i want to achieve is have a sequencer for each row. That means also having a play ahead indicator on each row.

I have tried implementing it for the second row, and i have run into a few problems.

First by doing a swaping of the $1 $2 $3 to only let pass the messages from row 2, im getting a delay. Meaning when turning triggers on or off, the monome only updates after the counter re starts from 0.

As I say im trying to learn my way back so apologies if this seem very obvious!

Here is my attempt for the second row of the monome:

and the patch:

secondmonome-mod.maxpat (17.3 KB)

Hope someone can help me out, thanks a bunch!

[dude]

is there a best/right/wrong way to use github for stuff i’m working on in attempts to share beloved tools? i’ve never used it before but my work is feeling more functional atm.

and here are 2 m4l patches direct from @Rodrigo!!! his blessing to share here were respectfully and directly procured and he did 100% of the building afaik (i had no hand in their making!).

Cloud.amxd (272.2 KB)
Resonator.amxd (293.4 KB)

i didn’t go deep into explorations with resonator but cloud blows my ass out of the water. using it is like improvising with yourself. it senses onsets and then bops around an constantly overdubbing buffer dynamically with key settings like pitch etc and 2 modes. it is at home equally with freaking out on rhythmic material or getting into more freely improvisatory or abstractive natures. it worked plug/play for me and i believe it is all self contained. super fun twitchy and lovingly responsive. support yourself in the cloud.

[Markus]

Would love to see the sequencer as m4l device!

[darwingrosse]

@thopa - two small issues with your patch, both on the left side of the patch:

1. You need to do the join/unjoin before you create the message using the message box.
2. You want to increment the row number, not the column number, so you need to increment the second number in the series.

secondmonome-updated.maxpat (17.1 KB)

When you start setting this up for all of the rows, you may want to do a few things: limit the updates on the right side of the patch (you don’t need to update columns, you just need to update the single cell), and make an abstraction with replaceable arguments using the #n character.

And have fun!

[ddg]

[thopa]

Thanks a lot for taking the time to look into it @darwingrosse !
I have been looking it and i think i can move on from here. Having some problems figuring out the right side of the patch and updating only the correspondent cell, but i hope i can sort it out!
Thanks a bunch for your feedback and inspiring work!
Gracias

[darwingrosse]

For that right side, you need to move from column updates to individual cell updates. Also, because you are working with single numbers, you can avoid vexpr and just do straight math.

secondmonome-upd2.maxpat (17.4 KB)

Cheers!

[ddg]

[thopa]

Much appreciated @darwingrosse !
That makes it much clearer, i get easily lost when vexpr is used.
I have been working on one row and i think its going to be better to use one as a play ahead, step indicator and for inputting triggers and another row underneath for tempo division, play mode and loop start end points. Im getting lots of mistaken actions only using one row.
Thanks a lot!

[philmaguire]

MC question for the room. I have a simple mc bpatcher with a stereo output. Is this mc.pack/unpack~ necessary? Or can I simply send the output of each mc.mixdown~ to an outlet?

For context the patch is a 16 oscillator bank running through a simple delay, 8 oscillators in each channel.

[tristan_louth_robins]

MC question for the room. I have a simple mc bpatcher with a stereo output. Is this mc.pack/unpack~ necessary? Or can I simply send the output of each mc.mixdown~ to an outlet?

For context the patch is a 16 oscillator bank running through a simple delay, 8 oscillators in each channel.

I think you’d have to unpack it since the signal would stay in mc. mode. I typically do this when I route out of an mc.mixdown or mc.stereo object.

[philmaguire]

Nice, that was my assumption. Cheers!

[darwingrosse]

My understanding is that if you run an mc. signal into a standard audio object input, you will get the first channel of the mc signal. Since your example has a 1-channel output for the mc.mixdown~, you should be OK without the pack/unpack combo.

Cursory tests seem to prove that out.

[ddg]

[dude]

this is my favorite thread up here right now. i don’t know shit but it is so provocative. priceless!!! thank you! and you ! and you!