#4

Are there some specific Live features you want this port to take advantage of? What makes the M4L version different from the Max version (aside from UI layout)?

#5

Yes max for live, sorry I didn’t specify. Having an m4l version is huge for me. Then I can use it with all the terms patches. I have not figured out a way to use m4l patches and patches that just run in max together simultaneously. Autofocus does not work with both.

1 Like
#6

OK, now I understand. Not promising anything at all, but I will store this away in the back of my mind, and if I happen to get around to it, llllllll.co will be the first to know. :wink: Maybe someone will beat me to it.

1 Like
#7

It’s a start! @jasonw22
Thanks.

2 Likes
#8

Yeah, this would be dope. Meadowphysics is my new favorite thing.

1 Like
#9

One day……one day………

#10

Alright, who’s down? I’ll throw cash at this immediately. The teletype interface from the @elquinto meadowphysics port is essential, too.

2 Likes
#11

@ithkaa,
Just thinking about meadowphysics again and what you did with control. Is this bridge you made something that I could hack to make it work with meadowphysics? My intuition says no but what do I know?

Screen Shot 2016-01-06 at 12.54.37 PM.png924×782 61 KB

Screen Shot 2016-01-06 at 12.56.07 PM.png1167×746 108 KB

#12

@jasper_ryder yes, this should be possible. You’d need to add udpsend and udpreceive in the main patch (make sure send and receive ports are the same as in the M4L device – but different from control-bridge or you can’t use them together). give the serialosc bpatcher in the M4L device the same argument as the one in meadowphysics. now just send grid output from M4L to meadow en send LED output from meadow to M4L

#13

That’s great news! I will try and make this happen. Thanks. :smiley:

#14

@ithkaa,
I don’t have a full max license so I can’t save any changes to the original meadow maxpat. I don’t think there is a work around this in the m4l editor. Maybe I will start a trial version so I can try this.

The udpsend stuff looks pretty minimal but the udpreceive has a lot more going on. Would it be all of these parts/objects/messages basically? (tried to get most of the group in the shot)

#15

@jasper_ryder I took some time today to put this in a M4L format. Just copy/pasted and edited it a bit for optimal M4L usability. I didn’t go deep into the app (never actually used it) but it seems to work.

Meadowphysics 2 M4L.amxd (475.0 KB)

7 Likes
Control - Open MIDI controller platform for 128 grids
#16

@ithkaa,
Well what can I say, you just put everything together so quickly man. Thank you. Will try it out later today.

#17

@ithkaa
So when you copy and pasted it over to m4l do you include the externals by freezing it then? Was just looking up what freezing does. What order do you have to do all that in?

#18

+1 for M4L version

-1 for the fact that Cycling '74 doesn’t provide a ‘port to M4L’ button. this is not a problem that anyone should have to routinely solve. this is a major design oversight in my view.

#19

@ingMob,
Try the M4L version @ithkaa just posted right above these last few posts and see how it goes. I have not tried it yet.

1 Like
#20

haha, thanks. i was blinded by rage :wink:

#21

@ingMob,
I know the feeling. Please post how the patch works for you. :grinning:

#22

@jasper_ryder here’s what I did:

first I created a new folder for the M4L version, copied all sub patches and .js files to this folder, then in Ableton opened new M4L MIDI device and saved it in the previously created folder. then, copy/pasted the original patch in the new M4L patcher and saved the device. after that I changed out some objects (f.i. sliders for live.sliders to allow MIDI mapping in Live) and changed the layout a bit …

1 Like
#23

I suspect the need to “change the layout a bit” might have something to do with the lack of a “port to M4L” button in Max. It’s not immediately obvious how one would automate that part of the workflow.