Who wants to help fund a port of meadowphysics 2

altoaiello · 2015-12-28T20:28:12.434Z

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

jasper_ryder · 2016-01-06T20:00:57.786Z

@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

ithkaa · 2016-01-06T20:15:59.177Z

@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

jasper_ryder · 2016-01-06T21:31:21.147Z

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

jasper_ryder · 2016-01-07T01:52:20.205Z

@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)

ithkaa · 2016-01-07T12:18:56.328Z

@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)

jasper_ryder · 2016-01-07T13:44:13.989Z

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

jasper_ryder · 2016-01-07T16:44:19.271Z

@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?

ingMob · 2016-01-07T16:55:03.753Z

+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.

jasper_ryder · 2016-01-07T17:00:05.609Z

@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.

ingMob · 2016-01-07T17:11:43.034Z

haha, thanks. i was blinded by rage

jasper_ryder · 2016-01-07T17:19:02.453Z

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

ithkaa · 2016-01-07T17:43:48.100Z

@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 …

jasonw22 · 2016-01-07T17:49:57.281Z

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.

sakul · 2016-01-07T17:58:02.952Z

also, be aware that the clock has to be coupled to live’s transport if I’m not mistaken, likely something you would want
(even if I had time… didn’t open max/m4l for quite some time, not of much help here sorry)

ithkaa · 2016-01-07T18:14:14.961Z

Yeah, that’s one of the things i edited. M4l port is driven by plugsync~ instead of the original qmetro

jasper_ryder · 2016-01-07T18:33:12.080Z

@ithkaa,
Just gave it a quick try and it seems great. Thank You.

@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 …

So then you freeze it so It’s just one amxd file then?

ithkaa · 2016-01-07T18:42:10.903Z

@jasper_ryder that’s right

jasper_ryder · 2016-01-07T18:47:24.742Z

Well thanks again @ithkaa! Not trying to discount your time, but damn you are efficient at getting patch work done!

mel_gonzalez · 2016-12-08T18:30:28.769Z

This works perfectly! Thank you!!